What Will Be in Linux 2.7?
Realistic_Dragon writes "The first discussion has been sighted on the Linux kernel mailing list to put together a feature list of things that should go into Linux 2.7 - including hotplug CPU & Ram support, network transparent sound and improvements to Netfilter to bring it up to the the level of OpenBSD's Packet Filter. And all this before most of us have started to run 2.6.0-preX, or even a 2.6 series stable release happening. Perhaps if you have a (sensible) idea now would be a good time to voice it, otherwise you will have to wait for 2.9 to get it included."
support the new AMD 64 bit processes and be optimized for them
Maybe we should start working on a way to re-load the kernel without rebooting. I don't know if it's practically possible, but it certainly would be neat!
Moderation: Put your hand inside the puppet head!
How about a userfriendly UI that'd let me configure everything without having to recompile eveything (or do it invisibly) just so that I can play and use without the pain and suffering that is require nowdays.
My main gripe with Linux has been that it's a bitch to configure for things that should't be so hard. Trying to get powermanagment to work on my IBM took me months and never worked right.
In Soviet Russia, the television watches YOU!
is a scheduler on the same caliber as Solaris, so that the kernel can utilize multiple schedulers simultaneously. Linux currently ships with only a timeshare scheduler, but Solaris supports a number of different schedulers which can all operate simultaneously. Administrators can also move processes between different schedulers on the fly as well. A Fair Share Scheduler, for example, would be nice so that resources on large systems can be partitioned effectively as to prevent certain processes from monopolizing system resources. The CPU/RAM hotplug support would be nice... glad to see Linux trying to catch up to where Solaris was years ago. Just kidding :)
Linux Journal's May 2003 issue had an article from Rob Love about what's new in the 2.6 kernel (new VM, ALSA, improved IO subsystem, preemptive kernel) and with a few items: SCSI needs to be rewritten to make it smarter than the drivers, and the TTY code needs a rewrite -- "it's looking like to be hack."
--
# Canmephians for a better Linux Kernel
$Stalag99{"URL"}="http://stalag99.net";
The beauty of Linux (IMO) is the ability to tweak the kernel. Why not take advantage of the fact that there is source code to be modified and make it simple for the average user to recompile the kernel? It's an ugly, ugly process right now and a lot of people are running distro kernels that aren't as optimized as they could be.
What if Digg added local news and a Slashdot inspired comment karma system? ---
http://houndwire.com
What I'd like to see is all the different dependancy based package managers like Red Hat's RPM system or Debian's Apt-Get be unified into a standard installer/uninstaller that all distributions can use.
Shh.
Currently even fairly advanced users can get hung up trying to get hardware to work. Windows has a huge advantage in this area even though you usually need a cd of drivers.
Even better would be a way to build a kernel that detects and includes support for your hardware automatically.
If you're compiling a large program, your motherboard and OS support hot-swap, and you add more RAM, then yes, the next GCC process to execute will see the extra RAM.
Removing RAM, on the other hand, would probably need a hardware switch on the motherboard that swaps everything in that bank to disk.
Will I retire or break 10K?
PLEASE include native support for SATA!!
"Ask not what your country can do for you." --John F. Kennedy
I would like to be able to share proc, mem, disk, and net resources across multiple machines (as is partially implemented in openMosix) AND run multiple instances of Linux on a single system (as in User-mode Linux). These two features combined would provide the ultimate solution in hardware resource flexibility and scalability in large server deployments. It looks like VMware Server provides similar functionality, but with cross-platform capabilities and at a cost of over $1500 per processor.
I wish there would be default stack protection, right out of the kernel. I'm tired of these repeated buffer overflows, and I know people can code right around them even with stack protection, but at least an attempt to make it harder for stack busting would be nice.
Gonzo Granzeau
"Nothing the god of biomechanics wouldn't let you into heaven for.." -Roy Batty