On Sun Aug 13 2000 at 16:03, [EMAIL PROTECTED] wrote:
> On Fri, 11 Aug 2000, Tony Nugent wrote:
>
> > So, to be safe, aim to have a small (say, 8-10Mb) partition for
> > /boot/ within the first 1024 cylinders of the hard drive. That way,
> > you are guaranteed that when the system boots, the kernel and initrd
> > boot images are physically located (in /boot/) at the start of the
> > disk.
>
> I observe that some of the linux distribution, they have
> /boot/vmlinuz. But what they actually do is they link /vmlinuz to
> /boot/vmlinuz.
That sounds very much like a slugware thing, yeech. Redhat and
other distributions keep it in /boot/ and specify in /etc/lilo.conf
something like...
image=/boot/vmlinuz-<kernel-version>
> Let says, I have /boot mount to the partiton < 1024
> cylinders, but my / is mount to a partition from let say > 500, so there
> is a possibility that they linux can't boot after I rebuild another
> kernel in / (but I link to /boot which is less that 1024. eg 0-499).
The symlink thing is (IMHO) a stupid waste of time and space. But I
guess lilo knows about symlinks and will correctly map the *real*
location (track/sector/cylinder) of the kernel image file and not
the symlink. [I'm not sure, I've never pushed my luck on this
technicality:-]
Just use /boot/vmlinuz-* in a small partition below cyl 1024 and you
can't go wrong.
> Am I right?
Yep, it's probably a risk doing it with symlinks.
Cheers
Tony
