Features...

(...and "use case").

Musl

A libc should not be infested with spaghetti code... legacy cruft... kludges and duct tape. It should not be the 9th circle of... "circular hell". A libc should NEVER have dependencies!

Busybox

It's back to future's past... (all over again). It's simple. Small footprint = Small attack surface. Command utilities should not be a ret2libc circular exploit hellscape. So just take the win.

Runit

No one's @ this back door (there just isn't one). The init daemon should be the solution not the problem. Your init should not phone home. Your init should work for you not a 3rd party.

Sysctl

Do you have everything under control or is the tail wagging the dog? Plain vanilla works fine when it comes to dessert. But when the wolves are at the door is your system up to the task?

Preload

Loading up on resources saves wasted time and effort. When the system has to fetch data that should already be in memory... efficiency is lost. Mitigating the reloading latency tax is key.

Prelink

Do you take out all the books in the library? Or... just the ones for the task @ hand? The only libraries in memory should be the ones that are essential. Anything else is... bloat.

FAQ

Frequently asked questions answered

Is fu11m00n a derivative?

Yes and no. It's packages come from a upstream repository. However, it's "ethos"... scripts and "use case" are an outlier.

Is fu11m00n immutable?

Short answer... yes. In the sense of "permission". What this means is... select binaries are symlinked to the iso image.

Is fu11m00n an outlier?

In a way. The use of Musl... Busybox and Runit is not typical. The GNU ecosystem is the default for most Linux systems.

Is fu11m00n secure?

It is secure. Musl (libc) does not have circular dependencies like glibc. And Musl is also... resistant to ret2libc exploits.