Hi, Marc Haber: > Will it be the norm that the binaries replacing well-used shell > scripts on early boot only implement the features that Lennart deemed > useful? That would be a major turn-off, adding to the fact that early > boot will become undebuggable since one will not be able any more to > dump -x'es in shell scripts to see what's going on.
This begs one question: Why would you want to? "systemctl status" tells you quite clearly what went wrong, "journalctl" shows you what the program printed in case it did get started … and so on. If you manage not to get a login prompt, enable debug.service and you'll have a root shell on TTY 9. systemctl has even grown a --root argument, so you can do that to a mounted file system if you can't get even get an emergency prompt, or you can use it from the kernel command line. This is a whole lot easier than munging random shell scripts or, worse, booting with /bin/bash as PID1. Sticking "-x" into scripts was a major PITA from the beginning. It grew even more pains as init-functions and colorful prompts came along, and I for one am VERY happy to finally get rid of that kind of "debugging". -- -- Matthias Urlichs -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140510095519.gc12...@smurf.noris.de
