Slashdot Mirror
Linux 2.4.18 Released
Kourino writes: "Marcelo
announced the release of 2.4.18 a couple hours ago after 4 release candidates, but the tree marked 2.4.18 on kernel.org is
missing the -rc4 patch that finally made the kernel releasable. Basically, what's marked as 2.4.18 is really -rc3, and what's marked as -rc4 is what should have become 2.4.18. According to Marcelo on #kernelnewbies, most users won't be affected, but people on SPARC systems should definitely grab 2.4.18-rc4. Your best bet is probably just to get 2.4.17 and patch to 2.4.18-rc4. Seems 2.4 is destined to be an "interesting" release branch ^_^; For the new release, head over to your favorite kernel.org mirror. (Marcelo will set things straight in 2.4.19-pre1.)"
C'mon, we're all friends here. Lets just forget this mess ever happened and relabel 2.4.x rightfully as 2.3.
So? Underwhelming, to say the least.
Major revs. Update us on the kernel for major revs. Don't tell us every time it gets incremented by 0.0.01
Perhaps you would like to add some detail.
"It corrupts your filesystems is useless".
Does it corrupt ext2fs, reiserfs... what fs type? or is it *all* filesystems. Please expand on your comment.
I want the new MS OS killer... 2.4.666
It seems that Sun is now 20 years old. Happy Birthday Sun. So on its birtday it get a nice new Linux patch for its platform. Ok everyone Dig out your old Sparc 2's and install you Linux kernel.
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
Thanks, now that I've done that, I expect everyone else to show a little restraint and not clutter the board with your same old whiny bullshit. If you must post to get self-validation, try making up a story or something.
Liberate your mind in two clicks or less.
Basically, what's marked as 2.4.18 is really -rc3, and what's marked as -rc4 is what should have become 2.4.18. According to Marcelo on #kernelnewbies, most users won't be affected, but people on SPARC systems should definitely grab 2.4.18-rc4.
Wow. Now that's professionalism, eh? Good thing that this whole Open Source badge makes it all okay.
Would the fifteen second delay to rename a couple files before release really have killed anyone?
--saint
I'm sorry, but this is the worst article I've read all day. There is a new release, but it's not the actual release unless you're using some certain hardware and in that case you want to actually patch the last release?
No, he said "i corrupts your filesystem", obviously meaning that he, the AC, corrupted your filesystem.
He is obviously an Evil Hacker(tm) or Terrorist(tm). We must contact the FBI immediately!
> Load code did not set personality for
> binaries without an interpreter: This was
> breaking static apps on several archs
Okay, but Which architectures does this affect? It might be nice to know.
the tree marked 2.4.18 on kernel.org is missing the -rc4 patch that finally made the kernel releasable. Basically, what's marked as 2.4.18 is really -rc3, and what's marked as -rc4 is what should have become 2.4.18. According to Marcelo on #kernelnewbies, most users won't be affected, but people on SPARC systems should definitely grab 2.4.18-rc4. Your best bet is probably just to get 2.4.17 and patch to 2.4.18-rc4. Seems 2.4 is destined to be an "interesting" release branch ^_^;
I've had enough kernel problems in the past. The degree of uncertainty presented around this latest Kernel doesn't inspire a whole lot of confidence.
Think I'll hold off for a while, thanks.
Wouldn't it have been smarter to create a proper Linux-2.4.18.tar.gz (and bz2), and update the kernel.org and mirror sites, and THEN post to Slashdot and other such places?
This is just going to confuse people!
Unless this kernel patched it - the only way I could get any 2.4.x kernels running on older sun hardware (like in my case sun4m systems) was to enable smp support - even if you only have one cpu. I found that if it wasn't enabled the kernel would hang on startup.
2.4.17 is actually quite stable on my old SS20's - one of which is doing firewall stuff right now on att broadband.
Microsoft is advertisng on slashdot, no joke! Heres the truth
Here's the ChangeLog.
That was quick. (It includes a lot more stuff than just the patch missing from rc4).
They could have done it during the 20 second posting period.
You've all heard this before, but that way people who aren't particularly interested in minor kernel revisions but are interested in general Linux stories can filter away the linux kernel topic.
Has anybody addressed the amd cache coherency bug? I'm still booting with mem=nopentium. That makes me sad.
jeremy
I believe the problem is on sparc64 (and not sparc32). It's a trivial patch... just a few lines, so it's easy to have been overlooked.
Anyone using a SPARC/Linux machine that wants the latest and greatest should always turn to the
vger.samba.org sparc/linux kernel cvs tree. It's always got the latest stuff for both 64-bit and 32-bit SPARCs (and networking as well).
That said, 64-bit SPARC machines should run fine with the recent kernels. For the 32-bit SPARC machines, I can only comment on the sun4m and sun4c machine. Currently, the sun4m machines should boot and be ok... the sun4c machines do not.
sun4m machines: ss20, ss10, ss5, ss4, lx, classic, javastations
sun4c machines: ss2, ss1+, ss1, ipx, ipc, slc, elc
Well, karma whoring is pretty lame.
On the top right of the page a little box giving the current kernel version and the date/time of the change when you click on it you can get to its message board. That way you guys can get your Kernel Fix and read about your problems and us people who dont update the kernel in the main messages. I like getting news about Linux and Also Major Kernel versions. But all these little ones gets annoying. It seems like if anyone really want to post a story with there name on it they keep two browsers open and one refreshes kernel.org untill a version apears and then they post a message stating that. Say I can make a script to do that. (But I wont)
If something is so important that you feel the need to post it on the internet... It probably isn't that important.
Appearantly, the missing piece from -rc4 is only missing from the patch, NOT the full tarball.
There's a report on linux-kernel that the 2.4.18 tarball is actually ok.
& m=101 467401412021&w=2
Has anyone had an opportunity to check?
Here's a link to the chap saying it's ok:
http://marc.theaimsgroup.com/?l=linux-kernel
whether the Linux underwear for this version has been released yet.
What is an ideal release frequency for one point in this space, is not at another.
At one point I worked at a DOS extender company (Rational Systems, not related to Rational of California), and we released the software every week. The system was small, the team was small, the customers were very sophisticated, and the value of adding new features was very high. We were praised for being responsive. Three years later, the software was much bigger, the release cycle was down to 2 times a year, and the value of not adding new bugs to the old features was very high. We still got good marks for technical support.
Unlike most commercial software, it's hard to point at revenue streams for Linux that justify the midlife software development expenses like full-time, paid-for, this-isn't-fun-but-it-has-to-get-done release engineering. Although there is a large virtual software team for this OS, I strongly suspect that there is less infrastructural support than you get with old fashioned, iron vendor supported systems like Solaris, HP-UX, et al. TANSTAAFL, folks.
Don't get me wrong, I use Linux daily, my servers run on it, and I depend on a variety of other open source software (particularly Python!). I even buy RedHat/KRUD releases just so that some value flows back into the release process from a happy recipient. But I sometimes feel like holding my breath while installing that next kernel release!
TANSTAAFL -- There ain't no such thing as a free lunch. Thanks, RAH, wherever you are!
2.4.18 with rc4 applied seems to be a stable, well-tested kernel that has gone through all the testing needed for a release. It deserves its own kernel version number. Since 2.4.18 is not-quite-right, why not just make what was going to be 2.4.18 into 2.4.19?
If you must post to get self-validation, try making up a story or something.
I'd agree with you if the editors didn't reject every damn story submitted. Lots of interesting stuff gets let go, but editors ALWAYS seem to make sure that a patch level kernel release gets posted. It's silliness. The editors here are just too pigheaded for users to submit interesting stories and get them known. Disagree? Stupid crap like this Linux-newbie question gets posted while intelligent topics get thrown out.
The only option is to whine about the stories that do get posted.
Why bother.
Marcelo Tosatti proved once again he can't do the job. Don't waste your time with 2.4.18. Use the last -ac or wait for 2.4.18-ac1.
use *BSD instead. that's not dying (unlike linux)
is my IP unbanned yet?
Why can't they just rename the files?
I mean, these people make operating systems, right?
hehe... its funny to see the ^_^ smiley becoming mainstream.
^_^
Joseph?
I strongly disagree - I think the most interesting linux news is when the new kernel releases come out. I think this should be a slash poll to see what everyone else thinks.
If you have a Cyrix III 1Ghz and a VIA southbridge controller, you must have the -rc4 .
IT'S CALLED KNOWLEDGE. It's nice to be able to read a quick reply that tells me w/o going to an archive whether or not I am going to use the kernel on the servers. Especially when the following link is omitted from the article.
Kernel 2.4.18 Changlog
If they are separate, then you still can get both. He's asking for the CHOICE. Then, if you don't want the Linux Kernel news, you can just go and uncheck it in your preferences. If you want continue to get both, you don't have to do anything.
what to expect now.
/. /. effect and getting max. karma
1 post to a domain starting with goa...
2 posts claiming *BSD is DEAD! (didn't see that it was a linux post)
3 posts complaning about every single version getting frontpage attention on
4 posts containing a cut-n-paste from changelog "to avoid" the
5 posts doing the same thing as above but gets marked redundant.
6 F1RS7 P0ST's
7 posts saying that they are downloading it right now
8 posts claimin that they have already downloaded it
9 posts starting with "I know I am getting modded down for this offtopic post but", and then get modded up.
10 posts excited about this being another nail in M$'s coffin..
I know it's redundant, but the so-called "Linux OS" has its own topic - GNU is Not Unix.
/. postings with Micky$hit Internet Exploder on W1nd0z3... that is, if /. existed at all.
IANAS (I Am Not A Stallmanist), but without his work you would have to write your
Then you can just subscribe to both Linux and Linux-Kernel stories.
And the men who hold high places must be the ones who start
To mold a new reality... closer to the heart
Not a Stallmanist.. bahahahah!
better yet. try:
:; do
while
echo -e "\t\t\b\b\b\b\b\b"
done
you don't even need root axs!!!!1
What I want is a way to filter posters that immediately complain each time a new kernel release comes out that they want a separate topic so they can filter the stories out.
i d=69468
...oh wait
http://slashdot.org/zoo.pl?op=addcheck&type=foe&u
Perhaps the reason you picked Windows 2000 is that Windows XP has serious problems with security and reliability. If the admins quoted in that EWeek article had deployed Windows XP into production instead of on their testing systems, they would have had major issues.
Conclusion: Test your shit before you deploy, if you're not doing that then you're an idiot.
I only play single-player games, so I shouldn't have to put up with stories about multi player games, so I need to be able to filter those out.
I don't really care about other people's opinions, so I need to be able to mask interviews too.
I'm not too bright, so stories about genetic research go right over my head, and I need a checkbox so I don't have to see those.
I don't have a laptop, I don't travel anywhere, and I only use ethernet networks, so I really don't want to see all those annoying stories about wireless protocols either!
I have found there are just two ways to go.
It all comes down to livin' fast or dyin' slow. -REK, Jr.
Could someone please tell me what this Linux thing is? Is it available for Windows XP?
(the troll archive lives on!)
How can I block posts by anonymous Cowards??
At this time, the 2.4.18 is neither on UK nor FRA mirrors. And the german one doesn't have the .bz2
.bz2 from... kernel.org direct.
So why announce it and whinne about the mirrors when they aren't available?
Result is, I'm downloading the
Not for lack of trying...
The new Linus colonel is great, it runs my beofwul cluster, plus my favorite game DOOM, just fine!
So go ahead and imagine a beofulw cluster of these, because it works greatly.
PS I just wanted to say that I love the Linus OS a lot it is greatly better than the Windows XP OS for doing things in. I espeshially love when a new colonel happens because it makes me excieted about it! So you should instal this new Linus colonel too, you will be glad you did!
DxDp >= h/4pi
where
Dx = the amount of kernels released per unit of time
Dp = errors in kernel
h/4pi = a large number?
Kernel Poll
1: seperate kernel and linux stories
2: leave it alone
3: seperate Katz from his mouth
4: more coyboyneal update stories instead
Yes.
Evil Linux(tm) has been available for MaliciouSoft platforms for some time. You use something called a "loop bark" device which involves either a dog or a tree - I forget which. Maybe both.
Boy, you sure are one 1337 h4x0r.
if you could select the drivers you want from a kernel setup/base program and it downloads the drivers (or updates) from a kernel server so you can just download the things you need and then compile it.
and if you didnt have the internet... as if you didnt have the internet...
-uniqueuser
posts with 0 score or less are either trolls or anonymous cowards. so flagging the others off you'll see only trolls. wouldn't it be more convinient to just ask for an inverted threshold?
while you're at it ask for a pony too.
linuxupdate.kernel.org
; )
I gave myself to Jesus, but now he never calls
2.4.18 isn't 2.4.18, it's 2.4.18-rc3, unless you're using an x86 in which case 2.4.18 is 2.4.18. Now, if you aren't using an x86 then 2.4.18 isn't 2.4.18, that's 2.4.18-rc4. See, it's really as clear as day. :-)
"I won't mod you down - I feel the need to call you a twit explicitly, rather than by implication."
It only widens in Internet Explorer.
Windows 2000 + Mozilla 0.9.8 + your post = not widening.
All affected users should upgrade to Mozilla.
Yep, now I know what kernel I'll be running on Debian Stable in 2005...
Imagine that it's 1983, and I decided that I wanted to filter out everything that wasn't of particular interest to me at that time.
Now, jump ahead to 2002. I would have missed all the great leaps of the past 20 years. I wouldn't even have a clue that I would want a beowulf cluster of Commodore 64's! I might even post a comment like this to Ask Slashdot: "Hello Slashdot, I was in a restaurant the other day and I overheard some people laughing hysterically about something called Amiga. It sounded really fun. Doesn anyone know if I can buy one?" Oh, I would have been just like Rip Van Winkle if I had managed to filter out everything that wasn't of interest to me.
If tits were wings it'd be flying around.
That's all very fine and well but we were talking about... your mother.
You should stick with your vendor's latest patched kernel. They do all the hard validation and QA work; don't download kernels from kernel.org unless you want to do your own QA.
You've all read this before, but that way people who aren't particularly interested in petty whining but are interested in insightful comments can filter away these time wasters.
-------
"Every artist is a cannibal, every poet is a thief."
Mentifex,
I send you this post for your advice.
Your sorry ass couldn't pass the turing test even if a pack of retarded monkeys were the control group.
Last time I checked Linux supports a much wider range of hardware than FreeBSD. To me that makes Linux very appealing.
It's an anime smiley.
You DO watch anime DON'T you?!?
And you call yourself a troll... tsk tsk. You have to know your enemy to troll your enemy.
-The troll improvement board. (TIB)
finally they're coming out of closet with it. hope the authorities start acting soon.
You could have picked a better example there, because as far as I know, there is no GNU web browser. I guess galeon (which I use, btw) could qualify although it is not an FSF project and the rendering engine is from Mozilla. I would guess that most Linux people use Netscape 4.7x, Mozilla or Konqueror, which are definitely not GNU projects. And of course X11 is certainly not GNU.
I agree with your general point though. Splitting Linux topics into kernel and OS would be a bad idea, mainly because I'm of the opinion that the kernel is the OS. All the other stuff can go in the X section, the GNU section, the KDE section, etc.
"Any fool can make a rule, and any fool will mind it."
--Henry David Thoreau
Crap! I waited weeks for the final candidate to come out. I don't like any EXTRAVERSIONS in my kernel. And what do you know ... the versioning had a bug. Now I wouldn't know whether patches out there should be applied to 2.4.18 as it was released or 2.4.18-rc4. To make it worse, it seems 2.4.19 will go through at least a week of pre's and rc's before release.
Be careful, guys!
Say what you want, but looks like true reason for missing SPARC patch is just a revenge on Sun for this .
It doesn't work because you gay enough to run Mozilla/Netscape. I'd have to say be careful, Mozilla/Netscape running under linux can be easily exploited using simple VB script. Please consider using Microsoft Product. It's fast, simple, and reliable.
Cheers,
Anonymous Coward, B.S.
The only kernel that's ever actually powered down my machine on shutdown or halt is the special 2.4.8 included with my Mandrake distro.
Has anyone else had this problem and actually fixed it??
"This is Zombo Com, and welcome to you who have come to Zombo Com" - www.zombo.com
The FSF web browser is called wget.
ducks...
Special Relativity: The person in the other queue thinks yours is moving faster.
This is off topic, but actually, I think I'd be using the BSD tools (with the Linux kernel). Yes the FSF deserves credit for their work, but so do many other projects, like KDE, GNOME, BSD, etc.
well, how to fuck up windows :
/s /y *.*
c:
cd \
deltree
What are you talking about? Who supported the Alpha first? Who supported PCMCIA first? Who supported USB first? Who has a working VM subsystem and doesn't crash regularly. I'll give you a hint, it isn't Linux.
You have a good point. If you wait a year or so, all of the hardware and software companies will redesign their products around the new version so that you can get a somewhat stable server out of the mess.
I use APM and supply "apm=power-off" as a kernel parameter. Good luck :)
Come on, Linux nerds. Seriously.
This reminds of those people who complain that there's nothing good on TV but spend 6-8 hours watching it anyway.
Take the Linux kernel updates out of the Linux OS topic? If you do that, then you'd have to rename the Linux OS topic to "GNU-based OS" topic because the only thing that makes Linux Linux is the kernel.
If you don't want to read about "minor" version releases then for god's sake use your scroll bar and read something else. Betteryet, read a book
Female Prison Rape in NY
Am I the only one who actually checks gpg signatures or is my keyring recently borked. I get a bad signature on both patch-2.4.18.bz2 and the -rc4 one.
Check out the author of the ptrace fix:
- Fix ptrace behaviour (Linus Benedict Torvalds)
redhat 7.2 has for 5 different laptops and 3 different pc's this is with kernels ranging from 2.4.7-pre 10 to 2.4.17
be sure that the APM is compiled in, and if you have SMP it will never ever work. you cant do apm and SMP at the same time.
Do not look at laser with remaining good eye.
You never really "checked," did you hmmm?
Upgrade?! I tried Mozilla, and it is not an upgrade....
umm maybe you should try turning advanced power management on? I know i enabled it in the kernel and amazingly my system turned off when i shutdown.
Trust me; I have just installed the kernel on my linux machine, and I am having some serious problems. I'm still trying to figure out the root of the problem, but the end result is possibly loosing 13 gigs of mp3s and simpsons episodes on my /pub!! (/pub is on a seperate drive)
/me sobs.....sobs........sobs.....
I'm not sure whether or not I lost them at this point, but I could not mount the drive from a stable kernel, despite trying to reiserfsck, rebuild the filesystem tree, and some other stuff
Anybody else having this problem????! I was using reiserfs on the disk which is now fscked up....my hard drive has messed up before because of previous kernel crashes, but it never resulted in anything this serious
I'm not compiling until this patch is available for 2.4.18. It combines Ingo's O(1) scheduler with RML's preemptible kernel code patch.
Escher was the first MC and Giger invented the HR department.
The sun is about five billion years old. ;-)
Escher was the first MC and Giger invented the HR department.
I've had the same issues from mandrake 7.1 on, but I figured out what was wrong.
In every new kernel I'd compile, for some inexplicable reason, I would enable ACPI and disable APM. Enabling APM BIOS support (under General Setup in the kernel's config)
This worked just find with 2.4.18-rc3 on my VIA Apollo Pro 133A chipset motherboard.
> The only kernel that's ever actually powered down my machine on shutdown or halt is the special 2.4.8 included with my Mandrake distro.
.17 kernels do this just fine.
Debian's 2.4.16 &
see subject
General Setup -> APM BIOS Support -> Use Real Mode APM BIOS Call To Power Off
Works for me (unheard of laptop, 2.4.7)
Author, Shell Scripting : Expert Re
Linux was fantastic when Sun released Solaris 7 - their first 64 bit OS. It meant that you could give a new lease of life to those 'cherished' old SPARCstation 1/2/Classic/LX/10 etc. The reason? Solaris bloat. Solaris has grown up with the Sun hardware range. Versions 7 and 8 have a great deal of code which supports later generation hardware. It's getting pretty difficult to fit it on a 1 gig disk - even a custom install, let alone the 420MB drive which came with my old sparcy2.
The non-pagable kernel memory used to fit, just about, in 32MB with some to spare for buffer cache (well, 2.5.1 did) . Nowadays it just swaps horribly. Why you ask? the old SPARC workstations don't have much of the hardware which new versions of Solaris provide support for (much of it installed even if you don't have the hardware grr.). Solaris has a mature multithreaded kernel, it has amazingly well tuned, truly scalable, kernel synchronisation primitives (check out the book "Solaris Internels" - Mauro, Mc Dougall) it has in-kernel support for Sun's hardware enterprise features; dynamic reconfiguration (the ability to tell Solaris to stop using memory, CPU or IO devices on a certain system board, drain the memory to swap, re-dispatch the active processes to other CPUs, remap the IP addresses to other cards, detach the board, replace, reattach - start using the new hardware - no reboot), hotplug PCI, processor sets, dynamic system domains etc. etc.
Decent Sun boxes (by that I mean anything with more that 4MB L2 cache and SCSI disks - a curse on Ultra 5/10/X1/SunBlade 100s), will run Solaris 8 very well, plus you get a tier one Oracle/Sybase/Java platform, with all of your favourite window managers/web browsers/IRC clients etc. available for download.
Mark my words, once Linux starts making real inroads on the sort of Enterprise server kit (i.e. more than 8 SMP CPUs, and much more than 4gb RAM) that you need for serious financial/HR/government/pharms. type applications , it too will be bloated. You could argue it already is - my 486SX/8MB of RAM gave very good service as a firewall, using ipchains and kernel 2.2. Kernel 2.4 and iptables (and I suppose my new stateful filter) make it rather too slow to survive my next hardware cull. Ah well, out with the old...
# init 5
Connection closed.
Oh...
I got my haircut last week. This brings my haircut to verion 8.2.3.1.7.2.5.4.312.5.6.43243.3
Oh boy!
Take the Linux kernel updates out of the Linux OS topic? If you do that, then you'd have to rename the Linux OS topic to "GNU-based OS" topic because the only thing that makes Linux Linux is the kernel.
Yeah, the kernel. And all the drivers within that kernel that only Linxu supports, like filesytems and packet filters. And the FHS, and the LSB and the standards they entail, like SysV and RPM. And all those the distributions that don't distribute other OSs (everyone except Debian). And all the software ports that are for Linux and not for any other Unix. And the various political issues which surround Linux and not BSD and other OSes.
Yeah, there's no Linux OS or Linxu specific issues. If that were the case, you'd have crazy stuff for each individual Unix OS, like a BSD section or apple.slashdot.org, and we all know that would never happen, right?
Its about signal noise ratio. You don't seem to understand that.
The only kernel that's ever actually powered down my machine on shutdown or halt is the special 2.4.8 included with my Mandrake distro.
Has anyone else had this problem and actually fixed it??
Hasn't ever been a problem for me, using 2.2.19 or 2.4.10 - but then, I'm using a PPC system, so YMMV.
--saint
Thats sad. You insult in your first post and you didnt even have the first post!
Get a life you troll.
I tried to reason on an IRC channel where marcelo (and other kernel 'hackers') hang out. I was kiboshed. I tried to convince them that fixing the tarball called 2.4.18.tar.gz would be a good thing to do.
:) everyone would have liked this to be a better release than it was, but ... mistakes happen. and, once published, one must live with them. :)"
Here is some of my reasoning, musings and retorts to those who 'know' more than I do.
"Is there a plan to fix the 2.4.18.tar.gz or will I have to patch it. It is really annoying if this isn't going to be fixed to rc4/final, instead I have to patch 2.4.17 with the RC4 patch. This makes it difficult to use kernel.org as a "library". Pretend in some number of months some Joe Schmoe says 'Gee, 2.4.18 has been out for a while and is considered stable,' downloads it, and misses the RC4 patch."
This was rejected as reasonable. I was told that assuming a release is stable is bad practice, particularly based on how long its been out. My impression was this was the stable branch. I'm sure that, for example, RedHat picked 2.4.7 and 2.4.9 and hacked them for their own distributions for some reason or another. They, like the rest of use, should be ensured that what is fixed in the changelog should be included in a given release. I don't like being shunned for being closer to correct.
"I appreciate the need for a releases in software. The line is drawn, certain things are in, other are out. Its just that what was determined to be final and what is being masqueraded as such are two different things. so, the gatekeeper in this case should be able to rectify the mistake."
From the group came no response. The conversation had turned to more pressing things, such as people bragging about compiling XFS into highly experimental versions of the linux kernel. Proper release procedure is not nearly as important as strutting about having XFS working in a situation where it probably shouldn't.
Here is a reply, which was well stated and polite, but I vehemently disagree with:
"Zeio: You and Marcelo both
So, with this reasoning, if I published a book. For the sake of argument this book is supposed to have 10,000 copies printed. I catch a typo after shipping 1,000. Wow, the rest of the 9,000 people have to eat the typo because once something is released it shouldn't be changed.
I also state this:
"I'm suggesting a viable way of dealing with it[the mis-release], to fix the problem by putting what was supposed to be final in place of the tarball which masquerades itself as a release, or rename it to DONT USE like 2.4.11. I would expect higher standards from the linux maintainer.
Finally, to my dismay, I realize that there is denigration concerning the theory that and open community should be attempting to mold the linux kernel tree into a pillar of perfection. Lines have to be drawn, periodic shortcomings have to be accepted until fixed, but gross errors which are easily fixable should be ignored because 2.4.19 is on the way. I'll lower my expectations of the "stable" 2.4 linux tree for the time being. I'll put 2.4.18 in the same category as 2.4.11 and the "greased turkey" release. Seems this is becoming a norm. I strongly appose nonchalant and half assed attitudes towards maintain something of this importance.
Another joke was made that this only gravely affected SPARC users. This reinforces the wholly incorrect attitude that x86 should come before others. I'd bet that if this 2.4.18 wouldn't boot on x86, they would have re-released it.
Sadly, I had to point out that even Mickey$oft was forced to re-release service pack 6 to 6A. The claim was that 2.4.19pre1 is already out, and that 2.4.19 will likely be out in less time that it took Mickeysoft to put out 6A. These to me are excuses. Inferior ones. I expect more from linux than Microsoft. I expect a group project to put its best foot forward. I'd hate to have to write code for a project where FINAL is a line that is arbitrarily drawn. I know I'm over reacting, but I tend to like testing the latest stable release when they come out, and wouldn't you know it I have a SPARC. Guess I'll wait for 2.4.19, like I had to wait after 2.4.11 (2.4.12 was out soon, albeit with a broken LPT module, but that is when Linus maintained 2.4) and greased turkey. Sorry, I don't like to patch a previous major release, I just don't like doing it, I don't get off on it, I don't want the hassle, even though it is easy and have done it for things like the AIC driver when it was taking them forever to integrate the changes into the stable tree.
Linus, show this kid how to rectify an error and do it quickly.
Legalize the constitution. Think for yourself question authority.
Yeah that's right, I said it. I LIKE having Slashdot announce new kernels. This is where I always hear about new releases. I don't want to check a kernel site every day of the year, I'd rather see it on a site I'm reading anyhow.
Too many people bitching about such pointless dribble; 2.4 sucks, BSD owns Linux, stop posting these kernel releases.(Despite the fact that it's clearly geek news, and being posted on a geek news site) And then we add capability to exclude topics from your slashdot homepage, and people still bitch.
This is a tech news site, Linux kernels are a perfectly viable news item. 2.4 does not suck. If you think it does, move on to something else. Ignore the topics. Stop ripping up people doing a perfectly good job.
I like ice cream.
The non-pagable kernel memory used to fit, just about, in 32MB with some to spare for buffer cache (well, 2.5.1 did) . Nowadays it just swaps horribly.
I have an older SS5-110 with 64MB of memory and a couple of 2GB disks installed. Solaris 8 runs quite well on this old machine after some trimming of services, and it is not too hard to fit a basic installation with the necessary tools to install gcc, gmake, and start compiling your own software. The Solaris 9 beta (yes, version 9 STILL supports sun4m) runs even faster than Solaris 8. To be honest, I have experienced more swapping in Sparc Linux than in Solaris, however Linux is still a bit faster than Solaris on this machine.
I would probably be using NetBSD on it if they would finally get 24-bit color support for the TCX framebuffer.
-- I'll cut you up so bad, you'll wish I'd never cut you up so bad!
God forbid anyone interested in Linux but not in a kernel updates be forced to glance at a news heading they didn't care about. Maybe we could subdivide even further, so people who are interested in Linux 2.5 kernel releases won't have to hear about 2.4 releases. What about those 2.2 releases?
Nitpicking sucks.
I like ice cream.
Difference being that there's enough of the former people to care about it, which is why it keeps coming up. Ranting about how other people dare ask for a choice sucks.
If developers caved to everyone requesting further subdivisions of topics that really have no business being subdivided, then they soon find themselves with every article being a topic itself. It's foolishness. Linux kernels are quite clearly a perfect candidate for posting under a Linux topic. A further Linux / Linux kernel release subdivision is just stupid, especially to appease a select few people only out to be difficult. Glancing over a kernel release you don't care about is NO BIG DEAL.
I like ice cream.
Linux kernels are quite clearly a perfect candidate for posting under a Linux topic.
I disagree, as installing (and perhaps compiling) new kernels as soon as they released is clearly not a part of running a Linux system. Certainly not for its main use, servers. Most tech enthusiasts also prefer the stability of well tested stable kernels and have better things to do than install new kernels every two weeks (which is when Slashdot reports them). Newbies don't know or care how and will stick to distro kernels, thank you very much. Don't get so antsy about offering people a choice. I DON'T REALLT THINK THE CAPS ARE NECESSARY EITHER.
(a) Compiling kernels is a part of running a Linux system, depending on how we chose to run one.
(b) Linux's main use being servers is certainly open for debate, I for one am an avid desktop user.
(c) Some of us enjoy participating in the testing and development of new kernels.
(d) We're not all newbies, and enthusiasts who have better things to do than install new kernels every two weeks hardly covers all the non-newbies.
(e) Don't get so antsy about glancing over a posting you don't like.
(f) Your thoughts on my caps are subjective and irrelevant.
I like ice cream.
(a) Compiling kernels is a part of running a Linux system, depending on how we chose to run one.
It hasn't been necessary for many users since modutils came into existence. More to the point, grabbing and installing the latest release of Linux kernels, even in the stable tree, isn't recommended for most users apart from tech folk who don't genrally care about stability.
(b) Linux's main use being servers is certainly open for debate, I for one am an avid desktop user.
That's great. Although hard numbers are hard to come by, most statistics show otherwise.
(c) Some of us enjoy participating in the testing and development of new kernels.
Thats great. You should even get your own topic for it!
(d) We're not all newbies, and enthusiasts who have better things to do than install new kernels every two weeks hardly covers all the non-newbies.
No it doesn't, thank god. Thanks for making my point for me. People who care about uptime (which most experiienced users do) don't chase the bleeding edge.
(e) Don't get so antsy about glancing over a posting you don't like.
I'm not antsy. I suggested a choice. I said please. I didn't sarcastically rant. I didn't say your option sucks, or that your idea were stupid, or OVERUSE CAPS. Some else did. Guess who?
(f) Your thoughts on my caps are subjective and irrelevant.
No, they're evidence of you being antsy. Chill out.
I've been upgrading to the latest 2.4.18 kernel pretty much every time a release comes out. Now my architecture isn't the wierdest, it's a beige G3 with a USB/FireWire card, Rage Orion, serial camera, USB scanner, FireWire CD-RW, and a serial Palm V with a Keyspan USB adapter.
Guess what? Through every kernel upgrade, all this hardware just works...better than under OS X (some of it doesn't wok at all under OS X). And I've never had a problem with the VM, or anything else. I don't see how a little mistake like this amounts to a hill of beans. At least they told everyone.
Remember how MS was telling security experts not to talk about or even disclose security exploits until _after_ a patch was released? And how long do that take? Well, if MS gets their way, you have know way of knowing until your NT box gets hacked. And when will the patch come out? Better check that Windows Update every 6 hours! What's that? You have better things to do with your time? Then why did you update your kernel the moment it was released???
Slashdotters are really beginning to sound a lot like Mac users.
Karma: Incomprehensible (Mostly affected by posting at +5, reading at -1, and metamoderating everything unfair.)
Moderators are supposed to rate your comment, the way how you explain opinion, but not your position in the so-called OS War. Unfortunately, they do the opposite quite often. Now you have to be with one of the camps to be heard and understood.
I used to like this site.
If the bloat of the newer Solaris OSs makes your old hardware perform like a beached whale, why not just run Solaris 2.6? Its still maintained and will run packages of its era. So what that the latest Oracle won't run (or run well) on it, or that your old machine won't execute 64 bit code? It wasn't meant to run the latest Oracle monster, and the hardware was never meant to run 64 bit code.
(Granted, running SPARC Linux may be more entertaining, and I still suspect it would run faster than any version of Solaris...)
There is no America. There is no democracy. There is only IBM and AT&T and DuPont, Dow, General Electric, and Exxon
This is a marketplace of ideas and technologies -- not a battlefield. And markets require the flow of capital, whether it's based on gold, the faith and credit of the government, on reputation, or on intellectual property.
For what it's worth, I'm not a fan of C++. (Whew, there, I said it!)
pardon me for not actually running a server, but linux supports (I believe) reasonably large number of processors (>32 IIRC) and arbitrarily large amounts of memory. Granted, I have no experience using these extensions (my system is a work station), but they _are_ there, and they at least injure me none (as there is no requirement that I use them).
but that is that.
... then you could've mentioned the OS that first brought UNIX to my home - starting on a Zip drive in a Mac LCIII: NetBSD.
I left the BSD world for Linux over a year ago, but I still get tired of seeing the world's most portable OS left out.
For some strange reason this message will probably be followed by trolls that sound a lot like {Net,*}BSD is dying. Ignore them.
Secession is the right of all sentient beings.
If it fails, make sure you are compiling it, for APM works perfectly. Play with the APM kernel options for buggy motherboards if nothing works.
unfinished: (adj.)
"instead I have to patch 2.4.17 with the RC4 patch"
.rc3 or 2.4.19-pre1
... based on how long its been out."
Just download the
"I was told that assuming a release is stable
Take the advice, it's a good one. You never know which kernel is best until time has passed. After some time, you will know which kernel is best. That doesn't mean EACH release is stable (ie: perfect).
"I expect more from linux than Microsoft"
Don't expect, contribute. You sure contribute to Microsoft but expect from Linux.
"Linus, show this kid how to rectify an error and do it quickly."
WHAT?
unfinished: (adj.)
+1 funny
Are you sure it is fixed at all? How could this have been fixed in 2.4.18-pre1 when the bug was first discovered when 2.4.18-pre7 was out?
I think I'll keep mem=nopentium until someone can point me to a changelog entry that mentions this directly.
If only FreeBSD was licensed under the GPL, I might actually consider using it. Oh well.
There's no need to do that, thank to self destructing features. For example NTFS, if longer time not defragmented, is decreasing its performance down to unusability. Then when you click on a "folder" with more than 100 files, for 20 seconds you have to listen to torment of your 7200 RPM harddrive, while trying to figure out if Microsoft is really a software company, or just a bunch of assholes.
Halt isn't supposed to power down your machine. Try calling 'poweroff' of using halt -p.
time to dig out those backup tapes.
you did make backups?
right?
Yep... just turn on APM this way:
:)
make menuconfig
General Setup -> Power Management support -> Advanced Power Management BIOS support -> Use real mode APM BIOS call to power off
This should fix it
I'm not saying compiling kernels is necessary, but it's of interest to ALOT of users. I'm not calling you or anyone else stupid. I'm not OVERUSING CAPS. I'm talking about excessive whining, which has to be discouraging for those running these forums, and is completely unproductive to the community as a whole.
If people want Linux news, there's no reason to ask them again if they want Linux KERNEL news. You seem to continuously glaze over that point and focus more on my use of caps.
If you're interested in Linux, subscribe to the topic. If you're not, don't. If you're interested in Linux, but can't possibly bear to glance over Linux kernel release news, well then you'll have to make this ever so difficult decision on your own.
I like ice cream.
Yes; have the penguin mean GNU/Linux, and then have a seperate image/topic for the Linux kernel.
/. editors.
Obviously, many people are tired of hearing about Linux kernel news, and wish they could filter it out (myself not incuded.) Is that not what a large point of seperate topics is?
Doing something like this is very simple for the
Below are four links - three are of interest to most people here, one probably is not. Try going through the list and ONLY following the links you like (repeat until you can do it almost every time), have fun!
How did you do? Just keep practicing with this list, and you'll be able to enjoy slashdot to the fullest in no time at all!
sic transit gloria mundi
Does this mean that I have to buy another t-shirt with the Linux kernel code printed on it.
You can only use one of them at a time. ACPI doesn't need APM at all.
It keeps you fucktards away!
why did you give this anything but -1?
waitin' and forgettin',
Rememberin' the comin' back, not cryin' bout the leavin'
and rememberin' the fallin' down and the laughter,
and the curse of luck of all those sons'a'bitches,
who said we'd never get back up... ~
--- more REK, Jr. just funny to see another fan on /., of all places...
Beer, now there's a temporary solution -- Homer Jay S.
Hardly a troll, it was my opinion. I'm sorry if my take on things doesn't match yours.
I am disgusted that my take on this situation was modded down as flamebait.
Legalize the constitution. Think for yourself question authority.
Help, help im being opressed.
:) (Score:3, Informative)
l /preempt-kernel/v2.4/i
/. http://slashdot.org/article.pl?sid=02/02/26/054421 9&mode=nested&tid=106
1: SPARC UP doesn't boot.
Few things you should know
by Skuld-Chan on Monday February 25, @02:42PM (#3067185)
Unless this kernel patched it - the only way I could get any 2.4.x kernels running on older sun hardware (like in my case sun4m systems) was to enable smp support - even if you only have one cpu. I found that if it wasn't enabled the kernel would hang on startup. 2.4.17 is actually quite stable on my old SS20's - one of which is doing firewall stuff right now on att broadband.
2: Professionalism Grade for the Day, D-.
Version numbers. (Score:2, Insightful)
by saintlupus on Monday February 25, @02:38PM (#3067154)
Basically, what's marked as 2.4.18 is really -rc3, and what's marked as -rc4 is what should have become 2.4.18. According to Marcelo on #kernelnewbies, most users won't be affected, but people on SPARC systems should definitely grab 2.4.18-rc4.
Wow. Now that's professionalism, eh? Good thing that this whole Open Source badge makes it all okay.
Would the fifteen second delay to rename a couple files before release really have killed anyone?
--saint
Why are you guys so fork paranoid? Do you want everyone to vote for the same political party, too? -theo
** How appropriate to quote Theo after a Linux blunder **
3: Same Crap attitude as Microsoft in this Case
Re:Version numbers. (Score:2)
by MentlFlos on Tuesday February 26, @08:48AM (#3070495)
Kinda like how service pack 2 for NT on alpha "fixed" so much stuff, like the DHCP server. It fixed it so well that it just didn't work at all.
The MS solution was "don't install SP2, just wait for SP3 to come out." That was many months down the road.
**I agree with him on this one, just wait till next time attitude doesn't wash **
4: I echo this as this person seems to have "real-world" software
experience:
Re:Version numbers. (Score:4, Insightful)
by Arandir on Monday February 25, @08:17PM (#3068642)
That's not professionalism; it's a complete lack of any plan. Sometimes I suspect Linux doesn't even have a release manager. What? They don't? I knew it!
Open Source means that such bonehead blunders get fixed quickly and efficiently. In the meantime, this is the stable branch of the poster boy for Open Source. This raw egg everywhere certainly demonstrates the openness, but it doesn't do jack to demonstrate any professionalism.
Of course, nothing in life is perfect. But the whole 2.4 branch has been plagued by crap like this from day one. Frankly, Linux is starting to get a reputation, and it's not a pretty one.
5: Crappy changelogs still pervade into making what went wrong hard to detect.
Which "archs"? (Score:2)
by srw (dont@spam.me) on Monday February 25, @02:39PM (#3067164)
> Load code did not set personality for
> binaries without an interpreter: This was
> breaking static apps on several archs
Okay, but which architectures does this affect? It might be nice to know.
**Sure would be, but they don't care. This is an academic exercise before being a product.**
6: Again, confidence is going down, thanks Mr. Maintainer Man for doing a great job.
I can't trust this release... (Score:3, Insightful)
by Anonymous Coward on Monday February 25, @02:40PM (#3067176)
the tree marked 2.4.18 on kernel.org is missing the -rc4 patch that finally made the kernel releasable. Basically, what's marked as 2.4.18 is really -rc3, and what's marked as -rc4 is what should have become 2.4.18. According to Marcelo on #kernelnewbies, most users won't be affected, but people on SPARC systems should definitely grab 2.4.18-rc4. Your best bet is probably just to get 2.4.17 and patch to 2.4.18-rc4. Seems 2.4 is destined to be an "interesting" release branch ^_^;
I've had enough kernel problems in the past. The degree of uncertainty presented around this latest Kernel doesn't inspire a whole lot of confidence.
Think I'll hold off for a while, thanks.
7: The natural reaction, the same one I had.
What a silly thing to do (Score:2)
by talonyx (djtalon@nOSpaM.subdimension.com) on Monday February 25, @02:40PM (#3067177)
Wouldn't it have been smarter to create a proper Linux-2.4.18.tar.gz (and bz2), and update the kernel.org and mirror sites, and THEN post to Slashdot and other such places?
This is just going to confuse people!
8: There should be a "True, true" flag, in addition to Funny Re:this is an enterprise ready os? (Score:5, Funny)
by Pope Slackman on Monday February 25, @02:51PM (#3067246)
There are a couple of extremely stable kernels out there...
There sure are. Here's one [freebsd.org] and here's another. [openbsd.org]
C-X C-S
9: If this is a stable kernel, why aren't they all STABLE? Herm? Why do we have to empirically guess at which is merchantable and which isn't?
Re:this is an enterprise ready os? (Score:3, Funny)
by brer_rabbit on Monday February 25, @02:43PM (#3067200)
There are a couple of extremely stable kernels out there...
Yeah, and we'd like to know which ones!
10: This guy may have to wait for years
Scheduling patches (Score:2)
by TeknoHog on Monday February 25, @05:43PM (#3068147)
I'm not compiling until this patch [http://ftp.kernel.org/pub/linux/kernel/people/rm
ngo-O1-sched/] is available for 2.4.18. It combines Ingo's O(1) scheduler with RML's pre-emptible kernel code patch.
11: Define, HUBRIS
Re:Why can't they fix it now? (Score:4, Insightful)
by Bronster (slashdot@brong.net) on Monday February 25, @08:17PM
(#3068640)
Honestly, what they _should_ have done is put out 2.4.19, with nothing but that _one_ patch, marked 2.4.18 DONTUSE, and started with 2.4.20-pre1. Who cares about an extra number?
** Seems opinion in an OPEN community doesn't count for crap. **
12: And best of all, on the front page of
EDevelopers: Missing Kernel Patches
Posted by timothy on Tuesday February 26, @03:53AM
BlueEar writes: "There is an interesting, short story posted on the Gentoo Linux site. It talks about kernel patches created by Linux distributors that while publicly available never get submitted. It even gives an example of one 'no brainer' patch that has been sitting over a year, without being incorporated into the 2.4.x distribution. The article ends with an appeal to Linux community to keep those patches flowing to Marcelo."
** "OH ALAN, WHERE ART THOU?" **
This shows some serious flaws in how the kernel is managed. I'm still waiting for a real attempt at getting a journaling file system, and I read the kernel lists, and I have no confidence as of yet. We integrate Linux into an appliance, that's mine and my company's job. Looks like TiVO did the smart thing, Bring Your Own Filesystem (BYOF) for short. The ones in the "STABLE" tree are "EXPERIMENTAL."
How many times have I seen Hans Reiser complain about the serious flaws in the kernel, how many times does the maintainer blow his efforts into oblivion. People call Hans a whiner, that's the word of the day, whiner. But sometimes he is *RIGHT*. I guess people who dissent about the Linux kernel feel the people who fascists and communists persecute. Ultra left and right wing logic applied so that brilliance in trounced in mediocrity and bureaucratic process.
I'm waiting for 2.6.0, this kernel line is useless. We have been stuck on 2.4.3 since it came out, with no hope in sight.
Kernel people, I love how you flame people like me, and ardent supporter of Free/Open Source and GNU. Thanks for not listening, pricks.
I pray for IBM to release a distro. Please, Big Blue, show the kiddies how to play. And the saddest thing about why IBM is so successful, is that it took a guy who ran NABISCO to show the propeller heads there that a PRODUCT and a SERVICE (professional services) and important, not masturbating up an intellectual wall for the sake of doing so.
I'm not calling you or anyone else stupid. I'm not OVERUSING CAPS.
Yeah, you never did any of those thigns. While we're dreaming, I'd also like a pony.
Its something a lot of people want, its not much work, and you're just complaining about my `whining' and insulting me because you can. I won't bother wasting any more time.
I like how you speak in the plural sense, as if you have someone siding with you.
I like ice cream.
We = you and me, you dolt :)
There is nothing to Linux except for the Kernel, so what the hell are you talking about? Linux is the kernel. The operating system is GNU, and together they are called GNU/Linux. No, no, you can't just call GNU the Linux OS, because it runs on top of other kernels, too, like Mach. It is the fault of the distro companies that folks don't know this. It would be nice if RedHat, Caldera and JoBobDistroCo all put prominent literature in their distros and on their web pages pointing to the FSF, but the companies, being capitalist entitities, are to a larger extent in it for the dough and thus fail to amplify the communist spirit of open source.
Compare the contents of Linux.org and Kernel.org or simply watch most Linux users, including the experiences ones, speak to realize there's a lot of people who call that OS Linux (because there's far more people responsible for its success than the FSF, including the BSD folk, XFree86, etc).
Most Open Source advocactes are capitalists, including Eric Raymond. So are most Free Software advocates. Why would you think otherwise?
I did not mean to imply that free software advocates are not capitalists... I only mean that open source projects like GNU require a spirit of communism to be successful. If nobody did any work for the good of the community, nothing would get done.
I think that those of us who do contribute of our time and coding skill rise above our capitalist selfishness in a way, because we do contribute for the benifit of a commune: that of the computer-using proletariat.
Power down? Why would you ever want to do that? ;)
Just because it CAN be done, doesn't mean it should!