Anne,
To your last question..."yes". The vmlinuz file is the kernel. You now
have two specific kernel files vmlinuz-2.4.18-6mdk on the hde6 /boot
partition and vmlinuz-2.4.19-16mdk on the hdf1 /boot partition. Vmlinuz
is a generic link that will work with the existing lilo.conf file.
That's why you have the line in lilo.conf
image=/boot/vmlinuz
You could instead have a line
image=/boot/vmlinuz-2.4.19-16mdk
The initrd files are RAM disk images that hold modules that must be
loaded to the kernel on startup but the construct is the same, the links
used in the same way, etc.
The problem is that you have two different /boot directories on
different drives. It would be better to move the specific vmlinuz and
initrd images to hde6 /boot and then amend your lilo.conf file to look
something like this
<snip>
default=Mandrake-9 (if that is what you want as default)
<snip,snip>
image=/boot/vmlinuz-2.4.19-16mdk
label=Mandrake-9
root=/dev/hdf1
initrd=/boot/initrd-2.4.19-16mdk
append <etc.>
image=/boot/vmlinuz-2.4.18-6mdk
label=Mandrake-8.2
root=/dev/hde6
initrd=/boot/initrd-2.4.18-6mdk
append <etc.>
<the next stanza is for failsafe. If you're going to use 9.0 use the 9.0
vmlinuz and initrd filenames. Leave everything else as is.>
The last two stanzas (windows and floppy) don't depend on your linux
kernel.
Terry Smith
Cape Cod USA
On Tue, 2002-11-19 at 14:43, Anne Wilson wrote:
> John is telling me that I need to specifically tell the bootup which img and
> initrd versions I'm using. I understand his point, but before I do that I
> would like to understand a little better just what is happening here.
>
> In the directory that has the 8.2 boot, subdirectory /boot, I have
> initrd-2.4.18-6mdk.img (size 218,650) and one that has an icon looking like a
> link, called initrd.img which is also 218,650 long. In the directory with
> the 9.0 boot there is a similar pair of files, relating to 2.4.19-16mdk. If
> I open them in an editor and scan the first few lines (I haven't done more
> than that) the pairs look identical. Are they? Are they interchangeable -
> they would have to be, I guess, to do as John suggests. Are they there for
> just this situation?
>
> There are similar pairs for vmlinuz - so I expect the answer will be the same
> for these. But why is one of each pair looking like a link? How are these
> files actually used at bootup?
>
> Anne
>
> On Tuesday 19 Nov 2002 10:40 am, John Richard Smith wrote:
> > Anne Wilson wrote:
> > >On Tuesday 19 Nov 2002 1:41 am, Terry Smith wrote:
> > >image=/boot/vmlinuz
> >
> > should be image=/boot/vmlinuz-2.4.18-6mdk
> >
> > > label=Mandrake_8.2
> > >
> > > root=/dev/hde6
> > > initrd=/boot/initrd.img
> >
> > should be initrd=/boot/initrd-2.4.18-6mdk.img
> >
> > > append="nobiospmp devfs=mount hdc=ide-scsi"
> > > vga=normal
> > > read-only
>
> >
> > You are not telling the system which kernel and initrd file to use, and
> > it's best to
> > define both kernels and initrd files for both Mandrake OS , even though
> > it has booted
> > one OS on the one ill defined version.
> >
> > When you get used to this you can download other peoples amended
> > kernel versions and install them in /boot partition, and write a new stanza
> > to boot on it, without removing anything of the old setup, that way you
> > can test
> > things out easily.
> >
> > John
>
>
> ----
>
> Want to buy your Pack or Services from MandrakeSoft?
> Go to http://www.mandrakestore.com
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
