2.4.9 Kernel Released 290
Justin writes: "Linus is off to Finland for a week or so and released 2.4.9. " Here is the Changelog for those of you interested. Yeah, it's probably gonna be a little crowded for a bit. Please post mirrors in the comments.
Mirror (Score:2, Informative)
Re:Mirror (Score:5, Informative)
This kernel tarball is identical with the ones being distributed from ftp.us.kernel.org (dynamic mirrors), BUT IT DIDN'T HAVE TO BE. A trojaned kernel distributed from a private mirror could compromise any number of systems.
Always check downloaded files from unknown sources.
md5sum:
ftp.us.kernel.org kernel: 8b0f6c18e9c09ca1e5d0bbbed95f7ef2
ecliptik mirror kernel: 8b0f6c18e9c09ca1e5d0bbbed95f7ef2
gpg sigs match, using:
% gpg --verify linux-2.4.9.tar.gz.sign linux-2.4.9.tar.gz
But -- DON'T TAKE MY WORD FOR IT! CHECK THEM YOURSELF.
Re:Mirror (Score:2, Funny)
Also, never trust people on slashdot saying that this unofficial mirror is ok, the md5sums/gpg sigs are identical.. _ALWAYS_ check for yourself!
My Mirror (Score:2, Informative)
my mirror contribution (Score:2)
oh great... (Score:1)
Nice change for Mozilla Users (Score:1)
Been using 2.4.9 for the last hour now. Other than a silly bug b0rking NTFS it works great. Simple fix for NTFS though that somebody else already pointed out on here. The updated emu10k1 driver along with the new emu-tools is just awesome.
The changes to VMA merging make a noticable difference in mozilla; that alone is worth the upgrade.
Side note: this is twice in a row that Linus has posted a kernel with a b0rked build, last time was with the emu10k1 driver as a module, this time good 'ole NTFS. Hope he has a relaxing vacation ;)
drivers/net/rrunner.c looks to be borked. (Score:2, Interesting)
make -C net modules
make[2]: Entering directory `/usr/src/linux-2.4.9/drivers/net'
gcc -D__KERNEL__ -I/usr/src/linux-2.4.9/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -malign-functions=4 -DMODULE -DMODVERSIONS -include
rrunner.c:1241: macro `min' used with only 2 args
rrunner.c:1252: macro `min' used with only 2 args
rrunner.c: In function `rr_dump':
rrunner.c:1241: parse error before `__x'
rrunner.c:1241: `__x' undeclared (first use in this function)
rrunner.c:1241: (Each undeclared identifier is reported only once
rrunner.c:1241: for each function it appears in.)
rrunner.c:1241: `__y' undeclared (first use in this function)
rrunner.c:1252: parse error before `__x'
rrunner.c:1221: warning: `len' might be used uninitialized in this function
make[2]: *** [rrunner.o] Error 1
make[2]: Leaving directory `/usr/src/linux-2.4.9/drivers/net'
make[1]: *** [_modsubdir_net] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.9/drivers'
make: *** [_mod_drivers] Error 2
SB Live! driver fixed (Score:5, Informative)
Re:SB Live! driver fixed (Score:3, Informative)
Re:SB Live! driver fixed (Score:3, Informative)
Re:SB Live! driver fixed (Score:5, Informative)
Alan Cox, for example, tried them out and found they didn't work on some of his machines, so he didn't include the new driver in the -ac patches.
So, it seems they work great for some people but not others. Linus decided to keep them in because the new driver is being maintained, and the old one wasn't - a buggy driver that's being worked on is better than a buggy driver that's being ignored... and the new drivers have much better support for the features of the SBLive.
Anyway, if you upgrade and find that your sound card quits working, you have several choices - revert to your previous working version, or try Alan Cox'es patched version of the kernel (look under
A lot of work is being done right now on getting the VM (Virtual Memory) balanced right. It works great for a lot of people, but depending on the workload, it can start to thrash really bad and swap itself to death. (kswapd will run, taking all the CPU time and making no progress.) If you run into this problem or others, read the documentation on reporting bugs (see the
(If you report bugs on the Linux Kernel Mailing list, be sure to note what kernel you're running and any non-standard changes you've made.)
Oh, and if you are not subscribed to the list and want to be cc'ed on replies, say so at the top of your email.
(I'm not really a kernel developer, yet, but I hack around in the code and read the list, so I know a little about what's going on.)
GN (Score:1, Informative)
Actually a trailing 'x' should be treated in the same fashion as a trailing 's', so it should be Alan Cox'. Sadly too few people are pedantic enough for you ever to see this.
:P
Question (Score:3, Insightful)
Any kernel hackers out there heard whisperings about this?
Re:Question (Score:2)
Linus has put in some changes to make this a bit better, but I don't know if it's fully supported in gdb yet, I haven't seen anything about it on the development list. However, all of the necessary data should be in there. I'ld imagine that this will work better than it used to (I think that the thread to die has it's memory dumped, which should be the same as all of the other threads).
If all else fails, you could use a slightly older version of AC, or work out the patches, I'ld imagine they're not much different.
ChangeLog... (Score:4, Insightful)
- David Miller: undo poll() limit braindamage
This would have helped Bush during the election.
- David Woodhouse: up_and_exit -> complete_and_exit
Up and at'em, Dave!
- me: make return value from do_try_to_free_pages() meaningful
Do try for meaningful return values.
- David Miller: "min()/max()" cleanups. Understands signs and sizes.
Ouch.
- Kevin Fleming: more disks the HPT controller doesn't like
And you have to wonder about this one...
- Ben LaHaise: use down_read, not down_write() in map_user_kiobuf.
We don't change the mappings, we just read them.
Re:ChangeLog... (Score:2)
Blazing Fast Kernel Mirror (Score:4, Informative)
http://linux.pantek.com/resource/kernel/linux-2.4
http://linux.pantek.com/resource/kernel/linux-2.4
http://linux.pantek.com/resource/kernel/patch-2.4
http://linux.pantek.com/resource/kernel/patch-2.4
Happy compiling!
Gah! (Score:1)
Slow down CowBoy ! (Score:2, Funny)
NTFS Updates! =) (Score:2)
(Disclaimer: I'm having my company [legato.com] sponsor Anton's work. ;) )
Re:NTFS Updates! =) (Score:2)
Due to an invalid assumption about putting baces inside macros (specifically, the max() and min() macros, which were changed in 2.4.9) which might be present inside the for() clause (which exists in 3 places in the kernel, 2 of which apply to NTFS code), the NTFS code isn't compiling. I made this patch [ipal.org] to fix it.
Stress-test it! (Score:2, Offtopic)
Is he taking his laptop to Finland... (Score:2, Funny)
Keep 'em comming (Score:4, Funny)
http://kernel.org/mirrors/ [kernel.org]
2.4.9 Changelog [kernel.org]
Wow, 2.4.8 lasted a whole week. [slashdot.org]
Righto.... (Score:4, Funny)
Under control [shoppersplazausa.com]
Re:Righto.... (Score:3, Funny)
NTFS filesystem (Score:2)
Re:NTFS filesystem (Score:4, Informative)
Note that- write support for NTFS is a dangerous, EXPERIMENTAL feature that you have to explicitly select in the kernel configuration. Until recently, it was almost certain to destroy your disk, and it is still not recommended although rumor has it that it "mostly works now".
If you blew up an NT partition running in the "read only" mode, send in a bug report to the mailing list. If you want to experiment with write support, send in bug reports for that too, I'm sure the developer will be interested, but don't expect a lot of sympathy if you wipe out important data.
There's often a good reason why "EXPERIMENTAL" features are called that, even though sometimes it seems political - reiserfs, for example, is pretty safe - reported problems with it usually turn out to be hardware failures.
Re:NTFS filesystem (Score:1)
Re:NTFS filesystem (Score:2, Informative)
Problems in the write support are less serious, because they are not on by default and the developers know about them anyway.
I suspect the original poster was using the experimental write support. That used to be so bad that it probably should not have been in the kernel at all, but started getting better around 2.4.5 or so - search the LKML archives for "PATCH" and "NTFS" for details.
NTFS read-only works fine on my dual-boot machine, btw.
Re:NTFS filesystem (Score:3, Insightful)
Bug in NTFS compilation (Score:3, Interesting)
#include <linux/kernel.h>
Re:NTFS filesystem (Score:1)
This is not a bright thing to do... a journaling filesystem of this type does not guarantee against data loss, it only guarantees against internal inconsistency -- meaning that when you reset, you may lose recent data and you may also find some files that are "corrupted" (i.e. seem to contain data from other files). The only thing ReiserFS buys you (relative to ext2) is a guarantee that file or metadata corruption won't spread after the reboot, without needing a time-consuming fsck to get such a guarantee.
Re:NTFS filesystem (Score:4, Interesting)
You can fix this by editing "/usr/src/linux/fs/ntfs/unistr.h" and adding the following at line 30:
#include <linux/kernel.h>
and then recompiling. I've not bothered to submit an official patch... there's probably dozens already.
mozilla help? (Score:2)
Can anyone with the know-how explain what this means?
Cheers.
Re:mozilla help? (Score:2, Informative)
2.4.x changed the way that vma's were merged. VMA's being the sections of virtual memory that you malloc. Mozilla (I'm guessing) has fairly fine-grained memory handling, so it malloc()'s and free()'s often, making for _lots_ of vma's.
The changes in 2.4.9 make contiginous (sp?) vma's merged into one, speeding up walking the list of vma's. Note that previous versions did this already, but only in very few (easy) cases. This change is a bit more 'expensive', but has made a noticable difference in mozilla for me. These changes could also help out lots of other programs that handle memory similarly (can't think of others atm though).
All in All.. i like ;)
Disclaimer: this is my understanding, but as I'm not Rik Van Riel, I'm probably talking out my ass
Is kerneli still being maintained? (Score:2, Interesting)
FreshMeat (Score:4, Funny)
STFU. When a kernel is released, I want to know about it. and who in their right mind looks at freshmeat every fucking day? NOBODY
So what is the point in starting a bitch session just to bitch? To waste Bandwidth? To blow time at your job? GIME A BREAK!
Now I can update my linux boxen tonight, and have a piece of mind that the IDE driver wasnt working correctly in 2.4.7 for me, is noted in the changelog as being fixed.
have a nice day
Re:FreshMeat (Score:5, Funny)
*me* whistles and taps toe while looking around the room quitely...
Re:FreshMeat (Score:1)
When you have problems with a current kernel you look at any resource which can help you.
If there's no problem with your kernel you don't need to upgrade.
Freshmeat can send you a mail on new releases (Score:2, Informative)
Shameless plug: Or you could subscribe to some [freshmeat.net] of [freshmeat.net] my [freshmeat.net] projects :-).
Cheers //Johan
Yet Another Mirror (Score:2, Informative)
ftp://ftp.wingnet.net/pub/linux/kernel/2.4.9/
All the standard files for 2.4.9 from kernel.org (bz2, gz, signatures, etc.) are there. Just the 2.4.9 though - no older stuff. Have at it!
wholy crap! (Score:2)
Re:wholy crap! (Score:3, Funny)
That's because they typically deny a bug's existence for a couple of months before they get around to fixing it.
Jay (=
I can't wait until XFS is standard... (Score:5, Interesting)
XFS (especially when combined with LVM) is great. No fscks, big files, ACLs, and you can grow a mounted file system (great with LVM and hot-swap drives).
Rescue floppys for XFS ? (Score:1)
Re:I can't wait until XFS is standard... (Score:3, Informative)
-adnans
Re:I can't wait until XFS is standard... (Score:3, Informative)
I like the fact that growing an XFS volume to take up more space is simple, and does not require unmounting the volume (in fact, you CANNOT grow an unmounted XFS volume, you MUST mount it first).
So, in a system with hot-swap drive bays, you can add a physical volume to the logical volume group, and just tell XFS to grow. Presto - more space.
I also like the fact that you can move the journal over to another block device. If "you feel the need, the need for speed" you can use a 10MB SCSI battery-backed up SRAM drive for the journal, and a big RAID array for the main storage. Speed and safety in one.
Re:I can't wait until XFS is standard... (Score:1)
> take up more space is simple, and does not
> require unmounting the volume (in fact, you
> CANNOT grow an unmounted XFS volume, you MUST
> mount it first).
FWIW, ReiserFS can do this too. That is, allow you to grow the filesystem while it is still mounted.
ReiserFS even goes a step further by allowing you to shrink the fileystem too. But you have to unmount said filesystem first to shrink it.
However, XFS is a full fledged journalling filesystem while Reiser just journals metadata.
- Arcadio
Re:I can't wait until XFS is standard... (Score:2)
Re:10MB SCSI battery-backed up SRAM drive? (Score:2)
http://www.buymemory.com/mr35.htm
These things aren't cheap, but they aren't marketed toward your average Joe. However, if I ever get the cash to get a Firewire camcorder, I'd want to do my video editing on a journaled system with the journal on something like this.
Gigbabyte Mirror Bandwidth (Score:4, Funny)
This mirror is so fast, it will speed your downloads up, even past your NIC/modem's supposed maximums.
Re:Gigbabyte Mirror Bandwidth (Score:5, Funny)
pcmcia-cs is broken with 2.4.9 (Score:3, Informative)
looks like some dangerous changes were made: I see errors that say macro 'min' used with only 2 args. this kinda scares me...
as I've not had much luck with wireless support inside the kernel tree, I've taken to using hinds' pkg instead. so for those who use pcmcia, perhaps wait for the next release..
Real news: glibc-2.2.4 was released today (Score:5, Informative)
Don't forget that the libc is just as important for your computers stability as the kernel. Most applications go trough the libc to access kernel services. Today glibc-2.2.4 was released, go to your local mirror (yes, that is a gnu mirror, not a kernel mirror) and do the upgrade now.
Slashdot: News for nerds ?
Why does the libc get so little publicity compared to the kernel ? I don't get it !
Re:Real news: glibc-2.2.4 was released today (Score:1)
Re:Real news: glibc-2.2.4 was released today (Score:3, Funny)
Because it has no charismatic leader. And many people are simply afraid to upgrade it (more so than the kernel).
Re:Real news: glibc-2.2.4 was released today (Score:5, Informative)
Enjoy
But glibc-2.2.4 is allergic to gcc-3.0 (Score:2)
*** This version of GNU libc cannot be compiled by GCC 3.x.
*** GCC 3.x will generate a library that is binary incompatible to
*** older and future releases of GNU libc.
*** You should compile this GNU libc release by an older GCC version
*** or wait for the next GNU libc release.
*** If you really mean to use GCC 3.x, run configure again
*** using the extra parameter `--disable-sanity-checks'.
Kernel Compilation Project? (Score:2)
Release early, release often (Score:3, Insightful)
Has anyone observed the GCC development? People say that Red Hat did a good thing by releasing a development snapshot as 2.96 (altho I dont agree with the version number, I agree with the release).
If a kernel patchlevel (remember v Major.Minor.Patchlevel?) breaks your application, then I am led to believe that your application is very poorly programmed...
Re:Release early, release often (Score:1)
I can't understand how that could possibly be correct. If the kernel changes and your program relies on the kernel, and your program breaks, the program is poorly written?
If something is tweaked in a patchlevel release that breaks a subtle nuance that you were relying on, it might be because that nuance was never meant to be there in the first place. A great example of this is a patchlevel release of Checkpoint Firewall-1 a short while ago that changed a very subtle behaviour that a friend of mine was relying on. The behaviour was not correct, but that's the way the software worked, so that's how he had things set up. When Checkpoint "fixed" it, his rules were broken.
With the sheer amount of code present in the kernel, it would strike me as very odd if some of these "features" don't exist.
meisenstRe:The problem with frequent kernel releases (Score:3, Insightful)
The only kernel releases that should break applications are the major and minor releases (not the patch/bugfix releases). If you have an app that works with 2.4.7 (for example) and breaks with 2.4.8 then either your app is broken or it's a driver issue where the maintainer fucked up. Which seemed to be what happened to me with Q3A and the SB Live! drivers in 2.4.8. Although I'm not certain wether it's an issue with the drivers or Q3A.
The patch level releases fix bugs. Sometimes serious bugs. So you should be greatful that they come out as fast as they do. The minor releases (2.2-2.4) only come out every couple of years so I would hardly consider that "Too fast! OMG I can't keep up!".
</rant>
--
Garett
Re:Please don't get me wrong (Score:2)
They might, except knowledge of the SP (let alone the changes) implies a knowledge of proprietary intellectual knowledge, and you must have code ultra-violet m$ clearance to even think about pondering its existence.
-CrackElf
Re:Please don't get me wrong (Score:2)
No, but there should be. That's important information to a large percentage of Slashdot readers.
In case you hadn't noticed, Linux is pretty popular around here.
Re:Please don't get me wrong (Score:1)
Re:Please don't get me wrong (Score:1)
Yes, /. is linux-centric. Yes I run linux and I like it.
If it wasn't, it wouldn't be my start page.
Re:Please don't get me wrong (Score:1)
Re:Please don't get me wrong (Score:1)
Nobody on slashdot wants to know when Microsoft releases a SP because they probably don't run Windows 2000, and plus when Microsoft releases a Service pack everyone seems to know..look at that patch for code red.
These are newsworthy stories, a 0.01 change in version number is not.
WindowsMe wasn't news worthy and there was a 0.01 change in it.
Re:Please don't get me wrong (Score:1)
It's not just the damn fact that the kernel is released that I care about, it's knowing that here on Slashdot people will discuss various problems/solutions or whatever about the kernel. How much is discusses about the NTFS support at freshmeat? Very little. Sure, the kernel mailing lists might be a good place to get kernel information also, but sometimes that's a hack job. Slashdot is fine.
Re:Please don't get me wrong (Score:2, Insightful)
It is interesting (Score:2)
People, I can only say one thing: try to be more open towards people and things that are different from what you might like or value. It is not up to you to judge whether they are right or wrong. They have to come to that conclusion by themselves.
Re:It is interesting (Score:2, Flamebait)
Re:Please don't get me wrong (Score:1)
Try and think before you post next time.
Re:2 compilation errors already (Score:1)
to work fine. I get the same compilation problem with unistr.c:
gcc -D__KERNEL__ -I/usr/src/linux-2.4.9/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -march=i586 -DNTFS_VERSION=\"1.1.16\" -c -o unistr.o unistr.c
unistr.c: In function `ntfs_collate_names':
unistr.c:99: warning: implicit declaration of function `min'
unistr.c:99: parse error before `unsigned'
unistr.c:99: parse error before `)'
unistr.c:97: warning: `c1' might be used uninitialized in this function
unistr.c: At top level:
unistr.c:118: parse error before `if'
unistr.c:123: warning: type defaults to `int' in declaration of `c1'
unistr.c:123: `name1' undeclared here (not in a function)
unistr.c:123: warning: data definition has no type or storage class
unistr.c:124: parse error before `if'
make[3]: *** [unistr.o] Error 1
make[3]: Leaving directory `/usr/src/linux-2.4.9/fs/ntfs'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux-2.4.9/fs/ntfs'
make[1]: *** [_subdir_ntfs] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.9/fs'
make: *** [_dir_fs] Error 2
Re:2 compilation errors already (Score:2, Funny)
it still doesn't explain/correct the Alpha/pc_keyb.c problem tough !!
Re:NTFS problem... (Score:1)
#include <linux/kernel.h>
and then recompile.
Re:NTFS problem... (Score:1)
Re:NTFS problem... (Score:2)
I made a patch [ipal.org] to fix that.
Re:NTFS problem... (Score:1)
Re:NTFS problem... (Score:2)
- not upgrading at all (do you really need the newest spiffiest kernel?)
- upgrade only after there was some discussion, so you'll be warned about trouble
- wait for the first patches, see if they fix the things you need
- wait for a precompiled kernel (say as rpm) for your distribution
If you want the newest Kernel from kernel.org the day it comes out you're expected to keep your old kernel so you can use that if the newest stuff don't work, and that you take a glance at the compile logs and use that option if something comes up you can't handle.
You don't need to edit "the friggin source code", it's an option. If that newest MS-Stuff breaks you're without that option, you have to roll back (if you can). Since users with the level of knowledge you hint at, are probably relying on their distribution for precompiled kernels i don't see your problem.
Re:NTFS problem... (Score:2)
The max() and min() macros have been changed throughout the kernel to now use 3 arguments instead of 2. The new argument is the first, which is the type for the temporary variables used. This avoids problems with multiple references to data. Usually those get compiled out, but with variables of type volatile, they do not. But in since cases you don't want multiple fetches from volatile variables. The problem here is that the max() macro has one instance and the min() macro has two instances of being used inside the for() clause. Simply changing back to the 2 argument usage won't fix it because the macro is defined for 3. My patch [ipal.org] just changes the 3 affected uses back to conventional C code.
Re:how many kernels realeased a year? (Score:4, Insightful)
1) The new one has fixed a bug in something you are using. Such as a new USB driver for your widget.
2) A major security flaw is patched. Which is done way faster (and more publicily) than in most commerical settings.
3) You enjoy cutting your teeth on new shit. Which would be a lot of us.
I personally usually only upgrade if there is a dangerous remote exploit or for some functionaility. I only upgraded to 2.4.x for iptables and firewire support. Even though the backport of firewire worked fine for me.
Re:how many kernels realeased a year? (Score:1)
Re:how many kernels realeased a year? (Score:5, Informative)
1994 - 10 (1.0.0 - 1.0.9)
1995 - 14 (1.2.0 - 1.2.13)
1996 - 28 (2.0.0 - 2.0.27)
1997 - 6 (2.0.28 - 2.0.33)
1998 - 3 (2.0.34 - 2.0.36)
1999 - 2/14 (2.0.37 - 2.0.28 & 2.2.0 - 2.2.13)
2000 - 5 (2.2.14 - 2.2.18)
2001 - 1/1/10 (2.0.39 & 2.2.19 & 2.4.0 - 2.4.9)
avg number of kernels per year: 11.75
The benefit is that you can have the latest and greatest version now instead of six months from now.
Re:how many kernels realeased a year? (Score:2)
Re:how many kernels realeased a year? (Score:3, Informative)
Re:Help, I can't keep up!!! (Score:1)
Re:Firewire???????? (Score:1)
Re:What will the next 2.4 revision be called? (Score:1)
Probably the geek high council will not release any stable updates but will release unstable ones instead like 2.5, and that will go on until 2.6. I wonder how many years it took kernel 2.2 to go to 2.4?
Re:What will the next 2.4 revision be called? (Score:1)
Re:What will the next 2.4 revision be called? (Score:1)
Re:What will the next 2.4 revision be called? (Score:1)
Re:What will the next 2.4 revision be called? (Score:2)
Re:What will the next 2.4 revision be called? (Score:2, Informative)
Because I had been overly optimistic in the naming of version 0.95, I was caught in a bind. Over the course of the two years it took to get version 1.0 out the door, we were forced to do some crazy things with numbers. There waren't many numbers between 95 and 100, but we continually released new versions based on bug fixes or added functions. By the time we got to version 0.99, we had to start adding numbers to indicate patch levels, and then we relied on the alphabet. At one point we had version 0.99, patch level 15A. Then version 0.99, patch level 15B, and so on. We made it all the way to patch level 15Z. Patch level 16 became version 1.0, the point where it was usable. This was released in March 1994 with great fanfare at the University of Helsinki Computer Sciences Department auditorium.
I never saw anything wrong with version X.YYY, IE: version 0.100, 0.101, 2.4.634, etc...
Re:I really hate... (Score:1, Troll)
Re:Another kernel update? (Score:1)
He would be arrested in the USA (Score:1)
Re:Fat FS fixes & CD Updates (Score:1)
What I was *trying* to say is that the sources are generally well documented. Knowing that the IDE/CD stuff was changed, it's quite simple to look at the commentary at the top of /usr/src/linux/drivers/ide/ide-cd.c to see what was done. If you want to make it really easy on yourself you could download the patch and search through the diff text.