Gustin Johnson wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Ralf Mardorf wrote: > <snip> > >> In /dev/disk you can see what the drive is named by id or label. Maybe >> using sdb1 is the problem, eg. sometimes sdb needs to be called hdb, if >> it's a IDE drive. You should use the id or the label. You can set a >> > > Not anymore, on recent kernels with up to date userspace utilities PATA > drives are also named /dev/sdX >
That's why I wrote "sometimes", Suse e.g. is using such a kernel module that IDE drives calls sdx. >> label by using tune2fs or you simply use the id, that always is there >> and the same for each distro. >> > > You can use the UUID, ID, or the partition label. Look in > /dev/disk/by-uuid or /dev/disk/by-id respectively. tune2fs -L <label> > <device> sets the label. man tune2fs should get you the info you need. > It's easier to see which partition is the wanted partition, when using the id instead of the UUID, because of the given names ;). >> I attached my /boot/grub/menu.lst as an example for different types of >> entries. >> >> > Most menu.lst files will not need to be that complicated. The grub > documentation can be found here: > http://www.gnu.org/software/grub/manual/ > That's true, but my menu.lst shows a lot of possibilities. I guess the problem is that title Zenwalk root (hd1,1) kernel /boot/sdb1/vmlinuz initrd /boot/sdb1/initrd.splash savedefault is nonsense, because there might be no folder /sdb1 inside the folder /boot. _______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
