Slashdot Mirror
Linux Kernel 2.6.0-test10 Released
antrix angler writes "Linus Torvalds released the 2.6.0-test10 Linux kernel today, tentatively calling it the "stoned beaver" release. Linus plans to hand the kernel over to Andrew Morton in a few weeks, and then it will be up to Andrew to decide when we see the final 2.6.0 stable kernel. Download it from a mirror."
i had some serious problems with my usb mouse in test9 (while it worked in test4 and before), and i don't see any mouse related fixes in the ChangeLog, so for now I guess usb mouse users should stick with older releases.
i really hope this gets fixed before 2.6.0, especially since it worked before..
...nice beaver!
It works for me. Upgraded from 2.6.0-test9-mm5.
:)
This may become the final 2.6.0
Rock on, Linus and team.
-- Note: If you don't agree with me, don't bother replying. I won't read it.
Here
Let's share our bandwidht!!
--
"Res publica non dominetur"
Is 2.6 really noticably faster than 2.4 for regular desktop use (X responsiveness, etc...)?
Why thank you, I just had it stuffed.
-- Note: If you don't agree with me, don't bother replying. I won't read it.
I think this name confirms Linus's rockstar-like role in the open source world, as it shows he is now addicted to both drugs and sex.
I think it's better to ignore such messages and let the moderators send it quickly to -1. You're advertising for the nut by respoonding with the same subject.
"I thought that since some big corporations like IBM and Novell are picking up Linux, things would get a little more professional."
Well, how about the Shaved Beaver?
Your boss would probably be more interested why you were running a test kernel on his hardware, rather than what code name it had!
Well I've been using the 2.6 series for about the last 3 months on my desktop. Not had one crash and its been under heavy load. Definitly shaping up well.
Now if I could just get iptables working right
Rus
Cheap UK and US VPS
Nope, you do not /have/ to enable devfs in 2.6. I'm using it on several machines just fine that do not have kernel support for devfs or the userspace devfsd component.
/vastly/ improved.
I've had both good and bad experiences with devfs+devfsd, but any problems I have had have been quickly debugged and fixed (or I've bashed my forehead for being pebkac error). Generally I err on the side of caution (except for this 2.6.0-test deal, since more testers can't hurt), so I've decided to remain without devfs+devfsd on several machines.
Yes, the build system in 2.6.0-test is
1. Register the in DNS beaver-overload.com
2. Wonder why there is no email
3. Correct registration to beaver-overlord.com
4. Read strange emails from hundreds of Kernel compilers voting on the above issues
5. ???????
6. Sell beaver-overload.com to a Sex site
7. Profit!!!!
Paul Gillingwater
MBA, CISSP, CISM
You severely overestimate the technical qualities of my boss.
Anyway, if you want to make sure your product works on the newest kernel, you want to start testing BEFORE the stable version comes out, no?
I could care less, but not without a lobotomy
I know I'm anonymous, but can anyone tell me whether I have to/ really really should turn on devfs if I upgrade to 2.6?
I've tried using devfs under 2.4 several times but have never succeeded in getting it to work with my crufty (been around since slink) debian box.
And since I use ALSA and XFS the 2.6 kernel would simplify compiling desktop kernels no end.
I don't know about 2.6, but I use 2.4.x with devfs on two stable boxes ("servers" running on obsolete desktop hardware) and two unstable boxes (a desktop and a Powerbook), and they all work fine. Tab-completing commands is so much nicer when you only have device nodes for hardware you actually have; it's also handy to be able to see (say) whether your CD drive was detected properly, or how many partitions a hard disk has, by looking at the device nodes.
If you're using at least Debian 3.0 stable (woody), install devfsd, install a devfs kernel, reboot, and everything should Just Work.
What specific problems do you have with it?
Not at all. In fact, devfs has been declared obsolete in 2.6; on those machines where I'm testing 2.6, I'm using a plain old /dev until I have time to figure out how sysfs and udev are supposed to work.
Now, if you want to use devfs, all you have to do is: 1) install devfsd, 2) compile a new kernel with devfs enabled and set to mount on boot, 3) install said kernel, 4) reboot. Doing 1 before 2 is the tricky stuff for me, I always forget that. You may also have to adjust some permissions and/or create some nonstandard devices you made yourself, but I've been using devfs on all my machines with 2.4 and it's working perfectly.
Now it's fun to think about it as "the final 2.6.0 stable kernel". I would rather call it the *initial* 2.6.0 stable kernel.
BTW, I'm not faking Linus, here is the signature :)
--
"Res publica non dominetur"
These explained a little:
... thousands?
udev presentation (PDF), Google HTML version.
Detailed paper on udev (PDF), Google HTML version.
devfs works fine for me, but since some people (see second link) want thousands of disks I guess I'm not the target market. I mean
Slashdot looked deep within my soul and assigned
me a number based on the order in which I joined
Well, the (code)name Longhorn has been in the tech media for some time now. Are you saying Microsoft could have called it "Big Floppy Donkey Dick", without negative effects?
One devfs gotcha in 2.6, which caught me out for a while, is that the devpts (pseudo-tty) functionality has been separated out. In 2.4 kernels, mounting /dev using devfs automatically mounted /dev/pts too; however, this behaviour has changed in 2.6, and you have to mount /dev/pts explicitly:
On some systems (such as Gentoo), the rc scripts are smart enough to do this automatically.
Tubal-Cain smokes the white owl.
No. This was fixed in 2.4.19 (well, /really/ fixed in .20 since .19 really just disabled it completely) and in 2.5. See this page.
I thought that since some big corporations like IBM and Novell are picking up Linux, things would get a little more professional.
Why? so that yet another culture can get swalled into the soulless, humourless, corporate machine? I for one don't want linux to be synonymous with IBM
I'm running 2.6.0-test10 at this very second, and have been running every test version since test2 except for test8 (screwed up my sound system for some reason). I gave udev and hotplug a try but found hotplug to be straying behind. They had a few notes on their web site about patches for pciutils and usbutils to add something that probed all the devices (especially for coldplugging), but also said that you won't need them for 2.6.x due to the new sysfs filesystem (mkdir /sys; mount none /sys -t sysfs). But then doesn't say anything else about hotplug utility support in 2.6.x. So without a working hotplug, udev is kind of useless (since it interfaces with the hotplug).
:).
ATM I'm using murasaki as my hotplug facility, as I've personally had the best luck with it (that's really the only reason), especially on the 2.6 test kernels. I'm also still using devfsd (which will be obsoleted by udev).
This is the extent of my knowledge about new things like udev, etc. in the new kernel. So anyone should feel free to correct any innacuracies, omissions or blatant stupidities
- Sil
Are you saying Microsoft could have called it "Big Floppy Donkey Dick", without negative effects?
But I always assumed that Longhorn was a euphemism *for* Big Floppy Donkey Dick.
A new interrupt controller dreamed up by Intel to enable multiprocessing. It seems to cause a disproportionate amount of problems under Linux (a dedicated server I run would crash something like every 4 hours before I enabled noapic)
Unless you've got more than one CPU, it's more trouble than it's worth. The old 'legacy' 8259 interrupt controller (or the interface your system chipset supplies that emulates it anyway) works just fine for single-CPU applications.
I don't really see how this has got anything to do with Linux or professionalism, since, as I said, the kernel is still "Linux", and this is a test kernel.
But whatever. IHBT.
Clever signature text goes here.
JFS seems to be abanodoned. Recenctly I've found serious bug in JFS and submitted it to their BTS. After 10 days there's no comments, no followups...
Almost everyday, I get spam telling me I can download images of stoned beaver... I never realised it was a new kernel! .
Note that this patch doesn't apply directly to any of the 2.6 kernels; I just make the change by hand, since it is only one line. I have no idea why Linus isn't including this patch; it has been available for months, and it isn't exactly huge. It does fix the Radeon frame buffer issues.
Also note that /. is munging the code; it insists on inserting a "&nbs p;" that shouldn't be in there. I can't seem to get rid of it. Gotta love buggy software.
The operating system is not called "Stoned Beaver". It's an internal codename for this particular version of the Kernel. The OS is called Red Hat, SuSE, Debian, GNU/Linux or Linux. Depending which style you prefer.
My OS is Linux. More presicely, Gentoo Linux. I don't call it 2.6.0-test9-mm1. If I ran test10 on it, it would still be just "Linux" or "Gentoo Linux" and not "Stoned Beaver"
Seriously, at least TRY to use your brains, OK?
Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss Programs - -all next week on Town Talk.
You should always leave a link allowing the uninitiated to learn
FYI, I saw Naked Gun on ABC here a few years ago and they had removed that comment by Jane. What is the point of showing a movie like that and then censor out the jokes?
Help fight continental drift.
RSB will be the actual 2.6.0 release. From there, incremental 2.6.x releases will be named as follows
2.6.1 - Serene Beaver
2.6.2 - Perturbed Beaver.
2.6.3 - Infuriated Beaver
2.6.4 - Flip Out and Kill Everyone Beaver
2.6.5 - Beavergeddon
2.6.6 - Beavercide
2.6.7 - Beaver of the Apocalypse
2.6.8 - Nuke the Beaver from Orbit. It's the Only Way to be Sure
You want the truthiness? You can't handle the truthiness!
Well, devfs appears to be depreciated in favour of sysfs. So no, you don't need devfs.
Black and grey are both shades of white.
I agree, if you want a pretty business name, go wrap the Stoned Beaver up in a distro or just call it by it's version number. You're free to do so.
That's intentional, and is part of the anti-page-widening-post code. It prevents really long lines causing the page to overflow.
1) open web broswer and goto www.google.com
2) type "building 2.6.0 with redhat"
3) browse results.
Or, goto kerneltrap.org, for eg.
http://kerneltrap.org/node/view/799 - a nice article, but slightly outdated now.
The biggest gotya is the requirement for a new modutils prior to running the newer kernel. Read the article for more info.
- I stole your sig.
2.6.9 - Ward, I think there's something wrong with the Beaver
The only reason we have the rights we have is that people just like us died to gain those rights. -- Cheerio Boy
I'd rather have badgers on shrooms instead.
Escher was the first MC and Giger invented the HR department.
The reason that devfs is not yet deprecated in favor of udev yet is that udev depends on the kernel using the new driver model for everything that gets a device. Of course, that's not udev work per se, but it means that, for example, input devices (IIRC) don't yet work quite right with it.
The kernel having explicit knowledge of what it's doing in a uniform format is a new feature in 2.6, and it's not completely universal yet. Once that all works correctly, udev should work perfectly, and it is a better design than devfs, because it puts device naming in userspace, but device numbering comes from the kernel, and the kernel tells userspace what each device actually is. This is how the division of labor is supposed to be: the kernel has internal information, which it maintains, and an API, which it defines, but userspace can use that API to specify policy.
Exactly what I was going to say. I've submitted this bug at least once, but probably twice, and I keep getting hammered with, "it's not a bug, it's a feature."
You know, because since the renderer is going to reduce the entire html-character code into a single character, it should obviously be treated as a group of 4 characters by SlashCode.
You know, not that I'm bitter or anything about them ignoring something that's as easy to fix as adding an alternative in a regular expression.
There's your half-line fix... well, to some degree... don't blame me entirely, I don't like perl. Fact of the matter is that it's a fairly simple regular expression change, and it will treat &...; as a single character, which it should.
I am unamerican, and proud of it!
Ever since the "greased weasel" series of
kernel releases I have been stuck for a good name.
This release is tentatively called the "stoned beaver" release (beavers are
_almost_ as good as weasels, as I'm sure Scott Adams would agree).
I think that the "Stoned Beaver" is almost as good of a name as "Greased Weasel". However, I would like to submit the following suggestion.
I feel that "Stoned Beaver" sends the impression that this release has problems with volatile (short-term) memory and gets the munchies for more resources.
To improve market visibility, I recommend that the next testing release be named "Shaved Beaver". I feel this name denotes something that is sleek and highly visible. The only shortcoming I could foresee for this name are emails or newsgroup postings with the subject line "Shaved Beaver ready for pounding". It may be a possible problem for SPAM filters.
I agree that it's tough to beat "Greased Weasel", but if you really are stuck coming up with a new name, I think "Greased Beaver" would be almost as good.
It is easier to build strong children than to repair broken men. -Frederick Douglass
And what's wrong with drugs and sex, anyway? I mean I could understand being against sex addiction, but drugs?
Oh wait, that came out all wrong...
No matter how many of my rights are taken away, somehow I still don't feel safe. -Frigid Monkey
you want only one of the two threading ports to respond to hardware events. Not a good idea, it's best to spread that out... especially since a thread could starve the other on scarce shared processor resources on the PIV
THIS THING CAN TURN ON A DIME, MACROSSZERO STYLE ALSO FUCK BETA, ~NYORON
That's wrong. "sysfs - _The_ filesystem for exporting kernel objects." (from Documentation/filesystems/sysfs.txt). sysfs exports kernel data structures to userspace and in the long run should leave /proc for processes like it was meant. it is no replacement for devfs.
but there already exists a userspace daemon called udev which simulates devfsd behaviour by taking the information found in sysfs.
i just upgraded to 2.6-test10 and found out that insmoding the nvidia module i compiled against 2.6-test9 loads just fine! i am of course going to compile it against 2.6-test10 for maximum stability but minor kernel version driver inconsistance problems allways gave me a headache with binary only drivers. (this really inproves that)