I have been using mandrake update for this which
should theoretically be similar to that...
Maybe I will try that next time just to confirm it.
However, I am hoping this info will help debug
mandrake update... which I like what they are trying
to do with it now....
--- michael <[EMAIL PROTECTED]> wrote:
> On Friday 13 April 2001 12:21 am, you wrote:
> > I just upgraded to 17 and had the same problem as
> > always. Since I have been doing it manually (using
> > make install in /usr/src/linux) I have had some
> > bizarre behavior after I first upgrade. Only
> vmlinuz
> > and system.map are properly linked to 17. Config
> was
> > still linked to 16 and initrd was linked to 12
> (having
> > overridden 16). 12 was the version I first had
> this
> > problem with.
>
> I used the rpm and put everything into one dir and
> typed rpm -Uvh
> forced of course and I had no prob's booting. All
> links seem to be good and I
> even have the option of booting the enterprise
> kernel!
> God favors fools sometimes!
> --
> pax
> -m-
>
=====
SI Reasoning
[EMAIL PROTECTED]
gnupg/pgp key id 035213BC
__________________________________________________
Do You Yahoo!?
Get email at your own domain with Yahoo! Mail.
http://personal.mail.yahoo.com/
