Re: Grub question
David Wright composed on 2022-04-21 12:28 (UTC-0500):
> On Thu 21 Apr 2022 at 05:30:31 (-0500), Richard Owlett wrote:
>> When creating a partition with Gparted the is a box titled "Label:".
>> I was referring to the content placed there.
> There are lots of partitioners, but only one set of useful names,
> those matched by * in /dev/disk/by-*. I let the Grub scripts play
> with the UUIDs, and switch over to LABELs when it's done.
>> > Grub itself, of course,
>> > supports their use, but not the scripts that generate grub.cfg.
>> IIRC several years ago I was told I could manually edit to display as
>> desired. It would be overwritten the next time update-grub was run.
> That's right. So you can change what Grub eventually does when booting
> at several levels:
> . Press E at the blue screen, and do what you like as it only lasts
> one boot. But remember what it was you did, in case it works.
> . Edit grub.cfg, and take some care, but if you screw up, you can
> boot from another entry, and grub-mkconfig will generate a fresh
> copy.
> . Edit /etc/default/grub, and take more care as screw-ups are
> more persistent.
> . Roll your own.
Roll your own includes using /boot/grub/custom.cfg composed and maintained
exclusively by the sysadmin. This file is never written by the installation
itself. It needs changing only when:
1-Distro is added or removed.
2-Admin wants Distro name in Grub menu to be changed.
3-An applicable volume LABEL is changed.
/boot/grub/custom.cfg is routinely incorporated by Grub into the tail of
/boot/grub/grub.cfg via /etc/grub.d/40_custom and/or 41_custom. If 40_custom and
41_custom are copied by the admin to 06_custom and 07_custom, then Grub
incorporates the content of /boot/grub/custom.cfg before the automatically
generated /boot/grub/grub.cfg entries, putting the custom entries conveniently
at
the top of each boot menu.
My current custom.cfg is using 7 lines per menuitem, compared to a more typical
autogenerated entry of about 17 lines. Example:
menuentry "Debian 11 Bullseye on Partition 14" {
load_video
set gfxpayload=keep
search --no-floppy --set=root --hint-baremetal=ahci0,gpt14 --label
exampleLabel
linux /vmlinuz root=LABEL=exampleLabel noresume mitigations=auto
consoleblank=0
initrd /initrd.img
}
Note lack of kernel and initrd versioning. Symlinks to current and previous
kernels and initrds are automatically generated in / on Debian installations.
Thus there's no need for custom.cfg change when kernels are installed or
removed or initrds rebuilt.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
Re: Grub question
On Thu 21 Apr 2022 at 05:30:31 (-0500), Richard Owlett wrote: > On 04/20/2022 05:44 PM, David Wright wrote: > > On Wed 20 Apr 2022 at 20:09:54 (+), Andrew M.A. Cater wrote: > > > On Wed, Apr 20, 2022 at 02:31:30PM -0500, Richard Owlett wrote: > > > > I have a machine set aside to test several configurations of Debian 11. > > > > > > > > Is there away to have the Grub Menu _automatically_ display the assigned > > > > partition name rather than than /dev/sdaN ? > > > > > > I wonder whether this changes if you use labels as references? > > > > I'm not sure quite what you mean by "as references". > > > > > To be honest, I never notice - it's a menu which says Debian and a couple > > > of other options and I jut hit [Enter] almost automatically :) > > > > If by "assigned partition name" the OP means either of LABEL or > > PARTLABEL, then I think the answer is no. > > When creating a partition with Gparted the is a box titled "Label:". > I was referring to the content placed there. There are lots of partitioners, but only one set of useful names, those matched by * in /dev/disk/by-*. I let the Grub scripts play with the UUIDs, and switch over to LABELs when it's done. > > Grub itself, of course, > > supports their use, but not the scripts that generate grub.cfg. > > IIRC several years ago I was told I could manually edit to display as > desired. It would be overwritten the next time update-grub was run. That's right. So you can change what Grub eventually does when booting at several levels: . Press E at the blue screen, and do what you like as it only lasts one boot. But remember what it was you did, in case it works. . Edit grub.cfg, and take some care, but if you screw up, you can boot from another entry, and grub-mkconfig will generate a fresh copy. . Edit /etc/default/grub, and take more care as screw-ups are more persistent. . Roll your own. (I think all that was more for the benefit of mick crane, BTW.) For using LABELs, the second approach is easiest, as long as you script it. Kernel and Grub upgrades will create a fresh grub.cfg which will require rerunning your script. > > If you allow grub-mkconfig to use UUIDs (the default), then > > it's relatively straightforward to script their conversion > > to LABELS, using the information in /run/udev/data/b* to > > build a conversion table. Just remember that you have to > > pair each change with the option names, --fs-uuid → --label. > > > > That probably falls outside the OP's definition of _automatically_ > > displaying them. > > It's outside of my ideal dream. My desired result should be achievable > with a batch file calling update-grub and then using a routine to do > the process in the paragraph above. 'Bout time I brushed up on batch > file prep ;} That's right. My script copies grub.cfg → grub.cfg-uuids and grub.cfg-edited → grub.cfg-old, then processes grub.cfg → grub.cfg-edited as described, and copies that back to grub.cfg. > Recommended reading that I wouldn't immediately find with DuckDuckGo? That depends on the language you choose for your script. I used shell, so Greg's pages are invaluable for, eg, bash arrays. You used to express a preference for TCL at one time. Cheers, David.
Re: Grub question
On Thu 21 Apr 2022 at 05:30:31 -0500, Richard Owlett wrote: > On 04/20/2022 05:44 PM, David Wright wrote: > > On Wed 20 Apr 2022 at 20:09:54 (+), Andrew M.A. Cater wrote: > > > On Wed, Apr 20, 2022 at 02:31:30PM -0500, Richard Owlett wrote: > > > > I have a machine set aside to test several configurations of Debian 11. > > > > > > > > Is there away to have the Grub Menu _automatically_ display the assigned > > > > partition name rather than than /dev/sdaN ? > > > > > > I wonder whether this changes if you use labels as references? > > > > I'm not sure quite what you mean by "as references". > > > > > To be honest, I never notice - it's a menu which says Debian and a couple > > > of other options and I jut hit [Enter] almost automatically :) > > > > If by "assigned partition name" the OP means either of LABEL or > > PARTLABEL, then I think the answer is no. > > When creating a partition with Gparted the is a box titled "Label:". > I was referring to the content placed there. > > > Grub itself, of course, > > supports their use, but not the scripts that generate grub.cfg. > > IIRC several years ago I was told I could manually edit to display as > desired. It would be overwritten the next time update-grub was run. > > > > > If you allow grub-mkconfig to use UUIDs (the default), then > > it's relatively straightforward to script their conversion > > to LABELS, using the information in /run/udev/data/b* to > > build a conversion table. Just remember that you have to > > pair each change with the option names, --fs-uuid → --label. > > > > That probably falls outside the OP's definition of _automatically_ > > displaying them. > > It's outside of my ideal dream. My desired result should be achievable with > a batch file calling update-grub and then using a routine to do the process > in the paragraph above. 'Bout time I brushed up on batch file prep ;} I take it you want to replace (on /dev/sda5) with something like (on LABEL). How about this? e2label will enable matching /dev/sda5 and other devices with a LABEL. Then a script to seach and replace (on /dev/sdaN) with the corresponding LABEL. The script could be run from update-grub and update-grub diverted. This looks like automatic to me. -- Brian.
Re: Grub question
On Thu, 2022-04-21 at 05:30 -0500, Richard Owlett wrote: > On 04/20/2022 05:44 PM, David Wright wrote: > > On Wed 20 Apr 2022 at 20:09:54 (+), Andrew M.A. Cater wrote: > > > On Wed, Apr 20, 2022 at 02:31:30PM -0500, Richard Owlett wrote: > > > > I have a machine set aside to test several configurations of Debian 11. > > > > > > > > Is there away to have the Grub Menu _automatically_ display the assigned > > > > partition name rather than than /dev/sdaN ? > > > > > > I wonder whether this changes if you use labels as references? > > > > I'm not sure quite what you mean by "as references". > > > > > To be honest, I never notice - it's a menu which says Debian and a couple > > > of other options and I jut hit [Enter] almost automatically :) > > > > If by "assigned partition name" the OP means either of LABEL or > > PARTLABEL, then I think the answer is no. > > When creating a partition with Gparted the is a box titled "Label:". > I was referring to the content placed there. To help people who don't use gparted: that looks like it's the label for the filesystem to be created in the partition, because there is a separate box for 'Partition name'. -- Tixy
Re: Grub question
On 04/20/2022 05:44 PM, David Wright wrote: On Wed 20 Apr 2022 at 20:09:54 (+), Andrew M.A. Cater wrote: On Wed, Apr 20, 2022 at 02:31:30PM -0500, Richard Owlett wrote: I have a machine set aside to test several configurations of Debian 11. Is there away to have the Grub Menu _automatically_ display the assigned partition name rather than than /dev/sdaN ? I wonder whether this changes if you use labels as references? I'm not sure quite what you mean by "as references". To be honest, I never notice - it's a menu which says Debian and a couple of other options and I jut hit [Enter] almost automatically :) If by "assigned partition name" the OP means either of LABEL or PARTLABEL, then I think the answer is no. When creating a partition with Gparted the is a box titled "Label:". I was referring to the content placed there. Grub itself, of course, supports their use, but not the scripts that generate grub.cfg. IIRC several years ago I was told I could manually edit to display as desired. It would be overwritten the next time update-grub was run. If you allow grub-mkconfig to use UUIDs (the default), then it's relatively straightforward to script their conversion to LABELS, using the information in /run/udev/data/b* to build a conversion table. Just remember that you have to pair each change with the option names, --fs-uuid → --label. That probably falls outside the OP's definition of _automatically_ displaying them. It's outside of my ideal dream. My desired result should be achievable with a batch file calling update-grub and then using a routine to do the process in the paragraph above. 'Bout time I brushed up on batch file prep ;} Recommended reading that I wouldn't immediately find with DuckDuckGo? Thanks. Cheers, David.
Re: Grub question
On Wed 20 Apr 2022 at 20:09:54 (+), Andrew M.A. Cater wrote: > On Wed, Apr 20, 2022 at 02:31:30PM -0500, Richard Owlett wrote: > > I have a machine set aside to test several configurations of Debian 11. > > > > Is there away to have the Grub Menu _automatically_ display the assigned > > partition name rather than than /dev/sdaN ? > > I wonder whether this changes if you use labels as references? I'm not sure quite what you mean by "as references". > To be honest, I never notice - it's a menu which says Debian and a couple > of other options and I jut hit [Enter] almost automatically :) If by "assigned partition name" the OP means either of LABEL or PARTLABEL, then I think the answer is no. Grub itself, of course, supports their use, but not the scripts that generate grub.cfg. If you allow grub-mkconfig to use UUIDs (the default), then it's relatively straightforward to script their conversion to LABELS, using the information in /run/udev/data/b* to build a conversion table. Just remember that you have to pair each change with the option names, --fs-uuid → --label. That probably falls outside the OP's definition of _automatically_ displaying them. Cheers, David.
Re: Grub question
On Wed, Apr 20, 2022 at 02:31:30PM -0500, Richard Owlett wrote: > I have a machine set aside to test several configurations of Debian 11. > > Is there away to have the Grub Menu _automatically_ display the assigned > partition name rather than than /dev/sdaN ? > I wonder whether this changes if you use labels as references? To be honest, I never notice - it's a menu which says Debian and a couple of other options and I jut hit [Enter] almost automatically :) All the very best, as ever, Andy Cater
Grub question
I have a machine set aside to test several configurations of Debian 11. Is there away to have the Grub Menu _automatically_ display the assigned partition name rather than than /dev/sdaN ?
Re: Grub Question
On Sat, Oct 25, 2008 at 04:12:33PM -0400, Thomas H. George wrote: I am trying to convert from lilo where boot=/dev/sdb0 and root=/dev/sdb1 in lilo.conf I have tried kopt=root=/dev/sdb1 ro and groot=(sdb,0) in grub's menu.lst (also kopt=root=/dev/sdb0 ro since I understand grub counts from 0). The MBR is unchanged and the system still boots with lilo. kopt is the kernel command line options: it should still be root=/dev/sdb1 since the kernel starts counting from 1 (not 0 like grub). Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Grub Question
* Raj Kiran Grandhi [EMAIL PROTECTED] 27.10.2008 On Sun, Oct 26, 2008 at 05:50:04AM +0530, Raj Kiran Grandhi wrote: Just install grub on all your disks, so that your system boots irrespective of the boot order in the bios. Also, it is better to use UUID for specifying the root filesystem in menu.lst as well as in fstab. findfs UUID=uuid You can use `udevinfo --query=all --name=/dev/partition' to get the uuid of any partition. If a filesystem does not have a uuid, you can use `tune2fs -U random' to set a random uuid to that filesystem. Hello Raj, I prefer LABEL in my /etc/fstab because when you e.g. clone a partition, it's possible that the partitions get unique UUIDs. This makes it difficult to debug some errors. So with LABELs you can be sure, you are on the secure side. Look at the net for label versus uuid and you will find some interesting discussions about this problem. Just my 2¢ Michael -- Do you trust one company to decide the future ? Chose Linux! signature.asc Description: Digital signature
Re: Grub Question
Thomas H. George wrote: I am trying to convert from lilo where boot=/dev/sdb0 and root=/dev/sdb1 in lilo.conf I have tried kopt=root=/dev/sdb1 ro and groot=(sdb,0) in grub's menu.lst (also kopt=root=/dev/sdb0 ro since I understand grub counts from 0). The MBR is unchanged and the system still boots with lilo. A problem could be that the bios setup detects the hard drive which lilo believes is sdb as Sata 3 (Sata 1 is another hard drive and Sata 2 is an optical drive). I thought maybe grub would think lilo's sdb is sdc but this didn't work either. A google entry indicated there is a command line continuation feature which should show the available drives which grub sees. I haven't been able to make this work. The google entries I've found have no examples for designating Sata drives. And you ran 'grub-install dev/hda' ? I use the Super Grub Disk: http://www.supergrubdisk.org/index.php Reason: the device allocations sda, sdb, sdc... You have no idea what the drive will be. So sgd allows this sequence: ... title 2.6.26.5-hvw SDB6 from D10 + NETWORK + 2-seat findf /wd80_0jd-60.06#look for unique file root$(out_device) kernel /boot/vmlinuz-2.6.26.5-hvw root=LABEL=wd80_0jd-60.06 noapic vga=791 apm=on ddcon=1 network quiet initrd /boot/initrd.img-2.6.26.5-hvw boot ... Note that 'root $(out_device)' that eliminates setting the hardcoded device designation. I have no idea how you get around this problem with legacy grub. Works like a charm. Hugo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Grub Question
On Sun, Oct 26, 2008 at 05:50:04AM +0530, Raj Kiran Grandhi wrote: Thomas H. George wrote: I am trying to convert from lilo where boot=/dev/sdb0 and root=/dev/sdb1 in lilo.conf I have tried kopt=root=/dev/sdb1 ro and groot=(sdb,0) in grub's menu.lst (also kopt=root=/dev/sdb0 ro since I understand grub counts from 0). The MBR is unchanged and the system still boots with lilo. A problem could be that the bios setup detects the hard drive which lilo believes is sdb as Sata 3 (Sata 1 is another hard drive and Sata 2 is an optical drive). I thought maybe grub would think lilo's sdb is sdc but this didn't work either. A google entry indicated there is a command line continuation feature which should show the available drives which grub sees. I haven't been able to make this work. The google entries I've found have no examples for designating Sata drives. What have I missed? Just install grub on all your disks, so that your system boots irrespective of the boot order in the bios. Also, it is better to use UUID for specifying the root filesystem in menu.lst as well as in fstab. How do I use UUID? I googled it for a definition, then tried apropos uuid which found vol_id and findfs as two programs to generate uuid's. findfs LABEL=label is unable to resolve any entry I have tried whether device, directory or file. vol_id apparently exists only as a man page, even apt-cache search vol_id finds nothing. Tom Tom -- If you can't explain it simply, you don't understand it well enough. -- Albert Einstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Grub Question
Thomas H. George wrote: On Sun, Oct 26, 2008 at 05:50:04AM +0530, Raj Kiran Grandhi wrote: Just install grub on all your disks, so that your system boots irrespective of the boot order in the bios. Also, it is better to use UUID for specifying the root filesystem in menu.lst as well as in fstab. How do I use UUID? I googled it for a definition, then tried apropos uuid which found vol_id and findfs as two programs to generate uuid's. findfs LABEL=label is unable to resolve any entry I have tried whether device, directory or file. vol_id apparently exists only as a man page, even apt-cache search vol_id finds nothing. findfs UUID=uuid You can use `udevinfo --query=all --name=/dev/partition' to get the uuid of any partition. If a filesystem does not have a uuid, you can use `tune2fs -U random' to set a random uuid to that filesystem. Simply use root=UUID=uuid in menu.lst and UUID=uuid instead of the partition name in your fstab -- If you can't explain it simply, you don't understand it well enough. -- Albert Einstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Grub Question
I am trying to convert from lilo where boot=/dev/sdb0 and root=/dev/sdb1 in lilo.conf I have tried kopt=root=/dev/sdb1 ro and groot=(sdb,0) in grub's menu.lst (also kopt=root=/dev/sdb0 ro since I understand grub counts from 0). The MBR is unchanged and the system still boots with lilo. A problem could be that the bios setup detects the hard drive which lilo believes is sdb as Sata 3 (Sata 1 is another hard drive and Sata 2 is an optical drive). I thought maybe grub would think lilo's sdb is sdc but this didn't work either. A google entry indicated there is a command line continuation feature which should show the available drives which grub sees. I haven't been able to make this work. The google entries I've found have no examples for designating Sata drives. What have I missed? Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Grub Question
Thomas H. George wrote: I am trying to convert from lilo where boot=/dev/sdb0 and root=/dev/sdb1 in lilo.conf I have tried kopt=root=/dev/sdb1 ro and groot=(sdb,0) in grub's menu.lst (also kopt=root=/dev/sdb0 ro since I understand grub counts from 0). The MBR is unchanged and the system still boots with lilo. A problem could be that the bios setup detects the hard drive which lilo believes is sdb as Sata 3 (Sata 1 is another hard drive and Sata 2 is an optical drive). I thought maybe grub would think lilo's sdb is sdc but this didn't work either. A google entry indicated there is a command line continuation feature which should show the available drives which grub sees. I haven't been able to make this work. The google entries I've found have no examples for designating Sata drives. What have I missed? Just install grub on all your disks, so that your system boots irrespective of the boot order in the bios. Also, it is better to use UUID for specifying the root filesystem in menu.lst as well as in fstab. Tom -- If you can't explain it simply, you don't understand it well enough. -- Albert Einstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Grub question..
I did Linux install on a Vista machine but wrote the grub info to partition (and not MBR) - I want to dual boot using grub on bootable CD. /dev/sda1, /dev/sda2 are NTFS partitions /dev/sd3 (Linux swap), /dev/sda4 (Linux /, all there) I copied the grub menu.lst entry from /boot/grub/menu.lst (on /dev/sda4) as: title Debian GNU/Linux, kernel 2.6.24-2.6.24.4.slh.5-sidux-686 root(hd0,3) kernel /boot/vmlinuz-2.6.24-2.6.24.4.slh.5-sidux-686 \ root=/dev/sda4 ro quiet vga=791 initrd /boot/initrd.img-2.6.24-2.6.24.4.slh.5-sidux-686 but grub fails to find the /boot/vmlinuz-2.6.24-2.6.24.4.slh.5-sidux-686 file. Also tried prepending (hd0,3) to file name but did not work. Any pointers? -ishwar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Grub question..
ISHWAR RATTAN [EMAIL PROTECTED] writes: I did Linux install on a Vista machine but wrote the grub info to partition (and not MBR) - I want to dual boot using grub on bootable CD. /dev/sda1, /dev/sda2 are NTFS partitions /dev/sd3 (Linux swap), /dev/sda4 (Linux /, all there) I copied the grub menu.lst entry from /boot/grub/menu.lst (on /dev/sda4) as: title Debian GNU/Linux, kernel 2.6.24-2.6.24.4.slh.5-sidux-686 root(hd0,3) kernel /boot/vmlinuz-2.6.24-2.6.24.4.slh.5-sidux-686 \ root=/dev/sda4 ro quiet vga=791 initrd /boot/initrd.img-2.6.24-2.6.24.4.slh.5-sidux-686 but grub fails to find the /boot/vmlinuz-2.6.24-2.6.24.4.slh.5-sidux-686 file. Also tried prepending (hd0,3) to file name but did not work. Any pointers? Use installation CD of the Debian. Boot with it typing at boot prompt: rescue. Choose the .../part4 where is your / directory. When came to the Rescue operations, choose to run a shell on this partition. Here you mount if you have to your /usr partition with: 'mount /usr' command. Run the command: 'grub-install /dev/sda' and 'update-grub'. Then Ctrl + Alt + Del and remove your installation CD and reboot. You should now to get the Grub menu. -- Regards, Paul Csanyi http://www.freewebs.com/csanyi-pal/index.htm -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
grub question read-only
Hi, I have this in my /boot/grub/menu.lst file. (pasted below) I'm wondering whey there is an option ro on the main kernel line, even though the system boots normal rw? What would I do if I actually wanted to boot and have my system / mounted read only? Thanks! ## ## End Default Options ## title Debian GNU/Linux, kernel 2.6.8-3-686 root(hd0,0) kernel /vmlinuz-2.6.8-3-686 root=/dev/md6 ro initrd /initrd.img-2.6.8-3-686 savedefault boot title Debian GNU/Linux, kernel 2.6.8-3-686 (recovery mode) root(hd0,0) kernel /vmlinuz-2.6.8-3-686 root=/dev/md6 ro single initrd /initrd.img-2.6.8-3-686 savedefault boot ### END DEBIAN AUTOMAGIC KERNELS LIST -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub question read-only
michael wrote: Hi, I have this in my /boot/grub/menu.lst file. (pasted below) I'm wondering whey there is an option ro on the main kernel line, even though the system boots normal rw? The initramfs is mounted read-only I believe, and for the initial mount, your root filesystem is also read-only, remounted read-write later in the boot process. If you use ext3, you'll notice after an unclean shutdown you'll see messages similar to the following: EXT3-fs: recovery required on read-only filesystem. EXT3-fs: write access will be enabled during recovery. -- Andrew J. Barr | http://www.pridelands.dyndns.org/ Why must I fail at every attempt at masonry? -- Homer Simpson, Mom and Pop Art [AABF15] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub question read-only
On Thu, Apr 19, 2007 at 01:17:28PM -0700, michael wrote: [...] What would I do if I actually wanted to boot and have my system / mounted read only? when / is remounted, the flags in /etc/fstab are used, so to have / finish up mounted ro, you have to set it up so in the fstab. i think. A signature.asc Description: Digital signature
Re: grub question read-only
On Thu, 19 Apr 2007 13:42:16 -0700, Andrew Sackville-West wrote On Thu, Apr 19, 2007 at 01:17:28PM -0700, michael wrote: [...] What would I do if I actually wanted to boot and have my system / mounted read only? when / is remounted, the flags in /etc/fstab are used, so to have / finish up mounted ro, you have to set it up so in the fstab. I ended up booting to single mode. (typed in root password for command line) # init 1 # mount -o remount,ro / This seemed to work. Thanks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub question read-only
On Thu, Apr 19, 2007 at 04:30:35PM -0700, michael wrote: On Thu, 19 Apr 2007 13:42:16 -0700, Andrew Sackville-West wrote On Thu, Apr 19, 2007 at 01:17:28PM -0700, michael wrote: [...] What would I do if I actually wanted to boot and have my system / mounted read only? when / is remounted, the flags in /etc/fstab are used, so to have / finish up mounted ro, you have to set it up so in the fstab. I ended up booting to single mode. (typed in root password for command line) # init 1 # mount -o remount,ro / This seemed to work. Thanks I see. I thought, from your question above, that you were ask how to do it in general. the fstab thing will cause it to always mount ro. For one-time use, yours is a fine solution. A signature.asc Description: Digital signature
Grub question: any risk in doing this?
I want to use Sidux to install Debian on a Thinkpad Z61M which has Ubuntu preinstalled (and I don't want to lose it). Question: is it safe to let the Sidux installation rewrite grub? More details if required: I have Ubuntu on a primary partition /dev/sda3, with /home on a logical partition /dev/sda5. I want to keep Ubuntu because I am not sure if I can get wlan to work on Sidux; ditto suspend to disk. I am thinking of installing Sidux on /dev/sda1, previously a Windows partition. If I allow Sidux to rewrite the boot partition to install grub, will it still be possible to access Ubuntu, presumably by editing /boot/grub/menu.lst? -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Linux Gnu-Debian http://www.acampbell.org.uk (blog, book reviews, on-line books and sceptical articles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Grub question: any risk in doing this?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Anthony Campbell wrote: I want to use Sidux to install Debian on a Thinkpad Z61M which has Ubuntu preinstalled (and I don't want to lose it). Question: is it safe to let the Sidux installation rewrite grub? More details if required: I have Ubuntu on a primary partition /dev/sda3, with /home on a logical partition /dev/sda5. I want to keep Ubuntu because I am not sure if I can get wlan to work on Sidux; ditto suspend to disk. I am thinking of installing Sidux on /dev/sda1, previously a Windows partition. If I allow Sidux to rewrite the boot partition to install grub, will it still be possible to access Ubuntu, presumably by editing /boot/grub/menu.lst? I don't think this list is the appropriate place to dicuss this issue, but... You have 2 choices. You can let Sidux install, and tell it's /boot/grub/menu.list where to find Ubuntu, or you can choose not to let it install the mbr and tell ubuntu's /boot/grub/menu.list where to find Sidux. AFAIK, the Sidux installer will let you define the other OS during the install so you don't have to modify files manually (but do check anyway). What I do? I keep a private /boot partition and always use my boot partition, so if one of my distro's update, I have to tell grub to rewrite the mbr to use my partition. This is done with: #grub grub root (hd0,0) grub setup (hd0) grub quit Keep in mind that if either system updates it's kernel, you will need to modify the menu.lst that you normally use to boot so that it points to the new kernel, whichever method you pick. Joe - -- Registerd Linux user #443289 at http://counter.li.org/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGFKkUiXBCVWpc5J4RAsPJAJwJcXBXwqAzf8ud393r2UqgzqATMQCeLWsK k5Ub357uSeL3Y0THVyh3sJ4= =76Ag -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
A Grub Question and some Grub Information
I set up a Debian serial console installation and am going to add another Linux kernel to the list in /boot/grub/menu.lst. When looking at the boot paragraphs, I see an interesting thing that I don't quite understand. Both the possible boot methods have the savedefault line as their last line. Here they are. title Debian GNU/Linux, kernel 2.4.27-2-386 root(hd0,0) kernel /boot/vmlinuz-2.4.27-2-386 root=/dev/hda1 ro console=ttyS1,9600n81 initrd /boot/initrd.img-2.4.27-2-386 savedefault boot title Debian GNU/Linux, kernel 2.4.27-2-386 (recovery mode) root(hd0,0) kernel /boot/vmlinuz-2.4.27-2-386 root=/dev/hda1 ro console=ttyS1,9600n81 single initrd /boot/initrd.img-2.4.27-2-386 savedefault boot The savedefault line is supposed to determine which boot method is 0 as far as I understand, so what do multiple savedefaults do? Now, the behavior I discovered. After installing a third paragraph to boot a test 2.6.5 kernel, I rebooted and accidentally hit a key on the remote system that was connected to the serial TTY on the headless box. What happened was that the headless system came up with the recovery mode boot instead of the first boot. I bet hitting any key to cause activity on the serial port will cause this behavior because there is no serial console alive at that point. I should have hit 0, 1, 2 or 3 on the headless system. This behavior could be useful if it is common. It could also be vexing if you had a serial line that had some activity on it while a headless system was booting. I remember how old Sun Sparc work stations using a serial console would reboot if sent a break signal. Turning off the power to the terminal sends a very long break. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: A Grub Question and some Grub Information
Martin McCormick wrote: When looking at the boot paragraphs, I see an interesting thing that I don't quite understand. Both the possible boot methods have the savedefault line as their last line. Here they are. title Debian GNU/Linux, kernel 2.4.27-2-386 root (hd0,0) kernel/boot/vmlinuz-2.4.27-2-386 root=/dev/hda1 ro console=ttyS1,9600n81 initrd/boot/initrd.img-2.4.27-2-386 savedefault boot title Debian GNU/Linux, kernel 2.4.27-2-386 (recovery mode) root (hd0,0) kernel/boot/vmlinuz-2.4.27-2-386 root=/dev/hda1 ro console=ttyS1,9600n81 single initrd/boot/initrd.img-2.4.27-2-386 savedefault boot The savedefault line is supposed to determine which boot method is 0 as far as I understand, so what do multiple savedefaults do? Suppose you selected the recovery mode option from the boot menu. The savedefault in that stanza will cause grub to default to the recovery mode at next boot. If each stanza has its own savedefault, then the next-boot default is always reset to the most recent stanza booted ... provided that you enable this behavior by setting this: default saved in menu.lst. The next-boot default is stored in /boot/grub/default. I eliminate savedefault from stanzas that I rarely use (like win2k), so that the default is not updated. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Grub question?
You may also need to be careful with how much space there is between the beginning of the disk and where your sda6 partition begins. Grub uses the BIOS for some (all?) of its disk access functionality and so it has the same limits on disk size that the BIOS has. I had this problem, because it happens that the BIOS on my machine has the worst case limit, 512 MB. I had a Linux partition beginning after a 2G other OS partition, and grub couldn't boot it. I had to make a small, separate partition for /boot, in front of that other OS partition (fortunately, I had a space set aside that I could divide in two to do this), so it was within the range grub could work with, to get the kernel loaded. Bob Lothar Braun wrote: On Wed, 2006-06-28 at 12:11 -0400, Ishwar Rattan wrote: I am thinking of installing debian on partition /dev/sda6 (on a SATA hard disk). Grub menu entry for root partition: will/should it be (hd0,5) or (sd0,5)? It is (hd0,5). Grub uses hd for all hard drives. -- Lothar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Grub question?
Bob McGowan wrote: On Wed, 2006-06-28 at 12:11 -0400, Ishwar Rattan wrote: I am thinking of installing debian on partition /dev/sda6 (on a SATA hard disk). Grub menu entry for root partition: will/should it be (hd0,5) or (sd0,5)? It is (hd0,5). Grub uses hd for all hard drives. You may also need to be careful with how much space there is between the beginning of the disk and where your sda6 partition begins. Grub uses the BIOS for some (all?) of its disk access functionality and so it has the same limits on disk size that the BIOS has. I had this problem, because it happens that the BIOS on my machine has the worst case limit, 512 MB. I had a Linux partition beginning after a 2G other OS partition, and grub couldn't boot it. I had to make a small, separate partition for /boot, in front of that other OS partition (fortunately, I had a space set aside that I could divide in two to do this), so it was within the range grub could work with, to get the kernel loaded. Also note this; On my system, I have these GRUB entries; (hd0) = 1st *system* Harddisk (hd1) = 2nd *system* Harddisk, but located at (SM) Secondary Master (which is the 3rd IDE position). Most are aware of this - but I recently noticed that my 2nd HD is on hd*c*, yet I would've assumed that BRUBwould assign that as hd2 - since it's the 3rd IDE device (the 2nd IDE device, hdb, is an ATAPI CD Drive). So, using an older Intel Mobo, PII, a typical IDE setup, I have PM = (hd0,0) = 1st Harddisk, 1st partition PS = CDRW = nothing for GRUB SM = (hd1,0) = 2nd Harddisk, 1st partition SS = DVDRW = nothing for grub Note that SM is the 3rd IDE device...yet GRUB sees it as the 2nd. IOW - my one (likely unnecessary) small point is; GRUB doesn't count ALL the IDE devices when assigning it's 0,1,2,3 - only Fixed Disks are noticed/seen...(likely something to do with the int13 extensions that IDE Harddisks use, but that's just a guess at best). Regards __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Grub question?
I am thinking of installing debian on partition /dev/sda6 (on a SATA hard disk). Grub menu entry for root partition: will/should it be (hd0,5) or (sd0,5)? -ishwar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Grub question?
On Wed, 2006-06-28 at 12:11 -0400, Ishwar Rattan wrote: I am thinking of installing debian on partition /dev/sda6 (on a SATA hard disk). Grub menu entry for root partition: will/should it be (hd0,5) or (sd0,5)? It is (hd0,5). Grub uses hd for all hard drives. -- Lothar -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
GRUB question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Having used LILO [quavering_voice] Since The Beginning, [/quavering_voice] I have done today my first install using GRUB. I would like the same console resolution I had with LILO with vga=791. How is that specified in GRUB? It's not specified in the docs or examples. 80x25 seems so wasteful! Curt- - -- September 11th, 2001 The proudest day for gun control and central planning advocates in American history -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iQEVAwUBQ+ZPbi9Y35yItIgBAQLq7gf/YPGITbQRJpr5MCOsEmvIVY8xupSG0WiT moTe+D9QXUD/pmVvdf2q6ksqFAJgJ4NTEzQBYCU9+6M/0mIkMtgC5KORQqGStmLP 1XvPatApQy5UVwk5NQsNp+sh/XxYGc1D/jZ0teSWbfd7todlpt90Y99Cwh7SGU88 AydpwSE4Vdf/QAnoT+KppYPmn2eewehaOADweXIUP+cPTJca5nloe0HANsLnB8Pn 1oDAuk850s4rjQzcf8OEnLeOODpU1+CGQSfAXDSz5DjarVGWZ8Xc2ufyprk6aFLc Gwr8E83mENe9+MoLA/sc3nMOj0NRbc05s39c0/PP6qHhw7tMkyUDgg== =qhp4 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB question
On Sun, Feb 05, 2006 at 02:18:06PM -0500, Curt Howland wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Having used LILO [quavering_voice] Since The Beginning, [/quavering_voice] I have done today my first install using GRUB. I would like the same console resolution I had with LILO with vga=791. How is that specified in GRUB? It's not specified in the docs or examples. 80x25 seems so wasteful! Take a look at /boot/grub/menu.lst. I've added the line # defoptions=vga=793 Then run `update-grub` to update the entries in the file. /M -- Magnus Therning(OpenPGP: 0xAB4DFBA4) [EMAIL PROTECTED] http://therning.org/magnus Software is not manufactured, it is something you write and publish. Keep Europe free from software patents, we do not want censorship by patent law on written works. Finagle's Fourth Law: Once a job is fouled up, anything done to improve it only makes it worse. pgpazfiLMjXY3.pgp Description: PGP signature
Solved Re: GRUB question
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ah, appended directly to the boot line. Thank you. Since LILO has a separate section called append, it wasn't clear where or how this variable was passed to the kernel. Many thanks, I'll give it a trySuccess! Curt- On Sunday 05 February 2006 14:54 it was so written: Curt Howland wrote: Having used LILO [quavering_voice] Since The Beginning, [/quavering_voice] I have done today my first install using GRUB. I would like the same console resolution I had with LILO with vga=791. How is that specified in GRUB? It's not specified in the In the bottom of /boot/grub/menu.lst FX: title Debian GNU/Linux, kernel 2.6.11.10 root(hd0,0) kernel /vmlinuz-2.6.11.10 root=/dev/hda8 ro vga=791 - -- September 11th, 2001 The proudest day for gun control and central planning advocates in American history -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) iQEVAwUBQ+Zcty9Y35yItIgBAQKSwgf8C6Cn4J15cwVqvfETmOLqW0piSdTWCOW6 SXxasjsyowcpF1pIHLtq1/15egPyq9IZjPR7BesR3U6cQpklg0Sld3ppndua4hQ9 Zo/RxPst7O8zkvRk3674OvYqJ3lo1fGcH0D/FCKIcupZ/oBwyuAb5vqp+fGkZPQx 5fkRuinV+hn2RSWgSDncne6Mj5AvH/4xidhfsPq85KGXctuMZjhLyshZa8jQUGzm 6caHQX2oLysig91pUK7k4k0NV+3mBwIiROJnqupOZe+tPpSBCwyX5c9uc8LzWRHu FDltY91SlgbGI4KSHWw1jE4QwSi/kPqW4kbhxKt8HPoQ6WmgVl9PIw== =aBl+ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Solved Re: GRUB question
On Sun, 5 Feb 2006 15:14:39 -0500 Curt Howland [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ah, appended directly to the boot line. Thank you. Since LILO has a separate section called append, it wasn't clear where or how this variable was passed to the kernel. Many thanks, I'll give it a trySuccess! Curt- It works like this ... until the next kernel-image upgrade ;) If you add it to defoptions as suggested then it will be kept on upgrades. Read the explanations inside and man 'update-grub' for more info. Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Debian Sarge Grub Question!
Dear: Fellow Debian Users; First a little hardware information: Tyan 2460 Tiger Motherboard. actual order of physical devices. /dev/hdc dedicated windows XP pro harddrive 40 gig. /dev/hdd dedicated Debian Gnu/Linux harddrive 120 gig. Grub is installed in the MBR of /dev/hdd. I have /dev/hdd setup in the bios as first harddrive to boot, which now acts like this, /dev/hdd/, /dev/hdc. Grub sees this as (hd0) (hd1) which is reverse as to physical installation. If I run update-grub it writes the physical location to menu.lst I then have to change all kernel configs to the opposite of physical, in grubs case from (hd1) to (hd0). This works great and I am able to boot into Debian. But it will not boot into Windows, even if I use the proper grub root device. Windows does not boot, but will stop, and I have to physically reset the machine. Now after reading some docs I tried to use the map command like this: map (hd0) (hd1) map (hd1) hd0) This is done at the command line in grub at first boot, then it will boot into windows like normal. I can also add the lines if I edit the windows stanza and will work within the boot sequence. But if I add it to my grub menu.lst under the Windows title it will not boot windows. Something like this, Title Windows map (hd0) (hd1) map (hd1) (hd0) root (hd1,0) makeactive chainloader +1 Now in order to boot into windows, I have to at boot time add the map lines under the command line, then boot into windows as normal, or hit esc, then highlight the windows stanza and hit return. How can I set this up in grubs menu.lst so it is done automatically? I have also tried to use map function outside any title area as a global setting, but it does not work either. Also would this be considered a bug, and should I submit a bug report if their is no way to set map function in menu.lst. Thanks, Rthoreau -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB question
On Sat, Apr 05, 2003 at 11:55:13PM -0700, Linux wrote: Could someone using Debian 3 please post the contents of /boot/grub/menu.lst for me to take a look at? Try the command: update-grub, it generates a menu.lst for ya. Greetings, Roman -- www: http://www.romanofski.de email: [EMAIL PROTECTED] pgp0.pgp Description: PGP signature
Re: GRUB question
Linux wrote: Greetings all. I've been with Linux for a few years, but trying Debian for the first time. I'm having a bit of a problem getting GRUB set up, and I know it's my fault Could someone using Debian 3 please post the contents of /boot/grub/menu.lst for me to take a look at? Thank you very much Skippi timeout 10 default 0 title Debian GNU/Linux 3.0 kernel 2.4.18 kernel (hd0,0)/vmlinuz root=/dev/hda1 hdc=ide-scsi title Windows 98 rootnoverify (hd0,3) makeactive chainloader +1
GRUB question - book2
book2 so the other thread isn't hijacked. What are the pros/cons of usin Grub vs Lilo? Lilo vs Grub? I have had great success with SystemCommander+PartitionCommander (not free and not expensive). Tried using lilo the other day with no issues. Tried switching over to grub with apt-get install grub and had to redo the harddrive. Any tips on using grub? Key deciding factor for me is no dependancy on an installed OS that is normally under use. _commander installs in its own 40meg partition at the front of the disk. -- = = Management is doing things right; leadership is doing the = = right things.- Peter Drucker= =___= = http://www.sun.com/service/sunps/jdc/javacenter.pdf = = www.sun.com | www.javasoft.com | http://wwws.sun.com/sunone = = -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB question - book2
On Sun, Apr 06, 2003 at 09:32:53AM -0500, Hanasaki JiJi wrote: book2 so the other thread isn't hijacked. What are the pros/cons of usin Grub vs Lilo? Lilo vs Grub? I have had great success with SystemCommander+PartitionCommander (not free and not expensive). Tried using lilo the other day with no issues. Tried switching over to grub with apt-get install grub and had to redo the harddrive. redo the harddrive i hope you dont mean reinstall? however much you fsck the bootsector you should still be able to boot from a floppy and sort it? Any tips on using grub? RTM make sure you have the relevant stage 1,1.5,2 vim /etc/boot/grub/menu.1st (not menu.lst as i thought it was when trying to seup grub!) and set how you like. if grub-install doesnt work, use setup from the grub shell. Key deciding factor for me is no dependancy on an installed OS that is normally under use. _commander installs in its own 40meg partition at the front of the disk. yeah, you could stick a grub floppy in a windows box and boot windows from it... wouldnt be much point but it would work. hugh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB question - book2
On Sun, 06 Apr 2003 09:32:53 -0500 Hanasaki JiJi [EMAIL PROTECTED] wrote: What are the pros/cons of usin Grub vs Lilo? Lilo vs Grub? I have *one* floppy disk with grub on it; I can use it to boot any Windows machine, any Linux machine, BSD machines, or OS/2 machines. You can't do that with lilo. I use kernel-package to build kernels. When I install or remove one of my kernels, update-grub is run to update my grub boot menu. I'm not limited to two kernels as I would be with lilo. Any tips on using grub? Go here for an excellent tutorial on using grub: http://www.linuxjournal.com/article.php?sid=4622 After you have grub installed on your hard drive and have made a grub boot floppy, run update-grub to generate a grub boot menu file. Read it carefully. Follow the instructions to customize it. Then run update-grub again. Kevin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
GRUB question
Greetings all. I've been with Linux for a few years, but trying Debian for the first time. I'm having a bit of a problem getting GRUB set up, and I know it's my fault. Could someone using Debian 3 please post the contents of /boot/grub/menu.lst for me to take a look at? Thank you very much. Skippi - Skippi On The Fly Photography http://204EastSouth.com Meditation -- Yoga -- Linux -- Muffins The Secrets of Life -BEGIN GEEK CODE BLOCK- Version: 3.12 GAT d-(?) s: a C++ L++(+++) P E- W++ !N o? K- w--- o@ M+ PS+ PE++ Y+ PGP- t++@ 5+++ X++ R+ tv-- b++ DI D+ G e+ h+ r- y++ --END GEEK CODE BLOCK-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB question
On Sun, 2003-04-06 at 01:55, Linux wrote: Greetings all. I've been with Linux for a few years, but trying Debian for the first time. I'm having a bit of a problem getting GRUB set up, and I know it's my fault. Could someone using Debian 3 please post the contents of /boot/grub/menu.lst for me to take a look at? use grub-install /dev/hd? and update-grub then go in and edit your menu.lst file. -- Scott Henson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub question - please help
also sprach Shyamal Prasad [EMAIL PROTECTED] [2002.12.07.2040 +0100]: martin -- Please do not CC me! Get a proper mailer instead: martin www.mutt.org He has a proper mailer. It's called hotmail.com ;-) consider yourself spanked! ;^ -- Please do not CC me! Get a proper mailer instead: www.mutt.org .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, and user `. `'` `- Debian - when you have better things to do than fixing a system NOTE: The public PGP keyservers are broken! Get my key here: http://people.debian.org/~madduck/gpg/330c4a75.asc msg17713/pgp0.pgp Description: PGP signature
Re: grub question - please help
also sprach Bruce Park [EMAIL PROTECTED] [2002.12.07.0046 +0100]: vmlinuz-2.4.18-bf2.4 resides in /boot vmlinuz resides in / but is a symlink to /boot/vmlinuz-2.4.18-bf2.4 so where possibly can kernel 2.4.-18-3 come from? also: please do not CC me on list replies! -- Please do not CC me! Get a proper mailer instead: www.mutt.org .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, and user `. `'` `- Debian - when you have better things to do than fixing a system NOTE: The public PGP keyservers are broken! Get my key here: http://people.debian.org/~madduck/gpg/330c4a75.asc msg17591/pgp0.pgp Description: PGP signature
Re: grub question - please help
Bruce == Bruce Park [EMAIL PROTECTED] writes: The leading '/' on the vmlinuz kernel name was probably his problem. Bruce OK, I edited the it to: Bruce kernel vmlinuz-2.4.18-bf2.4 root=/dev/hda4 ro Sorry, I mis-spoke. Bruce which results in: Error 1: Filename must be either an Bruce absolute pathanme or blocklist Bruce On my system: bash$ ls -l /boot | grep Bruce 'vmlinuz' -rw-r--r-- root root ... vmlinuz-2.4.18-bf2.4 Bruce I still can't solve this problem. When you get the grub boot screen hit the 'c' key. You should get a 'grub' prompt from the grub shell. Now set your grub root to your boot partition. Your mail has lost references, so I can no longer find your original post, but perhaps you have to type something like 'root (hd0,1)' if your /boot partition is on /dev/hda2. Press enter and grub should tell you what type of file system is on /dev/hda2 (or whatever you selected). Now type 'kernel /' and hit the tab key. See what it says. If it does not list vmlinuz-2.4.18-bf2.4 then look for the right kernel name. Go ahead and fill out the root and ro parameters. Hit enter. Then boot. I'm sorry if I'm not helping much hereI've lost track since I can't find your original post. Best regards, Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub question - please help
martin == martin f krafft martin writes: martin -- Please do not CC me! Get a proper mailer instead: martin www.mutt.org He has a proper mailer. It's called hotmail.com ;-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub question - SOVLED
Shyamal, Thanks to your help I finally figured out what was wrong. menu.lst was correct after all. title Linux root (hd0,1) kernel /vmlinuz-2.4.18-bf2.4 root=/dev/hda4 ro My boot partition was NEVER redone when I installed Debian. When I was installing Debian, I assumed that when Lilo was configured, it took care of the the boot partition. This was the problem. After mounting /dev/hda2, I looked at it and realized that this was from Redhat linux. I deleted everything and copied the correct directories and files from /boot. Thanks Shyamal. If you didn't tell me to go into grub shell at boot, I may never have figured this out. bp From: Shyamal Prasad [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: grub question - please help Date: 07 Dec 2002 13:37:27 -0600 Bruce == Bruce Park [EMAIL PROTECTED] writes: The leading '/' on the vmlinuz kernel name was probably his problem. Bruce OK, I edited the it to: Bruce kernel vmlinuz-2.4.18-bf2.4 root=/dev/hda4 ro Sorry, I mis-spoke. Bruce which results in: Error 1: Filename must be either an Bruce absolute pathanme or blocklist Bruce On my system: bash$ ls -l /boot | grep Bruce 'vmlinuz' -rw-r--r-- root root ... vmlinuz-2.4.18-bf2.4 Bruce I still can't solve this problem. When you get the grub boot screen hit the 'c' key. You should get a 'grub' prompt from the grub shell. Now set your grub root to your boot partition. Your mail has lost references, so I can no longer find your original post, but perhaps you have to type something like 'root (hd0,1)' if your /boot partition is on /dev/hda2. Press enter and grub should tell you what type of file system is on /dev/hda2 (or whatever you selected). Now type 'kernel /' and hit the tab key. See what it says. If it does not list vmlinuz-2.4.18-bf2.4 then look for the right kernel name. Go ahead and fill out the root and ro parameters. Hit enter. Then boot. I'm sorry if I'm not helping much hereI've lost track since I can't find your original post. Best regards, Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] _ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub question - please help
Bruce Park was roused into action on 2002-12-06 00:47 and wrote: Hello folks, I'm having a difficult time loading the linux partition in grub. I'm going to do the best that I can to explain what I understand and what I don't. I'm currenty using 2.4.-18-bf2.4 kernel. I am also using a floppy to test this. I have NOT loaded this into the MBR. Instead, the Lilo is in the MBR. My partition consits of: hd0,0 /dev/hda1WindowsNTFS hd0,1 /dev/hda2bootext2 hd0,2. /dev/hda3Swap Swap hd0,3 /dev/hda4Linux root ext3 Now, I got the Windows part down but I cannot get the linux part. I'm going to add line numbers to make this easier to read. Here's what I have so far: You've got the hardest part out of the way then... :) 1 title Linux 2 # load the boot partition to Grub 3 root (hd0,1) 4 load the kernel 5 kernel /vmlinuz root=/dev/hda4 ro 6 # this DOES NOT WORK 7 # kernel /vmlinuz-2.4.18-bf2.4 root=/dev/hda4 ro You probably want to comment out line 5 and uncomment line 7. And then add the following as line 8: initrd /initrd.img-2.4.18-bf2.4 Come to think of it, the leading '/' should probably be dropped for both. Of course the initrd image should exist as well... (I'm not even sure how you're booting a 2.4.x kernel without it, though it has been a long time since I set all this up and so I may be a little hazy on it now). You can also try absolute paths rather than relative ones; eg: kernel (hd0,1)/vmlinuz-2.4.18-bf2.4 root=/dev/hda4 ro initrd (hd0,1)/initrd.img-2.4.18-bf2.4 btw, what is Line 4 doing? -- David P. James 4th Year Economics Student Queen's University Kingston, Ontario http://members.rogers.com/dpjames/ The bureaucratic mentality is the only constant in the universe. -Dr. Leonard McCoy, Star Trek IV -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub question - please help
also sprach Bruce Park [EMAIL PROTECTED] [2002.12.06.0647 +0100]: X because kernel 2.4.-18-3 is running instead of 2.4.18-bf2.4. When I edit ^ can you find the corresponding kernel file on the harddrive? -- .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, and user `. `'` `- Debian - when you have better things to do than fixing a system NOTE: The public PGP keyservers are broken! Get my key here: http://people.debian.org/~madduck/gpg/330c4a75.asc msg17517/pgp0.pgp Description: PGP signature
Re: grub question - please help
Martin, vmlinuz-2.4.18-bf2.4 resides in /boot vmlinuz resides in / but is a symlink to /boot/vmlinuz-2.4.18-bf2.4 bp From: martin f krafft [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: grub question - please help Date: Fri, 6 Dec 2002 23:03:20 +0100 also sprach Bruce Park [EMAIL PROTECTED] [2002.12.06.0647 +0100]: X because kernel 2.4.-18-3 is running instead of 2.4.18-bf2.4. When I edit ^ can you find the corresponding kernel file on the harddrive? -- .''`. martin f. krafft [EMAIL PROTECTED] : :' :proud Debian developer, admin, and user `. `'` `- Debian - when you have better things to do than fixing a system NOTE: The public PGP keyservers are broken! Get my key here: http://people.debian.org/~madduck/gpg/330c4a75.asc attach3 _ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub question - please help
David == David P James David writes: David initrd /initrd.img-2.4.18-bf2.4 David Come to think of it, the leading '/' should probably be David dropped for both. The bf2.4 kernel does not use an initrd image unlike the other 2.4.18 kernel packages. So the poster does not need this. I too made the mistake of assuming there was an initrd file with bf2.4 recently. The leading '/' on the vmlinuz kernel name was probably his problem. David You can also try absolute paths rather than relative ones; David eg: David kernel (hd0,1)/vmlinuz-2.4.18-bf2.4 root=/dev/hda4 ro David initrd (hd0,1)/initrd.img-2.4.18-bf2.4 Yup, and going one step further, she/he could experiment and find the best option by getting to the grub prompt and using the 'find' command or otherwise interactively attempting to boot the system until it worked ;-) Cheers! Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub question - please help
From: Shyamal Prasad [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: grub question - please help Date: 06 Dec 2002 18:33:09 -0600 David == David P James David writes: David initrd /initrd.img-2.4.18-bf2.4 David Come to think of it, the leading '/' should probably be David dropped for both. The bf2.4 kernel does not use an initrd image unlike the other 2.4.18 kernel packages. So the poster does not need this. I too made the mistake of assuming there was an initrd file with bf2.4 recently. Hmm., that's interesting. The leading '/' on the vmlinuz kernel name was probably his problem. OK, I edited the it to: kernel vmlinuz-2.4.18-bf2.4 root=/dev/hda4 ro which results in: Error 1: Filename must be either an absolute pathanme or blocklist On my system: bash$ ls -l /boot | grep 'vmlinuz' -rw-r--r-- root root some other info vmlinuz-2.4.18-bf2.4 I still can't solve this problem. David You can also try absolute paths rather than relative ones; David eg: David kernel (hd0,1)/vmlinuz-2.4.18-bf2.4 root=/dev/hda4 ro David initrd (hd0,1)/initrd.img-2.4.18-bf2.4 Yup, and going one step further, she/he could experiment and find the best option by getting to the grub prompt and using the 'find' command or otherwise interactively attempting to boot the system until it worked ;-) Cheers! Shyamal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] _ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
grub question - please help
Hello folks, I'm having a difficult time loading the linux partition in grub. I'm going to do the best that I can to explain what I understand and what I don't. I'm currenty using 2.4.-18-bf2.4 kernel. I am also using a floppy to test this. I have NOT loaded this into the MBR. Instead, the Lilo is in the MBR. My partition consits of: hd0,0 /dev/hda1WindowsNTFS hd0,1 /dev/hda2bootext2 hd0,2. /dev/hda3Swap Swap hd0,3 /dev/hda4Linux root ext3 Now, I got the Windows part down but I cannot get the linux part. I'm going to add line numbers to make this easier to read. Here's what I have so far: 1 title Linux 2 # load the boot partition to Grub 3 root (hd0,1) 4 load the kernel 5 kernel /vmlinuz root=/dev/hda4 ro 6 # this DOES NOT WORK 7 # kernel /vmlinuz-2.4.18-bf2.4 root=/dev/hda4 ro Line 3 loads the boot partition into GRUB's root partition. In the boot partition there is NO kernel vmlinuz. There is ONLY vmlinuz-2.4.18-bf2.4. For ex: bash$ ls -l /boot | grep 'vmlinuz' -rw-r--r-- 1 rootroot not important vmlinuz-2.4.18-bf2.4 File vmlinuz exists at the Linux root partition. I did NOT load hd0,3 into Grub's root. bash$ ls -l / | grep 'vmlinuz' lrwxrwxrwx 1 rootroot not important vmlinuz-/boot/vmlinuz-2.4.18-bf2.4 If vmlinuz doesn't exist in the boot partition, why does that work? When I run this, it actually is executed but runs the WRONG kernel. I cannot start X because kernel 2.4.-18-3 is running instead of 2.4.18-bf2.4. When I edit line 5 to line 7, Grub states that the file cannot be found. Can someone please help me? bp _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: grub question - please help
Try line 7 without the leading /: kernel vmlinuz-2.4.18-bf2.4 root=/dev/hda4 ro The vmlinuz in / is just a symlink to the real file and is not needed. On Fri, Dec 06, 2002 at 12:47:48AM -0500, Bruce Park wrote: Hello folks, I'm having a difficult time loading the linux partition in grub. I'm going to do the best that I can to explain what I understand and what I don't. I'm currenty using 2.4.-18-bf2.4 kernel. I am also using a floppy to test this. I have NOT loaded this into the MBR. Instead, the Lilo is in the MBR. My partition consits of: hd0,0 /dev/hda1WindowsNTFS hd0,1 /dev/hda2bootext2 hd0,2. /dev/hda3Swap Swap hd0,3 /dev/hda4Linux root ext3 Now, I got the Windows part down but I cannot get the linux part. I'm going to add line numbers to make this easier to read. Here's what I have so far: 1 title Linux 2 # load the boot partition to Grub 3 root (hd0,1) 4 load the kernel 5 kernel /vmlinuz root=/dev/hda4 ro 6 # this DOES NOT WORK 7 # kernel /vmlinuz-2.4.18-bf2.4 root=/dev/hda4 ro Line 3 loads the boot partition into GRUB's root partition. In the boot partition there is NO kernel vmlinuz. There is ONLY vmlinuz-2.4.18-bf2.4. For ex: bash$ ls -l /boot | grep 'vmlinuz' -rw-r--r-- 1 rootroot not important vmlinuz-2.4.18-bf2.4 File vmlinuz exists at the Linux root partition. I did NOT load hd0,3 into Grub's root. bash$ ls -l / | grep 'vmlinuz' lrwxrwxrwx 1 rootroot not important vmlinuz-/boot/vmlinuz-2.4.18-bf2.4 If vmlinuz doesn't exist in the boot partition, why does that work? When I run this, it actually is executed but runs the WRONG kernel. I cannot start X because kernel 2.4.-18-3 is running instead of 2.4.18-bf2.4. When I edit line 5 to line 7, Grub states that the file cannot be found. Can someone please help me? bp -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB question
On Mon, May 13, 2002 at 11:25:03PM -0400, Allan Wind wrote: On 2002-05-13 23:11:43, Scott Henson wrote: I am trying to install grub on my system so I can try out the GNU/HURD, but I cant seem to get grub to install properly on my system. I can get grub to boot and everything. I can even boot into all my OSes, but I cant get it to show me a menu. My menu.1st file is attached. Did you actually save it as menu.1st (menu dot one st) instead of menu.lst (menu dot l s t)? It took me a couple of tries to figure out that you have to store it in /boot/grub/menu.lst. Curiously enough, with the proper invocation to install, GRUB will use /boot/grub/menu.1st. I should know ... $ ls /boot/grub device.map e2fs_stage1_5 fat_stage1_5 ffs_stage1_5 jfs_stage1_5 menu.1st minix_stage1_5 reiserfs_stage1_5 stage1 stage2 vstafs_stage1_5 xfs_stage1_5 No wonder setup never worked *g*. It's a bad choice of name, as l I and 1 are easy to misread (and most other files seem to have a 1 in the name...). Wonder why they didn't just use menu? -- Eric G. Miller egm2@jps.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB question
Here's a related question: does anyone know if there is a grub graphic available for Debian? Redhat's looks pretty cool, and Debian just has the text menu. The image goes in /boot/grub and is a .xpm.gz file. -- Nick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB question
On Tue, 2002-05-14 at 06:42, [EMAIL PROTECTED] wrote: Here's a related question: does anyone know if there is a grub graphic available for Debian? Redhat's looks pretty cool, and Debian just has the text menu. The image goes in /boot/grub and is a .xpm.gz file. Look for a thread about that on debianplanet a couple of weeks ago (should still be on the frontpage though).. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB question
Scott Henson wrote: I am trying to install grub on my system so I can try out the GNU/HURD, but I cant seem to get grub to install properly on my system. I can get grub to boot and everything. I can even boot into all my OSes, but I cant get it to show me a menu. My menu.1st file is attached. I basically pulled this thing out of the grub-doc package. I have tried the grub-install script and install and setup from inside grub. Nothing seems to work. Even though when I do grub setup (hd0) this tells me that it installed fine and everything. But then when I reboot it just gives me the grub command line without any menu. Anyone know how to get grub to give me a menu to boot /vmlinuz, /vmlinuz.old, windows98(not important dont use it anymore), and grub. Thanks -- -Peace kid Scott Henson [EMAIL PROTECTED] God's the ultimate playa, so naturally He's going to have some haters, rapper Ice Cube said. But these haters need to realize that if you mess with the man upstairs, you will get your ass smote. True dat. #sandm's menu.1st file to boot useing grub # By default, boot the first entry. default 0 # Boot automatically after 30 secs. timeout 30 # Fallback to the second entry. fallback 1 #For booting Debian GNU/Linux main title Debian GNU/Linux root = (hd1,0) kernel /vmlinuz hdb=ide-scsi root=/dev/hdc1 # For booting Linux old title Debian GNU/Linux old root = (hd1,0) kernel (hd1,0)/vmlinuz.old root=/dev/hdc1 # For booting the GNU Hurd title Debian GNU/Hurd root (hd1,0) kernel /boot/gnumach.gz root=hd0s1 module /boot/serverboot.gz # For booting Windows NT or Windows95 title Windows 98 root(hd0,0) makeactive chainloader +1 Hi... This is worth a read http://www6.software.ibm.com/developerworks/education/l-grub/l-grub-3-6.html -- Regards Ted Wager Libranet Linux user -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB question
On Mon, May 13, 2002 at 11:42:51PM -0500, [EMAIL PROTECTED] wrote:
The image goes in /boot/grub and is a .xpm.gz file.
I didn't know GRUB supported a graphical menu -- if it really does,
how do I enable it?
andrej
--
echo ${girl_name} /etc/dumpdates
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB question
In muc.lists.debian.user, you wrote: On Mon, May 13, 2002 at 11:42:51PM -0500, [EMAIL PROTECTED] wrote: The image goes in /boot/grub and is a .xpm.gz file. I didn't know GRUB supported a graphical menu -- if it really does, how do I enable it? The graphical stuff requires a patch that was done by somebody at RedHat. It's not in the official release of grub, though I think it's in CVS now. -- Grant Edwards grante Yow! I KAISER ROLL?! What at good is a Kaiser Roll visi.comwithout a little COLE SLAW on the SIDE? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB question
On Redhat, put: splashimage=(hd0,0)/grub/splash.xpm.gz in your /boot/grub/menu.lst and make sure splash.xpm.gz is in that directory. The thing is, I have no idea how the xpm format works. -- Nick On Tue, May 14, 2002 at 10:15:37AM -0100, andrej hocevar wrote: On Mon, May 13, 2002 at 11:42:51PM -0500, [EMAIL PROTECTED] wrote: The image goes in /boot/grub and is a .xpm.gz file. I didn't know GRUB supported a graphical menu -- if it really does, how do I enable it? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB question
A certain other major distro (which I'll leave unnamed, but it starts with an 'R' and rhymes with 'edhat') symlinks /boot/grub/menu.lst to /boot/grub/grub.conf. I suppose it makes the file more obvious for newbies, but it seems more stupid the longer I look at it. -- Nick On Mon, May 13, 2002 at 10:24:10PM -0500, Michael D. Crawford wrote: You wrote: menu.1st It's menu.lst, with a loweracse l, not a 1. dot ell ess tee. Grub rocks. I use it on all my x86 systems. No more failing to boot when I install a new kernel and forget to run lilo. Also I can try out new kernel parameters by just typing them in at boot time from the GRUb command line. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB question
On Tue, May 14, 2002 at 10:15:37AM -0100, andrej hocevar wrote: | On Mon, May 13, 2002 at 11:42:51PM -0500, [EMAIL PROTECTED] wrote: | The image goes in /boot/grub and is a .xpm.gz file. | | I didn't know GRUB supported a graphical menu -- if it really does, | how do I enable it? It allows you to specify a background image to display. Since grub doesn't have all of X built-in it has some limitations on the graphics :-). (VGA-only, IIRC) It's mentioned in the grub docs somewhere (maybe only on the web site or in the mail list archives) -D -- One OS to rule them all, one OS to find them, One OS to bring them all and in the darkness bind them, In the Land of Redmond, where the Shadows lie. GnuPG key : http://dman.ddts.net/~dman/public_key.gpg pgpRNW8BsW9iG.pgp Description: PGP signature
Re: GRUB question
On 14 May 2002, Grant Edwards wrote: In muc.lists.debian.user, you wrote: On Mon, May 13, 2002 at 11:42:51PM -0500, [EMAIL PROTECTED] wrote: The image goes in /boot/grub and is a .xpm.gz file. I didn't know GRUB supported a graphical menu -- if it really does, how do I enable it? The graphical stuff requires a patch that was done by somebody at RedHat. It's not in the official release of grub, though I think it's in CVS now. That's right. The graphical patch just missed 0.92. However, the stuff in CVS should be much better behaved than RedHat's patch, if I hear correctly. You can get GRUB off CVS and use the splashimage command to draw a picture in the background. Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB question
On Tue, May 14, 2002 at 10:54:23AM -0500, [EMAIL PROTECTED] wrote: A certain other major distro (which I'll leave unnamed, but it starts with an 'R' and rhymes with 'edhat') symlinks /boot/grub/menu.lst to /boot/grub/grub.conf. I suppose it makes the file more obvious for newbies, but it seems more stupid the longer I look at it. There's also a link from /etc/grub.conf /etc/grub.conf - ../boot/grub/grub.conf /boot/grub/menu.lst - ./grub.conf -- Grant Edwards [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB question
On Tue, May 14, 2002 at 10:54:23AM -0500, [EMAIL PROTECTED] wrote: | A certain other major distro (which I'll leave unnamed, but it starts | with an 'R' and rhymes with 'edhat') symlinks /boot/grub/menu.lst to | /boot/grub/grub.conf. I suppose it makes the file more obvious for | newbies, but it seems more stupid the longer I look at it. It does, except that I recently learned on the grub list that the upstream changed that too. I think the symlink is left there for us old hands :-). (except that old hands use debian and not, uh, what was that?) -D -- How great is the love the Father has lavished on us, that we should be called children of God! 1 John 3:1 GnuPG key : http://dman.ddts.net/~dman/public_key.gpg pgpmkHzKoOCVv.pgp Description: PGP signature
Re: GRUB question
On Tue, May 14, 2002 at 01:35:37PM -0400, Simon Law wrote: The image goes in /boot/grub and is a .xpm.gz file. I didn't know GRUB supported a graphical menu -- if it really does, how do I enable it? The graphical stuff requires a patch that was done by somebody at RedHat. It's not in the official release of grub, though I think it's in CVS now. That's right. The graphical patch just missed 0.92. However, the stuff in CVS should be much better behaved than RedHat's patch, if I hear correctly. What sort of improvements have been made? -- Grant Edwards [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB question
On Tue, 14 May 2002, Grant Edwards wrote: On Tue, May 14, 2002 at 01:35:37PM -0400, Simon Law wrote: The image goes in /boot/grub and is a .xpm.gz file. I didn't know GRUB supported a graphical menu -- if it really does, how do I enable it? The graphical stuff requires a patch that was done by somebody at RedHat. It's not in the official release of grub, though I think it's in CVS now. That's right. The graphical patch just missed 0.92. However, the stuff in CVS should be much better behaved than RedHat's patch, if I hear correctly. What sort of improvements have been made? There's a pager so that you can see more than a screen-full of text. An improved help system, and better booting. Simon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB question
I ran into that one also. The file should be named menu.lst (lowercase L) not menu.1st (one). Depending on font, it can look practically the same. Bob On Mon, May 13, 2002 at 11:11:43PM -0400, Scott Henson wrote: I am trying to install grub on my system so I can try out the GNU/HURD, but I cant seem to get grub to install properly on my system. I can get grub to boot and everything. I can even boot into all my OSes, but I cant get it to show me a menu. My menu.1st file is attached. I basically pulled this thing out of the grub-doc package. I have tried the grub-install script and install and setup from inside grub. Nothing seems to work. Even though when I do grub setup (hd0) this tells me that it installed fine and everything. But then when I reboot it just gives me the grub command line without any menu. Anyone know how to get grub to give me a menu to boot /vmlinuz, /vmlinuz.old, windows98(not important dont use it anymore), and grub. Thanks -- -Peace kid Scott Henson[EMAIL PROTECTED] God's the ultimate playa, so naturally He's going to have some haters, rapper Ice Cube said. But these haters need to realize that if you mess with the man upstairs, you will get your ass smote. True dat. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
GRUB question
I am trying to install grub on my system so I can try out the GNU/HURD, but I cant seem to get grub to install properly on my system. I can get grub to boot and everything. I can even boot into all my OSes, but I cant get it to show me a menu. My menu.1st file is attached. I basically pulled this thing out of the grub-doc package. I have tried the grub-install script and install and setup from inside grub. Nothing seems to work. Even though when I do grub setup (hd0) this tells me that it installed fine and everything. But then when I reboot it just gives me the grub command line without any menu. Anyone know how to get grub to give me a menu to boot /vmlinuz, /vmlinuz.old, windows98(not important dont use it anymore), and grub. Thanks -- -Peace kid Scott Henson [EMAIL PROTECTED] God's the ultimate playa, so naturally He's going to have some haters, rapper Ice Cube said. But these haters need to realize that if you mess with the man upstairs, you will get your ass smote. True dat. #sandm's menu.1st file to boot useing grub # By default, boot the first entry. default 0 # Boot automatically after 30 secs. timeout 30 # Fallback to the second entry. fallback 1 #For booting Debian GNU/Linux main title Debian GNU/Linux root = (hd1,0) kernel /vmlinuz hdb=ide-scsi root=/dev/hdc1 # For booting Linux old title Debian GNU/Linux old root = (hd1,0) kernel (hd1,0)/vmlinuz.old root=/dev/hdc1 # For booting the GNU Hurd title Debian GNU/Hurd root (hd1,0) kernel /boot/gnumach.gz root=hd0s1 module /boot/serverboot.gz # For booting Windows NT or Windows95 title Windows 98 root(hd0,0) makeactive chainloader +1
Re: GRUB question
You wrote: menu.1st It's menu.lst, with a loweracse l, not a 1. dot ell ess tee. Grub rocks. I use it on all my x86 systems. No more failing to boot when I install a new kernel and forget to run lilo. Also I can try out new kernel parameters by just typing them in at boot time from the GRUb command line. Mike -- Michael D. Crawford GoingWare Inc. - Expert Software Development and Consulting http://www.goingware.com/ [EMAIL PROTECTED] Subscribe to the GoingWare Newsletter at http://www.goingware.com/newsletter/ Tilting at Windmills for a Better Tomorrow. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: GRUB question
On 2002-05-13 23:11:43, Scott Henson wrote: I am trying to install grub on my system so I can try out the GNU/HURD, but I cant seem to get grub to install properly on my system. I can get grub to boot and everything. I can even boot into all my OSes, but I cant get it to show me a menu. My menu.1st file is attached. Did you actually save it as menu.1st (menu dot one st) instead of menu.lst (menu dot l s t)? It took me a couple of tries to figure out that you have to store it in /boot/grub/menu.lst. No clue about the hurd stuff... /Allan -- Allan Wind P.O. Box 2022 Woburn, MA 01888-0022 USA pgpxpct9P2oSS.pgp Description: PGP signature
