Slashdot Mirror
2.4.9 Kernel Released
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.
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.
meisenstGreen's Law of Debate: Anything is possible if you don't know what you're talking about.
"I mean is there a Slahdot article when Microsoft gives out a new Windows 2000 SP? Including the changes and fixes (mirrored in the comments)?"
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
"Blake is an idealist, Jenna. He cannot afford to think." - Kerr Avon, Star One, Blakes 7
Not even Microsoft cooks up that many service packs in this particular timeframe...
:)
That's because they typically deny a bug's existence for a couple of months before they get around to fixing it.
Jay (=
I have seen this problem too -- I _need_ NTFS fer chissakes, and 2.4.7 seemed
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
Just edit "/usr/src/linux/fs/ntfs/unistr.h" and insert this at around line 30:
#include <linux/kernel.h>
and then recompile.
--
Free Dmitry!
http://www.freesklyarov.org
I really don't understand why strong advocates of *nix are so anti MS. Maybe you take a look around and realize that some people don't like, not to mention know how, to edit the friggin source code, before compiling it, to make an upgrade!! this seems ridiculous! If you're gonna release soemthing, make sure it works on all cases. I'm glad I don't have to rewrite MS functions before installing Win2000. jmt
The Digital Couture Collection
Duh. 2.0 was really stable and 2.1 was being heavily worked on. Graph 2.1 in there and you'd get probably 50 or more kernels for that year.
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.
STOP . AMERICA . NOW
I mean is there a Slahdot article when Microsoft gives out a new Windows 2000 SP? Including the changes and fixes (mirrored in the comments)?
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.
Here's a mirror ftp://ecliptik.com/pub/linux-2.4.9.tar.gz
I might also add, that you don't want to fall to far behind the current kernel. A 2.0.36 to 2.4.9 upgrade is apt to be quit a bit more painful than 2.4.6 to 2.4.9. Sometimes, it's easier to bit off a number of small upgrade chunks, raher than one large one. YMMV
http://www.angelfire.com/geek/qdata/index.html
------
Random, useless fact: I type in startx entirely with my left hand.
forgive my ignorance, buy how can it trash the partition running in read-only mode? surely that means it doesn't write and therefore doesn't change anything......
And ofcourse, a slower release rate would also slow the entire development process.
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...
.stnemmoc eht ni srorrim tsop esaelP
ftp://209.203.218.6/pub/kernel/2.4.9 have fun
If you run ./configure in the top of the glibc-2.2.4 source tree on a gcc-3.0 system, it ill abort with the following output:
*** 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'.
If you don't like these kind of stories, you can always remove them with your /. preferences.
A one banana problem.
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
Well the last one was escaped* on the 10th!
Sure. Just enable CONFIG_IEEE1394 in your kernel config. It is listed under "IEEE 1394 (FireWire) support (EXPERIMENTAL)" in the main "make xconfig" menu. I don't know whether your particular drive would work or not, but you can try.
As the 2.4.x kernel series has been headed to higher and higher revision (x) numbers, I've been wondering what will occur when those numbers are exhausted. Seeing as how we're at 2.4.9, will all the next revisions be 2.4.9.x? It's probably way too early for 2.6. --Alex
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?
The next revision will be called 2.4.10, of course :-)
And 2.5 hasn't even been started yet, so yes, it is way to early for 2.6
Judging from what happened with the 1.2.x series, I'm sure the next 2.4 revision will be called 2.4.10, then 2.4.11... you get the picture.
I really hate the "I really hate slashdot is not freshmeat" posts
I usually am happy to hear of a new release (cause I get bored with the last one :), but man this sucks. I just got 2.4.8 working the other day, and now I gotta upgrade again? wowzers
btw, did anybody have problems with the emu10k1 drivers in 2.4.8? It looks like they may have fixed it in 2.4.9 according to the changelog.
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 ;)
Yes, one day I may actually learn to spell...
Okay, that does work. Someone else suggested (and actually I'd done this earlier anyway) removing 'unsigned int' from a for loop declaration (which also removes the compile error). I got the idea by looking at the 2.4.8 code. Is doing that going to be a bad thing with the ntfs updates? Which one is the 'correct' method -- I'm more likely to trust adding the #include line.
STOP MISUSING APOSTROPHES, YOU MORONS!!!
My post, which was intended to be controversial, sure triggers a lot of reaction. In Posters and Moderators. Just looking at the moderation totals is interesting by itself: Moderation Totals:Flamebait=1, Troll=1, Insightful=2, Overrated=1, Total=5. I am, personally, not that this would interest too many people, an advocat of the right OS for the right purpose. I run Win98 at home. I like to PLAY Computer Games like Baldur's Gate (and my wife does), I run Win2k at work (well, company policy) and FreeBSD for my webservers (stable, fast, I like it). And I would love to have information on every OS when I am reading "news for nerds, stuff that matters". Because other Operating Systems than Linux DO matter. Even if you don't like it. And, my quotes from the changelog where meant to stir the discussion (100% success on that one).
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.
Yes, /. is linux-centric. Yes I run linux and I like it.
If it wasn't, it wouldn't be my start page.
Liberty.
please see this post for further info
IIRC, before 2.4.0 they were around 2.3.99
They that quote Benjamin Franklin on liberty and safety deserve neither.
Submitted for amusement, a segment of make modules:
/usr/src/linux-2.4.9/include/linux/modversions.h -c -o rrunner.o rrunner.c
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
It would be called 2.4.10. The latest 2.2 is called 2.2.19
Though not a showstopper by any means, the EMU10K1 driver has been fixed from 2.4.8, and is now fully up-to-date. I've been using the drivers from opensource.creative.com since the release of the 2.4 kernel, and this is definitely a welcome change. Check it out!
Interested in open source engine management for your Subaru?
. When a kernel is released, I want to know about it. and who in their right mind looks at freshmeat every fucking day?
*me* whistles and taps toe while looking around the room quitely...
I count 15 or so since Jan 1 for W2K (minimum, I'm sure there's more)
Hey, does anyone know if they're going to support dumping debugging information for multi-threaded processes into core files? I'm really tired of not being able to post-mortem debug in gdb. I know the errata kernal drops per-pid cores, but that's not like having real core file support.
Any kernel hackers out there heard whisperings about this?
--
What happens when you outlaw guns
I love reading the ChangeLogs. Oftentimes they can be quite humorous:
// min(-400, 3) == 3 // ??
- 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.
I mean is there a Slahdot article when Microsoft gives out a new Windows 2000 SP?
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.
Check out the following blazing-fast mirror:
. 9.tar.gz . 9.tar.gz.sign . 9.gz . 9.gz.sign
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!
I have the same view as him and I did it to see what changes have been made. Looking at it made me realise it was a bit pointless.
Try and think before you post next time.
GNU's site has no mention of this and claims the current version is 2.2.3. Freshmeat had an announcement for glibc-2.2.4-pre4 on Wednesday. Who exactly is releasing this?
> 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).
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
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.
When everybody moves to Windows XP, NTFS will get supported REAL quick.
Bah, I just rebooted my machine TODAY to run 2.4.8 :-p
I made a patch to fix that.
now we need to go OSS in diesel cars
My old 486 computer here still did not finish compiling 2.4.7 ... at this rate, I will never get any work done.
There must be some pretty cool decryption functions in 2.4.9, if he has to go to a free country to release it.
This one is a lot faster. But it is currently a version out.
(Disclaimer: I'm having my company sponsor Anton's work. ;) )
David E. Weekly
Code / Think / Teach / Learn
h4x0r for
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.
What if I mess it all ?
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.
Should have had a mantis saying "BANJO!" in the slash-logo...
Someone set us up the bomb, so shine we are!
>but what is so exciting about:
>- Alan Cox: more driver merges
there was a very nasty bug, since 2.4.3, all VIA MVP3 systems (most of K6-2 users have that motherboard) were heavy slowed down, for example it was impossible to watch movies in mplayer/avifile, that problem was fixed in -ac series (IIRC 2.4.4-ac2)
See if it responds better than Banjo...
sulli
RTFJ.
... or do we have to wait a whole *two weeks* for 2.4.10?
Hey there, I'm currently on the run to catch a train, so I have no time to search the web for the right place to reportbugs, compile errors and the like. So, please bear with me. Here we go: make[3]: Entering directory `/usr/src/linux/fs/ntfs' gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -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/fs/ntfs' make[2]: *** [first_rule] Error 2 make[2]: Leaving directory `/usr/src/linux/fs/ntfs' make[1]: *** [_subdir_ntfs] Error 2 make[1]: Leaving directory `/usr/src/linux/fs' make: *** [_dir_fs] Error 2 This is a vanilla 2.4.9 tree on a SuSE 7.1 system. Please forward this to whereever it belongs and drop me a note (either here or in private mail), so I'll know better for the future. Thanks, Sebastian
http://kernel.org/mirrors/
2.4.9 Changelog
Wow, 2.4.8 lasted a whole week.
This sig intentionally left blank.
There is a developer actively working on NTFS support now. It should be safe for read-only mode.
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.
Torrey Hoffman (Azog)
"HTML needs a rant tag" - Alan Cox
Maybe... could it be that some people don't read freshmeat regularly?!?!?!
They that quote Benjamin Franklin on liberty and safety deserve neither.
Under control
If there's no problem with your kernel you don't need to upgrade.
You really don't understand the nature of addiction...
Special Relativity: The person in the other queue thinks yours is moving faster.
I read somewhere awhile back that Linus wanted to start trying to release newer kernel versions faster than revious. Personnally I like it. It gets things out to the community to test quicker. It really was pretty fast between 2.4.8 and 2.4.9. LIke less than a week I think. amazing.
what?
2.4.9 already!!
NTFS support (read only) seems to be broken completely, so no worries on it blowing up your filesystem this time. It fails to compile either in the kernel or as a module. Of course, it could be something else that I'm doing wrong, often support breaks occur when you have specific features enabled/disabled along with the one you want that won't work.
STOP MISUSING APOSTROPHES, YOU MORONS!!!
According to my numerological calculations, 2.4.10 is very bad luck!
Linus was all for it however I seem to remember some other people (Alan Cox beng one of them) saying its the only recognition they get and so no one implemented it.
There is a patch called the Linux Progress Patch which gives you a graphical startup with a bar and some explanation of what is going on. Its quite pretty and if there is an error the normal messages can be seen on the second console.
...for the Alpha + i386 arch on NTFS (unistr.c) and pc_keyb.c respectively :
personal box (AMD Duron) :
and on the Alpha Server 1000 :
I think it's important because Linux is a community supported software. It truly is software that blongs to you and me - we have all the rights we need to use it in almost any way. Windows is not *our* software - we rent it from Bill. Linus, Alan, Richard and countless others have rolled out a red carpet and have welcomed us - they have given us more than software, but have given us freedom to use our computer in the way we see fit. I'm gratfull to them and people like them - and I like to see what they are up to.
Moneyed corporations, non-working 'poor' and criminal prisoners are turning productive citizens into tax-slaves.
Hmm, I noticed this problem a few versions ago. It worked fine when I removed the wavelan stuff (didn't need it).
Escher was the first MC and Giger invented the HR department.
I think the point here is that while Microsoft can use (better: saturate) pretty much every information channel available to
announce whatever they want to peddle to the unsuspecting crowd, be it service packs and IIS hole-pluggers
or new products, the Linux community has this and couple of other web sites and couple of magazines as their only
venues for announcements and Linux-related information.
So, why should Slashdot give Microsoft an opportunity to do what they can do on ZDnet/C|Net, in 99% of IT rags, not to
mention TV and radio - here?
Actually there was a similar phrase in Linus's book.
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...
Huh? which planet do you come from? ;)
But Seriously, /. is the home of a lot of GNU/Linux nerds/geeks, but also BeOS and *BSD are regularly discussed, just like HURD. If you don't like GNU/Linux, then that isn't a problem, but that doesn't mean you should troll the news that DOES matter to a lot of us. Let us discuss all our latest kernels, and you can go back to BG, and we'll all be happy.
Everything is relative. Win2k SP's may matter to you, but i'm sure the majority of readers won't give a cow...
This sig is intentionally left blank
Because it has no charismatic leader. And many people are simply afraid to upgrade it (more so than the kernel).
now we need to go OSS in diesel cars
WTF! That's now in my favorites! After hitting 1.2MB/sec settled into 775KB/sec. Only prob was that the tar kept going way past 26 mb, just wound up cancelling. Got the bz @ 150KB (not bad!) Must be that KY jelly! Or maybe some Sensa.. I mean Kentucky Bluegrass Thanks
As many as needed. There are no set times or numbers. If enough little bugs are fixed, it is released. If a major bug is fixed, it is probably released sooner. In general, you only have three reasons to upgrade.
:)
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.
I spend "midsummer night" in Helsinki Finland... great! Met a young feminine lawyer there... oh my god... Have a nice holidat Linus!
Bizar technology?
To clarify your reply: how many fucking days do you have per month, on average? And why do you waste such a day by just looking at fresh meat? :)
karma capped
Look at the 2.2 and 2.0 trees - the last 2.2 version was 2.2.19, the last 2.0 version was 2.0.39.
Hmmm. Well the bridge chipset is the Oxford Semiconductor OXFW911 2nd generation FW to IDE bridge and the drive is an IBM Deskstar 75gxp 30gig. We shall see!
Presumably at some point, Linus will issue a freeze and we'll move on to the 2.5 devleopment series, leaving only O&M on the 2.4 line.
there are no stupid questions, but there are a lot of inquisitive idiots
You think you got it bad? I just got finished installing 2.4.8 on a box literally ten minutes ago. And I see 2.4.9 has a driver update for my Ethernet card, which, I suppose, means I really should upgrade. *groan...*
sed 's/In Soviet Russia/In NSA America/g' < yakov-smirnoff-jokes.txt
one theory:
:)
with the acquisition of cygnus, glibc is now basically a redhat-internal project these days, Ulrich being @redhat.com and all.
Think Taco wants to pimp the work of RH instead of the distro he loves that benefits from it? The kernel's leader is outside RH (although obviously many, if not most of the major contributers are inside RH), so slashdot can pimp the kernel without pimping RH.
Oh, and did I mention VA Linux is an RH competitor?
Just some thoughts.
Various ramblings
With longer gaps between kernel releases, people can write apps that interact with the kernel and actually have a reasonable expectation that they won't spend the majority of their time trying to update their code to work with the most recent version of the kernel. People who just want bug fix patches should be able to get just that, leaving the added features,etc which will invariably introduce new bugs to be introduced on the next release cycle. The debian distribution system would be perfectly suited for this concept, and would pretty much do away with the need for a "development" branch of the kernel.
I was reading the changelog and it said that one of the pre- 2.4 kernels improved NTFS support. Has anyone out there tried this? I tried it a while back and blew up my entire NT partition, and I'm about half afraid of it. What kind of progress has been made in this area?
XFS is great. I have it on 2 production servers (rock solid since installation). However, for my workstation I've recently switched (back) to ReiserFS. I do a lot of large compiles and move huge amounts of code around and that exposes the ONLY weak part in XFS: unlink() time. XFS is doog slow for deleting large directory trees. I sure hope they optimize this, soon.. Other than the long rm times, it's rock solid. The ACL ioctls should be sorted out too soon, so we can have access to extended attributes (I will NOT miss you Be, Inc.)....
-adnans
"In short: just say NO TO DRUGS, and maybe you won't end up like the Hurd people." --Linus Torvalds
- Ben LaHaise: make vma merging more generous, help Mozilla /proc/<>/maps
Can anyone with the know-how explain what this means?
Cheers.
My only experience with ReiserFS was on an SMP machine, and it blew chunks (corrupted file system, bad data, kernel panics). I tried XFS and it worked quite well. I've not given Reiser another shot since then (haven't had time). Perhaps they've fixed this bug.
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.
www.eFax.com are spammers
dont you know he would have to look at freshmeat every fucking day to find out that they will email you when new stuff is released?
-- john
I always thought the whole idea with the sub-decimal points was that you could have an infinite number of minor updates as opposed to just 10. So logically, the next kernel version will be 2.4.10, and this could go on forever if need be.
"Use mirrors" they whine...
But no one posts any mirrors.
Then when a few valid mirrors start popping up, none of them have any patches... only full source trees. What's the point in mirroring if you're only going to mirror the full tree?
C'mon... some of us (even those of us with lots of bandwidth) would rather patch up than download a whole new kernel tree.
Someone mirror the patch. Save the trees. Save the whales. Do it for the children. Do it because the voices in your head tell you to. Please?
-Twi
What happend in '97-'98 that made for so few releases?
A deep unwavering belief is a sure sign you're missing something...
Wonder how long before a .deb for Woody will appear?
There is much cruelty in the universe, John.
Yeah, we seem to have the tour map.
Does anyone know what the deal is with the kerneli patch? Short of an unofficial hacked patch to work with newer kernels, kerneli hasn't been updated since 2.4.3, and there seems to be some serious issues currently with file corruption when using kerneli with 2.4 series kernels. Alternative projects like cryptoapi and loop-aes have sprung up from currently foobar'd kerneli, and while they work great, I can't help but wonder what's going on with the kerneli project that it hasn't been updated in so long.
For those of you trols that think "Slashdot isn't Fresh Meat" here is my 2cents:
:)
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
Two infinite things: your stupidity and mine. But I'm not sure about the latter. If my sig offends you, I'm sorry.
I was just able to download 2.4.8 yesterday. Howmany kernel this week?
Several new kernels are released each year, according to the maxim "release early, release often." This is part of the open source philosophy as explained by Eric S. Raymond in "The Cathedral and the Bazaar." The idea is that when there are many releases, there is more opportunity for users to run into bugs in the system.
How about 2.4.10? Just a guess, but works for me.
Does anyone know the specifics, or a source of information, about these two changes listed in the "final" section at the top of the changelog ?
but what is so exciting about: ...
- Alan Cox: more driver merges
- Daniel Phillips: unlazy use-once
and so on? I mean is there a Slahdot article when Microsoft gives out a new Windows 2000 SP? Including the changes and fixes (mirrored in the comments)? When there is a new major release, yeah, that's worth a story (and I expect the same when Windows XP ships, when Apple OS XI is there and the next major FreeBSD is out). These are newsworthy stories, a 0.01 change in version number is not. And now, FLAME ON, but I had to write this
Just because they're released, that doesn't mean that you have to upgrade. I'm quite happy about how rapidly linux software, and the kernels especially, are developed, though. I would much rather get my features incrementally, instead of in an installment every few years. This way, by the time feature Y is released, features A through X are mature and have been tested and used by the community for some time.
Peter
bz2-compressed, full-source tree Enjoy,
Brian T Glenn
delink.net Internet Services
IBM is just losing 1 billion bucks, and all this huge ads along 101 is just my hallucination.. Just like the workstations of all our developers, in a very commercial company (will sell the product mostly for Solaris though..)
<^>_<(ô ô)>_<^>
I managed to grab all the 2.4.9 files earlier, and they're now mirrored at:
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!
I need to remember that plan. Release new version of application, go on holiday for week. Have extra time to handle initial bug reports. Repeat.
He's brilliant!
Woot w00t w007.
One kernel update isn't even downloaded or the next is already finished! Not even Microsoft cooks up that many service packs in this particular timeframe...
Never underestimate the relief of true separation of Religion and State.
2.4.10, clearly.
I just compiled 2.4.9 with read-only support for NTFS. It turns out that there is a small bug that stops it from compiling. To fix the bug, edit fs/ntfs/unistr.c, and add somewhere near the top (line 24 or 25 is fine):
#include <linux/kernel.h>
agreed, i was thinking the same thing... but the thing is, this happens with nearly EVERY thread. there are always 10 people saying exactly the same thing.
I can't wait until SGI gets XFS merged into the main tree. I'm running XFS on all my systems, and so I have to wait until SGI gets the changes merged back into their port.
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).
www.eFax.com are spammers
Uhm, I have no actual clue, but I remember when configuring 2.4.8 that I had to disable a bunch of FireWire support. It was actually on by default. So why don't you check the hardware guide and/or just try it.
Just because a few of us can read write and do a little math, doesn't mean we deserve to conquer the universe
http://linux.uky.edu/kernel/v2.4/
This mirror is so fast, it will speed your downloads up, even past your NIC/modem's supposed maximums.
I started my compile of 2.4.8 about 20:30. Went away to rent a movie, came back to boot my new kernel...and what is the first thing my Mozilla browser finds... 2.4.9! It's a bad day for Jedi power ;)
Real programmers never comment their code. If it's hard to write, it should be hard to read!
Thank God I don't have disks the HPT controller desn't like.
I demand a million helicopters and a DOLLAR!
Does any of the kernels support firewire and firewire hard drives? I'd like to put linux on my external Firewire Hard drive (kernel would obviously live on my ide drive tho) anyone know if this is possible?
Nothing like pushing 'em out the door ;-).
If you want to avoid such troubles you have some options:
- 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.
"By the way if anyone here is in advertising or marketing... kill yourself." -- Bill Hicks
364000 Red Hat users?
I gotta toss some water on this FUD unless some poor smuck actually believes it.
According to Netcraft there are >18,300,000. Assuming that 1/3 of these system's are running Linux, that leaves 6,100,000 Linux servers running Apache. Acording to your numbers there are 455000 servers running linux that leaves something like 13.5 webservers per user.
This does not include people using Linux as routers, File servers, and PDAs. It doesn't include workstations not running apache, clusters, or boxes behind firewalls.
And if you thing red ink is flowing like blood in the linux community, just have a look at how poorly the tech industry is doing. Linux companies are actually performing better than the market average.
If someone is passing you on the right, you are an asshole for driving in the wrong lane.
Linux isn't sick. Companies making money off it are. You're just spreading FUD, and you know it.
A witty
Is there any place where a meaningful ChangeLog is kept? Reading the individual changes isn't much of a help (many changes may have been made but what are their effect?). I'd like to have a place that explains the changes and tells which users should upgrade (eg. "SBLive support is much better, users with SBLives should upgrade" or the sort).
I once tried to find a place like this, but failed. Does it exist, and if not, why not?
I doubt, therefore I may be.
Just like it was done since 1.X.x, it'll be 2.4.10. 2.2 went all the way up to 19. I think 2.0 went even up into 39.
I have no direct experience with the battery backed up drives, but here is a typical link:
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.
www.eFax.com are spammers
I mentioned this as a reply to someone else, but I was wondering if anyone else had trouble enabling NTFS (read-only) support. I dual-boot between Linux and Windows 2000 and while ntfs reading isn't vital, it's rather helpful at times.
I normally copmile as a module, but this time I get:
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[2]: *** [unistr.o] Error 1
make[2]: Leaving directory `/usr/src/linux-2.4.9/fs/ntfs'
make[1]: *** [_modsubdir_ntfs] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.9/fs'
make: *** [_mod_fs] Error 2
Compiling it in the kernel doesn't work either. Bleah, is this broken or did I forget to enable something else?
STOP MISUSING APOSTROPHES, YOU MORONS!!!
Funny, my SB Live has been working ever Since I switched to SuSE 7.1 with the 2.4.0 kernel, and was working even before that.
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..
--
"It is now safe to switch off your computer."
Show yourself coward! What kind of loser reads articles at a threshold that includes 0?
Enjoy
RFC1925
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 !
RFC1925
Bill lives in a COMPLETELY different neighborhood. ;)
He don't come 'round our hood very much.
=tkk
Bill Gates - Creationist?!?
Here are the counts by year. Only the release versions are counted because development kernels can run into the hundreds.
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.
Shameless plug: Or you could subscribe to some of my projects :-).
Cheers //Johan
Installed the Bubblemon yet?
I use gcc3.0 with glibc 2.2.3 to compile kernel 2.4.9, after compile and reboot. The adaptec AIC7xxx scsi driver have error and I can't boot up my machine with new kernel:
Anyone have same problem?
Does anyone have a link to the kernel compilation project? I can't find anything.