Description of problem: My kickstart config says: bootloader --location=mbr --driveorder=vda,vdb --append="console=ttyS0,115200" I explicitly removed the "rhgb quiet" part from the anaconda-generated kickstart file. However when I install with this configuration, the final grub.conf still shows: kernel /boot/vmlinuz-2.6.18-156.el5 ro root=LABEL=/ console=ttyS0,115200 rhgb quiet Version-Release number of selected component (if applicable): 5.4 snapshot 1 Additional info: I observed this installing a virtual machine with virt-install ... -x "console=ttyS0,115200 ks=http://foo/ks.cfg"
simple workaround I'm using in ks.cfg: %post sed -i 's/rhgb quiet//' /etc/grub.conf
--append simply adds the given arguments to the bootloader configs, just like you would expect. Is having these arguments present causing problems when booting?
Hi Chris, anaconda puts "rhgb quiet" in the generated ks.cfg, as in: --append="console=ttyS0,115200 rhgb quiet". That would seem to imply that removing those args would have an effect on the installed host. I filed this report because I was surprised to see that anaconda will add them regardless. It's not really a problem for me, just something I didn't expect. Removing the args in the %post script is sufficient. I never want them on server installs or test installs; both cases where I want to see the full boot text. If anaconda is always going to add those arguments, it would perhaps be appropriate to remove them from the generated --append line, where they serve no purpose except to confuse. However it doesn't bother me if you'd rather punt and concentrate on real bugs. :-)
This issue should be fixed in the next major release of RHEL, and in Fedora rawhide in the meantime. Thanks for the idea - it's definitely the kind of little polishing issue we need to spend more time on. It sounds like you've got a decent workaround for now, but if you do require it in an update release of RHEL5, please raise it through the regular support channels so we can schedule the time for backporting the fix. Thanks.
This bug is still present in RHEL 6u1. I'd love to see the default for rhgb quiet go away. Thanks to Aron for the workaround, though.
(In reply to comment #1) > %post > sed -i 's/rhgb quiet//' /etc/grub.conf For anyone still stumbling upon this workaround, note that the quoted text will replace the symlink at /etc/grub.conf with a regular file copy of /boot/grub/grub.conf. Over time, the two copies will diverge, and -- in the worst case -- you will eventually end up with an unbootable system. If you must, run sed over the symlink's target instead: sed -i 's/rhgb quiet//' /boot/grub/grub.conf
(In reply to Saj Goonatilleke from comment #8) > (In reply to comment #1) > > %post > > sed -i 's/rhgb quiet//' /etc/grub.conf > > For anyone still stumbling upon this workaround, note that the quoted > text will replace the symlink at /etc/grub.conf with a regular file copy > of /boot/grub/grub.conf. Over time, the two copies will diverge, > and -- in the worst case -- you will eventually end up with an > unbootable system. > > If you must, run sed over the symlink's target instead: > > sed -i 's/rhgb quiet//' /boot/grub/grub.conf And on an atomic system this is a symlink as well! So you should really add --follow-symlinks to the command.
upstream request to have this configurable: https://github.com/rhinstaller/anaconda/issues/1079