On Sat, Sep 16, 2000 at 10:54:22PM -0500, Mike Meyer wrote:
> I cvsupped and rebuilt earlier to today, only to find that the kernel
> was installed as /boot/kernel/kernel instead of
> /boot/kernel/kernel.ko. While fixing this was trivial, it was a bit of
> a surprise.
>
> Is this a bug, or did I h
In message <[EMAIL PROTECTED]> Mike Meyer writes:
: Is needing to have a new loader installed to boot worth a mention in
: UPDATING?
Nah. People should be forced to puzzle it out for themselves ;-)
Warner
P.S. An entry will be committed shortly.
To Unsubscribe: send mail to [EMAIL PROTECTED
Ben Smithurst writes:
> Mike Meyer wrote:
> > I cvsupped and rebuilt earlier to today, only to find that the kernel
> > was installed as /boot/kernel/kernel instead of
> > /boot/kernel/kernel.ko. While fixing this was trivial, it was a bit of
> > a surprise.
> > Is this a bug, or did I happen to c
Mike Meyer wrote:
> I cvsupped and rebuilt earlier to today, only to find that the kernel
> was installed as /boot/kernel/kernel instead of
> /boot/kernel/kernel.ko. While fixing this was trivial, it was a bit of
> a surprise.
>
> Is this a bug, or did I happen to catch the world in a state of c
I cvsupped and rebuilt earlier to today, only to find that the kernel
was installed as /boot/kernel/kernel instead of
/boot/kernel/kernel.ko. While fixing this was trivial, it was a bit of
a surprise.
Is this a bug, or did I happen to catch the world in a state of change
described in a cvs-all or
