On Sat, Jan 08, 2000 at 06:57:39PM -0200, Henrique M Holschuh wrote:
> On Sat, 08 Jan 2000, matt garman wrote:
> > my /etc/lilo.conf, but /vmlinuz is a symlink into /boot, which hadn't
> > been updated to point to the new kernel.
> >
> > I thought when I built a kernel with make-kpkg and installed
On Sat, Jan 08, 2000 at 02:10:10PM -0700, Bob Nielsen wrote:
> I wonder if something is broken here. A few days ago I compiled 2.2.14
> with make-kpkg and installed it. When I rebooted, 2.2.13 came up. As
> I recall, the symlink looked correct, however.
No, now I recall that the symlinks hadn't
I wonder if something is broken here. A few days ago I compiled 2.2.14
with make-kpkg and installed it. When I rebooted, 2.2.13 came up. As
I recall, the symlink looked correct, however.
After I ran lilo 2.2.14 would boot. Previously, this was done as part
of the .deb installation.
Bob
On Sa
On Sat, 08 Jan 2000, matt garman wrote:
> my /etc/lilo.conf, but /vmlinuz is a symlink into /boot, which hadn't
> been updated to point to the new kernel.
>
> I thought when I built a kernel with make-kpkg and installed the
> resulting .deb with dpkg, that either /etc/lilo.conf was updated to see
I was getting a bit of a headache trying to get my new kernel to work,
until I realized the following: I had "image=/vmlinuz" on one line of
my /etc/lilo.conf, but /vmlinuz is a symlink into /boot, which hadn't
been updated to point to the new kernel.
I thought when I built a kernel with make-kp
5 matches
Mail list logo
