hi ya...
you can already upgrade the kernel w/o rebooting...
went looking for the project name ... but could not find it in my archived
emails
have fun
alvin
On Sat, 15 Sep 2001, dman wrote:
..
> | these machines are around: piper as a modem/fax server, and piper as a
> | print server. work
On Mon, 19 Jan 1998, Joel Klecker wrote:
> Regarding "Updating the kernel via patches" of 5:14 PM +0100 1/19/98,
> [EMAIL PROTECTED] wrote:
> >recently I tried to update my kernel (2.0.30) to version 2.0.33. I
> >used the script patch-kernel (I hope the
Regarding "Updating the kernel via patches" of 5:14 PM +0100 1/19/98,
[EMAIL PROTECTED] wrote:
>recently I tried to update my kernel (2.0.30) to version 2.0.33. I
>used the script patch-kernel (I hope the name is right) and the files
>
> patch-2.0.31.gz
> patch-2.0.
I remember that Carey Evans suggested some time ago downloading the
whole sources for upgrading. Is this the only easy way?
It is certainly the easiest way, and it's what I recommend for people
who are inexperienced at dealing with patches. (However, dealing with
patches is the only way to
Hi,
recently I tried to update my kernel (2.0.30) to version 2.0.33. I
used the script patch-kernel (I hope the name is right) and the files
patch-2.0.31.gz
patch-2.0.32.gz
patch-2.0.33.gz
from sunsite.unc.edu. The update stopped after a short time with an
error message, leaving me at
"Martin Jackson" <[EMAIL PROTECTED]> writes:
> I was wondering if there was anything special I needed to do to upgrade from
> kernel 2.0.30 to kernel 2.0.32 (or 33 if it's available). Red Hat requires
> an "rpm --install" to avoid overwriting the old kernel. Does dpkg require
> this too? I've m
Hello all.
I was wondering if there was anything special I needed to do to upgrade from
kernel 2.0.30 to kernel 2.0.32 (or 33 if it's available). Red Hat requires
an "rpm --install" to avoid overwriting the old kernel. Does dpkg require
this too? I've made an honest effort to read the documenta
7 matches
Mail list logo
