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 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.
Your boss would probably be more interested why you were running a test kernel on his hardware, rather than what code name it had!
I suppose the real answer is "it depends, but generally yes." I don't use kernel preemptibility, and it sure seems "feels" faster -- which is of course such a rambling description that it's difficult to qualify.
f set=29&rows=30
I'll point you to the response I made here:
http://www.osnews.com/comment.php?news_id=5208&of
(Mine's #29.) Yes, I know it's much more so the combination of XFS and mm than it is just mm. I should amend that comment...
I've had intermittent problems since test8, and noapic doesn't seem to have an effect (using VIA chipset). On some of the kernels I compiled, it would work on one, but not the other. The only differences between them usually were usualy which mm patch I was using. Test9-mm5 seems to be working, for now anyway.
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
No, it isn't -- it's actually slower, as it spends more time in the core kernel than the older versions. But it *feels* faster, because it is better at giving time to processes when they need it.
Worst-case scenario: Start two CPU-bound tasks on a single CPU, and measure their performance.
Best-case scenario: Start a huge amount of small tasks with unpredictable CPU needs, but which all in all saturates the bus. You'll see a gain.
My guess is that the old kernel scheduler is a little better for games and single-application server-use, while the new one is much better for normal desktop users or overloaded boxes.
Regards,
--
*Art
For reference here's how I fixed this, on my Debian machine: I edited /etc/X11/Xwrapper.config and removed completely the line which sets nice_value.
If you don't want to restart your X server to make the change have effect, then you can instead do:
renice 0 PID
where PID is the process ID of the X server.
Rich.
libguestfs - tools for accessing and modifying virtual machine disk images
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.
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.
for anyone thinking of posting this type of post, perhaps this information would be a little more useful if you indicated the particulars of your system. the fact that this kernel "works" for a particular slashdot reader is not much to go on, by its self.
#include <sound_of_karma_points_evaporating.ogg>
The Russians have won. They have made the world a cesspool of distrust, greed, fear and hate.
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!