matthew wrote: > It's been a while since I looked at it, but which of systemd's > utilities doesn't adhere to the 'do one job and do it well' > philosophy?
I've already removed that verbage, but see below. > I see systemd as a collection of utilities much like > coreutils and util-linux. I'd agree with your point if the systemd > package just delivered a single systemd binary that handled device > naming, system logging and login management. The problem is that the executables are so interrelated you can't use just some. Can you separate systemd-init and any one of a number of other commands -- systemctl, systemd-ask-password, journalctl, systemd-logind, loginctl, timedatectl, localectl, etc. They are all tied together so tightly that you can't pick and choose but must run all or none. Even udev, which we've shown can be run separately, is now tied so tightly in the libraries, that you have to build a dozen extra library files (not needed by udev), to get the programs to link. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
