Doesn't everyone know? Linus is recovering from alcholism. He just started the 12 step program. This week has been really hard for Linus because Alan Cox keeps talking about "putting away a few pints at the pub" (he is English) on the linux kernal mailing list. There have been a few flame wars too between the people working on the vm subsystem. Apparently one is a tea-totler and the other a hard core drinker so Linus is leaning towards using the tea-totler's code but Alan says the hard core drinkers code is better...
I think we all need to try to support Linus and Alan without choosing sides. Just grab the latest kernel of your choice and compile away... Try not to mention free beer on the linux kernel mailing list in the next couple weeks. Think free tea or something similar.
I was excited reading the kernel changelog until I got to this line:
- Trond Myklebust: make NFS use SLAB_NOFS, and not play games with PF_MEMALLOC
I'm sure NFS won't mind using SLAB_NOFS, but it's cruel to prohibit it from playing games with PF_MEMALLOC. NFS has reached the point where playing games with PF_MEMALLOC is the sole respite from the drudgery of its mundane life. None of the other protocols will play with it since the Trivial Pursuit incident of 1998, and it's banned from EQ for excessive Britishing.
Sure, we've all been inconvenienced a little now and again when NFS is playing games with PF_MEMALLOC, but it wasn't that bad, and it brought a glimmer of joy into NFS's otherwise bleak existence. Now NFS will be forced to sit alone in its room playing X Bill all alone until it goes mad and starts initializing remote filesystems at random.
Then where will we be?
Trond Myklebust, I hope you're happy with yourself. What did NFS ever do to you? It's just cruel, and we'll all have to deal with the consequences when people start running NFS on 2.4.13. You should be ashamed.
*telekon
--
To understand recursion, you must first understand recursion.
Slashdot Mirror
"Use the mirrors!"
"Make sure you patch, don't waste bandwith!"
"Damn, there goes my uptime"
"Heh, I'm STILL running Kernel 1.2.1!"
"Does anyone NEED to use the latest kernel? What does it add?"
"Use the latest kernel! Testing is vital!"
"2.4.13? I thought Linux was at 7.2?!"
If I've forgot any, post to this thread. Hell, if you're any of the above postings, post to this thread....
Doesn't everyone know? Linus is recovering from alcholism. He just started the 12 step program. This week has been really hard for Linus because Alan Cox keeps talking about "putting away a few pints at the pub" (he is English) on the linux kernal mailing list. There have been a few flame wars too between the people working on the vm subsystem. Apparently one is a tea-totler and the other a hard core drinker so Linus is leaning towards using the tea-totler's code but Alan says the hard core drinkers code is better...
I think we all need to try to support Linus and Alan without choosing sides. Just grab the latest kernel of your choice and compile away... Try not to mention free beer on the linux kernel mailing list in the next couple weeks. Think free tea or something similar.
I was excited reading the kernel changelog until I got to this line:
- Trond Myklebust: make NFS use SLAB_NOFS, and not play games with PF_MEMALLOC
I'm sure NFS won't mind using SLAB_NOFS, but it's cruel to prohibit it from playing games with PF_MEMALLOC. NFS has reached the point where playing games with PF_MEMALLOC is the sole respite from the drudgery of its mundane life. None of the other protocols will play with it since the Trivial Pursuit incident of 1998, and it's banned from EQ for excessive Britishing.
Sure, we've all been inconvenienced a little now and again when NFS is playing games with PF_MEMALLOC, but it wasn't that bad, and it brought a glimmer of joy into NFS's otherwise bleak existence. Now NFS will be forced to sit alone in its room playing X Bill all alone until it goes mad and starts initializing remote filesystems at random.
Then where will we be?
Trond Myklebust, I hope you're happy with yourself. What did NFS ever do to you? It's just cruel, and we'll all have to deal with the consequences when people start running NFS on 2.4.13. You should be ashamed.
*telekon
To understand recursion, you must first understand recursion.
I want to be a slashdot editor too (looks easy):
if(new_kernel_arrived) {
version=X.Y.ZZ
if(slow_week) {
version=X.Y.ZZ-preWW
}
print "Looks like Linux X.Y.ZZ is out. You can get it at the usual place (kernel.org) and the mirrors. Check out the Changelog."
if(CmdrTaco just upgraded to ZZ-1 ||
weekday=tuesday) {
print "This is lame."
} else {
print "Grab. Test. Enjoy"
}
}
Thomas S. Iversen
Alan Cox keeps talking about "putting away a few pints at the pub" (he is English) on the linux kernal mailing list.
Well, I guess that proves Alan doesn't read slashdot. He is Welsh. BIG difference. Especially when it comes to things like Rugby.
FreeBSD (http://www.freebsd.org/)
Don't forget
Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
Shoot - might as well go for the gusto:
/dev/random
chmod +x
/dev/random
Yep. That ought to do it. Hey, why is windows booting?!?
No thanks. I don't smoke anymore.
(Score +1; Ballsy)
:-)
You cannot apply a technological solution to a sociological problem. (Edwards' Law)