1 Small is beautiful.
2 Make each program do one thing well.
3 Build a prototype as soon as possible.
4 Choose portability over efficiency.
5 Store data in flat text files.
6 Use software leverage to your advantage.
7 Use shell scripts to increase leverage and portability.
8 Avoid captive user interfaces.
9 Make every program a filter.
1. systemd < sysv-init,cron,syslog,xinit,dbus
2. systemd has a little extra bin for each of above
4. portability was an unsolved issue in unix ancient times when every instance of a mainframe computer had its incompatibility in every aspect - unix philosophy was just an unsuccessful attempt of the big players to overcome their own problem. This issue is solved since decades. In times there are billions but not only a handful of computers the efficiency is most important!
5. Database theory is prior and more important: store every data once! This is not effectivly possible using text files. Despite this fact: Every text file is a binary in times of multi-cultural Unicode.
7. Systemd shell scripts are known as unit files in an extra simple language better fitting its purpose
8. I never saw a gui of systemd.
Last edited by ulenrich; 01-28-2013 at 03:06 PM.
and the Makefile contained in this tarball.
It would be much more convenient if it supported a --only-udev build, but my understanding from the LFS developers was that a) upstream weren't interested, and b) this standalone Makefile was actually easier than patching the systemd build files. Certainly, udev is one of those packages that doesn't benefit much from using an autotools build, since it's not intended to be portable, nor does it have a set of complex dependencies to check for.