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)
Are you kidding me? I'm using it to browse the internet right n-
Not everyone know the drill, perhaps a link to a step by step instructions on how to do it should be included. You don't want to sacare off the new people, do ya?
The Kruger Dunning explains most post on
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
until a bug in the 2.5.2 series prevented me from using my swapspace. Everything else worked perfectly though. I'm back to 2.4 until sometime in the near future...
- This isn't the sig you're looking for. Move along, move along..
Number of Maintainer Patches Dropped By Linus in 2.5.3:
5
10
30
69
CowboyNeal!
Why does the kernel go through stable and then unstable forks? Can't it always be a stable build, like with Windows?
--Metrollica
(1) If you get any link errors when compiling your new kernel which refer to lock_kernel and unlock_kernel. Just add #include to whatever files generate the complaints.
:).
(2) If you have any SCSI drives that were broken because of the Block IO Layer changes, then this kernel most likely fixes them. Apparently, the "various scsi driver fixes" includes the parallel port zip driver (ppa.c) for any who care
w o r l d w i d e w e b e r
Ok ok ok - we all know that kernel.org's got some cashflow problems, so people PLEASE use the mirrors and patches!! To apply the patch, from the older version, CD in, then use patch -p1 kernel-2.5.3.patch (or whatever.) Make sure to make clean first also, just for paranoia. Anyway, have fun.
--joshua
P.S. Not redundant, no one's said this yet.
I want MovieOS! You know MovieOS! It's the operating system used in such movies as Hackers. Where.. you know, you hack into a machine and your face appears on the computer! When does MovieOS become available for public release?
(italics just seemed whinier for some reason)
Not interested? DON'T CLICK ON THE FUCKING STORY AND DON'T POST TO THE FUCKING DISCUSSION. Get a life. Go outside and play.
I for one don't check kernel.org daily, I do want to know when the new patches come out, I do check /. daily - is the overwhelming sense of something logical and useful dawning on you yet?
sic transit gloria mundi
"I just stopped using Windows and now you tell me to use Mirrors?" - said Aunt Tillie, just before compiling 2.5.3 kernel.
Really, I still do not understand what the point of patch-release announcements are on /.! This what freshmeat.net is for. This is not major news - this is trivial for everyone except those who are experimenting with the new kernel or developing for it. That's a very tiny subset of the /. population.
No, Slashdot is what Slashdot is. No more, no less. You have some preconceived notion of what Slashdot *should* be. If you want something else, go somewhere else, because SLASHDOT ALWAYS HAS AND ALWAYS WILL(probably) REPORT ON SOFTWARE. Yes, even patchlevel releases. Instead of trying to tell Slashdot what you want, and the rest of the people what you think they *should* want, how about you go and find a site which caters to your tastes and your interests?
Barclay family motto:
Aut agere aut mori.
(Either action or death.)
If anyone is wondering about the future builds of Linux, here they are.
(This message is long, but hopefully interesting? Please read it!)
An idea for a "variation on the theme" for version numbers occurred to me a
while back, but with 2.4 coming soon, this seems like an opportune time to
suggest it and see if anyone likes it...
The Linux kernel established the current scheme with version 1.0, and it
has been widely copied since. (Was it used before then by anyone else?)
Even numbers in the version number for stable releases and odd numbers for
development releases has worked quite well. This encodes some meaning into
the version number, which makes the status of kernel versions easier to
identify. I'd like to extend this further by adding a digit to development
version numbers representing the current phase of the development cycle.
This is easiest to explain by way of an example proposal:
2.4.xx Current stable release series. (Well, almost current.)
2.5.0.xx Initial integration -- No architectural changes allowed
while the inevitable backlog of pending patches from the
last stabilization effort are integrated and stabilized.
The final 2.5.0.xx release should be re-released as a new
2.4.1 stable release. This series should resemble a
combination of 2.5.8.xx and 2.5.9.xx below, and should be
suitable for non-mission-critical production use. This is
a fork from the stable series that re-merges once before
diverging again for radical development work.
2.5.1.xx EXTREMELY unstable -- Major architectural changes, any new
features and major feature changes allowed as the tree is
thrown wide open for bizarre and wild experimental work,
much of which may be discarded as experimental prototypes
prove that some ideas that sounded good weren't so good.
Suitable only for the extremely brave or foolish. Even
developers may wish to avoid this series unless they're
doing the experimenting. Expect constant crashing.
2.5.2.xx VERY unstable -- Much like 2.5.1.xx series, but experiments
should a little less wild now. Best time to focus on the
major architectural changes that are goals for the 2.6.xx
stable series. Most developers would want to work with
this series, but not depend on it heavily for daily use.
Expect nearly constant crashing.
2.5.3.xx Unstable -- Significant architectural changes, new features
and major feature changes allowed. Most experimental work
should be finished by now; new experimental work should be
developed in a forked tree until suitable for integration
into development tree. Suitable for developers, should be
stable for short periods of time. Expect frequent crashes.
2.5.4.xx Almost stable -- Reasonable architectural changes allowed,
new features and major feature changes allowed. Suitable
for developers only, but "bleeding edge" users may want to
try it out briefly. Expect random crashes, but should be
stable enough to be more-or-less usable.
2.5.5.xx Somewhat stable -- Small architectural changes allowed,
new features and significant feature changes allowed.
Suitable for developers and "bleeding edge" users only.
Expected to crash once or twice per day, but should be
stable for hours at a time.
2.5.6.xx Reasonably stable -- Minor architectural changes allowed,
medium feature changes allowed. Suitable for experimental
servers or the more patient of the average desktop users.
Not suitable for any production use; may crash several
times per week.
2.5.7.xx Mostly stable -- No architectural changes allowed, new
features and small feature changes allowed. Should be
suitable for the average desktop user or for a test server.
Not suitable for most production use; expected to crash
every few weeks or so.
2.5.8.xx Initial release candidates -- No architectural changes, and
only minor feature changes or clean new features allowed.
Bugfixes and carefully selected patches only. Should be
suitable for production use only on non-mission-critical
systems. (This series would be equivalent to "pre" series
in the past preceding a new stable release series.)
2.5.9.xx Final release candidates -- No architectural, new features
or feature changes allowed at all. Bugfixes ONLY; final
tuning before 2.6.xx stable release series. Final release
candidates should be almost suitable for production use on
mission-critical systems, as any stable series release
should be. (This depends on getting 2.5.8.xx used on some
production systems first...)
The 2.5.9.xx series should REPLACE the traditional initial
stable series stabilization efforts. The final release in
this series should be re-released as 2.6.0 and 2.7.0.0 with
no changes but the version number -- if more bugfixes are
needed, it's not time yet. Only when it's time to fork for
a new development series should the stable series be
declared. (This should avoid embarassments like 2.2.0 --
a "stable" release that crashed rather easily...)
2.6.xx Next stable release series.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
--Metrollica
This is a very nice release. As you can see from the changelog the new ide drivers are finally in 2.5.x. Lets hope this will give Marcelo one more reason to include them in 2.4.x.
:-). But it has been said that Rik's VM brings the VM back to the -ac13 state.
The O(1) Scheduler from Ingo is also in here (version J9) at the moment.
All of these patches are also available for 2.4.x! Im running aa WM, scheduler O(1) and the new ide patches right now and have been for more than a wekk without any problems whatsoever. Also for those of you that want to try riks VM there's also a patch for that.
Anyway those patches are only for those of you adventoures like me
Really, I still do not understand what the point of patch-release announcements are on /.!
I have to agree, but only because this is a *testing* kernel. For all stable releases (ie: 2.4.x for now), I think announcments of new versions is a cool thing - it allows the much much larger base of linux 2.4.x users (as compared to 2.5.x) to discuss the new features/caveats/etc of the latest stable kernel.
The Free desktop that Just Works
Note:
mirrors.kernel.org is NOT the list of mirrors of the kernel, it's the list of mirrors of other sites.
For the kernel, you want www.kernel.org/mirrors/ to find your local mirror of kernel.org (which is usually www.COUNTRYCODE.kernel.org).
--Xandu
But where is XFS? Extended attributes (arbitrary tuples for files) support would be cool. But we need XFS for that since that's the only Linux FS that supports this right now, I think.
"In short: just say NO TO DRUGS, and maybe you won't end up like the Hurd people." --Linus Torvalds
It was a whine and it was insulting to those who run Slashdot.
I'd accept that argument if a) there had been no !. b) they had not said "this is not news", c) has not referred to freshmeat.net, and d) the part about it being trivial.
Barclay family motto:
Aut agere aut mori.
(Either action or death.)
I agree that Slashdot sometimes reports on certain software that lots of people consider important, even point releases of things like KOffice.
However, I don't remember ever seeing news posts about Linux 2.3, the previous unstable branch (I checked the archive and apparently there were just two). So why are things different now with 2.5?
It's about time the Google implemented a system to automatically mirror or cache every page linked to on Slashdot (as soon as the link appears) so we have some place to go when the original site gets slashdotted.
Give me my freedom, and I'll take care of my own security, thank you.
> I've been wanting to get into this Linux thing for a while, but I'm kinda confused. And nervous.
Understandable
>What is a kernal and changelog?
A kernel is computer code that makes your computer start up and lets you do stuff on it. This is all before your operating system. (the part you are most familiar with likely Windows or MacOS)
The Changelog is a developer documentation that says what has changed in this program.
> And how come everyone that uses it seems to hostile to a newbie asking questions?
Because these are the wrong people for newbies to be asking. This would be like asking the Mechanical engeneers how to change sparkplugs in a car. You need to try directing your questions to one of the distributions
http://redhat.com
http://mandrakelinux.com
http://debian.org
http://slackware.org
> Also, how do you run it?
It requires an install from a distribution first. (see answer from above)
>I tried opening it with winzip and that didn't work.
Yes opening it with winzip would work for the kernel source as you would get a bunch of "C" programming files in a nice neat directory. this is like getting the blue prints to a house to open the front door. (again please see the distribution list above)
>Adaware didn't call it (well, I downloaded something called from www.redhat.com but it didn't work) spyware or anything, but I know alot of freeware has spyware on it. Is linux like that?
Most stuff in linux does not have spyware. Although there is no technical reason for it, it is generaly frowned apon and seen as bad.
> Also, is it REALLY free?
Yes
>Or is it one of those things where you will use it for 30 days and then it takes forever to come up when you click on its icon until you pay?
no there is no payment needed to get the software.
I hope this helps.
Paying taxes to buy civilization is like paying a hooker to buy love.
Since most of 2.4.x has been pretty much beta why should I go to 2.5 for testing????
cat
python -c "x='python -c %sx=%s; print x%%(chr(34),repr(x),chr(34))%s'; print x%(chr(34),repr(x),chr(34))"
"--
.) MIDI sound. Ultimately Loom was more a work of art then it was a game, but it was one great work of art.
Ask me about Loom(tm)"
Loom was a great game my Lucas Arts I do believe. I may have a copy of it sitting around here someplace. It was a fantasy adventure game that was based upon a magical system that used musical notes.
The game was quite short, under a day to complete, but even in 1994 or so (long after its release) it was still capible of astrounding people with how nice it looked and how great it sounded. This is despite using only (as I recall. .
Need help treating your acne? Come here!
You know, I fired off my original post to parody the kind of whining that so often occurs when the news isn't about Linux. After hitting the submit button however, I realized that such whining was already in full effect for this news item. I despaired of having any success at all with my little joke. And, juding from the response I've received so far, I was right to despair. At least I can draw some consolation from my small success as a troll. HTH. HAND.
Any sufficiently well-organized community is indistinguishable from Government.
I noticed on kernel.org that there are now listings for the 2.0.xx kernels (sorry if I'm behind the times, I don't check the site every day). Is anyone out there still using the 2.0.xx kernel (or earlier version)? If so, what are the reasons? Maybe a little off topic, but I think it would be interesting to see what's going on with older Linux versions and how they are being used.
Smeghead every day of the week.
Yeah, I know, everybody and their mother whines about, "Why does slashdot post new kernel announcements, wah, wah wah!" And I'm going to do the same, but hopefully I'm a litte more constructive.
What I'd like to see in these announcements is a description of what's changed. Not the changelists; I want the executive summary. Something like "New kernel 2.5.3 released; includes fixes for the FCI bus problems of 2.5.2, as well as the new virtual monitor support!" That would be immensely useful to those of us who don't want to install every kernel and keep track of every new feature, but do like to stay aware of the bigger trends.
P.S. There is no such thing as the FCI bus or virtual monitor support, as far as I know, it was just an example. But if you're smart enough to come up with the executive summary for this release, please, post it. This time and every time.
damn, you did NOT just answer that seriously!!!
sic transit gloria mundi
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))"
The Drill is pretty well-documented all over the place, including in the kernel source documentation. Don't encourage linux newbies to use experimental kernels.
- A.P.
"Remember when the U.S. had a drug problem, and then we declared a War On Drugs, and now you can't buy drugs anymore?"
I really doubt that one person could compress all the relevant information about a new patch release into one paragraph, especially immediately after the announcement and if that person does other things too; besides you'd only get what JonKatz (for example) thinks of the new kernel release then, which may not always be as informative as you think.
sic transit gloria mundi
Why not???
I agree with you on this. While a good many people are probably interested in the stable branch point releases (me included), the unstable branch is generally not going to interest as many people. Those who are interested can check up on the kernel.org site for changes.
Now having said that, I think Slashdot should continue posting stories on whatever they see fit, and if a story doesn't interest me (which definitely happens), then I'll ignore it.
That's the big problem with those proposing censorship in any situation. The decision on what an individual gets to see and experience should rest solely with that individual. I don't want people making decisions for me, because they know 'what's best for me'.
I'd rather see more uninteresting (to me) stories on Slashdot than less interesting ones. Of couse, my interests vary from the interests of others, so I should expect to see stories that aren't interesting to me.
People should have the maturity to realize that everybody else in the world does not always agree with them, and shouldn't be punished for not agreeing with them. Take what you want and leave the rest. Judging by the number of comments that each article on the front page gets, every article interests somebody.
If you want a vision of the future, imagine a youtube comments section scrolling - forever.
To pick a nit, CML2 is the new config language. The new build system is kubild2.5, developed by Keith Owens.
© ilmari. All rights reserved, all wrongs reversed
Remember that with the 2.3.x series, the release of 2.4.x was somewhat rushed. Why? Because not enough people were testing. Linus couldn't make any further improvements without a wider base of testers, but people just weren't willing to "risk" an "unstable" kernel. So we got 2.4.x before it was really ready, causing a lot of general complaints and confusion.
With Slashdot announcing most major (?) 2.5.x releases, I think they're probably hoping that more people will be curious enough to try them out. The more different systems and use conditions it gets tested under, the more solid the final release will be.
"Lets go hit those servers!"
Hitting a server is not a good idea. Hit them too hard and you will break something important and the server will cease to function properly.
The once lively server will be dead. It won't be resting, it'll be stone dead. It'll have passed on. It'll be no more. It will cease to be!
It'll have expired and gone to meet its maker. It'll be a stiff. Bereft of life, it'll rest in peace. If it wasn't for the fact that it had been mounted to a rack it'll be pushing up the daisies!
Its processing cycles will be history. It'll be off the twig. It will have kicked the bucket, shuffled off its mortal coil, run down the curtain and joined the bleedin' choir invisibile!
IT WILL BE AN EX-SERVER!
Oh yeah, the sysadmin will be pissed at you too.
"Accept that some days you are the pigeon, and some days you are the statue." - David Brent, Wernham Hogg
The guy with the 5624 day uptime that just will NOT reboot for ANY kernel upgrade, damn it! :P
:-)
either that, or people are just too lazy to bother with it.
No, Slashdot is what Slashdot is. No more, no less. You have some preconceived notion of what Slashdot *should* be. If you want something else, go somewhere else, because SLASHDOT ALWAYS HAS AND ALWAYS WILL(probably) REPORT ON SOFTWARE.
Geeze, calm down, you'd think he insulted you personally.
Slashdot is a public media publication; as such we're perfectly within our right to ask that it be changed. Of course every suggestion is buried under flaming rants insisting that if we don't like it we shouldn't read it.
It's kind of a grade-school logical construction; which can be dismantled thusly--if I didn't like reading slashdot, I wouldn't post suggestions for what in my mind would improve it. I wouldn't care at all.
Have they finally fixed the i810_audi drivers to make them work with the 44.100hz playback rate?
;)
Looks like I'm going to have my first time unstable
X
Boycot? Blackout? Subscriptions?
I don't care!
> Is it safe?
"Oh yes, it's perfectly safe -- It's just us who are in trouble."
Well, not software in general... slashdot reports on patchlevel releases of the Linux kernel. Other OSes or software rarely get mention unless it's a major release (and sometimes not even then).
I should try submitting an article each time NetBSD's kernel version number changes or something and see if I ever get accepted... "NetBSD 1.5ZB Released!"
(I'm not affiliated with LWN. I just like the service.)
A good pace to find this information is Kernel Traffic. It's like a summary of the mailing list.
How do you pronounce that? Cuebild or Coobild?
BTW, does anyone else think that kbuild sounds like it is somehow related to KDE? Funny how that happens.
:wq
Just have kernel.org connect to the mirror, see if the filesize matches (assuming we know more or less where to find it, even searching through the kernel directory tree would probably be worth it) and if it does, the mirror is updated and you can add it to the list of mirrors you can redirect to. The bandwidth of listing a couple files should be well spent compared to having lots more downloading directly from kernel.org
Kjella
Live today, because you never know what tomorrow brings
It really annoys me that you can't count on the Linux developers to write good documentation. When Matt Dillon made his changes to FreeBSD's VM, he wrote up a bunch of documentation explaining it. When Andrea Archangeli did his changes to the Linux VM, he didn't officially document them at all. Now, we have this crazy new bio (block-I/O) layer that's supposed to be all super-cool, but there are no docs explaining how its works!
A deep unwavering belief is a sure sign you're missing something...