rhgb options and Grub
Okay, this is purely cosmetic, and shouldn't really matter, but it's driving me mad. I'm using Fedora Core 5 on my notebook, and defaulting to runlevel 5. Everything works great, but I want to see the details as I boot.
I want to use rhgb because it looks good, I just want to see the details without having to click on 'show details'. I've searched high and low on Google, and found the same question, but can't seem to find the answer, everyone just gives up and quits using rhgb. This must be a simple option. I noticed in grub/menu.lst that the default is "rhgb quiet", implying that there is an option besides 'quiet', but I can't find any documentation that might tell me what it is. Does anyone have any information on the options for rhgb in grub, or can point me in the right direction? Thanks much, Tim :scratch: |
You can "experiment" with the GRUB settings by using the "e" option when the boot menu is displayed. Changes made at that point are only made in memory, not in your grub.conf file.
As to the "quiet" option, the other option is to just remove it. You can also change settings in /etc/rc.d/rc.sysinit to get more output, and in the service startup files in /etc/init.d. And, if you want lots of detail, you can change the /init script (written in nash) loaded into the initial ram disk (by the initrd load parameter) to display a lot of messages. Personally, I find very little of interest in the verbose output, and would not even look at it unless I had a problem, and I couldn't find the error reported in the logs. But the choice is yours to make. A suggestion: If you do modify the rc.sysinit and/or the init.d scripts, do it so that any additional output goes to a log file you can review later. Trying to read it on the screen is problematic, even using the flow control keys. |
Meh, editing the grub.conf file means I can keep track of what I've done, and these changes don't seem to put me in any danger of breaking anything, they just don't seem to accomplish anything either :-/ and since I have to reboot to see what happens anyway. . .
Removing the "quiet" seems to have no effect whatsoever. It still requires me to click on details (I already did this). I looked in rc.sysinit, and it scared me, lol. I can only see two references to rhgb that doesn't seem to be a selinux command (wonder why selinux cares about rhgb. . .): Code:
# Start the graphical boot, if necessary; /usr may not be mounted yet, so we Code:
# Start the graphical boot, if necessary and not done yet. I guess this isn't 100% cosmetic, but more like 90%. Occasionally, I have noticed errors in this output that weren't immediatley apparent when the system was running, letting me get a jump on fixing it. Still, it's pretty minor, but still bugging the hell out of me. Thanks for looking into it for me, I was afraid that this message would fade into oblivion, lol. Tim |
Quote:
|
Hmm. . . so what did I do when I removed "quiet"?
|
Quote:
|
Aha! Thought something looked different, but couldn't place it. Thanks.
Still doesn't get me closer to figuing out my details problem tho. . . wonder who at redhat knows, think it would be fesable to ask them? |
All times are GMT -5. The time now is 12:56 PM. |