> Here is fdisk -l: > > [root@k5di ~]# fdisk -l > > Disk /dev/sda: 160.0 GB, 160041885696 bytes > 255 heads, 63 sectors/track, 19457 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > > Device Boot Start End Blocks Id System > /dev/sda1 1 140 1124518+ 82 Linux swap / Solaris > /dev/sda2 141 1360 9799650 83 Linux > /dev/sda3 1361 1970 4899825 83 Linux > /dev/sda4 1971 19457 140464327+ 5 Extended > /dev/sda5 1971 7071 40973751 83 Linux > /dev/sda6 7072 7085 112423+ 83 Linux > /dev/sda7 7086 8961 15068938+ 83 Linux > /dev/sda8 8962 9587 5028313+ 83 Linux > > Disk /dev/sdf: 160.0 GB, 160041885696 bytes > 255 heads, 63 sectors/track, 19457 cylinders > Units = cylinders of 16065 * 512 = 8225280 bytes > > Device Boot Start End Blocks Id System > /dev/sdf1 1 1000 8032468+ 7 HPFS/NTFS > [root@k5di ~]# > > > You want to know what is where: The main part is at /dev/sda5 and if > I ever get it right the /boot will be at /dev/sda6. > > -- > > Karl F. Larsen, AKA K5DI > Linux User > #450462 http://counter.li.org. > This is from grub's manual online. 11.2 How to specify files There are two ways to specify files, by absolute file name and by block list. An absolute file name resembles a Unix absolute file name, using `/' for the directory separator (not `\' as in DOS). One example is `(hd0,0)/boot/grub/menu.lst'. This means the file /boot/grub/menu.lst in the first partition of the first hard disk. If you omit the device name in an absolute file name, GRUB uses GRUB's root device implicitly. So if you set the root device to, say, `(hd1,0)' by the command root (see root), then /boot/kernel is the same as (hd1,0)/boot/kernel. Can't offer any more than that for now. Got to run. Jacques
