Ben Hutchings <b...@decadent.org.uk> writes: > On Sun, 2014-10-26 at 02:44 +0100, lee wrote: > [...] >> I strongly recommend to change the installer to *not* use the quiet >> option. Especially with the installer, there is much point in being >> able to see all messages, and not everyone installs Debian on up-to-date >> and/or fully known hardware. > > No, it is important to see the *error* messages. The bug is that this > error message is suppressed when 'quiet' is used.
This message is probably not the only error message you don't see when "quiet" is used. IIRC, you don't see it when the killing of modprobe is being delayed. I'll have to verify. >> Besides, the "quiet" option shouldn't be used by default after the >> installation has completed, either. > [...] > > It is the correct default. Those *expert* users who feel able to > interpret the extra information that may be logged to the console are > exactly the users that are most likely to know how to override this > default. You don't have to be that "expert user" to be able to figure out that something isn't right when you see the messages, and you cannot expect everyone to know about this option and how it may hide problems. I've been using Debian for over 20 years and didn't know it would hide so much. I only found out about it by chance and tried it in desperation. So I don't understand what should be correct about hiding potentially important and valuable information from users by default. It seems far more logical to display such information until the user has verified that everything works, in which case they can add this option if they want. Users who want as much as possible hidden from them can use other OSs. -- Again we must be afraid of speaking of daemons for fear that daemons might swallow us. Finally, this fear has become reasonable. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/871tpuhutf....@gulltop.yagibdah.de
