Slashdot Mirror
Linux 2.4.3 Released
Joel Rowbottom writes "Kernel 2.4.3 is out, time to thrash those mirrors kids!" Download, Compile, Reboot, Repeat. If anyone has linkage to changelogs or something, please post them in the comments. I've been reliably running 2.4.x on a few boxes and loving it. Both X and my DVD drive both thank the kernel hackers.
Does anybody know what the Automatic Stanford Checker is?
Seems that some guys at Stanford wrote some programs to scan the kernel source for various potential bugs, so that the maintainers could check them out. Here are some examples from Junfeng Yang and Dawson Engler. If you search the LKML archives for "CHECKER", you'll surely find more.
... if it is a slow news day I'd much rather have kernel 0.0.x releases announced than read some review of the latest anime release on DVD, the former which holds little interest for me and the latter which I have been actively boycotting for more than a year now (and I must say in light of the MPAA's implacable attack on Free Software authors and users over the last year, I find it profoundly depressing that a site which claims to be a forum for Free Software news and advocacy will, in effect, promote the products which help to finance such attacks, but that is a rant for another day).
... I would hope such stories would diminish about the time 2.4.11 is being released.
Which just goes to show there are numerous tastes and interests among slashdot readers, some of whome wait breathlessly for the next point release of any software.
More seriously, these announcements are I think more relevant early on in the new kernel cycle as more fundamental fixes are typically included
The Future of Human Evolution: Autonomy
And I just got 2.4.2 running
That, and Kernel 2.4.2 was just so industrial.
Back to the noise.
You say you want a revolution....
Thank you.
bp
-final:
- Kai Germaschewski: Makefile dependency fixes. ISDN update
- Chris Mason: another reiserfs tail writing fix
- unify pte/pmd allocation
- undo some VIA PCI fixups - conflicting behaviour
-pre8:
- Paul Mackerras: PPC update for thread-safe page table handling
- Ingo Molnar: x86 PAE update for thread-safe page table handling
- Jeff Garzik: network driver updates, i810 rng driver, and
"alloc_etherdev()" network driver insert race condition fix.
- David Miller: UltraSparcIII update, network locking fixes
- Al Viro: fix fs counts on mount failure
-pre7:
- more bugs found by the automatic stanford checker, yay!
- Andrew Morton: fix SAK locking bugs by moving it into a process context
- Johannes Erdfelt: USB updates
- Jeff Garzik: merge Hermes driver by David Gibson
- Jens Axboe: cdrom merges, ll_rw_blk proper accounting
-pre6:
- Jeff Garzik: network driver merge
- Andrew Morton: fix missed page_table_lock unlock
- David Miller: Qlogic,FC bufix, page allocation order problem.
-pre5:
- Rik van Riel and others: mm rw-semaphore (ps/top ok when swapping)
- IDE: 256 sectors at a time is legal, but apparently confuses some
drives. Max out at 255 sectors instead.
- Petko Manolov: USB pegasus driver update
- make the boottime memory map printout at least almost readable.
- USB driver updates
- pte_alloc()/pmd_alloc() need page_table_lock.
-pre4:
- Petr Vandrovec, Al Viro: dentry revalidation fixes
- Stephen Tweedie / Manfred Spraul: kswapd and ptrace race
- Neil Brown: nfsd/rpc/raid cleanups and fixes
-pre3:
- Alan Cox: continued merging
- Urban Widmark: smbfs fix (d_add on already hashed dentry - no-no).
- Andrew Morton: 3c59x update
- Jeff Garzik: network driver cleanups and fixes
- Gérard Roudier: sym-ncr drivers update
- Jens Axboe: more loop cleanups and fixes
- David Miller: sparc update, some networking fixes
-pre2:
- Jens Axboe: fix loop device deadlocks
- Greg KH: USB updates
- Alan Cox: continued merging
- Tim Waugh: parport and documentation updates
- Cort Dougan: PowerPC merge
- Jeff Garzik: network driver updates
- Justin Gibbs: new and much improved aic7xxx driver 6.1.5
-pre1:
- Chris Mason: reiserfs, another null bytes bug
- Andrea Arkangeli: make SMP Athlon build
- Alexander Zarochentcev: reiserfs directory fsync SMP locking fix
- Jeff Garzik: PCI network driver updates
- Alan Cox: continue merging
- Ingo Molnar: fix RAID AUTORUN ioctl, scheduling improvements
I ask this because one of the USB ethernet devices he supports (the CATC device) is not, as far as I can tell, included in the 2.4 kernel (although the pegasus USB-ethernet device is, but I'm not sure if that's his or not). Does anyone know why there is this split?
See above for my obligatory Beowulf reference...
-- "I am disrespectful to dirt. Can you not see that I am serious!"
It's a set of extensions to gcc (g++, actually) which can be programmed to look for semantic, rather than syntactic flaws in code, automatically. The theory is that if a class of bug turns up once, it'll probably occur throughout a given codebase. More details at http://hands.stanford.edu/.
It should be noted that 2.2.19 was also just released a few days ago.
The next site to slashdot will be ready soon, but subscribers can beat the rush and start slashdotting it early!
now they are actively merging Alan Cox in to the kernel, so now we'll have one kernel with multiple personality disorder, instead of two with a singular personality disorder
I know he isn't a kernel hacker, but i use KDE as my primary desktop so...
The other day, the games-sig of my local LUG (The Linux Gamers League) held a LAN here in Melbourne. One of the people that turned up, to my surprise at least, was Sirtaj Singh Khan, aka Taj, one of the KDE developers (he wrote KView, along with contributing code to various other parts of the KDE Project).
I took the opportunity there and then to walk up to him, and to thank him for providing me with what (IMHO) is a better desktop system than some of the more commercial efforts out there. (and yes, i know that KDE has it's fair share of bugs, but i don't care. It works for me). He had a lot of interesting things to say about the future of KDE and where he thought that Linux should be going. I could quite happily have given up all the gaming that day, just for the 15-20 minutes that i got to speak with him.
So, yes, if you ever get the opportunity to meet an author of the open source software you use, then say thank you, especially because these guys aren't getting paid to write this stuff.
life is a canvas/and the paint is hope and promise/the world is ours/no one can ever take it from us.
I know adaptec has taken over this driver, but what kind of improvements are in this kernel?
1. Active maintainership by the vendor. The author of the previous driver is no longer maintaining it.
2. More robust. This is not meant as a sleight again Doug. This driver has more bugs fixed. That's the one of the advantages of the previous point.
3. True U160 support. The old driver only worked with some U160 configurations, and didn't support U160 transfers.
4. Shared codebase with FreeBSD. This shouldn't surprise anyone, as Justin is a FreeBSD developer. And before you get your panties in a bunch, please remember that the old driver was a port of Justin's work.
Cat, the other, tastier white meat.
Let's keep to the facts and look at the numbers.
Troll leader Anonymous Coward states that there are 7000 users of "BSD is dying troll". How many users of "Red Hat is dying" are there? Let's see. The number of "BSD is dying" versus "Red Hat is dying" posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 "Red Hat is dying" trolls. "Mandrake is dying" troll on Usenet are about half of the volume of "Red Hat is dying" trolls. Therefore there are about 700 users of "Mandrake is dying" troll. A recent article put "Debian is dying" troll at about 80 percent of the Linux market. Therefore there are (7000+1400+700)*4 = 36400 "Debian is dying" trolls. This is consistent with the number of "Debian is dying" Usenet posts.
Due to the troubles of www.hotgrits.org, abysmal sales and so on, "Debian is dying" troll went out of business and was taken over by "Mandrake is dying" troll who sell another troubled troll.
Major marketing surveys show that "??? is dying" troll has steadily declined in market share. "??? is dying" troll is very sick and its long term survival prospects are very dim. If Linux is to survive at all it will be among troll hobbyists and dilettantes. "??? is dying" troll continue to falter. Nothing short of a miracle could save it at this point in time. For all intents and purposes, "??? is dying" troll is dead.
Get it through you thick head you boring troll!.. It's not funny nor is it fooling anyone.
Cheers... .*shrc is
--
$HOME is where the
$HOME is where the
-- silver_p
http://sig.mine.nu/~jbardin/linux-2.4.3.tar.gz Just try and slashdot me ;)
Jon Bardin
Now I can download a whole new kernel, go through the mess of installing it with weird hardware, and get no new features for what I'm running!
Not to sound too cynical, but excitement over 0.0.1 upgrades is a little silly, considering that lots of people are still happily chugging away with 2.2, and 2.4 won't really help them.
"Titanic was 3hr and 17min long. They could have lost 3hr and 17min from that."
IBM had PL/1, with syntax worse than JOSS,
And everywhere the language went, it was a total loss...
Remember that if you allready have 2.4.0, 2.4.1, or 2.4.2 source, you don't need to download the full tarball, just the patches. Apply in order until your at the current version.
/usr/src /usr/src
cd
gzip -cd patchXX.gz | patch -p0
or
cd
bzip2 -dc patchXX.bz2 | patch -p0
Oh, and access via http seems to be working better than ftp.
I'm going to go back in my box and will think within the limits of my box: MS Sucks Linux Good I read too much Slashdot.