On Sat, Apr 17, 1999 at 02:07:14PM +0200, [EMAIL PROTECTED] wrote:
> If all this is correct so far, what's the point in running lilo to update it?
Because LILO makes reference to the absolute location on disk of the vmlinuz
file (at the far end of the symlink) in the boot code it writes out. Chang
Thanks everyone, I got lilo dual booting the two kernels. I'm having some
trouble since the new kernel does not recognize hdd as a block device, and
therefore I can't mount my iomega zip drive. I've checked both
/boot/config-2.0.35 and /boot/config-2.0.34, and this might be the cause:
# CONFIG_B
Hi,
cd to /etc to edit the file lilo.conf as
original lilo.conf
===
boot=/dev/hdxn
where x = hard disk a or b; n = partition number 1, 2, 3 etc
(could be boot=/dev/hda if you have written the master boot record (MBR) during
your
initial install
Subject: New Kernel install (II)
Date: Sat, Apr 17, 1999 at 02:15:55PM +0200
In reply to:[EMAIL PROTECTED]
Quoting [EMAIL PROTECTED]([EMAIL PROTECTED]):
> I believe it's possible to maintain both kernel and have a dual boot (eg. one
> for kernel-2.0.34 and another
[EMAIL PROTECTED] wrote:
>
> It seems I've finally succeeded into compiling the kernel successfully (cross
> fingers). Now, for installation, I have to:
>
> # cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-2.0.35
> # cp /usr/src/linux/System.map /boot/System.map-2.0.35
--
I believe it's possible to maintain both kernel and have a dual boot (eg. one
for kernel-2.0.34 and another for kernel-2.0.35)... how do I go about this with
lilo?
TIAYA
Horacio
--
Claves - GnuPG/PGP - Keys : http://www.rediris.es/cert/keyserver
o/or
Envía un mensaje vacío a [EMAIL PROTECTED] co
It seems I've finally succeeded into compiling the kernel successfully (cross
fingers). Now, for installation, I have to:
# cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-2.0.35
# cp /usr/src/linux/System.map /boot/System.map-2.0.35
# cp /usr/src/linux/.config /boot/config-2.0.35
Next, r
7 matches
Mail list logo
