Slashdot Mirror

← Back to Stories (view on slashdot.org)

Linus Torvalds On Linux 2.6

Posted by Hemos on from the checking-in-with-the-man dept.

ceebABC writes "Linus Torvalds talks about the upcoming Linux 2.6 kernel, in an interview with eWEEK. Linus discusses the scalability and memory management in the new kernel. They also have a story about what's supposed to be in Linux 3.0."

5 of 323 comments (clear)

  1. What�s in and what�s out by Karpe · · Score: 5, Informative

    To see whats already in 2.5, check kernel status

    1. Re:What�s in and what�s out by rainwalker · · Score: 5, Informative

      I suggest keeping tabs on LWN's weekly kernel page for good explanations of what's going on...you can also read Kernel Traffic, which, although it is usually fairly technical, tends to give you the gist of what is going on in the world of the kernel devs. Good luck-

  2. Re:Important questions.. by zdzichu · · Score: 5, Informative
    Will it support pci modems?

    It supports even now (2.4).

    Will it support touchpads on laptops?

    It supports.

    Will the frame buffer work properly on 3dfx cards

    Didn't saw any problem reports on lkml.

    Will it get rid of the fucking cli for good and boot DIRECTLY in to X?

    Are you insane?

    Will it tell Stallman to fuck off for trying to put gnu/ on it.

    GNU/Linux (The GNU Operating System with Linux kernel) is not Linux (the kernel).

    and last but most importantly, will you be able to to swtich kernels with out rebooting (is it that hard?, why dosent the kernel just unload it self from memory and go back to the boot menu?)

    You talk about Kexec? It's trying to be included in 2.5 right now.

    --
    :wq
  3. LVM is included in 2.6 by crsm · · Score: 5, Informative

    To all of those worried about LVM: 2.6 will include a LVM implementation. The EVMS won't make it though.

    The story is that 2.4 included LVM1 (I am running it right now on my RH8 box) which had some restrictions and were generally regarded as a kludge. For the 2.6 kernel two competing replacements arised: LVM2 and EVMS. LVM2 is basicly a rewrite of LVM1 while EVMS is an entirely different beast aimed at the BIG IRON in the datacenters. After some (heated) discussion on LKML Linus decided to include LVM2 and scrap EVMS.

    The reaction from the EVMS team (sponsered by IBM) was noble: They decided to remove their kernel-land code and rewrite their user-land utilities to use the winning LVM2 kernel interface and create a win-win situation for everyone. Kernel traffic covered the story here and Linux Weekly News made a mention of it here.

  4. Re:What is up with the LVM? by Steve+Hamlin · · Score: 5, Informative

    According to Kernel Trap, Linus merged the "device mapper" code, the kernel component of Sistina's LVM2 volume manager, around 2.5.45.

    In addition, the EVMS team then recognized the implication of this decision vis-a-vis the inclusion of EVMS in Linus' tree in the near future, and decided that a significant rewrite of some of their code was in order.

    "As many of you may know by now, the 2.5 kernel feature freeze has come and gone, and it seems clear that the EVMS kernel driver is not going to be included. With this in mind, we have decided to rework the EVMS user-space administration tools (the Engine) to work with existing drivers currently in the kernel, including (but not necessarily limited to) device mapper and MD."

    This announcement was met with TONS of positive praise on lkml: for the actual technical decision, for the mature and pleasant manner in which it was handled, and for the public policy of removing duplication of kernel code in general, simplifying the MD/device mapper code specifically.

    Finally, Alan Cox stated about 2.4:

    "I plan to try and push LVM2 to Marcelo after the next release. Whether he will take it I don't know. Obviously its good to have the ability to move back nicely to older kernels."