some people do not want to upgrade their distribution because it will mean a
lot of work
updating their scripts. and to move from 2.0.x to 2.2.x you need to upgrade a
lot ...
it took me for instance, a lot of time to upgrade my server from 2.0.36 (rh5.2)
to 2.2.x (rh6.1)
Also,
Oden [EMAIL PROTECTED]
To: [EMAIL PROTECTED] [EMAIL PROTECTED]
Cc: Moran [EMAIL PROTECTED]; ILUG [EMAIL PROTECTED]
Date: éåí ùðé 13 ãöîáø 1999 18:29
Subject: Re: [Fwd: [BUGTRAQ] Big problem on 2.0.x?]
some people do not want to upgrade their distribution because it will
mean a
lot of work
1999 21:24
Subject: Re: [Fwd: [BUGTRAQ] Big problem on 2.0.x?]
The answer is download.xs4all.nl:/pub/mirror/redhat-updates
- yba
On Fri, 10 Dec 1999, James Olin Oden wrote:
What are you talking about?
RH contrib? Some other site where you can get kernels
packaged as RPMs?
We're
Hi Moran,
Moran wrote:
Date: Wed, 1 Jan 1997 08:01:24 +0200
...
who use 2.0.X this days.
just upgrade to 2.2.13 kernel.
And who uses ancient dates these days? And even before Y2K hits us ;-)
Just upgrade your date to Sun Dec 12 19:56:05 IST 1999...
BTW: The same problem is known (for
1999 21:24
Subject: Re: [Fwd: [BUGTRAQ] Big problem on 2.0.x?]
The answer is download.xs4all.nl:/pub/mirror/redhat-updates
- yba
On Fri, 10 Dec 1999, James Olin Oden wrote:
What are you talking about?
RH contrib? Some other site where you can get kernels
packaged
What are you talking about?
RH contrib? Some other site where you can get kernels
packaged as RPMs?
We're talking about an enterprise environment here,
OFFICIAL RH errata. Whether or not this is the right
way to go, this is where people look.
Why don't you head on over to
This was posted to BugTraq today, and it seemed
important enough to pass on (even though if you are
a sysadmin and do not regularly read BT, you might
deserve what you get).
It's what I'd call a HUGE problem, not
merely a big problem (unless of course you have
no local users). In any case, I'd
It fixed long time ago on kernel 2.0.38
Hetz
Omer wrote:
This was posted to BugTraq today, and it seemed
important enough to pass on (even though if you are
a sysadmin and do not regularly read BT, you might
deserve what you get).
It's what I'd call a HUGE problem, not
merely a big
On Fri, Dec 10, 1999, Omer wrote about "[Fwd: [BUGTRAQ] Big problem on 2.0.x?]":
This was posted to BugTraq today, and it seemed
important enough to pass on (even though if you are
a sysadmin and do not regularly read BT, you might
deserve what you get).
It's what I'd call a HU
Irrelevant.
Most people will not upgrade the kernel on their own
to the latest stable version, but rather would only
upgrade using the official vendor errata. This is how
it is for all of the big-time operating systems, and
since Linux is poised to make it to the big time, you
have to expect
Well, if YOU CHECK you will find that there are RPM's for kernel 2.0.38
for redhat 5.x - compiled and ready.
Just rpm -Uvh kernel-2.0.38(whatever the name is) and thats it..
Hetz
Omer wrote:
Irrelevant.
Most people will not upgrade the kernel on their own
to the latest stable version,
, the bt post was not completely
accurate - in the middle of a huge db sweep).
BTW, no kidding, it's called a DoS attack? I never
heard of those *cough* :)
Nadav Har'El wrote:
On Fri, Dec 10, 1999, Omer wrote about "[Fwd: [BUGTRAQ] Big problem on 2.0.x?]":
This was posted to Bug
12 matches
Mail list logo
