Slashdot Mirror
Linux Kernel v2.6.23 Released
diegocgteleline.es writes "After 3 months, Linus has released Linux 2.6.23. This version includes the new and shiny CFS process scheduler, a simpler read-ahead mechanism, the lguest 'Linux-on-Linux' paravirtualization hypervisor, XEN guest support, KVM smp guest support, and variable process argument length. SLUB is now the default slab allocator, there's SELinux protection for exploiting null dereferences using mmap, XFS and ext4 improvements, PPP over L2TP support. Also the 'lumpy' reclaim algorithm, a userspace driver framework, the O_CLOEXEC file descriptor flag, splice improvements, a new fallocate() syscall, lock statistics, support for multiqueue network devices, various new drivers, and many other minor features and fixes. See the changelog for details."
After 3 months, Linus has released Linux 2.6.23. This version includes the new and shiny CFS process scheduler, a simpler read-ahead mechanism, the lguest 'Linux-on-Linux' paravirtualization hypervisor, XEN guest support
Yes, what they don't mention is that the XEN "guest support" is in the form of a crowbar.
The theory of relativity doesn't work right in Arkansas.
...the extra flavor that makes this release a little bit more headline-worthy than usual is probably the whole controversy involving the Completely Fair Scheduler. Between Con Kolivas leaving kernel development, the Really Fair Scheduler flamewar and almost ten release candidates, the whole 2.6.23 development was some kind of geek soap opera.
Hello everybody out there using Linux -
:-)
:-(.
I'm doing a (free) operating system based on GPL3 (just a hobby, won't be big and professional like Linux) for x86. This has been brewing since april, and is starting to get ready. I'd like any feedback on things people like/dislike in Linux, as my OS resembles it somewhat (same physical layout of the file-system (due to practical reasons) among other things).
I've currently ported bash(3.2) and gcc(4.2.2), and things seem to work. This implies that I'll get something practical within a few months, and
I'd like to know what features most people would want. Any suggestions are welcome, but I won't promise I'll implement them
PS. Yes - it's free of any Linux code, and it has a multi-threaded fs. It is NOT protable (uses 386 task switching etc), and it probably never will support anything other than AT-harddisks, as that's all I have
You needn't worry about the kernel in this case, because the applications aren't paying any attention. Mozilla happily passes all open file descriptors (sockets, pipes, and files of any kind) to subprocesses like Adobe Reader. There's been a bug open on it for eons. Other applications have the same problems. It may be convenient to have O_CLOEXEC in open(2) calls, but it won't help of the application writers don't know what they are doing, or if they have "abstracted" their platform interaction to such a degree that they can no longer interact with any platform services (*cough* jvm *cough*).
personally, i think, that the height of computing was 'cron'. you needed a report every morning, put it in cron. you needed to analyze data every week, put it in cron.
;) i mean, heavily under the influence.
computing was supposed to automate. supposed to make everyones lives easier by helping the person. now look at it. walk into any corporate office and you'll see countless people (myself included) clicking on this and that to satisfy what the computer wants out of you. it feels like you are there to help the computer achieve uptimes, or defragged disks, getting rid of viruses, blocking ports, unblocking ports...
am i there to help the computer do it's job? or is the computer there to help me do mine?
why does the computer occupy the center of my desk? why isn't it tucked away in the utility closet?
but that's a more philosophical discussion to be had - under the influence
Dude, if you actually read the kernel mailing list you would know that Linus has said that he can change the license whenever he wants. All he has to do is post a notice to the list, and add the same notice to the license file specifying a date when the license will switch over. Anyone who doesn't agree will have an opportunity to opt-out, at which point their code will be pulled out and rewritten, or opt-in. The ones that don't do either can be assumed to opt-in until such time as they complain.
This has been done before.. with the syscall interface exception.
Stop repeating myths and do some research.
How we know is more important than what we know.
You forgot the hardcoded support for Swedish keyboard layout, only.
I just think in order to get Linux adopted by the populous, it's going to take more than kernel enhancements to see that through.
But see, the problem is that nobody's arguing that kernel enhancements alone *are* going to result in the rise of desktop-Linux-for-the-masses. What you're doing is akin to walking into a university campus that's just expanded a bit and proclaiming how they're not doing enough to save the baby whales. Yes, some of the facilities and information dispersed therein may be getting used by people looking to save the baby whales, and some of the staff may even be interested in saving the baby whales themselves, but the university is not in fact there to save the baby whales, but instead serve as general resource that can be utilized in a number of different and often drastically divergent ways.
Just take OpenBSD and re-release it under the GPLv3!
Lolnus?
:-(
I can has new scheduler?
I had new scheduler but Linus eated it
Climate Progress - Hell and High Water
"It takes a specific type of person to get Linux running and to a point where it can be productive even for nontechnical users (which is the majority of users that use computers)"
WTF???
Linux installation for dummies, PHBs and Windows sysadmins (but I repeat myself)
If you can't follow that, print it out and pay some PFY* in grade 9 $20.00 to help you.
(if you don't recognize the reference, you're obviously new here and deserve to be beaten with a clue-by-four, both ways, in the snow, etc...)
An exploit with feature-complete proof of concept was released for x86_64 linux kernel ia32syscall emulation by cliph at isec in Poland. Exploit code was wildly popular on milw0rm, indicating that this local exploit has lots of potential.
http://tinyurl.com/4ny52
the lguest 'Linux-on-Linux' paravirtualization hypervisor
Linux on linux, that's so hot!
Richard, is that you?
Slashdot: Failed Car Analogies. Amateur Lawyering. Anecdote Battles.
Not to nitpick, but the milw0rm main page says '2007-09-27' beside that exploit. I'd hardly call that today's Linux news.