PDA

View Full Version : Where to modify grub timeout?



de4mator
19-Feb-2012, 18:49
Hi,
I would like to modify the default grub timeout (10 seconds) using Custom scripts or Overlay files in the SUSE Studio. It seems that /etc/sysconfig/boot (CONFIRM_PROMPT_TIMEOUT) is not the right place. File /boot/grub/menu.lst is not present in the image. How is the menu.lst created/where to set the timeout?
Thanks in advance.

SUSE Studio, Based on: openSUSE 12.1

malcolmlewis
19-Feb-2012, 19:30
Hi,
I would like to modify the default grub timeout (10 seconds) using
Custom scripts or Overlay files in the SUSE Studio. It seems that
/etc/sysconfig/boot (CONFIRM_PROMPT_TIMEOUT) is not the right place.
File /boot/grub/menu.lst is not present in the image. How is the
menu.lst created/where to set the timeout?
Thanks in advance.

SUSE Studio, Based on: openSUSE 12.1



Hi
If you start the appliance in Test Drive, you can then modify the
menu.lst file and save the modified configuration menu.lst file.

--
Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 3.0.13-0.27-default
up 21:06, 3 users, load average: 0.00, 0.01, 0.05
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

de4mator
19-Feb-2012, 22:01
Hi
If you start the appliance in Test Drive, you can then modify the
menu.lst file and save the modified configuration menu.lst file.

--
Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 3.0.13-0.27-default
up 21:06, 3 users, load average: 0.00, 0.01, 0.05
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

I tried that but it seems that the menu.lst is overwritten after the file overlay. My menu.lst started with:

timeout 1
gfxmenu (hd0,0)/boot/message
...
But the image (Build->View files) contains:

color cyan/blue white/blue
default 0
timeout 10
...

There must be some script that modifies that. I would like to know its location.

malcolmlewis
19-Feb-2012, 23:47
malcolmlewis;2485 Wrote:
There must be some script that modifies that. I would like to know its
location.

Yast -> bootloader which should rebuild (mkinitrd) it. So changing it
manually and running mkinitrd should work as well.

--
Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 3.0.13-0.27-default
up 1 day 1:23, 3 users, load average: 0.15, 0.07, 0.06
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

de4mator
20-Feb-2012, 20:09
Yast -> bootloader which should rebuild (mkinitrd) it. So changing it
manually and running mkinitrd should work as well.

--
Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 3.0.13-0.27-default
up 1 day 1:23, 3 users, load average: 0.15, 0.07, 0.06
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

I cannot put "mkinitrd" into the "end of build" script. It ends with the following:

Kernel image: /boot/vmlinuz-3.1.9-1.4-default
Initrd image: /boot/initrd-3.1.9-1.4-default
device node not found
root device (/dev/vda) not found
There was an error generating the initrd (1)

I solved my problem by putting this into the "boot time" script:

if [ -f /etc/init.d/suse_studio_firstboot ]
then
# Put commands to be run on the first boot of your appliance here
echo "Running SUSE Studio first boot script..."
sed -i 's/timeout 10/timeout 1/' /boot/grub/menu.lst
fi

It is not optimal, but better than nothing. Thank you anyway, I forgot the possibility to watch modifications in the Test Drive.
Btw. I discovered that the boot timeout is mentioned here (http://mindfluxinc.net/?p=286). Author of the article left that as an exercise for the reader [wonderful :-\].