Slashdot Mirror
Linux 3.0
An anonymous reader writes "In a post to the kernel mailing list, Rob Landley, sitting in for the floating Linus, cracks the whip over what will be in Linux 3.0. His orders are on Linux and main."
← Back to Stories (view on slashdot.org)
You mean it was determined the kernel is going to be called 3.0 instead of being called 2.6 after all?
"Evil will always triumph because good is dumb." -- Dark Helmet
LKCD: Linux Kernel Crash Dumps. Really, I wish this had been there for the first half of 2.4 (testing-pre?). Supposedly it'll be able to save an image of kernel memory when the kernel panics to a special partition so that it can be recovered after reboot allowing easy analysis of the image. This alone should cut down greatly on the amount of work required to submit bug reports.
Try not. Do or do not, there is no try.
-- Dr. Spock, stardate 2822-3.
I've been reading the list and well..
... Linus essentially said he wasn't leaving anyone in charge so they're trying to get one main list to give to linus (with links where possible) so that he can quickly go threw everything when he gets back
This is about 1 of 3 different posts talking about 'what needs to be shown to linus when he gets back'
This is also the very first post of this one thread specific.. theres been about 5 or 6 more major things added to the list that people are hoping to get in
Also.. it seems noone on the list is sure whether this will be 3.0 or 2.6 at least noones given any real definate answer as far as I could see..
the lastest version of this list is here.. which compiles all the other threads in one.. is here
Are you from Mars? There are two versions of automount in Linux and there is something called "supermount". But if you use Linux for servers, then you are deeply wrong if you put these things into action. The automount feature is not embedded to Linux just for that reason. A good secured server should in no way give a chance to automount third party media. Only the admin should do it and he shall have a chance to do it flexibly and correctly. Believe me, that this is the true way of administration. Maybe where you work people may think it is too bad that Linux doesn't automount every piece of crap that may either trash the system or give a chance for information leaks. But, on my years of sysadmin I consider that this is one of the best features not only of Linux but of the whole *NIX family.
Because Slashdot is a site for technical people. They care. I'm not a kernel developer, but I care about Linux development.
If you don't care, then:
1) You do not belong here. Go find yourself a different news source.
2) Change your account settings to hide Linux-related stories.
Point taken on the blue screen, but how about in Linux when a process running off the CD freezes your console, adn the only way to get around it is to reboot (since you can't just open the CD and have the process die like in windows)? This has happened to me several times in the past. Nont to mention the number of time sI was in windows and wanted to read a serial # off of the cd, so I just open it, blue screen appears, write it down, put it back in, hit enter. No harm done. I construe the opening of cd == death to be a feature, not a detriment.
Why is this modded up as funny? I swear I've seen this gag every single time there's an article about any software that's at version 3. Gets a bit old is all I'm saying.
why do i care?
The kernel is the framework that connects to the hardware. Its like the chassis on your car, designed to give all components a secure mounting point to connect to each other. Without the kernel, all your component software would still be functional, but not to useful as they would be laying on the ground in a proof of concept state. The kernel supplies all the hardware to hook things up and make them into a fully functional machine.
The init process and scripts, libraries, and applications are the engine, powertrain components, interior, and all the other details to make a complete operating system. The kernel is simply the framework and body to make it all possible. Compile options allow you to have lightweight race car or a dumptruck.
Consider a CD with Rock Ridge that has device files (/dev/hda comes to mind) with ownership to a non-root user. A user can get around /dev/ permissions by doing this if it's mounted without nodev. Also consider a suid executable owned by root. A user can run it and get root privs unless the nosuid option is set. When one user can mount as another user (as supermount would do) or with the wrong options, that's a security hole. Secondly, suppose root is copying stuff off a CD or wants to access it remotely. Do we let joe user umount it by pressing eject?