2.4.0 came with 7.1 .. 2.4.10 came with 7.3 (an October 2001 release)
and they did a final release of 2.4.16 about 3 months later. The .10
release was the first release with the new VM (virtual memory) and it
had some pretty major issues. So they banged out the issues and .16 is
the stable release. If you don't wish to upgrade...and don't care about
an increase in preformance..then don't update. You have to understand
that Microsoft and Sun both do kernel updates quite regularly..they come
bundled in the form of service packs and Recommended pkg clusters in
Sun's case. What your seeing with Linux is just more out in the open.
SuSE could release on huge RPM every so often with these updates..but
they and many other distributions do not do this..it's just not how it
works. :)
You have the choice to update what you want..when you want. You don't to
download a 50M compressed file and run a whole patch cluster just for a
few updates. If you were to download the 8_Recommend.zip from Sun it
would be about 50-60M and uncompressed be about 200M. It's just how it
works.
Do what you like..it's your choice. It's the nice thing about Open
Source..the developers and companies put the updates there and if you
choose to not read the list of fixes and choose to just sit tight with
what you have..it's your choice. :)
Cheers!
* Jeffrey Taylor (jeff.taylor@ieee.org) [020210 15:29]:
->I was looking at the kernels in the d2 directory. Why are there
->kernels in two places? What is the rationale for the two different
->series? I tried 2.4.0 because it came on the CDs. Why release a
->kernel that must immediately be upgraded?
->
->Jeffrey
->
->Quoting Ben Rosenberg :
->> * Jeffrey Taylor (jeff.taylor@ieee.org) [020210 07:49]:
->> ->I just reverted a new production machine from the initial install of
->> ->SuSE-2.4.0 to SuSE-2.2.18 and then updated to SuSE-2.2.19. Too much
->> ->did not work. When I have time and a stable machine, I will try again
->> ->to inch up the 2.4 series. Note: I have SuSE 7.1 and 2.4.2 is the
->> ->latest SuSE kernel available for it.
->> ->
->> ->Calling it a stable production release does not make it one. The 2.4
->> ->series has been troublesome.
->>
->> Yes, and using a 1st..out the door revision like 2.4.0 then condemning
->> the 2.4.16 release that came out one year later as not production
->> quality is not very sound logic. You can use whatever release of SuSE
->> you wish but know this..they don't just do . releases to make cash off
->> the public there are fixes for what they produce in those CD's ;)
->>
->> BTW..you might want to keep up on what's in the update directory on the
->> ftp site..did you there like last fall or something? ;)
->>
->> Check here:
->>
->> ftp://ftp.suse.com/pub/suse/i386/update/7.1/kernel/2.4.16
->>
->> You should maybe read the bugfix release.
->>
->> And yes, if Linus releases something as stable it's usually very close
->> to being stable.
->>
->> Cheers! And I hope this helps to get you up with the current stuff.
->>
->> Ben Rosenberg mailto:ben@whack.org
->> "I've never been quarantined. But the more I look around the more I
->> think it might not be a bad thing." -JC
->>
->
->--
->To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com
->For additional commands send e-mail to suse-linux-e-help@suse.com
->Also check the FAQ at http://www.suse.com/support/faq and the
->archives at http://lists.suse.com
->
-----=====-----=====-----=====-----=====-----
Ben Rosenberg mailto:ben@whack.org
-----=====-----=====-----=====-----=====-----
"I've never been quarantined. But the more I look around the more I
think it might not be a bad thing." -JC