Bug 120275
| Summary: | "Show details" boot option is not remembered | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Need Real Name <lsof> |
| Component: | rhgb | Assignee: | Daniel Veillard <veillard> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-10-12 09:59:25 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Need Real Name
2004-04-07 15:13:44 UTC
Why should it be persistent? If I'm a basic user, I don't want to see the detail. If I'm a power user, I want to see see the detail. Once I've decided which category I'm in, I'd like to stay there :) Any idea if this will be fixed by RHEL4 - I'd like the option to see boot messages on our servers without doing anything. Problem still exists. Upping to FC2. For most users, "show details" is only needed if you have a problem being reported. Your point seems that you want to see the log messages on your server, I don't see why desactivatng rhgb on them is not the right option then. Can be as simple as rpm -e rhgb. Why is this not the right solution if you want to see the boot messages ? You can also suppress the rhgb kernel option in grub/lilo configuration file. I don't consider the normal behaviour a bug at this point, unless you can explain why desactivating rhgb is not the right option. Daniel My sole reason for opening the bug is simplicity. If a user wants to view the boot messages, the simplest way would be for them to click the "show details" button. The setting would be remembered. If they then changed their mind later on, one click of the button Switches them back. Simple. It's true that rhgb could be removed (or "quiet"/"rhgb" removed from /boot/grub/menu.lst), but that isn't nearly as simple. FC3 seems to switch to non-graphical mode when it encounters an error, so this bug can probably go away. I'll reopen if I'm wrong. |