Questions[grub](server)

I'd like to remove the rhgb and quiet kernel parameters which are used by default when the kernel is booted in CentOS 6, but I want this to apply to all currently installed kernels as well as any kernels installed in the future. I need to do this from a script, so manually editing files isn't an option and any file changes should be done as cleanly as possible.

In Debian/Ubuntu I would change GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub and then run update-grub. I can't find such a setting in /etc/sysconfig/grub or /etc/sysconfig/kernel however, nor is there an update-grub script.

I have weird situation - order of disks as reported by BIOS, is different than order of disks that Linux sees.

Which makes for problematic run - grub installs to sda, but bios boots from sdd or something like this (this machine has 7 disks, 4 on internal controller, and 3 on external.

Is it possible to make grub install (and later on update) to all disks, and not just /dev/sda? I have no idea which disk is the one that bios wants to boot (all disks are the same, and since I have raid over it, I can't remove them at will), so the only solution I see is to make grub install on all sda-sdg.

This is Debian stable, with Grub2.

I have Ubuntu 10.10 Server installed on a single-board machine in a semi-embedded environment; no keyboard or screen, just SSH access to it.

So it's really frustrating when it occasionally boots up and gets stuck on the GRUB menu, waiting for a keystroke to select the first option.

How do I configure GRUB to under no circumstances wait for a keystroke?

Update #1: There is no menu.lst, since this is GRUB 2. But I do have an /etc/default/grub which is like so:

GRUB_DEFAULT=0
#GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=2
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""

Update #2: I figured it out. On boots which follow unsuccessful boots, GRUB disables its own timeout. Since showing the menu makes a boot unsuccessful, this is an inescapable loop. This behaviour may be disabled by editing the /etc/grub.d/00_header file, and changing the make_timeout function:

make_timeout ()
{
    echo "set timeout=0"
}

Now exit and re-run the grub configuration updater script:

sudo update-grub2

It makes no sense to me that this behaviour would be the default for Ubuntu Server, a product intended for machines accessed by console.

I would like to install 2 completely independent instances of Windows XP (no data should be shared) in my computer within 2 different primary partitions. I know that grub can handle booting them correctly, but I have no idea if it's possible to install it and configure it within a 100% NTFS system and without any extra linux partition/distribution.

OS: Ubuntu 8.04 LTS Server Edition

We just rolled back an kernel update using the following command:

sudo apt-get remove linux-image-2.6.24-24-server

The uninstallation was successful, but it had the following message before apt-get exited:

The link /vmlinuz is a damaged link
Removing symbolic link vmlinuz
 you may need to re-run your boot loader[grub]
The link /initrd.img is a damaged link
Removing symbolic link initrd.img
 you may need to re-run your boot loader[grub]

Should we be worrying about this message? Do we need to re-run GRUB? How do we go about doing this if we have to re-run GRUB?

Thanks in advance.