Hi Peter The symlinks aren't broken: the grub.conf file is located in /boot/grub/. /etc/grub/menu.lst points to it and so does /etc/grub.conf ... [root at server grub]# ls -l /etc/grub.conf /boot/grub/menu.lst /boot/grub/grub.conf -rw------- 1 root root 974 Feb 3 13:59 /boot/grub/grub.conf lrwxrwxrwx 1 root root 11 Dec 15 10:04 /boot/grub/menu.lst -> ./grub.conf lrwxrwxrwx 1 root root 22 Dec 15 10:04 /etc/grub.conf -> ../boot/grub/grub.conf -- TIA Paolo On Tue, Feb 3, 2009 at 3:07 PM, Peter Kjellstrom <cap at nsc.liu.se> wrote: > On Tuesday 03 February 2009, Paolo Supino wrote: > > Hi Ralph > > > > You're right and I'm partially wrong: I changed /boot/grub/menu.lst from > > acpi=off to pci=nommconf and rebooted the system expecting it to come up > > with the new command line parameters. As you've shown me in the paste of > > the dmesg output I posted this isn't the case. Which makes me wonder, and > > ask, where does it take the boot parameters from if not from > > /boot/grub/menu.lst? > > On CentOS the grub config file is /boot/grub/grub.conf. There are normally > two > symlinks pointing to this, /etc/grub.conf and /boot/grub/menu.lst. > > If your /boot/grub/menu.lst is broken (now a file not a symlink) then this > is > expected behaviour. Check it out with the file command. > > /Peter > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20090203/92317ccc/attachment-0005.html>