The Dinit Init system is only 123kb, compared to the ~200kb of s6-rc, while seemingly providing more features.

Here is the Blog and Github Repo:

https://davmac.wordpress.com/category/dinit/
https://github.com/davmac314/dinit

This would help to add more people working together in the project.
Like, make a session in the website about what the project needs, like bugs to be fixed or ideas to be implemented.
I'd like to help. :^)

By the way, this is a really amazing project, it really have potential.

Hiya!
Do you think this will run on bare metal? If yes, how can I install it?

(The metal in question is a ThinkPad E495)

I tried IMG, and the 2 ISO methods.

First of all hello and congrats, impressive work. Your project is closest to what i've been thinking about for quite some time. I have few recommendations for improvements.

1. Vim is great but have too many features to be suckless IMHO. Kilo has no dependencies and can only save, search, type text . It less than 1000CLOC. If its too simple then you can take a look at bim, which is simpler and smaller vim clone, but still have many features.
2. Core Utilities: asmutils is minimal implementation of UNIX utilities written in assembly. There's also 9base, busybox and its WIP better rewrite toybox.
3. Minimal init system sinit and daemon
4. Remove Native Language Support (NLS).
5. Instead of using nnn its simpler and faster for file manager function to write simple script using fzy or its equivalents.
6. On the wiki/philosophy page 'Non-GNU', which can't be completely true. I've read that Google is pushing another compiler and trying to get rid of using GCC for kernel. But who knows if it ever happens or at least when. I know that you're working on graphics stack right now so it should sound completely dumb for you to drop all your work. Ideally I recommend to look at something more simplistic, because Linux have millions of LOC.
   The simplest of possibilities is one of microkernels. If you thinking about bad performance- looks like that's a myth because Apple is using GNU Mach multiserver microkernels on every their product these days... and IBM Workplace OS too!
   Of course I aint mean to use exactly it- there's a plenty of opensource kernels.
   Best regards.

https://github.com/martanne/vis/wiki/FAQ#why-dont-you-just-use-vim

Vis is a much better and less bloated alternative to Vim.

This seems to be a rather common issue when working with cross-compilation toolchains, specially those involving the use of musl as their libc of choice.

Previously, musl didn't provide stdc-predef.h which was thought to be the main cause for this ignored error, but it seems that this error is surfacing again without a valid cause.

Initially, I got rid of this error by specifying the following flag--with-native-system-header-dir=/include (the trailing slash before include is needed) to the configure function for cross gcc, which when combined with --with-sysroot=$DIRECTORY (according to gcc's current documentation), will cause gcc to search for header files within $DIRECTORY/include.

But now, it seems that this error managed to pop up again with no apparent reason, and it should be treated as an ignored warning more or less.

Debian recommends creating an empty stdc-predef.h file to silence this error, according to Debian's bootstrap issues.

In my opinion, the real reason why this error is showing is due to the C library (which is musl in our case) not being available in $sysroot (along with its headers, including stdc-predef.h) at the time of running the build function, which means that it's a harmless error and should remain ignored.

Since the build is continuing just fine, and isn't exiting with various missing header files, creating an empty stdc-predef.h in $sysroot's appropriate include directory seems the right way to go.

For further reading:

• https://wiki.debian.org/toolchain/BootstrapIssues#stdc-predef.h_not_found
• https://linaro-toolchain.linaro.narkive.com/8YVGCJeE/stdc-predef-h-failed-during-gcc-linaro-snapshot-6-1-2016-07-compile
• https://gcc.gnu.org/legacy-ml/gcc/2017-12/msg00002.html

Hello,
I am looking for the cerata of your minimal Wayland setup atlanticus, but I couldn't find it. Would you mind to share these?
Greetings

Hello, your system looks kinda interesting.

but i dont really know how to build a testsetup with it. Is there some kind of build instructions or how the folder structure has to be, to run radula to build a toolchain?

Thanks in Advance!

how i can install a windows manager on this distro and sound

Seems the scripts folder has been removed.
Thanks