----- Original Message -----
From: Pixel <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, December 21, 1999 10:13 AM
Subject: Re: [Cooker] Cooker glitches - Follow up
> "Hoyt" <[EMAIL PROTECTED]> writes:
> > lilo also failed, with a cylinder too big message. This was probably my
> > fault as I was installing to a partition above 1024 cylinders and did
not
> > provide for a /boot partition below that since I wanted to see what
would
> > happen. Of course, had I been able to make a boot disk, this would not
have
> > ben an issue, but I wanted to see what the install program would do in
this
> > case since larger hard drives are becoming more common.
>
> didn't diskdrake told you you were running into problems?
>
Of course, but I "knew" what I was doing; I just wanted to see what would
happen; your
typical newbie is not too aware of the 1024 cylinder limit and may just have
a large disk.
(I have a 13G hda and 6.4G hdb; hda has 16 partitions - I boot three
different Linux distros,
Win98 and BeOS). Everything would have been fine if I could have made a
bootdisk (I could also use loadlin from DOS/Windows, but I would need a copy
of the kernel that isn't available until after the install. It would be nice
to be able to have the install program copy the kernel to /dev/ha1,
typically the c:\ drive on a dual boot system, or have a copy on the CD - I
know you have -lots_ of space left, but matbe when you get to 2 CDs?).
Perhaps
a specefic warning that lilo _will_ not run successfully if /boot is above
the limit? I recall that the
warning given was pretty general.
But, this was not a cooker problem, just a generic Linux/lilo thing.
Hoyt
