oasis
src
Our great sponsors
oasis | src | |
---|---|---|
26 | 745 | |
2,701 | 3,036 | |
1.9% | 1.4% | |
8.8 | 10.0 | |
6 days ago | 6 days ago | |
Roff | C | |
GNU General Public License v3.0 or later | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
oasis
- Oasis – a small, statically-linked Linux system
-
After tens of hours and a numerous amount of coffee, I proudly did it
You reminded me for trying Oasis: https://github.com/oasislinux/oasis
-
Idea: Steam should delete all native Linux ports from its library to prevent ABI breakage issues and SteamOS should be made into a statically linked OS
IMO, would eliminate issues with glibc and other libraries breaking ABI compatibility. Statically-linked distros like oasis could be used as inspiration.
-
An estimation of what distros and desktops have the largest userbase?
Oasis and its native desktop Velox.
-
Compile webkit2gtk to be as minimal as possable.
I wonder why suckless team chose to build its browser on webkit2gtk instead of NetSurf, things like these and others like their adherence to Xorg makes me think seriously to move to Framebuffer (fbpad, fbpdf, fbff ..) or Oasis (Wayland + SWC + Velox).
- In theory, could you compile all of the libraries required to run a Linux environment into a single, massive .so file?
-
Are Hoistings Possible for C++?
When you say a fork of LLVM, am I correct in assuming that you specifically mean a fork of Clang? I don't see how the compiler backend would affect support for language extensions, regardless of whether it's an exception to that such as Tcc, Cproc, the MIR C jitter, lacc, 8cc, 9cc, and chibicc. Most of those are not for production, excluding Cproc and Tcc (at least according to Suckless or Oasis).
- Oasis。小型静态链接的Linux系统 (Oasis: Small statically-linked Linux system)
- Oasis: Small statically-linked Linux system
src
-
OpenBSD Upgrade 7.3 to 7.4
The OpenBSD project released 7.4 of their OS on 16 Oct 2023 as their 55th release 💫
-
OpenBSD System-Call Pinning
Well since https://www.openbsd.org/ still says
> Only two remote holes in the default install, in a heck of a long time!
I'm assuming not, but I could always be mistaken.
- Project Bluefin: an immutable, developer-focused, Cloud-native Linux
-
From Nand to Tetris: Building a Modern Computer from First Principles
> building a cat from scratch
> That would be an interesting project.
Here is the source code of the OpenBSD implementation of cat:
> https://github.com/openbsd/src/blob/master/bin/cat/cat.c
and here of the GNU coreutils implementation:
> https://github.com/coreutils/coreutils/blob/master/src/cat.c
Thus: I don't think building a cat from scratch or creating a tutorial about that topic is particularly hard (even though the HN audience would likely be interested in it). :-)
-
OpenBSD – pinning all system calls
> I don't know how they define `MAX`, but I'm guessing it's a typical "a>b?a:b"
Indeed: https://github.com/openbsd/src/blob/master/sys/sys/param.h#L...
> Then `SYS_kbind` seems to be a signed int.
It's an untyped #define: https://github.com/openbsd/src/blob/master/sys/sys/syscall.h...
I believe your whole analysis is correct, that running an elf file with an openbsd.syscalls entry with .sysno > INT_MAX will allow an out-of-bounds write.
- Une nouvelle mise à jour de Systemd permettra à Linux de bénéficier de l'infâme "écran bleu de la mort" de Windows, mais la fonctionnalité a reçu un accueil très mitigé
-
tmux causing ANSI color-response garbage on attaching?
I can reproduce it. And this is the commit that causes the issue: https://github.com/openbsd/src/commit/d21788ce70be80e9c4ed0c52c149e01147c4a823
-
Sudo-rs' first security audit
This doesn’t really change your conclusion, but I think that’s the wrong file. This is the real doas afaict: https://github.com/openbsd/src/blob/master/usr.bin/doas/doas...
Still just a tidy 1072 lines in that folder though.
I spent 5 minutes staring at your file trying to understand how on earth it does the things in the man page, but of course it doesn’t.
-
OpenBSD: Removing syscall(2) from libc and kernel
OpenBSD developers are making serious effort to kill off indirect syscalls, the base system is completely clean, take a look at the work Andrew Fresh did to adapt Perl. He write a complete syscall "dispatcher" or emulator for the Perl syscall function so that it calls the libc stubs.
https://github.com/openbsd/src/commit/312e26c80be876012ae979...
The ports tree is also being cleansed of syscall(2) usage, until they're all gone.
msyscall, pinsyscall, recent mandatory IBT/BTI, xonly. OpenBSD is making waves, but people aren't really seeing them yet.
-
"<ESC>[31M"? ANSI Terminal security in 2023 and finding 10 CVEs
Actually, I got it wrong, too many vulnerabilities in flight. They did fix it: https://github.com/openbsd/src/commit/375ccafb2eb77de6cf240e...
What are some alternatives?
iglunix - Linux (and other kernels) distro with no GNU components
cosmopolitan - build-once run-anywhere c library
glaucus - A simple and lightweight Linux® distribution based on musl libc and toybox
bastille - Bastille is an open-source system for automating deployment and management of containerized applications on FreeBSD.
Ceedling - Ruby-based unit testing and build system for C projects
buttersink - Buttersink is like rsync for btrfs snapshots
muslrust - Docker environment for building musl based static linux rust binaries
PHPT - The PHP Interpreter
Sourcetrail - Sourcetrail - free and open-source interactive source explorer
Joomla! - Home of the Joomla! Content Management System
kiss - KISS Linux - Package Manager
frr - The FRRouting Protocol Suite