Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
Linux Software

Linux 2.4.18 Released 391

Kourino writes: "Marcelo announced the release of 2.4.18 a couple hours ago after 4 release candidates, but the tree marked 2.4.18 on kernel.org is missing the -rc4 patch that finally made the kernel releasable. Basically, what's marked as 2.4.18 is really -rc3, and what's marked as -rc4 is what should have become 2.4.18. According to Marcelo on #kernelnewbies, most users won't be affected, but people on SPARC systems should definitely grab 2.4.18-rc4. Your best bet is probably just to get 2.4.17 and patch to 2.4.18-rc4. Seems 2.4 is destined to be an "interesting" release branch ^_^; For the new release, head over to your favorite kernel.org mirror. (Marcelo will set things straight in 2.4.19-pre1.)"
This discussion has been archived. No new comments can be posted.

Linux 2.4.18 Released

Comments Filter:
  • by Nailer ( 69468 ) on Monday February 25, 2002 @05:46PM (#3067218)
    You've all heard this before, but that way people who aren't particularly interested in minor kernel revisions but are interested in general Linux stories can filter away the linux kernel topic.
  • amd cache coherency (Score:4, Interesting)

    by theEdgeSMAK ( 467213 ) on Monday February 25, 2002 @05:46PM (#3067223) Homepage
    Has anybody addressed the amd cache coherency bug? I'm still booting with mem=nopentium. That makes me sad.

  • by Bradee-oh! ( 459922 ) on Monday February 25, 2002 @07:27PM (#3067802)
    The only kernel that's ever actually powered down my machine on shutdown or halt is the special 2.4.8 included with my Mandrake distro.

    Has anyone else had this problem and actually fixed it??
  • by N8w8 ( 557943 ) on Monday February 25, 2002 @07:40PM (#3067872)
    I use APM and supply "apm=power-off" as a kernel parameter. Good luck :)
  • by spinlocked ( 462072 ) on Monday February 25, 2002 @09:49PM (#3068371)
    Linux was fantastic when Sun released Solaris 7 - their first 64 bit OS. It meant that you could give a new lease of life to those 'cherished' old SPARCstation 1/2/Classic/LX/10 etc. The reason? Solaris bloat. Solaris has grown up with the Sun hardware range. Versions 7 and 8 have a great deal of code which supports later generation hardware. It's getting pretty difficult to fit it on a 1 gig disk - even a custom install, let alone the 420MB drive which came with my old sparcy2.

    The non-pagable kernel memory used to fit, just about, in 32MB with some to spare for buffer cache (well, 2.5.1 did) . Nowadays it just swaps horribly. Why you ask? the old SPARC workstations don't have much of the hardware which new versions of Solaris provide support for (much of it installed even if you don't have the hardware grr.). Solaris has a mature multithreaded kernel, it has amazingly well tuned, truly scalable, kernel synchronisation primitives (check out the book "Solaris Internels" - Mauro, Mc Dougall) it has in-kernel support for Sun's hardware enterprise features; dynamic reconfiguration (the ability to tell Solaris to stop using memory, CPU or IO devices on a certain system board, drain the memory to swap, re-dispatch the active processes to other CPUs, remap the IP addresses to other cards, detach the board, replace, reattach - start using the new hardware - no reboot), hotplug PCI, processor sets, dynamic system domains etc. etc.

    Decent Sun boxes (by that I mean anything with more that 4MB L2 cache and SCSI disks - a curse on Ultra 5/10/X1/SunBlade 100s), will run Solaris 8 very well, plus you get a tier one Oracle/Sybase/Java platform, with all of your favourite window managers/web browsers/IRC clients etc. available for download.

    Mark my words, once Linux starts making real inroads on the sort of Enterprise server kit (i.e. more than 8 SMP CPUs, and much more than 4gb RAM) that you need for serious financial/HR/government/pharms. type applications , it too will be bloated. You could argue it already is - my 486SX/8MB of RAM gave very good service as a firewall, using ipchains and kernel 2.2. Kernel 2.4 and iptables (and I suppose my new stateful filter) make it rather too slow to survive my next hardware cull. Ah well, out with the old...

Experience varies directly with equipment ruined.