Posted
by
timothy
from the jamie-has-the-munchies dept.
punkmac writes "It's that time again to do the thing we all love to do, compile your shiny new kernel. This time its 2.4.20. The changelog can be found at the usual places, and please use a mirror for all your downloads"
This discussion has been archived.
No new comments can be posted.
American English is akin to Microsoft English. Take a published standard and alter it ever so slightly, but annoyingly, so that documents (applications) have to be rewritten.
In case you wanna see if you even need the nwe kernel. You can find the changelog here [kernel.org]. Dont download it now if you dont need it. there are peopel waiting to use those servers.
Why? ISC increased their bandwith from 100 Mbps to 250 Mbps. It rarely reached 90% usage, often during a new Red Hat release. The main site works just fine, and will continue to do so.
Hm, I read that they've got a 250 Mbits/s link now, and I was going to respond "hey, let's stress-test it!" But www.kernel.org was very slow to me, in spite of that
Current bandwidth utilization 57.87 Mbit/s
That's actually rather weird, because it is not that uncommon to have that load. If this number is correct, there has to be something wrong with the server. But probably, they are getting more traffic.
Well me? I went directly to a mirror after getting the announcement from the announcement list this morning and downloaded it from there before reading/.
The new kernel fixes the lcall DoS. While I have no untrusted users on my system, things like that is always good to have out of the way.
<hch@lst.de>:
o dump_stack()
o backport yield() and conditional reschedule changes from
o small VM updates from -aa (1/5)
o small VM updates from -aa (2/5)
o small VM updates from -aa (4/5)
o small VM updates from -aa (5/5)
Is this using a Linus definition of small, or a normal definition of small?
Is this using a Linus definition of small, or a normal definition of small?
I mostly used Linux (Debian) in the past with a little Free and OpenBSD.
After I read an interview with Linus where he was asked about the current Linux kernel versus new BSD and XP features, he said something to the effect of "I haven't really looked much at BSD or XP, but I don't see much of value there".
Which pretty much sounded to me like "I have not looked, I don't see any good".
This was during the times that the VM shamozzle was occuring and my Linux machine was becoming unstable.
This was the point where I decided that Linus was getting a bit arrogant. I am glad though, because my OpenBSD servers are very clean and stable and Theo not only sticks to his moral grounds but also has well thought out moral grounds.
For 2.4 series it's not up to Linus what gets merged. Marcelo Tosatti is the maintainer of Linux kernel 2.4 and he's the dictator-for-life of the stable tree.
am I the only one who's noticed?
I just patched my source tree and
linux/version.h still reads that I've got 2.4.19.
Did I screw up? Or am I right that they've forgotten to update it?
You've screwed up: include/linux/version.h is a generated file.
Most targets (e.g. mrpoper, menuconfig) will update the file with the version numbers from the main Makefile.
Quote from main Makefile:
I don't know what the slashdot editors are on today. This has already been covered
here [slashdot.org]
and here [slashdot.org] and here [slashdot.org].
Wait a minute. Do those funny little numbers after the name actually mean something? Oh well, nevermind.
I haven't tried it myself yet, but I found no reference to this ptrace vulnerability [google.com] in the changelog. I suspect this is still a problem (it was in 2.4.19).
I haven't tried it myself yet, but I found no reference to this ptrace vulnerability [google.com] in the changelog. I suspect this is still a problem (it was in 2.4.19).
It was fixed in 2.4.20-rc2, see the "[PATCH] Fix lcall DoS" entry in the ChangeLog or this bk comment [bkbits.net] (and the corresponding patch [bkbits.net]).
anyone know where i can read about this zlib(compression|decompression) library support? there is some very interesting mentioning of it in./inculde/linux/zlib.h and of course in menuconfig as well.
There is also zisofs -- read-only support of compressed ISO CDs. In read-only systems the compression actually makes sense, because the size does not change, and decompression is much faster than compression. To use these, you need additional tools, probably called mkzisofs.
Unfortunately, many CDs are used to store mp3/ogg/divx and the like, which don't really compress much. So zisofs is not necessarily very useful.
I couldn't find any notes about USB. I usually have problems when I try to mount a memory stick on my Sony Clie on Linux (system freezes... nothing can be done except hard reboot, can't even ssh/telnet into the box). Anyone had any similar problems?
I couldn't find any notes about USB. I usually have problems when I try to mount a memory stick on my Sony Clie on Linux (system freezes... nothing can be done except hard reboot, can't even ssh/telnet into the box). Anyone had any similar problems?
Reading and installing the patch from the pointers from here [linux-usb.org] changed everything for me. Re-compiled the kernel just 2 days ago. Also generally, if you want to get the latest out of your usb in Linux, I have noticed that linux-usb.org [linux-usb.org] has it first (or atleast soon).
I do not think it was originally a joke. Older printers used to give that error message when they got a paper jam. The paper would then get hot enough from the friction of whatever was trying to roll it through would cause a fire, and thus by the time the user got the error message the printer would be on fire.
Eh, I guess it still in a way was a joke, but a joke based more on reality. Of course now, that is just preposterious, but eh whatever.
With changes such as "fixed typo in whatever.c" or "It didn't compile because a semicolon was missing, so I added it", we'll soon need to create ISO images for the changelogs...
What I've always wondered is this -- don't they notice that their program doesn't compile, and fix it before releasing it? It's easy to forget a semicolon on the end of a line, but I can't say I've ever released a program that had fatal compile errors. Is there something behind the scenes I'm missing?
Anybody know if this version fixes USB optical mouse support which seems to have been broken for some users with 2.4.19? (Yes, I've checked groups.google.com and know about enabling CONFIG_USB_HIDINPUT but this does NOT help). It seems Red Hat 7.3 users were affected, as well as Mandrake (although I know only what broke for me -- RH 7.3). Thank god my optical usb mouse had a usb->psmouse converter plug which I'm using as a temporary workaround.
There is at least one nasty VM-related bug which has been reported in Linux 2.4.19 and possibly earlier revisions. Rumors of more abound; this is the one that's personally happened to me.
Kernel BUG at page_alloc.c:91! (kills kswapd) Google groups [google.com] for "page_alloc.c:91". Usually blamed on NVidia drivers but notable cases have occurred without them. It's not clear whether the kernel team has made a notable effort to debug them, but they are real and occur on a variety of systems. When this happens kswapd stops working, which causes more bugs later on, and eventually a system reboot is required.
There are other period reports of BUGs being flagged with an otherwise normal kernel on the linux-kernel list.
You should thoroughly test your new kernel before putting it into production. Even if the kernel works well for everyone else, you could personally discover a new bug. You could save yourself a lot of pain by testing first, as well as help the kernel developers.
A while back I wrote a couple articles on Linux kernel testing:
The Open Source Development Lab kindly provides Japanese translations
here [www.osdl.jp].
(The articles are under the GNU Free Documentation License. I would be quite stoked if you copied or translated them. There are articles on other quality topics
here [sunsite.dk].)
PS. I meant to post the LinuxQuality links as MichaelCrawford, but I used a different computer that still had a cookie that logged me in as goingware. I want to be known online by my own name now.
No problem... writing isn't easy, most of my friends and family do it, some for a living.
The slashdot crowd is interesting and harsh in its own way; thousands of people and thousands of viewpoints view and judge what you say. Even in this admittedly non-objective forum, it took me 6 months of effort to get my first story posted, and there were plenty of "flames" in response to it.
So, carry on, and I wish you good luck!
ps: my own site is embarrassingly out-of date and soon to be updated (next 72 hours) but here's a link to it: http://steigenlinux.org I'm especially proud of the "Documentation" page
I've been programming for a long time. I'm good at it, and I suppose if I really put some time into coding for a Free Software project, I could do a lot of good.
But most of my contribution to Free Software has really been in the form of writing. I have also written a lot of stuff which is not copylefted, but posted publicly on the web.
here some more [byteswap.net] as well as
this [goingware.com].
I have contributed some to
zoolib [sourceforge.net], but that's mostly in the form of qa, project management (for the initial open source release) and marketing.
One reason I prefer to contribute by writing is that my normal programming work is so hard, that when I get time to take a break from it, it's difficult to work up much enthusiasm to write more code, no matter how fun the project might be. I imagine that's a common problem.
Another reason is that I feel that any contribution I could make to Free Software, at least in the limited time I have, would be small. I could fix some bugs, add some features, do some testing. But how many people would benefit from my personal contribution? I don't think that many would, at least not until I had the time to develop a really serious package, and I just don't have the energy for that. I have lots of ideas, but no time.
But I feel that passing on my experience by writing can benefit others far out of proportion to the effort I put in. That is because I aim my writing to enable others to do better. By writing well, I enable many other developers to code a little better, and many users to do better testing and bug reporting.
I could lead by example by writing good code, but how many people would learn by reading it? When's the last time you studied the source for some package you weren't really actively involved with? Prose is much more accessible.
This is all the more important because so few engineers of any sort are good writers. When my father was a civilian electrical engineer for the Navy, the shipyard sent him to a writing class so he could write better test plans! The man has a master's degree! But the Navy put lots of people through that class because so many of their engineers didn't know how to write.
What is funny is that I find writing much more difficult than programming. With software, you know when you're wrong. It's not always so clear with writing. The main reason I write so well is because most of my effort is put into editing - and I still find lots of mistakes later.
Even more ironic is that I used to hate writing with a passion. One major reason is that I have terrible handwriting - I can't read my own handwriting, and can't imagine how anyone else could. But the schools always used to require handwritten essays. They used to send me to remedial handwriting classes, which I really hated because they made my hand hurt. It's painful for me to write much by hand.
What did it for me was two things - a composition class I took at the community college during the summer when I was sixteen, that was just really well taught, and being able to type. I type really fast now, and there's no pain.
My senior year Advanced Placement English Teacher asked me to drop the class because of my poor handwriting. He was quite taken aback when I started screaming at him. I'd had enough of teachers criticizing my handwriting, I didn't need to hear it again when I was seventeen years old.
He was concerned that I couldn't pass the exam (which could get me college credit) because the judges wouldn't be able to read my essays.
He proposed a compromise. He suggested that I block print.
I had no problem with that. And at the exam at the end of the year, I turned in my exam neatly block-printed in all capital letters. I just used bigger capitals for where a capital was really required.
I was the only student in my school that year to get a 5 on the english AP exam (a perfect score).
[PATCH] : sock_writable not appropriate for TCP sockets
hi marcelo-
[ i sent this patch August 30 against 20-pre5, and it appears to have been
dropped. this is an important performance fix that should be included in
2.4.20. i apologize for not tracking this more closely. ]
sock_writeable determines whether there is space in a socket's output
buffer. socket write_space callbacks use it to determine whether to wake
up those that are waiting for more output buffer space.
however, sock_writeable is not appropriate for TCP sockets. because the
RPC client's write_space callback uses it for TCP sockets, the RPC layer
hammers on sock_sendmsg with dozens of write requests that are only a few
hundred bytes long when it is trying to send a large write RPC request.
this patch adds logic to the RPC layer's write_space callback that
properly handles TCP sockets.
patch reviewed by Trond, Alexey, and DaveM, and already accepted in 2.5.
I wonder if I can get the name changed from Linux to Evilix by sending a patch to Marcelo and just mentioning that Trond, Alexey and DaveM have reviewed it and it's already in 2.5...;)
As some people here on slashdot (an article IIRC) hinted at patches in 2.4.20 being in possible violation with the DMCA, and hence waiting to release.20, I guess these are all either cleaned up by now or not in the patch at all.
Can somebody give me a pointer to information on the actual problems and the resolution as well?
IIRC, it wasn't so much the patch itself that was in violation of the DMCA (Dilbertized Merkin Copyright Anomaly) as the description of the problem. [theregister.co.uk] So I can't describe it to you, but if you *aren't* American, you can safely click on this link, [thefreeworld.net] which will tell you. (Read & click-through the licence/disclaimer, then pick it off the drop-down menu thingy. Yeah, it sucks, but so does a copyright law that prevents people from fully documenting software bugs. Sorta like the evening news in some places--"Scientists think this common household substance could kill you! We'll tell you more on Channel 11's News at Eleven!")
Having read both the changelog and searched the kernel archives it's interesting to note that way back in 2.4.20-pre3 the Athlon MP/XP prefetch bug work around was pulled out of the kernel.
Subsiquently, Alan Cox in the kernel mailing list archives responds to someone asking about this and says that he thinks some of the VM changes have fixed at least the AGP problems but not the mmap ones, to quote:-
-ac has it removed. I didn't know Marcelo had it removed. Andi Kleen has
a patch for doing most of the right things without trashing performance.
That may be what Marcelo merged. It fixed AGP but not O_SYNC mmap I
believe
this was posted on the 17th August and there's no further mention of the problem as far as I can see.
If this hasn't been fixed in the full 2.4.20 release then there is no way I can install this kernel on our three dual processor Athlon MP boxes we use for mathematical simulations as the machines need to be able to run for many weeks on the problems and hence have to be rock-solid stable.
Does anyone know if the new VM fixes fully fix the Athlon MP/XP problems?
..can be found at the usual places, and please use a mirror for all your downloads"
Apologies if this has been discussed before and I missed it. (If so, ignore and silently send me the link to the discussion please.)
Why don't the kernel guys distribute the kernel sources over the well established P2P networks to reduce load on their servers and to speed up downloads for everyone?
I mean, why not put it into the donkey and publish the e2k link on the official kernel.org web page and also submit it to the sharereactor?
MD5 or other hashing can guarantee that the official release has not been tampered with.
Happily (running a 2.4.19pre) I tried
our local official mirror "ftp.de.kernel.org".
Nope, no 2.4.20 there.:-( So at least
I fetched the.19 patch.
This is just sad. I don't want
to hit the master "ftp.kernel.org" over and over
again and won't do it, but can't they wait
at least with the announcement until
most of the official mirrors
have caught up?
10000 people hitting "ftp.kernel.org" now -
this doesn't have to happen but it is on nearly
every kernel release. This leads the whole
mirror concept ad absurdum on every release.
Disclaimer: I don't need
2.4.20 "within the next days", but as many others
I like to hack around with new stuff, so if
it is announced, I want to fiddle with it.:-)
Reading the changelog, I was just happy to see they updated the drivers for the Adaptec AHA-2840 VLB SCSI controller and the SMC 91C92 Ethernet chip, which is found on my VESA Local Bus Ethernet cards. Ah, I'm thrilled because I just so happen to be building a file server right now that uses both.
Hey, you can't tell me I'm the only person in here who uses the VESA Local Bus on his servers!!!
It's not a matter of "Linux" having service packs. I'm assuming you use a specific distribution. You have to trust that distribution to release updates for your system as necessary. You can't binary patch the Linux kernel, because no binaries are released, only source. Red Hat, for example, has binary releases of the kernel (included in their distribution), but doesn't bother releasing service packs, instead they release updates as they see fit (pretty much the same thing).
I don't quite understand the obsession with using the latest and greatest. I'm not going to grab this and compile it for my machine; a) 2.4.19 works fine and b) I skimmed through the changelog and didn't really see anything that affected my situation, and c) My roommate will scream at me if I take down the server just to update the kernel by a double-point revision.
You mentioned when you update the kernel/compiler it breaks a lot of applications. You'll have to be more specific. I can see problems when migrating from a 2.2 kernel to a 2.4 kernel, or from gcc 2.x to gcc 3.x, but if you use one of the major distributions, this is trivial. The thought of using "service packs" on an open source operating system indicates to me that you don't have a clear handle on the way things work in Linux.
I don't quite understand the obsession with using the latest and greatest. I'm not going to grab this and compile it for my machine; a) 2.4.19 works fine
I used to be latest/greatest, but I've discovered that I wind up with a lot more time to do other things when I go with a more basic approach: keep up-to-date with Slackware's security updates.
I'm still running 2.4.18 with a -- *gasp* -- default kernel. I don't even bother compiling 'em for my machine anymore. Too damn lazy.:lol:
I tend to use the prebuild debian kernel images too. I do occasionally compile a 2.5 kernel but it really isn't worth it that much. When the 2.4.20 kernel enters SID my computer will automatically download and install it during an update.
I have a self compiled 2.5.44 kernel, but... you're right it really isn't worth the time it takes to configure, compile, and possibly try again.
Although I am an avid supporter of linux, I have alot of trouble keeping up with the latest version of my principal programs as well as the ever-changing kernal.
Then you would be aware that Linux is the kernel and nothing more. In this instance, your service pack is patch-2.4.20.bz2 [kernel.org], and that's it.
installing service packs in windows2000/XP, it updated the kernal and main programs like IE and media player all at once
Here's the thing: Linux doesn't have programs tied into the operating system that much. You could have a running Linux system without using a single GNU tool. As such, proposing service packs for Linux is nonsensical.
but I won't begin to start using [Linux] as my primary OS untill it has service packs.
Linux itself has service packs. Your distribution, on the other hand, is responsible for the rest of the pieces of software on your computer, and each distro has a different means of staying current. RedHat has up2date [redhat.com], Debian has 'apt-get update', and Gentoo has 'emerge -u'. Take your pick.
Just a point of interest, MS Service packs don't upgrade the media player, web browser, etc..., they update the base install. As a person who is forced to upgrade far too many Windows machines for my mental health, I know that even on windowsupdate.com, these are seperate updates from the service packs.
Absolutely and with debian if you stick apt-get update apt-get upgrade
as a weekly.... or daily.... cron-job
Argh. Don't do that. Really. You know those annoying questions that the upgrade process asks you? That is because the user is supposed to be
smarter than... Oh. Nevermind. Sorry I brought
it up:-)
You raise some good points but I have to say this. Microsoft has the benefit of actually owning the software that they release Service Packs for - from the Kernel to their Web Browser. The same cannot be said for OSS projects.
There is an equivelance to service packs in the Linux world, and that is the distro. If you think about it, each *.* distro is basically a service pack, bringing updated and more robust code in an easy to use package.
Funny, last time I installed a Windows Service Pack it did not upgrade MS Office nor Photoshop...Upgrading a kernel won't break apps, though you might need to recompile/reinstall certain "module" drivers (NVIDA for example). For an "avid" supporter of Linux, you don't seem very balanced or accurate in your critique of the system. Odd. Of course, you could also be a MS plant trying to sow discord among the faithful...I'm sure there are quite a few around here. Hey, if I had billions to spare I'd sure hire a few people to spread FUD on the web sites associated with the "competition."
#!/bin/sh # ##### # # Linux Update # *Almost* as dangerous as # Windows update # sudo/usr/bin/apt-get -qq update sudo/usr/bin/apt-get -qq -y upgrade
# Save file in/usr/local/bin # chmod o+x filename # Create link on desktop # Name link Linux update # You now have the ability to upgrade your system # with *no* way of controlling what gets put # there! Just as with windows!
There was at least one very important change for me personally - support for KT-400 motherboards (by adding support for VIA8235 southbridge). I had gotten 2.4.20-rc3 for this support when I got my new motherboard, but now it's official.
Incedentally, 2.4.19 will sorta work on a KT-400 board, but disk access is really slow because it can't turn on DMA.
I beleive the reiserfs write_file function was added to the reiserfs filesystem. This speeds up writing large files on a reiserfs formatted volume. Which on my boxes is every partition except/boot and swap.
I've released a total of 0 kernels so far and I intend to release a total of 0 more kernels for the next many many months to come. By your rating Linus' got nothin on me:)
I continue to wonder why every kernel release some one must complain why it isn't news or express how they don't care. Slashdot does not revolve around you, although by tweaking some of your preferences you can get it close.
Uhm... are you SURE? You sure it's not the new 2.5 development kernel you're talking about? Cause i think if you looked into it, you'd realize that all these massive changes you mentioned, improving threading, I/O, VM and the rest are changes happening in the 2.5 kernel. They are major changes, and very significant. But they're happening in 2.5.
This release is just an incremental release. Bugfixes here, added support there... no major changes, just evolutionary changes.
Good to see the mods are looking for informative comments... however, it's sad when they mod up comments that don't reflect the facts.
I bet a few portscanners would have fun with that one. However, there are other ways to deal with that sort of thing, AFAIK.
I'm happy with my 2.4.19 on my SMP boxes, and I didn't notice any bugfixes that I just *have* to have. Well, I *did* add kernel-pre-empt and the (0)1 patches as soon as they came out....
*sigh* Looks like I'm gonna wait for 2.6, I bet that one really rocks!
vojtech_suse.cz
[PATCH] Add vt8235 support
Hi!
This patch adds support for the vt8235. Marcelo, please apply it to current 2.4.20 rc. It doesn't break anything, basically adds an entry to the table of supported devices. Thanks.
If you do a search of the changelog for 8235 you'll find it.
i386 support is still there, those i586/i686 distro's are just that, distro's.
I've got an old (circa 1991) 486-DX25 machine here that I'm going to play around with as soon as I can dig up an old ISA NIC.
Actually I have a 486/25 in the corner here... I bet it would be good for a LFS (linux from scratch) install, since the whole thing would only be maybe 150Mb...
Hrmmm, excuse me, I've got to log off and try that one out.
first compile... (Score:4, Funny)
Re:first compile... (Score:2, Funny)
Repeat! (Score:5, Funny)
Wait a sec...
Oh sorry, I guess I was developing a reflex action.
</humour>
Re:Repeat! (Score:2, Funny)
American English is akin to Microsoft English. Take a published standard and alter it ever so slightly, but annoyingly, so that documents (applications) have to be rewritten.
I know, I know... Score -1 (Anti-US post)
Haiku (Score:4, Funny)
A new kernel is released.
Truly, it is good.
A tree, bare of leaves.
A kernel, being released.
Note nature tie-in.
Re:Haiku (Score:5, Funny)
thinks he's cool as the fall wind
but he's a loser
Re:Haiku (Score:3, Funny)
No you stupid fool
You're an insensitve clod
I have no humor
Be kind to kernel.org (Score:5, Informative)
Re:Be kind to kernel.org (Score:4, Insightful)
Re: Be kind to kernel.org (Score:5, Funny)
> Dont download it now if you dont need it. there are peopel waiting to use those servers.
No problem, we can listen to Beethoven's 9th Symphony [slashdot.org] a few times while we wait.
These changelogs are getting too long... (Score:5, Interesting)
just my $2*10^-2.00
Re:These changelogs are getting too long... (Score:2)
Re:Be kind to kernel.org (Score:2, Interesting)
Informative? (Score:2)
Re:Be kind to kernel.org (Score:3, Interesting)
That's actually rather weird, because it is not that uncommon to have that load. If this number is correct, there has to be something wrong with the server. But probably, they are getting more traffic.
Well me? I went directly to a mirror after getting the announcement from the announcement list this morning and downloaded it from there before reading /.
The new kernel fixes the lcall DoS. While I have no untrusted users on my system, things like that is always good to have out of the way.
for all new users to linux... (Score:4, Funny)
When's the duplicate show up? (Score:5, Funny)
great! (Score:4, Funny)
Re:great! (Score:5, Funny)
*takes long drag*
WHOOOOOOA. that kernel is shiny.
No! Don't do it (Score:2)
How will you type with your hands shaking like that?
Unable to hit the enter key and start compiling... The horror... the horror.
Re:great! (Score:2)
Anybody else remember... (Score:2)
small VM updates... (Score:5, Informative)
<hch@lst.de>:
o dump_stack()
o backport yield() and conditional reschedule changes from
o small VM updates from -aa (1/5)
o small VM updates from -aa (2/5)
o small VM updates from -aa (4/5)
o small VM updates from -aa (5/5)
Is this using a Linus definition of small, or a normal definition of small?
Re:small VM updates... (Score:5, Funny)
It's small because part (3/5) contains all the code.
Re:small VM updates... (Score:2, Informative)
Marcelo Tosatti is managing the 2.4 tree.
Re:small VM updates... (Score:2, Insightful)
But you already knew that too...
Re:small VM updates... (Score:2)
I mostly used Linux (Debian) in the past with a little Free and OpenBSD.
After I read an interview with Linus where he was asked about the current Linux kernel versus new BSD and XP features, he said something to the effect of "I haven't really looked much at BSD or XP, but I don't see much of value there".
Which pretty much sounded to me like "I have not looked, I don't see any good".
This was during the times that the VM shamozzle was occuring and my Linux machine was becoming unstable.
This was the point where I decided that Linus was getting a bit arrogant. I am glad though, because my OpenBSD servers are very clean and stable and Theo not only sticks to his moral grounds but also has well thought out moral grounds.
Re:small VM updates... (Score:2)
Still 2.4.19 in linux/version.h (Score:2, Interesting)
I just patched my source tree and
linux/version.h still reads that I've got 2.4.19.
Did I screw up? Or am I right that they've forgotten to update it?
Re:Still 2.4.19 in linux/version.h (Score:2)
Re:Still 2.4.19 in linux/version.h (Score:5, Funny)
Is that you Yoda?
Re:Still 2.4.19 in linux/version.h (Score:2)
MmmHmmm, MmmHmmm!
Re:Still 2.4.19 in linux/version.h (Score:2)
'uname -a' gives the version number as well.
Re:Still 2.4.19 in linux/version.h (Score:5, Informative)
Its a dupe... (Score:4, Funny)
I don't know what the slashdot editors are on today. This has already been covered here [slashdot.org] and here [slashdot.org] and here [slashdot.org].
Wait a minute. Do those funny little numbers after the name actually mean something? Oh well, nevermind.
Re:Its a dupe... (Score:3, Funny)
Did they fix the new ptrace vulnerability? (Score:3, Interesting)
Re:Did they fix the new ptrace vulnerability? (Score:4, Informative)
I can't find it! (Score:5, Funny)
zlib in the kernel? (Score:2, Interesting)
Re:zlib in the kernel? (Score:2)
Re:zlib in the kernel? (Score:3, Informative)
Re:zlib in the kernel? (Score:3, Interesting)
Unfortunately, many CDs are used to store mp3/ogg/divx and the like, which don't really compress much. So zisofs is not necessarily very useful.
For anyone using reiserfs (Score:5, Interesting)
Re:For anyone using reiserfs (Score:3, Informative)
===
2.4.19 was released
2.4.20-pre1 to 2.4.20-pre11 were released
2.4.20-rc1 to 2.4.20-rc4 were released
2.4.20-rc4 became 2.4.20
Pre's come before rc's (release candidates)
usb fixes? (Score:2)
Re:usb fixes? -- see here (Score:2)
Reading and installing the patch from the pointers from here [linux-usb.org] changed everything for me. Re-compiled the kernel just 2 days ago. Also generally, if you want to get the latest out of your usb in Linux, I have noticed that linux-usb.org [linux-usb.org] has it first (or atleast soon).
Re:usb fixes? (Score:2, Interesting)
No more printers on fire? (Score:5, Funny)
Alan Cox (alan@lxorguk.ukuu.org.uk):
* replace end user confusing "on fire" joke with real info
We've just lost the best part of our kernel!
Re:No more printers on fire? (Score:2)
Re:No more printers on fire? (Score:2, Informative)
Eh, I guess it still in a way was a joke, but a joke based more on reality. Of course now, that is just preposterious, but eh whatever.
The great thing about open source: (Score:5, Funny)
Here's a patch [achurch.org] to put it back.
use the mirrors to download the changelog (Score:4, Funny)
Re:use the mirrors to download the changelog (Score:3, Interesting)
It works! (Score:4, Funny)
Re:It works! (Score:2, Funny)
Re:It works! (Score:2)
Hi, ComicBook Guy, how are you?
Broken USB mouse support fixed? (Score:2, Interesting)
Thank god my optical usb mouse had a usb->psmouse converter plug which I'm using as a temporary workaround.
Did they fix these showstopper bugs in 2.4.20? (Score:2, Interesting)
Kernel BUG at page_alloc.c:91! (kills kswapd)
Google groups [google.com] for "page_alloc.c:91". Usually blamed on NVidia drivers but notable cases have occurred without them. It's not clear whether the kernel team has made a notable effort to debug them, but they are real and occur on a variety of systems. When this happens kswapd stops working, which causes more bugs later on, and eventually a system reboot is required.
There are other period reports of BUGs being flagged with an otherwise normal kernel on the linux-kernel list.
Can't resist... (Score:2, Funny)
Re:Can't resist... (Score:2)
Tips on testing your new kernel (Score:5, Informative)
A while back I wrote a couple articles on Linux kernel testing:
(The articles are under the GNU Free Documentation License. I would be quite stoked if you copied or translated them. There are articles on other quality topics here [sunsite.dk].)
Re:Tips on testing your new kernel (Score:2)
Well thank you (Score:2)
I work hard to write good articles. Some are very difficult to write, and take a lot of time. But I believe in doing well by doing good [goingware.com].
PS. I meant to post the LinuxQuality links as MichaelCrawford, but I used a different computer that still had a cookie that logged me in as goingware. I want to be known online by my own name now.
Re:Well thank you (Score:2)
The slashdot crowd is interesting and harsh in its own way; thousands of people and thousands of viewpoints view and judge what you say. Even in this admittedly non-objective forum, it took me 6 months of effort to get my first story posted, and there were plenty of "flames" in response to it.
So, carry on, and I wish you good luck!
ps: my own site is embarrassingly out-of date and soon to be updated (next 72 hours) but here's a link to it: http://steigenlinux.org
I'm especially proud of the "Documentation" page
Why I write (Score:3, Interesting)
But most of my contribution to Free Software has really been in the form of writing. I have also written a lot of stuff which is not copylefted, but posted publicly on the web. here some more [byteswap.net] as well as this [goingware.com].
I have contributed some to zoolib [sourceforge.net], but that's mostly in the form of qa, project management (for the initial open source release) and marketing.
One reason I prefer to contribute by writing is that my normal programming work is so hard, that when I get time to take a break from it, it's difficult to work up much enthusiasm to write more code, no matter how fun the project might be. I imagine that's a common problem.
Another reason is that I feel that any contribution I could make to Free Software, at least in the limited time I have, would be small. I could fix some bugs, add some features, do some testing. But how many people would benefit from my personal contribution? I don't think that many would, at least not until I had the time to develop a really serious package, and I just don't have the energy for that. I have lots of ideas, but no time.
But I feel that passing on my experience by writing can benefit others far out of proportion to the effort I put in. That is because I aim my writing to enable others to do better. By writing well, I enable many other developers to code a little better, and many users to do better testing and bug reporting.
I could lead by example by writing good code, but how many people would learn by reading it? When's the last time you studied the source for some package you weren't really actively involved with? Prose is much more accessible.
This is all the more important because so few engineers of any sort are good writers. When my father was a civilian electrical engineer for the Navy, the shipyard sent him to a writing class so he could write better test plans! The man has a master's degree! But the Navy put lots of people through that class because so many of their engineers didn't know how to write.
What is funny is that I find writing much more difficult than programming. With software, you know when you're wrong. It's not always so clear with writing. The main reason I write so well is because most of my effort is put into editing - and I still find lots of mistakes later.
Even more ironic is that I used to hate writing with a passion. One major reason is that I have terrible handwriting - I can't read my own handwriting, and can't imagine how anyone else could. But the schools always used to require handwritten essays. They used to send me to remedial handwriting classes, which I really hated because they made my hand hurt. It's painful for me to write much by hand.
What did it for me was two things - a composition class I took at the community college during the summer when I was sixteen, that was just really well taught, and being able to type. I type really fast now, and there's no pain.
My senior year Advanced Placement English Teacher asked me to drop the class because of my poor handwriting. He was quite taken aback when I started screaming at him. I'd had enough of teachers criticizing my handwriting, I didn't need to hear it again when I was seventeen years old.
He was concerned that I couldn't pass the exam (which could get me college credit) because the judges wouldn't be able to read my essays.
He proposed a compromise. He suggested that I block print.
I had no problem with that. And at the exam at the end of the year, I turned in my exam neatly block-printed in all capital letters. I just used bigger capitals for where a capital was really required.
I was the only student in my school that year to get a 5 on the english AP exam (a perfect score).
How to get patches accepted? (Score:3, Interesting)
[PATCH] : sock_writable not appropriate for TCP sockets
hi marcelo-
[ i sent this patch August 30 against 20-pre5, and it appears to have been dropped. this is an important performance fix that should be included in 2.4.20. i apologize for not tracking this more closely. ]
sock_writeable determines whether there is space in a socket's output buffer. socket write_space callbacks use it to determine whether to wake up those that are waiting for more output buffer space.
however, sock_writeable is not appropriate for TCP sockets. because the RPC client's write_space callback uses it for TCP sockets, the RPC layer hammers on sock_sendmsg with dozens of write requests that are only a few hundred bytes long when it is trying to send a large write RPC request. this patch adds logic to the RPC layer's write_space callback that properly handles TCP sockets.
patch reviewed by Trond, Alexey, and DaveM, and already accepted in 2.5.
I wonder if I can get the name changed from Linux to Evilix by sending a patch to Marcelo and just mentioning that Trond, Alexey and DaveM have reviewed it and it's already in 2.5...
DMCA Violations (Score:2, Interesting)
Can somebody give me a pointer to information on the actual problems and the resolution as well?
Re:DMCA Violations (Score:3, Informative)
Windows compatible now... (Score:2, Funny)
Athlon MP/XP prefetch bug. (Score:3, Interesting)
Subsiquently, Alan Cox in the kernel mailing list archives responds to someone asking about this and says that he thinks some of the VM changes have fixed at least the AGP problems but not the mmap ones, to quote:-
-ac has it removed. I didn't know Marcelo had it removed. Andi Kleen has a patch for doing most of the right things without trashing performance. That may be what Marcelo merged. It fixed AGP but not O_SYNC mmap I believe
this was posted on the 17th August and there's no further mention of the problem as far as I can see.
If this hasn't been fixed in the full 2.4.20 release then there is no way I can install this kernel on our three dual processor Athlon MP boxes we use for mathematical simulations as the machines need to be able to run for many weeks on the problems and hence have to be rock-solid stable.
Does anyone know if the new VM fixes fully fix the Athlon MP/XP problems?
mirrors and P2P (Score:3, Interesting)
Apologies if this has been discussed before and I missed it. (If so, ignore and silently send me the link to the discussion please.)
Why don't the kernel guys distribute the kernel sources over the well established P2P networks to reduce load on their servers and to speed up downloads for everyone?
I mean, why not put it into the donkey and publish the e2k link on the official kernel.org web page and also submit it to the sharereactor?
MD5 or other hashing can guarantee that the official release has not been tampered with.
Am I missing something here?
silence
Linux and Mirrors (Score:2)
Happily (running a 2.4.19pre) I tried our local official mirror "ftp.de.kernel.org". Nope, no 2.4.20 there. :-( So at least
I fetched the .19 patch.
This is just sad. I don't want to hit the master "ftp.kernel.org" over and over again and won't do it, but can't they wait at least with the announcement until most of the official mirrors have caught up?
10000 people hitting "ftp.kernel.org" now - this doesn't have to happen but it is on nearly every kernel release. This leads the whole mirror concept ad absurdum on every release.
Disclaimer: I don't need 2.4.20 "within the next days", but as many others I like to hack around with new stuff, so if it is announced, I want to fiddle with it. :-)
See you all in #waitingforftpconnect .
VESA Local Bus (Score:3, Interesting)
Reading the changelog, I was just happy to see they updated the drivers for the Adaptec AHA-2840 VLB SCSI controller and the SMC 91C92 Ethernet chip, which is found on my VESA Local Bus Ethernet cards. Ah, I'm thrilled because I just so happen to be building a file server right now that uses both.
Hey, you can't tell me I'm the only person in here who uses the VESA Local Bus on his servers!!!
VServer patch for 2.4.20 (Score:3, Informative)
For those of you looking for the vserver with security contexts patch for 2.4.20.
Re:Decisions, Decisions... (Score:4, Funny)
*ducks*
*counts to 20, formkeys formkeys formkeeeys*
Re:how long will it be... (Score:5, Informative)
I don't quite understand the obsession with using the latest and greatest. I'm not going to grab this and compile it for my machine; a) 2.4.19 works fine and b) I skimmed through the changelog and didn't really see anything that affected my situation, and c) My roommate will scream at me if I take down the server just to update the kernel by a double-point revision.
You mentioned when you update the kernel/compiler it breaks a lot of applications. You'll have to be more specific. I can see problems when migrating from a 2.2 kernel to a 2.4 kernel, or from gcc 2.x to gcc 3.x, but if you use one of the major distributions, this is trivial. The thought of using "service packs" on an open source operating system indicates to me that you don't have a clear handle on the way things work in Linux.
Re:how long will it be... (Score:2, Insightful)
I'm still running 2.4.18 with a -- *gasp* -- default kernel. I don't even bother compiling 'em for my machine anymore. Too damn lazy.
Re:how long will it be... (Score:2)
I have a self compiled 2.5.44 kernel, but... you're right it really isn't worth the time it takes to configure, compile, and possibly try again.
Re:how long will it be... (Score:5, Insightful)
Here's the thing: Linux doesn't have programs tied into the operating system that much. You could have a running Linux system without using a single GNU tool. As such, proposing service packs for Linux is nonsensical.
Linux itself has service packs. Your distribution, on the other hand, is responsible for the rest of the pieces of software on your computer, and each distro has a different means of staying current. RedHat has up2date [redhat.com], Debian has 'apt-get update', and Gentoo has 'emerge -u'. Take your pick.
Re:how long will it be... (Score:2)
Re:how long will it be... (Score:2)
Re:how long will it be... (Score:2, Insightful)
There is an equivelance to service packs in the Linux world, and that is the distro. If you think about it, each *.* distro is basically a service pack, bringing updated and more robust code in an easy to use package.
Re:how long will it be... (Score:2)
Secret l33t update hints (Score:2, Funny)
#
#####
#
# Linux Update
# *Almost* as dangerous as
# Windows update
#
sudo
sudo
# Save file in
# chmod o+x filename
# Create link on desktop
# Name link Linux update
# You now have the ability to upgrade your system
# with *no* way of controlling what gets put
# there! Just as with windows!
Re:how long will it be... (Score:2)
Re:who cares? (Score:5, Funny)
Now, how exactly am I going to change your settings?
Re:who cares? (Score:2)
Re:Important changes? (Score:5, Informative)
Incedentally, 2.4.19 will sorta work on a KT-400 board, but disk access is really slow because it can't turn on DMA.
Re:Important changes? (Score:4, Informative)
Re:BSD-like unionfs for Linux? (Score:2, Informative)
Re:I'll wait for 2.4.20-ac1 or -ac2. :) (Score:5, Informative)
How is this impressive? (Score:4, Funny)
Re:Linux is truely impressing me now... (Score:3, Informative)
Re:That's all well and good, but is this really ne (Score:2, Insightful)
Re:Apparently (Score:5, Informative)
This release is just an incremental release. Bugfixes here, added support there... no major changes, just evolutionary changes.
Good to see the mods are looking for informative comments... however, it's sad when they mod up comments that don't reflect the facts.
Re:Apparently (Score:2)
I bet a few portscanners would have fun with that one. However, there are other ways to deal with that sort of thing, AFAIK.
I'm happy with my 2.4.19 on my SMP boxes, and I didn't notice any bugfixes that I just *have* to have. Well, I *did* add kernel-pre-empt and the (0)1 patches as soon as they came out....
*sigh* Looks like I'm gonna wait for 2.6, I bet that one really rocks!
Re:Is VIA KT400 (8377+8235) finally supported? (Score:3, Informative)
vojtech_suse.cz
[PATCH] Add vt8235 support
Hi!
This patch adds support for the vt8235. Marcelo, please apply it to current 2.4.20 rc. It doesn't break anything, basically adds an entry to the table of supported devices.
Thanks.
If you do a search of the changelog for 8235 you'll find it.
Re:Seriously - 486-33 (Score:2, Informative)
I've got an old (circa 1991) 486-DX25 machine here that I'm going to play around with as soon as I can dig up an old ISA NIC.
Re:Use Slackware (Score:2)