What about rebooting to start using the new kernel ?
On Thu, 2003-01-23 at 23:53, Jesse Keating wrote:
> On Thu, 23 Jan 2003 14:46:50 -0800
> "Jerry Roy" <[EMAIL PROTECTED]> wrote:
>
> >
> > If I do a Kernel update to RedHat 8.0 via the "up2date" utility, is
> > there anything else I have to do
On Fri, 2003-01-24 at 08:16, Jerry Roy wrote:
> Hi All,
>
> If I do a Kernel update to RedHat 8.0 via the "up2date" utility, is there anything
>else I have to do once the .rpm's are downloaded and installed?
If you use nvidia drivers, you will have to recompile them, and if you
use vmware, you wi
On Thu, 23 Jan 2003 14:46:50 -0800
"Jerry Roy" <[EMAIL PROTECTED]> wrote:
>
> If I do a Kernel update to RedHat 8.0 via the "up2date" utility, is
> there anything else I have to do once the .rpm's are downloaded and
> installed?
Not if you use grub.
--
Jesse Keating RHCE MCSE
For Web Services
On Tue, 24 Dec 2002, Joe Betts wrote:
> After updating and rebooting the system, GRUB no longer works. The
> system goes through the boot process and then halts with the word 'GRUB'
> displayed on the screen. The system will not go any further.
Can't confirm it. For me, it worked (though, can
Evaluating security issues are hard for me, I readily admit. The more I learn about
security the less I know.
The alert was about local users being able to start a denial of service attack on a
local box. None of our local
users are (I hope!) savvy enough to do such a thing, but like you I always
me thinks security issues is good reason ;-)
That said... up2date doesn't replace the kernel, so you can look what is
broken and try to repair it.
If you cannot fix it, kick your supplier in his *ss to provide a newer
version of the drivers... the only reason to update a kernel is
security, and thi
Charles:
Thank you for the response. Fortunately, my momma taught me good! I do
still have the earlier kernel and am booting to that. As for upgrading the
krenel, when RedHat says there's a known security flaw (or two) and the
upgrade is intended to fix them, isn't that sufficient reason to do
Hey, listen to your momma! *Never* (did I say *never*) *ever* (did I say *never*
*ever*)
update your kernel, or allow up2date to update your kernel, without a good reason,
especially for binaries that are compiled against a particular kernel. This almost
always (in my humble opinion and limited
On Wed, 2002-11-13 at 13:35, [EMAIL PROTECTED] wrote:
[snip]
> >If you have compiled / installed display drivers (nvidia for example)
> >they may be working with one kernel, but not with the other. This could
> >cause some performance problems.
> Me compile drivers? I can't compile my own first na
> >After updating kernel, we usually reboot. This often gives the wrong
> >impression that a problem was caused by the kernel change. Frequently
> >the problem is unrelated, and is just noticed because of the reboot.
[snip]
>If you have compiled / installed display drivers (nvidia for example)
>t
On Wed, 2002-11-13 at 07:32, [EMAIL PROTECTED] wrote:
> On 12 November 2002 nbecker said:
>
> >After updating kernel, we usually reboot. This often gives the wrong
> >impression that a problem was caused by the kernel change. Frequently
> >the problem is unrelated, and is just noticed because of
On 12 November 2002 nbecker said:
>After updating kernel, we usually reboot. This often gives the wrong
>impression that a problem was caused by the kernel change. Frequently
>the problem is unrelated, and is just noticed because of the reboot.
But when you have both kernels on the same machine
After updating kernel, we usually reboot. This often gives the wrong
impression that a problem was caused by the kernel change. Frequently
the problem is unrelated, and is just noticed because of the reboot.
--
Psyche-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/list
13 matches
Mail list logo
