Slashdot Mirror


2.5.4 Kernel Out

Saint Aardvark writes: "Just in time for my 30th birthday, the new kernel is out...how did he know? Thanks, Linus! Change log here. I usually stick to stable stuff, but I think I'll try this for fun." Reader Scooby Snacks writes: "Be sure to use the patches and pick from the fine list of mirrors."

206 comments

  1. Congratulations Timothy! by Anonymous Coward · · Score: 0, Funny

    Are you going to post stories now when you get an email from your grandma? Because a point release is about as pathetic.

  2. A Minor update to a development kernel? by joshv · · Score: 1, Flamebait

    This must be a slow geek news day...

    1. Re:A Minor update to a development kernel? by baptiste · · Score: 2
      Actually, read the January and February threads on the kernel list. Some really heavy debate about changes to low level stuff like schedulers and such. I found it a VERY interesting read and I think the things being proposed for 2.5.x are pretty impressive. I found Ingos O(1) scheduler work and the debate it generated very interesting.

      It may not be "Justice wins over Microsoft" but its still a notable event.

    2. Re:A Minor update to a development kernel? by Anonymous Coward · · Score: 0

      It must be wonderful to live in a morally black and white world.

      It's alright. The taxes are a little high and if you get sick, Canadian ambiguity looks kinda attractive.

  3. Uh, who cares? by Anonymous Coward · · Score: 0, Insightful
    A minor rev on the main branch -- maybe. Minor revs to the "experimental, may even blow up your computer" branch DON'T MEAN SHIT. I certainly wouldn't fuck up my system with it.

    If the open source/Linux development holds up on this one, with any luck, there will only be 220 more notices before we see 2.6.0. Yay!

    1. Re:Uh, who cares? by NewbieSpaz · · Score: 1

      A minor rev on the main branch -- maybe. Minor revs to the "experimental, may even blow up your computer" branch DON'T MEAN SHIT. I certainly wouldn't fuck up my system with it.

      As somebody replied to the last Troll-ish post relating to kernel 2.5.3: it shows that there's forward progress towards the next stable kernel. So it does in fact mean something. To further reply to your post, nobody asked you to use this kernel. All kernels in the development tree are strictly for testing for the few brave enough, or with the curiosity and time to try it.

      If the open source/Linux development holds up on this one, with any luck, there will only be 220 more notices before we see 2.6.0. Yay!

      220? Hmmm, seems a bit high of a guess.

      --
      ------
      Random, useless fact: I type in startx entirely with my left hand.
  4. Patchdot by Anonymous Coward · · Score: 4, Funny

    2.6.0 released
    2.5.20 released
    2.5.19 released
    2.5.18 released
    2.5.17 released
    2.5.16 released
    2.5.15 released
    2.5.14 released
    2.5.13 released
    2.5.12 released
    2.5.11 released
    2.5.10 released
    2.5.9 released
    2.5.8 released
    2.5.7 released
    2.5.6 released
    2.5.5 released

    Expect all these articles on this site soon.
    Slashdot, news for "nerds", notifying you of minor changes to the penguin!

    1. Re:Patchdot by __aahlyu4518 · · Score: 3, Funny

      notifying you of minor changes to the penguin!


      Did he do something to his hair ? :-b

    2. Re:Patchdot by negativekarmanow+tm · · Score: 0

      That should be:
      2.6.0 still not ready for desktop
      2.6.0 released
      2.6.0 expected soon
      2.5.20 still not ready for desktop
      2.5.20 released
      2.5.20 expected soon
      2.5.19 still not ready for desktop
      2.5.19 released
      2.5.19 expected soon
      2.5.18 still not ready for desktop
      2.5.18 released
      2.5.18 expected soon
      2.5.17 still not ready for desktop
      2.5.17 released
      2.5.17 expected soon
      2.5.16 still not ready for desktop
      2.5.16 released
      2.5.16 expected soon
      2.5.15 still not ready for desktop
      2.5.15 released
      2.5.15 expected soon
      2.5.14 still not ready for desktop
      2.5.14 released
      2.5.14 expected soon
      2.5.13 still not ready for desktop
      2.5.13 released
      2.5.13 expected soon
      2.5.12 still not ready for desktop
      2.5.12 released
      2.5.12 expected soon
      2.5.11 still not ready for desktop
      2.5.11 released
      2.5.11 expected soon
      2.5.10 still not ready for desktop
      2.5.10 released
      2.5.10 expected soon
      2.5.9 still not ready for desktop
      2.5.9 released
      2.5.9 expected soon
      2.5.8 still not ready for desktop
      2.5.8 released
      2.5.8 expected soon
      2.5.7 still not ready for desktop
      2.5.7 released
      2.5.7 expected soon
      2.5.6 still not ready for desktop
      2.5.6 released
      2.5.6 expected soon
      2.5.5 still not ready for desktop
      2.5.5 released
      2.5.5 expected soon

      --
      No security through obscurity: my password is goatse. Stop me before I troll again.
  5. New Topic Please by Dredd13 · · Score: 4, Insightful
    Can we have a topic "Linux-Kernel-Release", so that those of us who care about "Linux news" (and so don't want to check-to-exclude the "Linux" topic) can still send these Freshmeat-intended stories to /dev/null where they belong?

    1. Re:New Topic Please by Sircus · · Score: 1

      While the guy's clearly trolling, I actually think this is a fine idea. If nothing else, it'd get rid of the crowd of trolls on every kernel story.

      --
      PenguiNet: the (shareware) Windows SSH client
    2. Re:New Topic Please by Dredd13 · · Score: 5, Insightful
      I don't think I was trolling at all, I'm actually really sick of having to wade through kernel announcements.

      .0's are newsworthy

      .FINAL_VERSION's are newsworthy

      .PATCH_OF_THE_WEEK's are not "Stuff that matters" for the majority of folks out there. If you ARE one of the folks that it matters for, chances are you're monitoring the kernel.org site already.

      Just my $0.02 worth anyhow....

    3. Re:New Topic Please by hal200 · · Score: 5, Insightful

      I'm not trying to troll here, but I don't get it. Maybe it's just me, but is it really so onerous to read a headline and move on if you're not interested? (Just to go on the record though, I happen to like the Kernel X.Y.Z is out! news items.)

      Are you paying for your desktop real estate by the pixel or something?

      I rather effectively screen out JonKatz by reading the headline, and seeing the big green JonKatz underneath. Then I know it's drivel and I move on.

      I just don't understand the motivation behind, "I should be able to filter this out!"...It's not like they're forcing you to read the article and all the comments. Just move along if it doesn't pique your interest. Considering how many stories flit past the front page in a day (and more with judicious use of Slashboxes), it's not hard to find something more personally interesting.

      Then again, maybe I'm just being obtuse. Anyone care to enlighten me?

      --

      I just want to take over the world...Why does that automatically make me EVIL?

    4. Re:New Topic Please by Anonymous Coward · · Score: 0

      I wholeheartedly agree. Slashdot must be really stuck for decent stories if point releases of a kernel development branch are counting as newsworthy on this kind of site. I don't think we see such frequent postings tracking development point releases of anything else (including point releases of other kernels/OS), and neither should we. There are more targetted sites for that sort of thing, which people who care about that sort of thing will track for frequent updates.

    5. Re:New Topic Please by Anonymous Coward · · Score: 0
      Uh...

      This is a "Pro Linux" site you moron. If you don't like it you should simply not click on the "Read More" link. I mean really. Was there some special intergalactical force that made you click the little link and read all the stupid comments? Sheesh. I mean really. What kind of an idiot clicks a link then complains about it?

      Moron.

      Thank You.

    6. Re:New Topic Please by Dredd13 · · Score: 0, Flamebait
      Wow ... "moron"... your intelligent debating skills amaze me.

      I'm pro-linux as well, but I don't need to be bothered every time the development tree has a patchlevel release, and, since the Slash engine could easily accomodate both the folks who want to know every time a new version comes out AND those who don't want to see every version, wouldn't it make sense to set things up so that EVERYONE gets what they want?

      Or is the concept that both factions can be easily made happy just beyond your comprehension?

    7. Re:New Topic Please by Sircus · · Score: 1

      I don't contend that the point itself was trolling, but your phrasing could certainly have been way more diplomatic. Throwing stuff about /dev/null and freshmeat into the post turns it, in my mind, from a decent point about a way to make things better for everyone into something that's a decent point made in a deliberately inflammatory way. I guess it depends on your definition of trolling.

      --
      PenguiNet: the (shareware) Windows SSH client
    8. Re:New Topic Please by Dredd13 · · Score: 2
      Do you call CNN every time they run a story you don't care about, or do you just change the channel?

      If CNN had this cool engine built that allowed me to customize the news articles I saw, and then didn't actually USE that engine to the proper granularity, I think I'd call CNN and bitch, yes.

      But since they don't, I'd change the channel.

      However, since Slashdot DOES have the capability to customize the news so you see the things you WANT to see, doesn't it make sense for Slashdot to actually USE that capability?

    9. Re:New Topic Please by Anonymous Coward · · Score: 1

      HE's not asking about not reading the 'DAMN STORIES' he's asking about getting them off the damn frontpage. A way to filter them without losing all the other Linux stories. I don't blame him either, while I find it interesting when a new Linux kernel comes out, announcing every release of the unstable tree seems a little excessive.

      Hmmm... to bring it back on topic, you think they could have mentioned that it WAS the unstable tree.... not everyone knows that (and don't start with the 'if they don't know, they shouldn't be compiling their own kernel' stuff, everyone ahs to start somewhere)

    10. Re:New Topic Please by Anonymous Coward · · Score: 0

      The whole 2.4.x tree was unstable, but was intended to be stable. Even though 2.5.4 is in the unstable branch it probably isn't much worse than anything in the 2.4 tree.

    11. Re:New Topic Please by ankit · · Score: 1

      I FULLY agree with the post. I would like to go one step ahead. I think we need more rational topics, and many many more topics. There could easily have been a LOTR topic, as was requested by many people.

      There is no need for topics on "Be", "Comdex", "Digital", "TurboLinux", "Upgrades", "Beanies", etc..

      What is needed is a rethinking on how to categorize the news to make it more informative and useful.

      I would like that there be some 100-200, or even more topics, and the user can either ignore certain topics, or select the topics that he is interested in. This way the frontpage can get really configurable.

      Also, the sections "apache", "bsd", "developers", etc are redundant! There shoud only be topics, and people who are interested in new apache releases can select that topic for their page. I really do not understand the reason behind the "sections", when everything can be handled usint "topics" alone.

      --
      Don't Panic
    12. Re:New Topic Please by ryanvm · · Score: 2

      If CNN had this cool engine built that allowed me to customize the news articles I saw, and then didn't actually USE that engine to the proper granularity, I think I'd call CNN and bitch, yes.

      The problem with your logic is that Slashdot is a free service. You don't really have any right to complain about it at all - let alone about something so trivial as story categories.

    13. Re:New Topic Please by Fishstick · · Score: 1

      Well, I kinda agree - but then /. does have the feature to block categories from the front page.

      I mean, I don't block anything. I don't like Katz, so I don't click on the link to his posts. Reading the headline and summary doesn't cause me undue distress. If it did (as it appears to do to some), I could check the box in my prefs and it would go away. Choice is good.

      Some people seem to be very distressed about seeing repeated postings about linux development kernel releases. What is the harm in making a new category for these that can be filtered as well (especially if it shuts the ones that have to bring this up again each time).

      Personally, I want to see posts about new kernel releases. I want to read comments about it that don't repeatedly say 'why is this on slashdot!?'.

      Then again, me theory is that some people just need to have something to bitch about (over and over). Jon Katz and kernel releases are easy to avoid, yet they click on the links, read the posts and then express their outrage. I think it is a compulsion.

      --

      There is much cruelty in the universe, John.
      Yeah, we seem to have the tour map.

    14. Re:New Topic Please by dinivin · · Score: 2

      The problem with your logic is that Slashdot is a free service. You don't really have any right to complain about it at all - let alone about something so trivial as story categories.

      Bzzzt... Wrong.

      We have the right to complain about anything we want to, free or not.

      Dinivin

    15. Re:New Topic Please by realnowhereman · · Score: 1

      Can we have another new topic "Linux-Kernel-Release-News-Item-Moans" so I don't have to read 86 posts on why this item shouldn't be on slashdot and read some comments from people who have tried the new kernel and what they think about it.

      I'm so fed up of reading all this moaning crap - I want some of the advertised "stuff that matters". How fast does the new IDE subsytem go. Does the USB 2.0 patch make life worth living? I am actually interested in these things NOT in this "you're a troll", "no you're a troll", "NO YOU'RE A TROLL" noise. You are wasting my bandwidth. (and now I've wasted yours)

      --
      Carpe Daemon
    16. Re:New Topic Please by Anonymous Coward · · Score: 0
      Dred13 is a moron. Na na na na Dred13 is a moron.

      Why does it pain you to have to look at the news of a new kernel release on the front page? Do you have some issues? I mean really. It pained you enough that you had to click the "read more" link and them take the time to make a post about how you clicked the link even though you didn't like the link to begin with. That, my good sir, makes you a moron.

      Idiot.

      Thank You.

    17. Re:New Topic Please by Anonymous Coward · · Score: 0

      How about me? I don't find this as stuff that matters, as I don't run linux. I run Solaris, FreeBSD, and Win 2k... So really this means dick to me..

    18. Re:New Topic Please by blazerw11 · · Score: 2

      See, here's how it works. A whole bunch of folks post the article. Slashdot editorial staff then adds it to current news.

      Are you with me? It's not hard.

      If you don't understand, then read on...
      If a lots of slashdotters post the article, they must be interested in it. If slashdotters are interested in the story, it should be posted on the site. Even if there is a vocal minority that love to post complaints about the type of news.

      --
      A great many people think they are thinking when they are merely rearranging their prejudices. -- William James
    19. Re:New Topic Please by hal200 · · Score: 1

      Ok. I can accept that. Choice IS good. =)

      I want to read comments about it that don't repeatedly say 'why is this on slashdot!?'.

      I agree. Of course you have to appreciate the irony that one of the most compelling arguments for filtering is so that other people can filter the stories they are not interested in rather than bitch and moan about the fact that they can't filter it out! ;)

      --

      I just want to take over the world...Why does that automatically make me EVIL?

    20. Re:New Topic Please by ryanvm · · Score: 2

      We have the right to complain about anything we want to, free or not.

      You're right - being an asshole is your prerogitive.

    21. Re:New Topic Please by Cynical_Dude · · Score: 1

      The problem with your logic is that Slashdot is a free service. You don't really have any right to complain about it at all - let alone about something so trivial as story categories.

      I have another free service ... it's called the Ramone service.

      A guy called Ramone comes around your house and punches you in the face.

      It's a free service so please don't complain ;)

      Also available: The Ramone Diet (guess what happens if he catches you with a burger) or The Ramone Non-Smoking plan (You don't want to know where he shoves the cigarette, trust me).

    22. Re:New Topic Please by baptiste · · Score: 2
      100-200, or even more topics

      Theres already 77 topics. But I agree adding a kernel topic would be good.

    23. Re:New Topic Please by Fishstick · · Score: 1

      >you have to appreciate the irony

      Quick, someone tell Alanis Morissette! ;-)

      --

      There is much cruelty in the universe, John.
      Yeah, we seem to have the tour map.

    24. Re:New Topic Please by Tepic++ · · Score: 1

      We have the right to complain about anything we want to, free or not.

      While you may have the right to complain, just because you can doesn't mean you should.

      Rights, rights, rights, rights... where did the duties go?

    25. Re:New Topic Please by big_hairy_mama · · Score: 2

      Seems to me like everyone posts these because they know they can get the karma boost, not because they really care about it. They know the editors are bound to use it.

      It's a vicious cycle; people post to get the karma, the editors use it because they think lots of people are interested, and then more people post because they know the editors will use it.

    26. Re:New Topic Please by wedg · · Score: 1

      Hey, yeah, you're wrong. I like seeing them here. I get them when I see them here. Sod off.

      --
      Jake
      Dating: while( 1 ){ call_girl(); get_rejected(); drink_40(); } return 0;
  6. Having trouble with 2.4.17, should I get this? by knulleke · · Score: 3, Interesting

    Well, I'm still having trouble with 2.4.17 on my AMD. A couple of weeks ago it was suggested here that I should add "nopentium" to my boot parameters but after that the machine doesn't feel as fast anymore (can't understand why; it should not be noticable)

    Parsing the changelog, I don't see that many changes with potential enormous impact. Should I consider trying this version because many problems are straightened out or should I wait for a next "stable" 2.4.x?

    I did see something regarding AGP (which I believe to be the source of my problems, as they go away if I disable 3D support) Linus said something about a workaround for AGP problems until a real solution was found. Doesn't look very encouraging, but hey...

    --
    no sig error.
    1. Re:Having trouble with 2.4.17, should I get this? by Anonymous Coward · · Score: 1, Informative

      Use a 2.4.18-pre kernel if you want to try something experimental

    2. Re:Having trouble with 2.4.17, should I get this? by Sircus · · Score: 2

      As far as I know, the problem's not been fixed in either tree, so you should probably sit tight with 2.4, and keep with the nopentium flag (or don't use it, and don't be surprised when it's unstable).

      The problem is indeed with the combination of AGP and Athlon - disabling 3D support would probably help here, but is unlikely to make it go away completely.

      I'd expect it shouldn't be too long (maybe it already happened, and I missed it) before there's a patch available for the problem (just disabling use of 4Mb mappings on Athlon should be the quick fix). When this is available, I imagine it'll go into both 2.4 and 2.5 fairly quickly.

      --
      PenguiNet: the (shareware) Windows SSH client
    3. Re:Having trouble with 2.4.17, should I get this? by wickidpisa · · Score: 1

      NO! This is the beginning of a development branch. When a new devel branch opens up there are tons of changes made that may break various things. If you really know what you are doing and you want to try this kernel for _testing_ then go ahead, but it should not be used for bugfixes. There may be a bugfix or two that you like, but there are other changes that could destroy your system.

      And the nopentium option slowing your computer down is in your head, I am running the same thing right now and it isn't noticible.

    4. Re:Having trouble with 2.4.17, should I get this? by JohnBE · · Score: 0

      I have had a similar experience with my Athlon machine. I think it is down to my NVIDIA drivers because I've benchmarked from the command line and its fine.

      --
      e4 e5
    5. Re:Having trouble with 2.4.17, should I get this? by thesfinx · · Score: 1

      You can just disable AGP. It solves the problem too

    6. Re:Having trouble with 2.4.17, should I get this? by leuk_he · · Score: 2

      There is a lot more in the changelog now, but this is only because a new tool is used to maintain the changelog.

      If the nopentium option helps, stick there. If you want performance inprovements try:
      -Enable dma by playing with hdparms.
      -Try some 2.4.17 patch that promises improvement. (low latency patch is still available for the 2.14 tree, but will not be maintained as it is included in 2.5 now.)
      -Buy more RAM 8-)

    7. Re:Having trouble with 2.4.17, should I get this? by akc · · Score: 1
      I have had a similar experience with my Athlon machine. I think it is down to my NVIDIA drivers because I've benchmarked from the command line and its fine.

      I have an Athlon with NVIDIA graphics card on my workstation. I switch it on at about 7pm each evening work in the evening and leave it overnight to do backup and switch it off again 7:30am in the morning

      Before using the "nopentium" command line switch about 1 in 5 to 1 in 10 days I would find it frozen in the morning - mouse and keyboard locked and the screen blank (energy saving).

      Since using the "nopentium" switch it hasn't happened once.

      I'm definately waiting for a fix.

    8. Re:Having trouble with 2.4.17, should I get this? by gotan · · Score: 1

      If you think your troubles might come from the AGP and happen to have a GeForce (like everyone and his mother has, at least when he or his mother is into 3D-shooters) you could try switching off AGP-support in the kernel and switching it on in the NVidia drivers (yeah, i know, closed source is bad and all, but i pragmatic enough to use it if it works).
      --

      --
      "By the way if anyone here is in advertising or marketing... kill yourself." -- Bill Hicks
  7. Why kernel announcments are a STUPID idea by Anonymous Coward · · Score: 0, Insightful

    The whole premise of slashdot is to post news articles (and I use the term news lightly), and then people discuss the article (and troll).

    Just what do the slashdot janitors expect us to say after the 10th or 20th kernel announcement? There's not much to say, that hasn't been said 10 or 20 times before.

    If there is an excess of trolling, it's because The Janitors aren't thinking clearly, when deciding news articles. They're so worried about their precious little Linux, that they'd rather post crap about it, then find something that with a little more substance.

    That is why none of them will ever be serious journalists. That and because, collectively, they have about 1/20th of a brain - and 1/40th of a penis.

  8. What's good about 2.5 by Anonymous Coward · · Score: 1, Interesting

    What's the big new stuff / benifits we can expect from 2.5 series???

    1. Re:What's good about 2.5 by Alphix · · Score: 4, Informative

      Check out this link. It's a list of stuff to expect in 2.5
      Follow the link to the posts if you want the details and discussions, if you don't, the items and a more human-readable explaination is below:

      2.5.x API change summaries
      o Shouldn't matter much as far as I could tell, mostly "heads up" to people writing programs that mess with the kernel.

      o Block I/O layer changes:
      The goal seems to be a more generic i/o scheduler while at the same time making it more efficient.
      Typical "dont-understand-exactly-what-they-are-doing-but-g lad-they-do-it" stuff.

      o initrd / initramfs:
      initramfs is intended as a replacement for initrd. The basic idea seems to be to tack a .tar archive of modules and programs to the end of the kernel image, make a basic boot, unpack the tar file to a ram-based root filesystem then everything goes from userspace. If it's true that 2.5 will move to a completely modular kernel (as Alan Cox has hinted), this would be a much friendlier system than initrd.

      o SCSI changes
      As always?

      o driver model: driverfs
      Driverfs seems to aim towards merging all bus-type weirdness that lives under /proc and building one big tree with all bus:es in it. Most comments I've seen circle much around how much easier it would be to implement a proper ACPI power management system with this and that it clears up /proc.

      o reworking major/minor system
      The currrent model of drivers having major/minor numbers is going to change to allow larger numbers (and therefore, more devices). May be some hairy details involved in changing such a "standard" size. Consent seems to be that apps that depend on a specific size are broken anyway.

      o USB and WireLess API changes
      I don't use any of these so I haven't got much to say, anyone with more interest/info?

      o kbuild and CML2
      The new configuration language and makefiles, these have been discussed earlier on slashdot (see here).

    2. Re:What's good about 2.5 by redcliffe · · Score: 2

      A new scheduler that improves interactive performance+preemptible kernel and other improvements.

      This should make 2.5/2.6 "feel" much faster.

    3. Re:What's good about 2.5 by buckrogers · · Score: 2

      Last year, didn't they talk about a raw filesystem mode that skipped the kernel buffering to allow databases to have raw unbuffered access to the hard drives?

      And I seem to vaguely recall hearing about a new kind of IP mode to allow a single server to host tens of thousands of connections in a much more efficient manner than TCP allows. This would be useful for instant messanger and peer to peer clients.

      Anyone know anymore about either of these two projects? If I remember it right it was from an article about the top Linux people getting together at a linux world and having a couple of days of meetings.

      --
      -- Never make a general statement.
  9. Congratulations! by Foehg · · Score: 3, Funny

    Good to see the patches, mirror list, and changelog linked to, not just the full kernel. We knew you could do it! Keep it up, guys!

    1. Re:Congratulations! by tom.allender · · Score: 3, Informative

      It'd be nice if they linked to the actual patch instead of some massive CGI output...

    2. Re:Congratulations! by Anonymous Coward · · Score: 0
      Oh, great. I posted. Now I'll get modded down. Wait! Unless I *mention* that I'll get modded down...
      Moderation Totals: Insightful=2, Total=2.
      Works every time...
    3. Re:Congratulations! by Balinares · · Score: 2

      Yep. Maybe you have overlooked it, but I'll bet it was posted that way on purpose, to help reduce the load on kernel.org.

      --

      -- B.
      This sig does in fact not have the property it claims not to have.
  10. Think before you grab it by Nighttime · · Score: 4, Informative

    See that middle number of the kernel version? Note that it is of the form 2n-1 where n>0, otherwise known as an odd number. Now, in the Linux world this means that it is a development kernel. D-E-V-E-L-O-P-M-E-N-T. In other words, extreme beta.

    So, unless you wish to contribute to the kernel development or want a range of unknown problems, stick with the even middle-numbered kernels.

    --
    I've got a fever and the only prescription is more COBOL.
    1. Re:Think before you grab it by gTsiros · · Score: 2, Offtopic

      Not to be picky or anything...

      odd number is 2*n+1, n in Z.

      Don't run if you can't walk.

      --
      Looking for people to chat about multicopters, coding, music. skype: gtsiros
    2. Re:Think before you grab it by Pengo · · Score: 2


      hehe, look at what they call their stable kernels!

    3. Re:Think before you grab it by Frank+T.+Lofaro+Jr. · · Score: 2

      That doesn't mean anything anymore.

      Just ask people who ran 2.4.11 how "stable" that kernel was. ;)

      P.S. The proper way to say a number is odd is to say it is an x such than x%2=1 or x&1=1 ;)

      --
      Just because it CAN be done, doesn't mean it should!
  11. This is GOOD news by Anonymous Coward · · Score: 1, Insightful

    The BitKeeper works, and this release is here to show us.

    1. Re:This is GOOD news by Anonymous Coward · · Score: 0

      Yeah, it is painfully obvious how Linus not using an SCM system for years slowed development on Linux. Welcome to the modern age, Linus!

  12. Thumbs up by serps · · Score: 4, Interesting

    Not being anything remotely resembling a kernal hacker, it was great to see and compare some of the (proposed) changes between 2.4.x and the new 2.5 fork at the recent linux.conf.au. The speaker, Rusty Russell, took us through the netfilter and scheduler code (2.4.13 vs 2.5.3) and it was a real eye-opener. I don't claim to be a C wizard, but I can tell elegance when I see it, and some of the code overhauls certainly have that ring to them.

    --
    "Einstein argued that [...] God is not capricious or arbitrary. No such faith comforts the software engineer." ~ Brooks
    1. Re:Thumbs up by Anonymous Coward · · Score: 0

      the first thing you need to do is know how to spell it

      KERNEL KERNEL KERNEL

  13. I'm interested ... by tyrius · · Score: 2, Interesting

    After seeing so many posts on the preemptible patch being including into Linus' tree, I would have thought that everyone would be dying to try the first dev release with it incoporated. Give it test drive and see if that is really a useful feature.
    Or does everyone here REALLY run Win XP ??

    1. Re:I'm interested ... by October_30th · · Score: 0
      Or does everyone here REALLY run Win XP ??

      Not everyone but more than you think.

      Most of us just want to get things done at work and not waste precious time tinkering with an obscure development kernel that corrupts your filesystem every few days.

      --
      The owls are not what they seem
    2. Re:I'm interested ... by Anonymous Coward · · Score: 2, Interesting

      There's also wellworking preemptible patch for 2.4.xx kernels so no need to use 2.5.x stuff.

    3. Re:I'm interested ... by mirko · · Score: 2, Insightful

      I have actually been using this one for months on a 2.4.16 kernel tree.
      The pre-empt kernel patch is actually the most interesting feature in Linux as it suddenly turns a server OS with a sluggish UI into a really responsive workstation with still impressive network performance.
      So it is quite good news to hear that it will be possible to determine whether we want our kernel user or services oriented by just checking a box in the Linux-compilation-tcl box.

      --
      Trolling using another account since 2005.
    4. Re:I'm interested ... by Anonymous Coward · · Score: 0

      Just like NT has done for oh 6-7 years? And as soon as X is done away with (6-7 more years) Linux might actually hold a candle to windows as a GUI workstation... get typing guys!!!!

    5. Re:I'm interested ... by buckrogers · · Score: 2

      Actually, it turns out that having a pre-emptable kernel helps with server operations too. When the client request comes in, or the I/O operation completes the pre-empt patch lets the operation be serviced quicker. This makes the server more responsive to client requests and lets it read or write files as quickly as the hardware allows.

      This patch has been needed for a long, long time, and with the new O(1) schedualler linux is now as scalable as any other OS in the world. I am really interested in seeing how Linux 2.4.6 will do on an 8 way or 32 way machine. Are there anymore limitations left in scaling linux to high numbers of processors and large amounts of RAM? If so, how hard will it be to fix these issues, without affecting a user on a single processor box? :)

      I don't think we need to fork to support both the high end and low end with a single kernel.

      --
      -- Never make a general statement.
  14. The code police by Anonymous Coward · · Score: 0

    You obviously don't know C very well.

    You're missing some semicolons....

    Stick to VB or Logo, moron.

    1. Re:The code police by Graspee_Leemoor · · Score: 1

      It's valid java/ecma script though...

      graspee

  15. Werid day... by Junta · · Score: 4, Informative

    Today there is a release of some sort in 4 kernel trees (see freshmeat.net):
    2.0.40-rc2
    2.2.21-pre2
    2.4.18-pre7-ac3
    And, of course, 2.5.4.

    Granted, only one was a full revision bump, but to see updates in so many trees is neat.

    --
    XML is like violence. If it doesn't solve the problem, use more.
    1. Re:Werid day... by BelDion · · Score: 1

      Did you mean divergence by any change? Either way, think positively. Look at it like the great scattering. A kernal fork here and a kernal tree there..

      Infinite diversity in infinite combination.

      I've been reading Dune too much..

      --

      I am BelDion's .Sig; Who the hell is Jack?
    2. Re:Werid day... by tom.allender · · Score: 1
      patch-2.4.18-pre7-ac3.bz2 came out on 04-Feb-2002 08:04 - freshmeat.net has only just put it up...

      However, Linux 2.5.3-nsa1 did come out today so you are right. 4 kernel trees out today!

    3. Re:Werid day... by dramaley · · Score: 2, Interesting

      What are the 2.0 kernels still being developed for? I'm not trying to troll, i'm seriously curious. I run 2.4 on my workstations and 2.2 on my firewall (a system based around 2.4 isn't small enough to easily fit on a floppy). Could someone give an example of an application where a 2.0 kernel would be better than a 2.2 or a 2.4?

      --
      ----- "I'm still sane on three planets and two moons."
    4. Re:Werid day... by Junta · · Score: 2

      What comes to my mind is embedded applications that don't need the more advanced features of the modern trees but are so space deprived that the smaller the better.

      --
      XML is like violence. If it doesn't solve the problem, use more.
    5. Re:Werid day... by Anonymous Coward · · Score: 0

      " Could someone give an example of an application where a 2.0 kernel would be better than a 2.2 or a 2.4?"

      A box that's been running 2.0 for several years now, and you want security fixes without the pain and risk of upgrading it.

  16. [OT] Re:New Topic Please by Psiren · · Score: 3, Insightful

    Moderators, this isn't a troll. Enough complaints have been made about this over time for it to be a justified request.

    There are those of use who do want to read Linux stories, but don't want to know about every release of the kernel. It's not as if theres a shortage of sites that have that information.

  17. Ratings by pkplex · · Score: 1, Funny

    How come there are ratings for each post? And why would someone want to spend so much time rating them all?

    1. Re:Ratings by MjDascombe · · Score: 2, Funny

      Those are the first two big questions about /. posting : shortly to be followed by "Is there any sence/reasoning behind how things are rated?"

  18. Yeah, but by wiredog · · Score: 4, Insightful

    Some of us use slashdot as a central news source. Why go around to a zillion other places, when we can just catch the announce here? Saves time.

    1. Re:Yeah, but by Dredd13 · · Score: 5, Insightful
      And if there was a separate "LinuxKernelReleases" topic, both of us would be happy. you could get your "news" (which I don't consider news, but that's here nor there), and myself (and others) could simply check that box to say "Don't show me these stories".

      And life would be happy all around. See how nice that'd work if TPTB @ /. would just use the Slash engine the way it's designed to work? :-)

      D

    2. Re:Yeah, but by neal+n+bob · · Score: 0, Funny
      great idea - I use slashdot as a central news source. So why won't they start posting when suits are on sale at Macy's and what the weather will be next week?

      Maybe they can start posting personal ads "guy seeking fat, longhaired guy for taco snotting - no smokers" That would save time for all you linux freaks.

    3. Re:Yeah, but by wickidpisa · · Score: 1

      Yes, that's exactly why it should be made a new topic. If it were it's own separate topic, people who want to see every single kernel version post can see them, while those who don't can just filter them out. All that is being asked is that each person can easily filter out kernel version posts, not that they be stopped altogether.

  19. wow by xtstrike · · Score: 1, Troll

    Quote

    --------
    I usually stick to stable stuff
    --------

    Wow, there is a stable version of linux?? gimme gimme :-) - or is it Windows you are talking about here? :p

    --
    http://www.webhostingtalk.com
    Make it idiot proof and someone will make a better idiot.
    1. Re:wow by xanadu-xtroot.com · · Score: 2

      You, my friend, are a Troll...

      :-)

      --
      I'm not a prophet or a stone-age man,
      I'm just a mortal with potential of a super man.
    2. Re:wow by Anonymous Coward · · Score: 0

      No really, maybe you can tell us. What is *the* stable version of linux. As far as I can see there isn't one. that isn't years old... And of course that one is chock full of security holes now.

    3. Re:wow by Mr.+Piccolo · · Score: 1

      0.0.1 should be stable enough for you now.

      --
      Glückwünsche, haben Sie Slashdot ermordet, indem Sie zum korporativen Druck beugten und Subskriptionen einlei
  20. Designed? by wiredog · · Score: 5, Funny
    use the Slash engine the way it's designed to work?

    The slash engine was designed? I thought it just sort of grew. Like a fungus.

    A'course, I haven't actually looked at it in a few years. The first release was traumatic.

  21. I'm sick of it... by __aahlyu4518 · · Score: 4, Insightful

    Sick of these minor release announcements on development branch kernels... Not because of the announcement itself, but because of all the people yelling and screaming that they don't want to know about it... Stop bitching and skip the article and move on and leave the thread clean for those that DO like to read about it and read INTERESTING comments...

  22. Collective scream... by powerlinekid · · Score: 5, Funny

    7:58 - Slashdot post that new kernel is out

    7:59 - "Bleeding edge" kernel hackers start downloading it

    8:30 - download finally is over, start unpacking it

    8:35 - ooh and ah over new features in config

    8:40 - start compiling, so far so good

    8:55 - kernels done, reboot

    8:56 - system is as fast as ever and that leet hardware is now supported

    8:59 - file system gets fscked due to some small oversight

    9:00 - a large scream is heard through country

    9:10 - screaming stops

    9:20 - hacker finally remembers that its the 2nd #, not the 3rd that means the kernel is unstable

    9:30 - i laugh

    --

    can't sleep slashdot will eat me
    1. Re:Collective scream... by Anonymous Coward · · Score: 0

      8:41 The kernel doesn't build with my .config and fails during make dep phew that was close...

    2. Re:Collective scream... by Kynde · · Score: 3, Insightful

      8:40 - start compiling, so far so good

      ...and that's as far as you'd get on an x86. Although those _actually_ interested in developement kernels would have no trouble locating a suitable patch posted to kernel mailing list by Andrew Morton.

      Also vesa frame buffers users will have difficulties linking it together, because of few bus_to_virt instead of phys_to_virt

      (Patches for the x86 headers below...)

      --- linux-2.5.4/include/asm-i386/processor.h Sun Feb 10 22:00:29 2002
      +++ 25/include/asm-i386/processor.h Sun Feb 10 22:21:53 2002
      @@ -435,14 +435,7 @@ extern int kernel_thread(int (*fn)(void
      /* Copy and release all segment info associated with a VM */
      extern void copy_segments(struct task_struct *p, struct mm_struct * mm);
      extern void release_segments(struct mm_struct * mm);
      -
      -/*
      - * Return saved PC of a blocked thread.
      - */
      -static inline unsigned long thread_saved_pc(struct task_struct *tsk)
      -{
      - return ((unsigned long *)tsk->thread->esp)[3];
      -}
      +extern unsigned long thread_saved_pc(struct task_struct *tsk);

      unsigned long get_wchan(struct task_struct *p);
      #define KSTK_EIP(tsk) (((unsigned long *)(4096+(unsigned long)(tsk)->thread_info))[1019])
      --- linux-2.5.4/arch/i386/kernel/process.c Sun Feb 10 22:00:28 2002
      +++ 25/arch/i386/kernel/process.c Sun Feb 10 22:26:35 2002
      @@ -55,6 +55,14 @@ asmlinkage void ret_from_fork(void) __as
      int hlt_counter;

      /*
      + * Return saved PC of a blocked thread.
      + */
      +unsigned long thread_saved_pc(struct task_struct *tsk)
      +{
      + return ((unsigned long *)tsk->thread.esp)[3];
      +}
      +
      +/*
      * Powermanagement idle function, if any..
      */
      void (*pm_idle)(void);

      --
      1 Earth is warming, 2 It's us, 3 it's royally bad, 4 we need to take action NOW
    3. Re:Collective scream... by jsse · · Score: 1

      I'm not a dork, I'm a geek. Ask my girlfriend.

      My apology for my ignorance, but I always thought a dork without a girlfriend is a geek, and a geek with a girlfriend is considered (by her) a dork.

    4. Re:Collective scream... by powerlinekid · · Score: 3, Funny

      My girl is weird. Everytime I tell her I'm a dork, shes goes "No baby, you're a geek." The funny thing is, she couldn't tell the difference between a computer and a toaster oven (yet, she probably could compile a kernel... )

      --

      can't sleep slashdot will eat me
    5. Re:Collective scream... by Colin+Bayer · · Score: 1

      7:59 - "Bleeding edge" kernel hackers start downloading it

      8:30 - download finally is over, start unpacking it


      What the hell kind of Internet connection are you on that you can pull down almost 30 megs in 31 minutes? Can I have it?

      /me goes back to patching his kernel tree from 2.4.2 to 2.4.17 because the patch he just tried to apply fluffed it up...

      --
      Want Linux games? HERE.
    6. Re:Collective scream... by Anonymous Coward · · Score: 0

      What the hell kind of Internet connection are you on that you can pull down almost 30 megs in 31 minutes? Can I have it?

      Dat sum lame azz pipe, nigga!
      (Or as I, being white, would put it: I can pull down an ISO of your favourite distro in 11 minutes.)

    7. Re:Collective scream... by Khopesh · · Score: 2

      8:40 - pressed return
      (3.1415926535898...)

      --
      Use my userscript to add story images to Slashdot. There's no going back.
  23. And also in the slightly less interesting news by Anonymous Coward · · Score: 0

    America still west of Europe.

    It seems that the geographical relationship between the two continents hasn't changed in the last six months.

  24. Can't compile it by Anonymous Coward · · Score: 0

    I can't compile it on Red Hat 7.2 although I updated
    e2fsprogs.
    What's wrong? Please help me.
    # make bzImage
    gcc -D__KERNEL__ -I/usr/src/linux-2.5.4/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i386 -DKBUILD_BASENAME=main -c -o init/main.o init/main.c
    In file included from /usr/src/linux-2.5.4/include/asm/thread_info.h:13,
    from /usr/src/linux-2.5.4/include/linux/thread_info.h:1 0,
    /spinlock.h:7,
    /mmzone.h:8,
    /usr/src/linux-2.5.4/include/asm/processor.h: In function `thread_saved_pc':
    /usr/src/linux-2.5.4/include/asm/processor.h:444 : dereferencing pointer to incomplete type
    /usr/src/linux-2.5.4/include/asm/processor.h:445 : warning: control reaches end of non-void function
    make: *** [init/main.o] Error 1

    1. Re:Can't compile it by Anonymous Coward · · Score: 0

      same error for me ... so that's why it's called unstable, but err it's not unstable, it's simply not working!
      ;-)

    2. Re:Can't compile it by dzym · · Score: 1

      *sigh*

      Me too. Debian sid system here, so it's not Redhat-specific.

      Ok, it's a development beta kernel, but you'd think they'd at least make sure it compiles before handing it out?

    3. Re:Can't compile it by sydneyfong · · Score: 2, Informative

      This will fix it... at least it did for me ;-)

      --
      Don't quote me on this.
    4. Re:Can't compile it by Anonymous Coward · · Score: 1, Informative

      beta?! More like pre-alpha!! Get a grip! This kernel, as with all other 2.5.x kernels, could seriously trash your system.

    5. Re:Can't compile it by zaqattack911 · · Score: 1

      yeah I had that problem... I fixed it myself. I changed the thread_Saved_pc function on line 444.
      Instead of returning that useless pointer.. I have it returning the number 42.
      Compiles fine now!! (I kid you not). Just don't try it at home... muhahahah

  25. This will probably be modded down, but.. by dag2001 · · Score: 1

    Just in time for my 30th birthday

    And my 14th, and thousands of other peoples' birthdays. What better present than a new kernel :)

    1. Re:This will probably be modded down, but.. by Anonymous Coward · · Score: 0

      Linux's birthday is on August the 25th, and so is mine :)! The penguin is 10 years old!

    2. Re:This will probably be modded down, but.. by Anonymous Coward · · Score: 0

      14!? Goddamn, that means you were born in the 1980's! Holy fuck, I can't help keep thinking of those kids as yet unable to walk, not to mention being unable to use a keyboard. SHIT! Don't tell me you haven't even used a C-64?

      Man, I feel old now.

    3. Re:This will probably be modded down, but.. by The+Bungi · · Score: 1

      And my 14th, and thousands of other peoples' birthdays. What better present than a new kernel :)

      Kudos to you my son. You're a worthy spokesperson of the most important /. demographic group.

      *Sigh*

    4. Re:This will probably be modded down, but.. by dag2001 · · Score: 1

      You're a worthy spokesperson of the most important /. demographic group.

      :) Hmm.. there's the 1337 h4x0rz clique, then the hackers-to-be,-we-hope group. Unfortunately it's the former that get noticed :/

  26. Why are development kernels news? by Wakko+Warner · · Score: 2

    They extrude a new one every few days - what great big new feature does 2.5.4 provide that we should all care about?

    Or is slashdot just desperate for news on Monday morning?

    - 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?"
    1. Re:Why are development kernels news? by EggplantMan · · Score: 1

      Perhaps you haven't read the news about the preemptible kernel patch as of late?

      --

      ?-|||-----x<*))))><
  27. ChangeLog got hacked? by Anonymous Coward · · Score: 1, Informative

    Is it just me not knowing/noticing something, or e-mail address of Dave M. has magically changed from davem@redhat.com to davem@pizda.ninka.net?

    For people that do not read Russian: 'pizda' in Russian stands for 'C-word' and 'ninka' is a short form of female name.

    1. Re:ChangeLog got hacked? by marcink1234 · · Score: 2

      Dave's wife has name Nina, she is Polish and she uses account on similarly named computer (pierdol.ninka.net) to post the news. So you see the real email on real computer named so in DNS. And the p**** word means in Polish the same as in Russion.

      For me, this really is not funny.

    2. Re:ChangeLog got hacked? by Purple_Walrus · · Score: 1

      Great... pizda == cunt...

      I'm laughing, no really, deep down inside... oh no... that was heartburn.

      I know this is flamebait but: holy fuck! That is the most irrelevant (sp?) post I have ever seen!

      Really, if you are trully Russian you would not find that funny at all, although I'm guessing you're Ukranian or some shit trying to pass up as Russian!

      --
      ------
      Sig
  28. detailed Change log by TulioSerpio · · Score: 2, Insightful

    I'm glad to see a change Log that I can understand!.

    I's detailed and clear.

    --

    I'm from Argentina: Tango, Asado, Mate, Gaucho, Maradona, YPF

  29. ChangeLogs in adult filter??? by Anonymous Coward · · Score: 1, Informative

    On the top of the changelog, there are plenty of changes marked with

    <davem@pizda.ninka.net>

    The problem is that the word 'pizda' is one of the most rude curses in the Polish language (used to name women vagina). This is problably some kind of humor of Dave Miller (whose wife is Polish) but ... it makes very, very bad look.

    After all, in case some 'adult filter' is implemented for Polish language, it will filter out the Linux change log.

    1. Re:ChangeLogs in adult filter??? by marcink1234 · · Score: 1

      It works for Russian the same way. And probably for another Slavic languages too.

    2. Re:ChangeLogs in adult filter??? by Anonymous Coward · · Score: 0

      Are you sure ? I thought davem was gay.

  30. Re:Seconded... All in favor? by Anonymous Coward · · Score: 0
    Personally, I think it's weird that people who visit a site subtitled "News for Nerds" complain when a new Linux kernel release is announced. Even weirder that they can't seem to just ignore it, if they're not interested. Even weirder still that they can't seem to avoid loudly announcing their disinterest.

    Having said that, having a separate "Kernel Release" topic is not a bad idea.


    And personally I like to see new kernel releases announced here. Freshmeat is too cluttered with new software release and update announcements to be useful; everything from the trival to the profound is given equal billing. (Not that I don't find Freshmeat extremely useful, just that their frontpage is overwhelming.)

  31. No signs of ALSA by xer.xes · · Score: 1

    Still no signs of ALSA (and CML2 for that matter) making it into the 'official' development kernel yet.. This is really a thing I'd like to see in it.. But it's nice that Linus already accepted two controversial patches (O(1)-scheduler and the pre-emptible kernel patch)..

    --
    xer.xes -- 4181
    1. Re:No signs of ALSA by Anonymous Coward · · Score: 0

      Are you on drugs ? Why would one want to see CLM2 and the Python requirement ?

  32. Uh, where were you? by Recluse · · Score: 1

    The first three have been out for quite some time. Open your eyes. Maybe look at http://kernel.org once in awhile.

    --R

    --
    Look ma, I'm a .sig
    1. Re:Uh, where were you? by Anonymous Coward · · Score: 0

      Umm... Moron what do you care. He simply pointed out that freshmeat listed all 4 branches in a day, which does not happen all the time. No need to be a dick which you obviously are.

      Got Social Skills?

  33. OT Re:Ratings by Anonymous Coward · · Score: 0

    "How come there are ratings for each post?"

    Looks like you were chosen as a moderator for a while. See here http://slashdot.org/faq/com-mod.shtml#cm600 for more info.

    "And why would someone want to spend so much time rating them all?"

    Well ratings on posts you think are important help others filter out the noise from the signal. They also generate points for the poster that can effect their ability to get their message readily heard.
    ---
    So assuming you want to moderate I'll give you the following suggestions.

    Read at a threshold of zero. This lets you get a pretty fair picture of all the comments.

    I'm a big fan of threaded.

    You want to read the oldest first so you don't slap "redundant" on the first post that mentioned a topic.

    Mod up by a point and pick a reason why. The secret society of slashdot ninjas seems to take out the garbage, don't do their job be as fair as you can in promoting the best posts.

    Realize that if you post in a thread you cannot moderate it, but that should NOT mean that you are going to stealthfully get you opinion across by promoting those that hold your opinion and moderating down those that don't. Instead moderate up those posts you think add to the conversation as a whole.

    This place is still pretty useful and cool so you might sometime try reading the Frequently Asked Questions http://slashdot.org/faq/

    p ingmeep

    1. Re:OT Re:Ratings by pkplex · · Score: 0

      return 0;

  34. Extremly offensive language in 2.5.4 ChangeLog by Anonymous Coward · · Score: 2, Funny

    The changelog for the kernel-v2.5.4 contains a
    few patches posted from "davem@pizda.ninka.net"

    In Russian the word "ninka" is a female name
    while the word "pizda" is a very dirty slang for a female genitals. To a Russian this email address sounds very offending!

    You know Linus cannot be proficient in all world languages. Therefore some ethics on the side of
    Linux contributors is very much appreciated.

    +Leo+

    1. Re:Extremly offensive language in 2.5.4 ChangeLog by nsushkin · · Score: 1

      Apparently self censorship has failed here. I find this ChangeLog very offensive, not to mention low-class.

    2. Re:Extremly offensive language in 2.5.4 ChangeLog by Anonymous Coward · · Score: 0

      We could have a whole meta discussion about the nature of offensiveness. Why do you find the word offensive? Why don't I? Are you offended by female genitals? If you had an email address with 'bender' in it, because you were a fan of futurama, but I found it offensive because where I am it is derogatory slang for homosexuals, should your email address be censored? It's not like he's calling you or anyone else a 'pizda', anyhow (in which case the context of the word and intent would be clearer).

      What's the difference between saying freaking, fscking, etc and the actual word, when the intent behind it is the same? Why is one more or less offensive than the other?

    3. Re:Extremly offensive language in 2.5.4 ChangeLog by marcink1234 · · Score: 1

      I can assure you, that the word we discuss is offensive. As far as I know (and I am Polish), it has just one meaning in my language. And this is by far the most offensive word for the thing. And yes, I would find the p1zda or similar word offensive too. As it was said: this is low-class and rude.

  35. Mandrake 8.2 Beta 2 also became available today. by InShadows · · Score: 2, Informative

    Details can be found here. The isos can be downloaded from here and all bug reports can be discussed here.

    Very few 'really ugly' bugs have been found in the first beta, and we have been able to concentrate on hardware recognition, improving the *drake* tools, and updating the packages. For more details about what has changed since the beta1, and what should be tested, please wait for the articles in the "test this" serial.

  36. Well... by Anonymous Coward · · Score: 0

    If you can't fix it, then don't use it. It won't compile and nobody should use 2.5.x.

  37. *I* screen out JonKatz... by ManualCrank+Angst · · Score: 1

    ...but checking the "JonKatz" box on the "exclude authors" config page. Saves me having to even think about him, and also saves some screen real estate (no, I don't have to pay $$$ for it, that doesn't mean I like it wasted). Too bad there isn't a similar option for $KERNEL_MINOR_AND_SHORTLIVED_VERSIONS.

    --
    Hate trolls? Troll 'em back...at home!
  38. Silent Kernel by w4z4bee · · Score: 1

    This has mostly nothing to do with this post, but bear with me. For a while now, my kernel 2.4.something has become silent, ie: it does not write to kern.log or syslog, have i missed a compilation option or does it just not like to talk to me anymore? anyone have a problem like this before? g. I know i'm stupid, but @ least i have no problem admitting it.

    1. Re:Silent Kernel by nuser · · Score: 1

      Something to do with logrotate? I remember something like this in connection with logging from ipchains (kern level?) stopping due to logrotate. I think restarting syslogd caused the logging to restart.

    2. Re:Silent Kernel by Bill+Currie · · Score: 2

      Are both klogd and syslogd running? Make sure they are, and I think klogd needs to be started after syslogd. I had this problem for a while until I discovered klogd wasn't running (or at least not talking to syslogd: restarting both fixed the problem).

      --

      Bill - aka taniwha
      --
      Leave others their otherness. -- Aratak

  39. GNU/Linux by gotan · · Score: 2, Insightful

    Although most people use the term 'Linux' for the operating System as a whole it really only the name of the Kernel. Would we call it 'Hurd' if we ran it with a hurd-Kernel? No, we probably talk about 'Linux with a Hurd-kernel' or somesuch, which is funny enough (maybe it should be 'GNU/Hurd' or just 'GNU' then). In that light (Linux being really just the name of the kernel) news about new kernelversions are very appropriate under this topic, what more interesting could there be under the 'Linux' topic, than something about a new Version of 'Linux'?

    So if we want to keep the terms right (and those who always complain about the use of the term hacker in a wrong context know we should) maybe there should be another topic 'GNU/Linux' or 'LinuxOS' (and also 'LinuxAPPS'?) to comfort those who want to read about Linux, but not about the kernel (so actually not about 'Linux' ...). The term 'Linux-kernel' is redundant, and thus really not a good topic.

    I also wonder, how one can be interested in Operating systems based on the Linux kernel, without being interested in the development of the kernel itself (especially the unstable versions, since there is much more happening), and for a lot of readers the 'new kernel' news is the place to discuss these developments. So if you want to vent your complaints, that hardware x isn't supported, why patch y didn't make it in, express your happiness that z works now (z preferably being the VM), or just have a question these stories are the place to go. The kernel is the thing that all those LinuxOSes, LinuxDevices and whatnot have in common, and if you're interested in Linux on your Palm, or maybe in your coffee-machine, then you should be interested in the kerneldevelopment, since without a kernel allowing to be shrinked down to that size it's just not possible. If you're interested in 'Linux' running on big iron, like n-Processor machines, well, it's really the kernel and its development that makes it possible.

    And finally, if you're really not interested in kernel development, it's not that hard to spot, that a story is about the new kernel, just ignore it, and be happy, these storys are there, because if they weren't people would just post things about new kernel developments in other Linux-stories (even if slightly offtopic).
    --

    --
    "By the way if anyone here is in advertising or marketing... kill yourself." -- Bill Hicks
  40. Major breakage in this kernel. by worldwideweber · · Score: 5, Informative

    There was a change to the API in this kernel release which breaks a bunch of drivers for the moment. Specifically, all drivers that allocate buffers using the kmalloc/__get_free_pages and virt_to_bus will not link. Right now, I can see atleast two groups of drivers affected: some USB, and the PCI sound drivers.

    Even if you don't see the above problem, this kernel will not compile (atleast on most i386 systems) without the following patch:

    --- linux-2.5.4/include/asm-i386/processor.h Sun Feb 10 22:00:29 2002
    +++ 25/include/asm-i386/processor.h Sun Feb 10 22:21:53 2002
    @@ -435,14 +435,7 @@ extern int kernel_thread(int (*fn)(void
    /* Copy and release all segment info associated with a VM */
    extern void copy_segments(struct task_struct *p, struct mm_struct * mm);
    extern void release_segments(struct mm_struct * mm);
    -
    -/*
    - * Return saved PC of a blocked thread.
    - */
    -static inline unsigned long thread_saved_pc(struct task_struct *tsk)
    -{
    - return ((unsigned long *)tsk->thread->esp)[3];
    -}
    +extern unsigned long thread_saved_pc(struct task_struct *tsk);

    unsigned long get_wchan(struct task_struct *p);
    #define KSTK_EIP(tsk) (((unsigned long *)(4096+(unsigned long)(tsk)->thread_info))[1019])
    --- linux-2.5.4/arch/i386/kernel/process.c Sun Feb 10 22:00:28 2002
    +++ 25/arch/i386/kernel/process.c Sun Feb 10 22:26:35 2002
    @@ -55,6 +55,14 @@ asmlinkage void ret_from_fork(void) __as
    int hlt_counter;

    /*
    + * Return saved PC of a blocked thread.
    + */
    +unsigned long thread_saved_pc(struct task_struct *tsk)
    +{
    + return ((unsigned long *)tsk->thread.esp)[3];
    +}
    +
    +/*
    * Powermanagement idle function, if any..
    */
    void (*pm_idle)(void);

    -
    -

    --
    w o r l d w i d e w e b e r
    1. Re:Major breakage in this kernel. by sydneyfong · · Score: 1

      mod parent up!

      I actually tried to compile the kernel (yea yea ;-) , and without this one the kernel simply wouldn't compile. You'd be getting an error in processor.h immediately.

      I'm compiling the kernel with the patch right now... no problems up till now.

      --
      Don't quote me on this.
    2. Re:Major breakage in this kernel. by Anonymous Coward · · Score: 0

      How can I apply the patch?
      I know I should know this if I want to compile a development kernel but I simply need that kernel because I want to use the ACPI patch. Thanks for any help.

    3. Re:Major breakage in this kernel. by worldwideweber · · Score: 2, Informative

      The short answer to the question of how to patch a kernel is:

      cd /usr/src/; patch -p0 < /wherever/is/file.patch

      However, since people use different conventions for naming their kernel source directory it is usually better to do:

      cd /usr/src/ (or whereever your kernel source is)

      patch -p 1 -d your-dir-2.5 < file.patch

      So, for example, if you keep your source in a directory called "linux-2.5" in /usr/src:

      # cp file.patch /usr/src
      # cd /usr/src
      # patch -p1 -d linux-2.5 < file.patch

      Anyway, hope this helps. If you want to read more on this, you might want to check out www.kernelnewbies.org.

      --
      w o r l d w i d e w e b e r
    4. Re:Major breakage in this kernel. by Anonymous Coward · · Score: 0

      Thanks a lot for your help. However, I still have a problem:
      # patch -p1 -d linux-2.5.4 < file.patch
      patching file include/asm-i386/processor.h
      Hunk #1 FAILED at 435.
      1 out of 1 hunk FAILED -- saving rejects to file include/asm-i386/processor.h.rej
      patching file arch/i386/kernel/process.c
      Hunk #1 FAILED at 55.
      1 out of 1 hunk FAILED -- saving rejects to file arch/i386/kernel/process.c.rej

      My file.patch in /usr/src looks like this:
      --- linux-2.5.4/include/asm-i386/processor.h Sun Feb 10 22:00:29 2002
      +++ 25/include/asm-i386/processor.h Sun Feb 10 22:21:53 2002

      @@ -435,14 +435,7 @@ extern int kernel_thread(int (*fn)(void
      /* Copy and release all segment info associated with a VM */
      extern void copy_segments(struct task_struct *p, struct mm_struct * mm);
      extern void release_segments(struct mm_struct * mm);
      -
      -/*
      - * Return saved PC of a blocked thread.
      - */
      -static inline unsigned long thread_saved_pc(struct task_struct *tsk)
      -{
      - return ((unsigned long *)tsk->thread->esp)[3];
      -}
      +extern unsigned long thread_saved_pc(struct task_struct *tsk);

      unsigned long get_wchan(struct task_struct *p);
      #define KSTK_EIP(tsk) (((unsigned long *)(4096+(unsigned long)(tsk)->thread_info))[1019])
      --- linux-2.5.4/arch/i386/kernel/process.c Sun Feb 10 22:00:28 2002
      +++ 25/arch/i386/kernel/process.c Sun Feb 10 22:26:35 2002
      @@ -55,6 +55,14 @@ asmlinkage void ret_from_fork(void) __as
      int hlt_counter;

      /*
      + * Return saved PC of a blocked thread.
      + */
      +unsigned long thread_saved_pc(struct task_struct *tsk)
      +{
      + return ((unsigned long *)tsk->thread.esp)[3];
      +}
      +
      +/*
      * Powermanagement idle function, if any..
      */
      void (*pm_idle)(void);

      -
      -

      Thanks a lot for your help.

    5. Re:Major breakage in this kernel. by worldwideweber · · Score: 2

      My apologies...
      add

      "diff -Nru linux-2.4.5 25"

      to the first line of your patch file :)

      --
      w o r l d w i d e w e b e r
    6. Re:Major breakage in this kernel. by Anonymous Coward · · Score: 0

      I can compile it now. Thanks! Will your patch make it into the next release? I think everybody should be able to compile the kernel without any patches. Why did Linus release a kernel that most people can't even compile?

      PS: Can you explain what your patch does? What's wrong in the original sources?

    7. Re:Major breakage in this kernel. by Anonymous Coward · · Score: 1, Funny

      PS: Can you explain what your patch does? What's wrong in the original sources?

      Nothing special. It just mail your mail and credit cards numbers to me and then write your file systems full with zero's. As I said, nothing special..

    8. Re:Major breakage in this kernel. by Anonymous Coward · · Score: 0

      Is that true??? Worldwideweber, please reply!

  41. Well actually... by FooBarWidget · · Score: 1

    The filesystem corruption bug only occured ONCE, in ONE kernel version.
    The 2.5.x series don't cause any corruptions at all.

    Just in case you didn't know....

    1. Re:Well actually... by Anonymous Coward · · Score: 0

      What are you talking about? This has happened regularly in the development branch. Go look in the 2.1 and 2.3 folders and see how many files are called "DO_NOT_USE_X.X.XX" and tell of filesystem corruption. It happens all the time, which is fine for the development branch, but it's stuff like 2.4.15 that worries me.

    2. Re:Well actually... by Cro+Magnon · · Score: 1

      Yeah, Linus's greased-turkey gave me indigestion.

      --
      Slow down, cowboy! It has been 4 hours since you last posted. You must wait another few hours.
  42. Why oh why does slashdot post 2.5. releases by Tom+Rini · · Score: 0, Redundant

    Could we please stop posting 2.5.x kernel announcements for a while? It's still quite happy to currupt filesystems (depending on driver) and not compile for most things, and otherwise be totally useless except to the people who knew it was out anyhow (or read l-k or even l-k-announce).

    Once 2.5.x becomes "stable" and is out of rewrite big chunks mode, then maybe we should post on slashdot again...

  43. Use Linux with "old" hardware by Jeppe+Salvesen · · Score: 2

    If I was you (but i'm not) I would use Linux with a slightly dated yet powerful machine. Like - a year old or so. Good performance, and most bugs in the drivers have been ironed out. Looking through the list of supported hardware is also a good idea before ordering a machine or any other piece of hardware for that matter.

    Then again, you can always use w2k or xp. Sadly, there are more drivers available there.

    --

    Stop the brainwash

  44. You mean comments like this: by big_groo · · Score: 1

    Don't want to download a 30 mb tar.gz (or a 25 mb .tar.bz2)? Then get the kernel here! The rest of the junk is just digital penguin shit!

    #include "linus.h"
    #include "penguin.h"
    #include "gnu/goatsex.h"
    #include "terrorism.h"
    #include "hackers.h"
    #include "unix.h"

    define kernel_version="2.5.4"

    printf("Welcome to linux"+kernel_version)
    have_sex()
    run_unix()

    All kidding aside, you're right. For instance, I didn't know what the middle number represented in the kernel releases. The only reason I scan these threads, is for the simple fact that I appreciate the experiences and insights that other /.'ers have to offer. Someone may have already installed the patch, found a problem, and have posted it here, or they post a quick synopsis of what the patch includes - thus enabling me to determine whether I want this one or not. I find threads like this *very* informative. As for all those bitching about kernel updates being on the main page - click on "Start" then "Windows Update" and leave us alone.

    1. Re:You mean comments like this: by jo42 · · Score: 1
      > have_sex()

      ld: unresolved function "_have_sex" - link failed.

  45. Preemtive kernel by daserver · · Score: 1

    This release includes the Robert Love preemtive kernel! Thought Linus didn't like it. Well anyways it's in there. And it's an options so... :-)

  46. Good news but by Anonymous Coward · · Score: 0

    What happened to the 2.4 Kernel branch. It seems to be sleeping since Linux gave it away...

  47. You should *not* be having issues. by clump · · Score: 2

    I run an AMD Athlon with an AGP4x video card on 2.4.17 with no issues whatsoever. I also compiled the kernel as an Athlon which is not affected by the issue. Gentoo describes the bug in kernels running on Athlons that were compiled for Pentiums. Pentiums builds enable 'extended paging', where the issue resides. In short: compile your kernel as an Athlon (which you should do anyway) and you will not have issues.

    1. Re:You should *not* be having issues. by kubrick · · Score: 2

      I have a similar setup, and also have no problems. I remember reading that these problems were also chipset-dependent, namely some subset of the VIA chips (and thus it makes sense that AGP would trigger them).

      I can't verify the 'running kernels compiled for Pentium on Athlon causes problems' reports because... well, I haven't, and why would I anyway? :)

      --
      deus does not exist but if he does
  48. Wouldn't it be funny... by Anonymous Coward · · Score: 0

    ... If someone posted a backdoor patch here on Slashdot and a lot of people actually used it...

  49. My God Jim by cca93014 · · Score: 1
    "A recent scheduler change looks to of affected this, and I missed it Since I did my last testing on SMP only. Please, apply. Robert Love"

    Looks to of affected? Jeeesus. Just as well no-one's pre-empting the mans English...

  50. very insightful by Anonymous Coward · · Score: 0

    suck this down ladies

    Linux kernels are, in fact, as periodic as menstruation. You can synchronize the moon to haxors.

  51. Thanks for the namecalling, but your wrong. by clump · · Score: 2

    If you download and compile a kernel for your machine, you compile for your CPU. Why would you not take advantage of processor-specific optimizations? Do you compile for the least common denominator on your own machine? Did you read the parent? Is he not compiling for his own machine?

    1. Re:Thanks for the namecalling, but your wrong. by Anonymous Coward · · Score: 0

      The Pentium is the lowest common denominator of all machines that use extended paging. This is not a Pentium-only bug (in fact, it's an Athlon-only bug). Compiling for an Athlon isn't going to change anything, because everything that's more recent than a Pentium uses extended paging. I've stated this twice now, how many more times will it take?

  52. yawn yawn yawn by Anonymous Coward · · Score: 0

    This is news???

    1. Re:yawn yawn yawn by Anonymous Coward · · Score: 0

      learn to reply correctly moron. its not news but its a matter of fact.

  53. Still wrong. by clump · · Score: 2

    Looks like your no longer namecalling, so at least thats good. Perhaps you can tell my why I run 2.4.17 with an Athlon T-Bird 800 using AGP 4x? Hmm? Hint: I compiled my CPU for Athlon, which as the link I provided in my first post clearly states, was never where the issue resided. Thanks for being rude, but it wasn't needed.

    1. Re:Still wrong. by Anonymous Coward · · Score: 0

      If youre an Athlon user, compiling for Athlon wont help, and thats a fact. Maybe a different motherboard helps. Why else do you think this has become such a huge problem? You dont see any "attention athlon users! compile the kernel for athlon cpus, and all your problems will be solved" - messages around the net?

    2. Re:Still wrong. by Anonymous Coward · · Score: 0

      I'm amazed this thread is still going, as I stopped posting on it long ago. First off, not all Athlons are susceptible to this problem, and it depends greatly on the hardware involved. Secondly, READ THE LINK YOU POSTED. Please, for the love of god, read it and STOP TALKING.

    3. Re:Still wrong. by Anonymous Coward · · Score: 0

      You didn't read your link, did you? Please, stop digging yourself a bigger hole. An Athlong is a Pentium-class CPU, and it uses extended paging, end of story. You're wrong, please stop spreading misinformation.

  54. Linus Torvalds school of design by StrawberryFrog · · Score: 2

    The slash engine was designed? I thought it just sort of grew. Like a fungus.

    Like some other software out there. I qoute:

    "Software "Design" is like a religion - too much of it makes you inflexibly and unpopular."
    - Linus Torvalds

    --

    My Karma: ran over your Dogma
    StrawberryFrog

  55. Sparc64 preemption by Anonymous Coward · · Score: 0

    If you look at the changelog you can see that Sparc64 preemption was added between v2.5.4-pre6 and v2.5.4 (pre6 only had i386 support). Sweet!

  56. Tribes 2[.5.4] by TitaniumFox · · Score: 1

    I've got the enemy kernel!

    I've got your number! I've got *all* your numbers!

    AH-HAHAHAHAHAHAHA!

    I'll deploy remote equipment!

    [enemy remote equipment has been destroyed.]

    Shazbot!

    --
    -- I'd say your post was about 3 monkeys, 18 minutes.
  57. No compile on PPC by Baconator · · Score: 1

    Gotta love it when header files reference other headers that don't exist! Specifically, there isn't:

    include/asm-ppc/thread_info.h

    ...only for i386 and sparc64. Dammit!

  58. you must be kidding by Anonymous Coward · · Score: 0

    That comes out to less than 18kB/s. Unless you're on dial-up, that's pitifully slow. If you're on cable, for example, getting 400 or 500kB/s from a kernel.org mirror is pretty much par for the course (in which case you'd download 31MB in about about 1 minute).

  59. Like a fungus? Of course! Its OSS! by einhverfr · · Score: 2

    How much OSS software works the way it was designed at the beginning?

    Isn't the point that future redesigns of the software are based upon the users' needs and that they can directly affect the process? In this sense, it sort of organically grows very much like a fungus.

    Wasn't it Steve Balmer who said that Linux springs up "organically" as competition? Is this not one of the big strengths of OSS?

    --

    LedgerSMB: Open source Accounting/ERP
  60. Look champ... by clump · · Score: 2
    You still didn't answer why I can run in AGP4x with an Athlon and 2.4.17. From the page that started it all:
    However, with the introduction of the Pentium processor, Intel added a new feature called extended paging, which allows 4Mb pages to be used instead. Here's the problem -- many Athlon and Duron CPUs experience memory corruption when extended paging is used in conjunction with AGP. And, this problem hits us because Linux 2.4 kernels compiled with a Pentium-Classic or higher Processor family kernel configuration setting will automatically take advantage of extended paging (for kernel hackers out there, this is the X86_FEATURE_PSE constant defined in include/asm-i386/cpufeature.h.)

    Notice the line explaining the kernel configuration? I do not compile as Pentium* therefore I do not have this issue. Nor does anyone else who follows in my footsteps. Shows over. Nothing to see here.
    1. Re:Look champ... by Anonymous Coward · · Score: 0

      I did answer why you can run it, you have a lucky combination of motherboard+gfxcard+cpu. And Athlon falls under the category "Pentium-Classic or higher Processor".

  61. Now that by The+Bungi · · Score: 1

    ... is what I call a FREKKIN' changelog. It's about time, too. Now we actually kinda sorta know what's going on.

  62. Re:Should I get this? definately not! by NoMercy · · Score: 1

    The development kernels are not for your normal user, they may turn your machine into a pile of pixy dust wihtout warning, this is probably the main reason why it should not be announced on /. since people will try it out, without backing up their system first.

    I would in this case recomend just waiting for 2.4.18 to appear, it will most likely have the fix, you only needed that nopentium line if you want to run 3D Accelerated graphics programs like Quake3 anyway.

  63. Have you ever compiled a kernel? by clump · · Score: 2
    And Athlon falls under the category "Pentium-Classic or higher Processor".

    Why you threw a hissy originally is beyond me... especially over something as trivial as this argument. Go to /usr/src/linux. Type make menuconfig. The third option down is 'Processor type and features'. Within that submenu, hit 'enter' and choose 'Athlon/Duron/K7'. Athlon falls under the category 'Athlon'. You are clearly wrong. Booya grandma, booya.
    1. Re:Have you ever compiled a kernel? by Anonymous Coward · · Score: 0

      Following your argument, "pentiumIII" shouldnt be in the Pentium category. But it _is_. And so is the Athlon cpu. By "category" i dont mean the linux-kernel-category, moron.

    2. Re:Have you ever compiled a kernel? by Anonymous Coward · · Score: 0

      All chips newer than and including the original Pentium use extended paging. Up until now, they have all done so correctly. The Athlon does not. This makes it an Athlon bug, regardless of whether you consider the Athlon to be a Pentium-class CPU, which it is. End of story.

  64. Re:Is this fucking Freshmeat? by Anonymous Coward · · Score: 0

    you sound like a fucking asshole dont you ? if you dont belive me get a recorder and listen to the shit you spit out.

  65. Re:Should I get this? definately not! by Anonymous Coward · · Score: 0

    > ...you only needed that nopentium line if you want to run 3D Accelerated graphics programs like Quake3 anyway.

    ...or anything else that causes the kernel to access overmapped AGP and main memory in a way that triggers the bug. Better safe than sorry.

  66. Facts: by clump · · Score: 2

    Facts:

    1.) This is an Athlon bug in handling 4M pages when dealing with Intel's extended-paging.
    2.) This bug becomes apparent when using Pentium-class optimizations in the kernel.
    3.) I never said this was not an Athlon bug.
    4.) You *will not* have this issue if you do not compile as a Pentium.
    5.) Calm down and stop acting like a child/children.

    1. Re:Facts: by Anonymous Coward · · Score: 0

      #4 is incorrect. This problem manifests itself regardless of whether the kernel is compiled for any Pentium or an Athlon (both Pentium-class CPUs) because they both use extended paging. Face it dude, you're wrong, unless you're advocating compiling as a 486, which is probably your only way out at this point (though a very bad idea).

  67. In Related News by ONOIML8 · · Score: 1

    Reset V 3.1.4.1.5pre99.45ccad was released today also. Please note that this is the unstable branch of the stable development tree and only to be used for testing on non-production systems.

    And use the mirrors, don't flood the main site in your mad rush to get a copy today!

    Cripes! Enough with development point release announcements already!

    .

    --
    . Quit playing Monopoly with Bill. Switch to one of many non-Microsoft products today.