Josh Triplett wrote: > Do you mean the options used within d-i itself, or on the installed > system? The latter; d-i does not run with systemd. > If you mean the latter, that configuration is owned by the grub-common > package, not by d-i. grub-installer configures the grub menu file to include quiet and other kernel options. > And in any case, grub-common should not be abusing > its configuration of the *kernel* command line to override the defaults > of packages other than the kernel. d-i is not setting quiet with the intention of making systemd quiet, but with the intention of suppressing ugly kernel messages. And I really only wanted to do that for desktop installs. The difference is that verbose kernel messages as it enumerates all hardware and so on are unlikely to be useful if you're sitting at a system that has somehow deadlocked on boot, while seeing which daemons systemd is starting is, IME, quite useful when it's gotten into such a situation.. > More generally, a quiet boot is a feature, not a bug. The bug you filed > is absolutely legitimate, but making bootup noisier by default isn't the > right way to fix it. To the best of my knowledge, with "quiet", systemd > is supposed to behave the same way the kernel does: shut up about > commands that succeed, but still shout about failures, making them > *easier* to notice. If that's not happening, that's a bug to be fixed. Well, I filed the bug I mentioned about just that. I have seen systemd boot to a black screen with no indication what it was waiting on. I've seen this more than once, in different installations. > And in any case, step 1 in debugging a failure to boot should be "try > booting without quiet" (or boot in recovery mode, which also omits > quiet). No, step 1 in debugging should be "look at the screen and see what went wrong". systemd has a great web page with extensive documentation about how to coax information out of systemd when it fails, but this web page is entirely useless when you were booting the computer you use to read web pages. And it's nearly as useless when you're debugging someone else's system remotely and can't get them to read off the last things that went on without first walking them through a crazy kernel command line edit process in the boot loader. -- see shy jo
Attachment:
signature.asc
Description: Digital signature