On 10.2.2014 22:31, Bruce Dubbs wrote: > Armin K. wrote: >> The reply below is for linux users/administrators in general, not for >> LFS users/administrators. > >> What systemd does is set up few builtin tasks, like basic stuff that's >> expected and required (more or less) to have on any linux os, then parse >> unit files which are in fairly understandable format and start the >> service as described in the unit file, in the order dependent on the >> scripts contents. Then it starts its other components, blah blah, and >> everything else. > > And if I want to do something my way can I disable the old way? Let's > say I wanted to replace login or message handling with my program and I > want to prevent systemd's version from running. Can I do that? >
Login, well probably YES if there was another one. If you meant logging, then also YES (for some values of YES). You can use custom logging daemon (sysklogd, rsyslog, etc) but systemd requires journald to be running. That doesn't however prevent you from using your own solution atop the deafult one if you feel the need. Same way you can use several desktops/wm's atop the XServer, but still the XServer needs to be running, no matter what (not really a good analogy, but I think you get the point). I don't know what message handling program you mean. If that's journald, then it's already answered. People seem to rather abuse "freedom of choice" since the developers can choose to do what they want with their software or to use anything they see fit for it. If you don't like it, write your own solution. >> As my message above says, not everyone wants to understand the most >> basic tasks that's used everywhere these days (mostly everywhere). > > I agree, but some do. And I think it's important to know for > administrators and developers. > I don't think that any admin, and especially developer (not a Distro developer though) needs to know at which point fsck is being run (although systemd will record that), or how and when exactly devtmpfs or proc were mounted. It's rather important that they *are* mounted or that fsck was run and the filesystem was without errors to most (if not all) administrators. I doubt that non-distro developers even care for anything in the boot process except when their login prompt appears (be it GUI or tty one) and if the filesystem is healthy (or if their service was started that they need). > -- Bruce > -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
