Slashdot Mirror
Kernel 2.5.3 Released
cybercyst writes: "You know the drill... Lets go hit those servers!" As usual, see kernel.org for the download or the changelog. Anyone using 2.5 for anything except testing?
← Back to Stories (view on slashdot.org)
← Back to Stories (view on slashdot.org)
final:
- Doug Ledford: i810 audio driver update
- Evgeniy Polyakov: update various SCSI drivers to new locking
- David Howells: syscall latency improvement, try 2
- Francois Romieu: dscc4 driver update
- Patrick Mochel: driver model fixes
- Andrew Morton: clean up a few details in ext3 inode initialization
- Pete Wyckoff: make x86 machine check print out right address..
- Hans Reiser: reiserfs update
- Richard Gooch: devfs update
- Greg KH: USB updates
- Dave Jones: PNPBIOS
- Nathan Scott: extended attributes
- Corey Minyard: clean up zlib duplication (triplication..)
pre6:
- Asit Mallick: mtrr update
- Patrick Mochel: split up kernel/device.c into drivers/base
- Mikael Pettersson/Al Viro: fix missing in-core inode initialization
in ext2 introduced by Al's inode trimming
- David Miller: sparc and network updates
- Frank Davis: firewire video mmap page remapping fix
- me: fix configure help scripts to fix breakage noticed by Dave Jones
- Greg KH: USB updates
- Kai Germaschewski: ISDN fixes, Config.help entries
- Douglas Gilbert: SCSI doc update
- Ingo Molnar: x86 taskswitch optimizations, scheduler updates
- Mikael Pettersson: make APIC work on old external setups
- Al Viro: more inode trimming
pre5:
- Patrick Mochel: devicefs locking cleanups, refcount fixes
- Brian Gerst: apic timer cleanup
- Adam Richter: fix loop over block device bio breakage, ipfwadm compile fix
- me: split up Configure.help over the subdirectories where it is used
- Peter Anvin: bootproto v2.03
- Jeff Garzik: net driver updates
- NIIBE Yutaka: SuperH update
pre4:
- Patrick Mochel: initcall levels
- Patrick Mochel: devicefs updates, add PCI devices into the hierarchy
- Denis Oliver Kropp: neomagic fb driver
- David Miller: sparc64 and network updates
- Kai Mäkisara: scsi tape update
- Al Viro: more inode trimming, VFS cleanup
- Greg KH: USB update - proper urb allocations
- Eric Raymond: kdev_t updates for fb devices
pre3:
- Al Viro: VFS inode allocation moved down to filesystem, trim inodes
- Greg KH: USB update, hotplug documentation
- Kai Germaschewski: ISDN update
- Ingo Molnar: scheduler tweaking ("J2")
- Arnaldo: emu10k kdev_t updates
- Ben Collins: firewire updates
- Björn Wesen: cris arch update
- Hal Duston: ps2esdi driver bio/kdev_t fixes
- Jean Tourrilhes: move wireless drivers into drivers/net/wireless,
update wireless API #1
- Richard Gooch: devfs race fix
- OGAWA Hirofumi: FATFS update
pre2:
- David Howells: abtract out "current->need_resched" as "need_resched()"
- Frank Davis: ide-tape update for bio
- various: header file fixups
- Jens Axboe: fix up bio/ide/highmem issues
- Kai Germaschewski: ISDN update
- Greg KH: USB and Compaq PCI hotplug updates
- Tim Waugh: parport update
pre1:
- Al Viro: fix up silly problem in swapfile filp cleanups in 2.5.2
- Tachino Nobuhiro: fix another error return for swapfile filp code
- Robert Love: merge some of Ingo's scheduler fixes
- David Miller: networking, sparc and some scsi driver fixes
- Tim Waugh: parport update
- OGAWA Hirofumi: fatfs cleanups and bugfixes
- Roland Dreier: fix vsscanf buglets.
- Ben LaHaise: include file cleanup
- Andre Hedrick: IDE taskfile update
free (as in mp3s) electronic music
Use The Mirrors, Luke!
Please refrain from flooding kernel.org every damn time you post that a new kernel is released. You should link directly to the list of mirrors. As has been said before, anyone who would even venture on compiling and using something like this could easily find the appropriate folder on an FTP mirror from which to download the new source.
That is all.
- Eric Krout
If you celebrate Xmas, befriend me (538
As a regular Slashdot reader, and avid FreeBSD user, I really really find these announcements to be useless spam. I can't turn off the LINUX category because there is interesting stuff there, but it is really necessary to annouce each DEVELOPMENT kernel? I can see announcing a new stable release, or a release with some really serious changes... But this is a bit excessive.
Maybe *you* don't consider the single most successful open source software releasing a new microrev to be news, but... it is. Maybe when it's a bit down the pipe, nobody'll care all that much, but Lord knows, I'm interested. And not to compile, either: 2.5.x is *w-a-y* too unstable for any except thems that want to watch machines crash-n-burn, but it's the first true development kernel we've had in ages, and (IMH, somewhat nerdy, opinion) exciting to see what goes in. *blam* Block devices broken... but only to fix 'em even better with nifty abstraction layers. *blam* CML (well, not yet, but *some day). *blam* You get the idea. Don't care? THEN DON'T READ IT. Sheesh.
Did I miss anything?
python -c "x='python -c %sx=%s; print x%%(chr(34),repr(x),chr(34))%s'; print x%(chr(34),repr(x),chr(34))"
Because Linux development is don't in public in front of everyone, The unstable portion of Windows development is done behind closed doors and not seen by the public (given Windows past tendancy to crash when sneezed on it's arguable that some portion is really done in public).
That's the difference between open source and closed source - you get to see the stuff as it's being developed and if you want you can get involved and do some yourself. On the other hand if you only want to use the stable versions stick with the even numbered releases (2.0, 2.2, 2.4).