Slashdot Mirror
Linux 2.4.15 is out; Linux 2.5.0 has also begun.
jbondjr writes: "It appears 2.4.15 is released. It's not quite updated on kernel.org's main page, but it is there if you dig through the tree. You can find 2.4.15 on one of your friendly Kernel.org Mirrors (note the 2.4.15 Changelog) From the 2.5 readme: "Linux-2.5.0 is exactly the same as 2.4.15, except for a version number change." So, enjoy the
The 2.5 Tree
so they can be cool and trendy and be on the development tree while it's still stable?
Boffoonery - downloadable Comedy Benefit for Bletchley Park
Build 2.4.15 with some modules. Look where it installs them... (Clue: Think when it was released)
;-))
Linus is a little joker, isn't he?
Don't forget the Preemptible Kernel patch. This will reduce latencies and overall make a desktop machine feel snappier.
From what I hear, however, it's not recommended for servers where bandwidth is more important. But then again, you wouldn't be putting a bleeding edge kernel on there anyway, now would you?
XML is like violence. If it doesn't solve the problem, use more.
Just look at the kernel name, for 2.4.15
You'd think it would be 2.4.15, consistent with all other kernels.
but NoooOOooo...
he has to name it:
2.4.15-greased-turkey
I'm sure there isn't a Todo list. And I assume there never will be one.
I was just wondering (read karma-whoring) what the first big change in 2.5.0 will be.
I guess cml2, the new config/make system.
Some other changes that might be expected;
Jfs and Xfs in the main kernel,
Fixing the latency, and maybe make the kernel pre-emptive.
There will be a scsi layer rewrite and maybe a ide layer rewrite (that's correct?),
Well, don't worry about that. We can get you back before you leave. (Dr. Who)
Linus has a little package in the v2.4 directory. It is called drm-4.0.x.tar.gz. You can use it to get DRM for XFreee86 4.0.x.
Looks like kernel.org has updated their main page and their 100Mbps connection looks pretty maxed.
/. Also surprised my first submission got accepted :)
http://www.kernel.org/mirrors/
Sorry, seldom post, so don't know how to make a link on
Now, for the people who use ext3:
You will not need to download ac/ext3 patches anymore to get your journaling running.
I hope that all the kbuild stuff gets in soon !!!
regards
john jones
Bleh, whatever... This comes up every time a kernel release is announced on /. I for one like to see these releases announced on the front page. If you don't like it, edit your preferences. Perhaps I should just check kernel.org every day and see whats up, or freshmeat. The fact is that I've grown accustomed to coming here as my first news spot of the day and generally just get new kernel release info from here - as it's always here. Personally, I don't mind a bit.
- alpha : the development tree
- beta : developers realise that they have done all the tests they could and call 'stable' the development tree. More users starts using the new kernel (users which would not have used a 'development' release). New bug and problems come out; some of them may not be fixable with small patches, but may require some strong re-enginering.
- final : the developers and beta users are satisfied with the current performances of the stable kernel ( and maybe also tired of working on it
;^>). The stable kernel is given to the maitainers. A new development kernel begins.
This is not a bad model. Maybe the kernel is getting too big for the two-stage model. And maybe too many people are using Linux for critical business, starving the 'development' releases of the testers it needs to get production quality.Ciao
----
FB
just code html to make a link. you should type:
k ernel.org/mirrors/</a>
<a href="http://www.kernel.org/mirrors/">http://www.
This works in html formatted <B> and </B> plain old text. (i think code as well).
just a tip.
Is this Freshmeat or Slashdot ?
It's slashdot. You can tell it is because it says "Slashdot - News for nerds" at the top.
You can easily recognise freshmeat when you see it as well - it has a logo at the top with "FM" written in it.
I'm surprised you have difficulty telling them apart. They really are quite different.
-- MartinG To mail me: echo kewyjlcxyzvjfxbqwh | tr bcefhjklqvwxyz
Since the kernel is now on the 2.4 series kernel, is it officially considered a "stable" kernel yet? With the recent discussions of the VM system and pre-emptable kernels, I wonder if the latest version is stable enough for my server. I'm still running 2.2.19 and it's working fine, but I'm looking forward to upgrading some time in the next couple weeks (maybe).
One big thing I'm looking for a fix for (hopefully with the 2.4.x series) is for the SNMP/netstat info to use more than 32 bit integers to store the number of bytes transferred. Mine keeps resetting after 4 GB transferred and over 6 months that would've added up, but right now it resets itself back to zero after it hits the 4 billion byte limit.
Also, the SMP is supposed to be better, but will that really make a difference on a server which does mild web serving, other miscellaneous duties, and who's primary purpose is serving Unreal Tournament games? As of now, it doesn't look like UT takes advantage of both processors, it just uses one...
The readme file in 2.5.0 says:
Linux-2.5.0 is exactly the same as 2.4.15,
except for a version number change.
Subsequent releases diverge, with Marcelo Tosatti
maintaining the stable 2.4.x kernels, while the 2.5.x kernels are for development work.
and looking at the filesizes we find what we expect that
linux-2.5.0.tar. takes up 129 699 840 bytes
linux-2.4.15.tar takes up 129 699 840 bytes
are the same. But if we look at the packed versions
linux-2.5.0.tar.bz2 23 748 963
linux-2.4.15.tar.bz2 23 747 061
A difference of 1902 bytes
linux-2.5.0.tar.gz 29 404 635
linux-2.4.15.tar.gz 29 404 736
A difference of -101 bytes
How come?
There is a new technique called "Don't Click On The Link Of Stories You Don't Want To Read". Apparently it allows people to decide whether they want to read the story just by looking at the headline, and if it says "New Linux Kernel Out", it allows the user to not click the link, thus avoiding the story they didn't want to read. I can't see how this new-fangled "Don't Click The Link" technology could possibly work, but some people say they are very happy with it.
So... has anybody found any bugs on 2.4.15 yet?
...
My guess is that the Slashdot editors do this to answer the eternal philosophical question:
"How many people who can't read 'use the mirrors' can fit over a 100MB pipe?"
:)
Want Linux games? HERE.
I want support for ATAPI/IDE CD Burners. The SCSI emulation solution isn't the best solution I don't think. That's the extent of my wishlist. I'll be happy with whatever else Linus gives us in his infinite wisdom. Anyone else got a wishlist for 2.5.x?
Does anyone know the reason why they haven't included ALSA in the main kernel yet?
I finally switched my Red Hat 7.2 and recompiled KDE with Alsa support, and things are SO MUCH nicer than free-OSS. I can finally use Real Player or Quicktime Player (via CrossOver) seemlessly with KDE. No more fussing with artsdsp to get Real Player to work, or terminate artsd in order for Wine audio to play.
It's probably stable.
But why take my word for it (or anyone else's) - download, compile, install, stress test, use.
If you don't have a test machine - wait a while, read the mailing list, see if anyone reports bad uptime / errors which affect you.
If you're so worried about stability, I don't see any other real option for you. Certainly, it seems naive to consider an 'official' designation of 'stable' sufficient to jump in with both feet. Either test it yourself, or read other peoples reports - there's plenty of them.
My experience? I have had no trouble with the 2.4 series, except for VM probs in 2.4.9 which brought my desktop machine to a short lived pause once or twice. I installed 2.4.13 last night and am hoping Andrea's VM will cure this.
Yours Sincerely, Michael.
For some reason I couldn't get the loopback block device module building in 2.4.14 on my laptop (depmod chocked on undefined symbols)
.29) 3.1.30 pcmcia-cs package there
works again in 2.4.15
There is also a new (at last! almost 4 months since
Please avoid slashdoting the main server. Here is list of direct links to mirrors, by country.
Version 2.4.15, full tarball:
al
dz
as
ad
ao
ai
aq
ag
ar
am
aw
ac
au
at
az
av
bs
bh
bd
bb
by
be
bz
bj
bm
bt
bo
ba
bw
bv
br
io
bn
bg
bf
bi
kh
cm
ca
ic
SSL Certificate
...reading this I went over to catch up on AC's diary. More human interest than the change log. Got to November 5th and read:
"Windows installation day one. Getting rid of the old windows was easy - they fell apart quite happily, and certainly wont be re-installable anywhere else. "
Blimey, I thought, until I remembered his house is getting done up...
~~~~~ BigLig2? You mean there's another one of me?
Preemptability is just a feature that you can add to your kernel to make kernel threads preemptable (using the in-place SMP infrastructure).
Preemptability is not:
-an attempt to fix a bug in linux or make linux more stable
-a way to make Linux slightly more advanced than MacOS
-Something that is desperately needed
Preemptability is:
-A way to make processes that have long execution threads inside the kernel not take away from higher priority user-space threads (priority is not the same as niceness).
So PLEASE, lets stop this bandying about of "preemptability" when you know not of what you speak.
Quick question: I was wondering why there is so much fuss about this KBuild thing, and why there is going to be so much time / resouces spent on it in 2.5. I have never had a problem with the current kernel config, and find it quite intuitive (make xconfig especially). I can think of many more things which I would think deserve a higher priority than this. Someone care to enlighten me?
Fatal: Label "2415-greased-turkey" is too long
While it's easy enough to fix (edit lilo.conf), I bet this is going to cause problems for someone.
really, I am.
/boot/vmlinuz and System.map into /boot/System.map, and move your old vmlinuz and System.map to vmlinuz.old and System.map.old, then reran lilo.
but anyway, last I checked "make install" put bzImage into
Never used make bzlilo myself. Sounds like one of those features of the kernel you really shouldn't use, but some people do, and if you do use it you should really know what you're doing, but I guess that should be true of anyone compiling their own kernel.
Marcello is maintaining 2.4.15> because Alan Cox won't, it seems he made a personal choice.
Alan Cox is going to be in touch more with the customers of his employer, RedHat.
Marcello is a knowledgeable guy, he has proven to be sceptical and is imho able to discriminate well between a 'bad' patch and a Good(TM) patch. Alan said he would assist and advice Marcello if he needed help.
If you want to know more about Alan Cox, please search google for Alan's diary and website. (Or try Telsa's website, might be even more fun to read.)
It's actually not emulation, but transport. ATAPI is actually SCSI, implemented on top of IDE. Remember those parallel port zip drives? They are SCSI over parallel port. SCSI "emulation" simply lets userspace apps talk to the devices in their "native" tounge.
Desperation is a stinky cologne
sheesh. 2.4 to 2.5 and not a single change.
Got friends?
While we are talking about incompatible kernel patches, please be aware that ALSA 0.5.12 does not work under 2.4.15. You need to get the CVS version, as described here. ALSA 0.5.12 compiles, but does not work.
It's not that bad! I track the XFS tree, so I tend to compile the kernel every few pre-patches (this is a personal workstation, so it doesn't matter). It takes 15 minutes to do the compile, as long as you keep your config files around. Quite painless, really.
A deep unwavering belief is a sure sign you're missing something...
I have been trying to figure out how the pre-release kernel patches are applied. I have tried using the patch-kernel script to no avail. Are they patches against the previous prerelease, or the previous release?
According to openwall, the non-exec stack and other security patches so useful in 2.0.x and 2.2.x are finally on the way to 2.4.x, giving you that extra bit of protection. Of course, it looks like it will have its own beta period, but those patches protected my 2.0.x box for quite a while from 0-day exploits, and let it manage a full year of uptime at one point despite dozens of users and a bunch of services (including the ever-dangerous wu-ftpd).
No one, least of all me, said that a non-exec stack was all you needed to keep a box safe. However, it is still useful to have, and contains a variety of other useful patches, just as restricted access to /proc and some things to avoid games in /tmp, like symlinks to other system files, etc. Nonetheless, there's also such a plethora of buffer overruns available, and they are still common, probably because there is so much "example" code available, and smashing the stack is easier to code than trying to heap overrun malloc'd values or whatever a would-be exploiter might choose to do. Furthermore, many exploits that make it into the wild begin as proof-of-concepts, and therefore START as buffer overflows, since the writer has no intention of cracking anything. Several buffer exploits have been out in 2001. If you buy yourself any extra time, it is a patch well-applied, and the other features may be useful depending on the system.
Alternately, a lock on your house door won't protect you from a burglar (the *only* entry that a lock will stop is a standard check-for-open-door entry, in case you didn't know), so you can have a lock on your door, as long as Assumption #0 is that the lock won't even slow down a burglar.
You aren't supposed to use block and character devices for the same device at the same time!
;)
You have the raw device ignore the buffer cache. If you must switch between block and char devices (unlikely), use the block device, then flush it before any access to the character device (unless it already has been flushed).
Just because using raw char devices messes up the block device cache isn't a reason to remove the feature. It is a reason to NOT MISUSE the feature.
Do your light sockets have anything in them designed to keep your tougue out of them?
Just because it CAN be done, doesn't mean it should!
If you try to cut and paste from the mailing list archives, you'll probably have spaces instead of tabs in the patch, causing patch to choke on it. I've put a tabbed patch up here.