On Fri, Jun 24, 2011 at 09:51:14PM +0100, Brian wrote:
> On Fri 24 Jun 2011 at 21:35:16 +0200, Sven Joachim wrote:
>
> > Having switched to grub2 recently, I do that as well. But I suspect
> > most people will be content with the simpler configuration options
> > offered by editing /etc/default/grub and running update-grub.
>
> That's me! Although I do have a little change made to debian_theme.
>
> Why is it some people dislike GRUB2? My experience isn't great but it
> boots Debian kernels reliably on my machines. Nothing complicated I
Grub2 didn't like my setup during upgrade.
My menu.lst of Grub 0.97 included numerous different rc levels to select
from. Just a way of selecting between different interfaces while booting.
So the following blocks in the automagic section of menu.lst resulted in a 4
item menu for each kernel, one item booting into GDM, the next starting
xinit with Openbox--booting from rc5.d, rc4.d rc3.d and rc2.d respectively.
## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## altoptions=(single-user) single
# altoptions=(GDM) 5 vga=791 quiet
# altoptions=(Openbox) 4 vga=791 quiet
# altoptions=(Screen) 3 vga=791
# altoptions=(single-user mode) single
## controls how many kernels should be put into the menu.lst
## only counts the first occurence of a kernel, not the
## alternative kernel options
## e.g. howmany=all
## howmany=7
# howmany=all
When grub2 setup hit that, it gave me some garbled menu item that failed,
followed by its basic boot items for console and maintenance.
So now I have an /etc/grub.d/09_custom that renders a menu above Grub2's
default menu. I manually edit it for kernel upgrades with "find and
replace" of kernel numbers. I don't like having a fractured, two part menu
that doesn't completely upgrade automagically. But it works:
#!/bin/sh
exec tail -n +3 $0
# mine
menuentry "> -- // Deneb HD II -- Debian GNU/Linux \\\\ -- <" {
set root=(hd1,mdos3)
}
menuentry 'Debian GNU/Linux, Kernel 2.6.37-1-amd64 (GDM)' --class debian
--class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd1,msdos3)'
search --no-floppy --fs-uuid --set
ab51dc6e-10ca-4c02-b9dd-d6a4d393cb9e
echo 'Loading Linux 2.6.37-1-amd64 ...'
linux /boot/vmlinuz-2.6.37-1-amd64
root=UUID=ab51dc6e-10ca-4c02-b9dd-d6a4d393cb9e ro irqpoll 5 quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.37-1-amd64
}
menuentry 'Debian GNU/Linux, Kernel 2.6.37-1-amd64 (OpenBox)' --class debian
--class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd1,msdos3)'
search --no-floppy --fs-uuid --set
ab51dc6e-10ca-4c02-b9dd-d6a4d393cb9e
echo 'Loading Linux 2.6.37-1-amd64 ...'
linux /boot/vmlinuz-2.6.37-1-amd64
root=UUID=ab51dc6e-10ca-4c02-b9dd-d6a4d393cb9e ro irqpoll 4
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.37-1-amd64
}
menuentry 'Debian GNU/Linux, Kernel 2.6.37-1-amd64 (Screen)' --class debian
--class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd1,msdos3)'
search --no-floppy --fs-uuid --set
ab51dc6e-10ca-4c02-b9dd-d6a4d393cb9e
echo 'Loading Linux 2.6.37-1-amd64 ...'
linux /boot/vmlinuz-2.6.37-1-amd64
root=UUID=ab51dc6e-10ca-4c02-b9dd-d6a4d393cb9e ro irqpoll 3
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.37-1-amd64
. . .
> admit, and I'm not overfussed about configuring it to display fancy
> menus. What basic changes to grub.cfg cannot be made from the files in
> /etc?
>
> As an aside: Is having 'DO NOT EDIT THIS FILE' and making the file
> read-only really an invitation to do the opposite?
>
Without any other information, I'd have to edit the file to see what
happens. =:0
--
Regards,
Freeman
"Microsoft is not the answer. Microsoft is the question. NO (or Linux) is the
answer." --Somebody
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110624221113.GA4325@Deneb.office
