IPX and install to large hard drive
I remember hearing that some of the older Sun machines could only boot from the first GB of the disk. Is there any need to have a separate partition at the beginning of the disk for /boot with the kernels and silo in it? Installation was smooth. The only problem came when I was asked to choose the hostname. ;) I did make a 16MB partition starting at offset 0 for /boot, and silo didn't want to find the kernel image on reboot.
Re: IPX and install to large hard drive
On Sun, May 14, 2000 at 01:44:05AM -0700, [EMAIL PROTECTED] wrote: I remember hearing that some of the older Sun machines could only boot from the first GB of the disk. Is there any need to have a separate partition at the beginning of the disk for /boot with the kernels and silo in it? Installation was smooth. The only problem came when I was asked to choose the hostname. ;) I did make a 16MB partition starting at offset 0 for /boot, and silo didn't want to find the kernel image on reboot. That's because silo has to know the full path of the kernel. If you put silo on part1 (/) and /boot on part2, then silo needs to look for: image=2/vmlinuz-2.2.15 Where 2 is the partition number of the current drive and /vmlinuz-2.2.15 is the path to the image relative to the partition it is on (in this case, it is not in /boot, since that is the partition we are looking on). I'm not sure there is a sane way to handle this in dbootstrap, but I'll take a look. Ben -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---'
Re: IPX and install to large hard drive
Question is, do I even NEED /boot to be seperate? ROM version is 2.6, disk is a 9.1GB. On Sun, 14 May 2000, Ben Collins wrote: On Sun, May 14, 2000 at 01:44:05AM -0700, [EMAIL PROTECTED] wrote: I remember hearing that some of the older Sun machines could only boot from the first GB of the disk. Is there any need to have a separate partition at the beginning of the disk for /boot with the kernels and silo in it? Installation was smooth. The only problem came when I was asked to choose the hostname. ;) I did make a 16MB partition starting at offset 0 for /boot, and silo didn't want to find the kernel image on reboot. That's because silo has to know the full path of the kernel. If you put silo on part1 (/) and /boot on part2, then silo needs to look for: image=2/vmlinuz-2.2.15 Where 2 is the partition number of the current drive and /vmlinuz-2.2.15 is the path to the image relative to the partition it is on (in this case, it is not in /boot, since that is the partition we are looking on). I'm not sure there is a sane way to handle this in dbootstrap, but I'll take a look. H. Need to change the 'partition' option in silo.conf, but then one would need to mangle the 'vmlinuz' symlink into the root of whatever partition that is. Ouch, definately not trivial. Ben -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
