On Sun, Feb 16, 2014 at 1:26 PM, Mick <michaelkintz...@gmail.com> wrote: [snip] > You may have lost it in the link that Volker posted (thanks Volker), but this > comment from HaakonKL probably sums it up: > > "... I will give Upstart this though: Should something better come along, you > could replace upstart. I guess this holds true for OpenRC as well. > > You can't say that about systemd."
I had read that blog entry before. Is full of errors, like believing that everything that systemd does is inside PID 1. There is actually little code inside PID 1; most of systemd functionality comes from separated binaries. You know, do one thing, do it right? >From [1]: "If you build systemd with all configuration options enabled you will build 69 individual binaries. These binaries all serve different tasks, and are neatly separated for a number of reasons." > Can you surgically remove systemd in the future without reverse engineering > half of what the LSB would look at the time, or will its developers ensure > that this is a one time choice only? You guys talk about software like if it was a big bad black magical box with inexplicable powers. If someone is willing and able, *everything* can be "surgically remove[d]". We got rid of devfs, remember? We got rid of OSS (thank the FSM for ALSA). We got rid of HAL (yuck!). GNOME got rid of bonobo, and ESD. KDE got rid of aRts (and who knows what more). You can get rid of *everything*, if so you desire. But *someone* needs to write/patch the code. Regards. [1] http://0pointer.de/blog/projects/the-biggest-myths.html -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México