Slashdot Mirror


Linux 2.6 Turns 1 Year Old

Paul Kucher writes "On December 17th, 2003, Linux 2.6 was released by Linus Torvalds, saying 'The beaver is out of detox.' This was a reference to the last pre-release of the 2.6 kernel, which was called Beaver in Detox. Although a stable release, the 2.6 kernel has added many new features in the past year due to the new development model. It will be interesting to see what else is in store for this kernel, and I imagine it will be years before it is in maintenance mode."

24 comments

  1. Well I'll be the first to say it.... by Holi · · Score: 1

    Happy Birthday

    --
    Sorry, teleporters just kill you and then make a copy. A perfect, soul-less copy.
  2. Also... by Plake · · Score: 2, Interesting

    RoTK also was released in theaters on the same day. It was a great day all round.

  3. Still on 2.4 here by Anonymous Coward · · Score: 0, Offtopic

    My USB doesn't work in 2.6, which is a shame as not only would I like to update my desktop system but it also means that I can't use any live CDs (like the Ubuntu ones I sent for) since my keyboard and mouse are USB, and so is my printer. :-(

    1. Re:Still on 2.4 here by advocate_one · · Score: 0, Flamebait
      My USB doesn't work in 2.6, which is a shame as not only would I like to update my desktop system but it also means that I can't use any live CDs (like the Ubuntu ones I sent for) since my keyboard and mouse are USB, and so is my printer. :-(

      oh, piss off.... you must have the weirdest usb going for it not to work with any of the current live CDs that have 2.6 kernels... it's one of the things they really make sure works.

      --
      Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
    2. Re:Still on 2.4 here by n1ywb · · Score: 3, Interesting

      You may have an oddball USB controller that isn't enabled by default in most kernels, even though it probably IS supported by 2.6. Do you have "assign IRQ to usb" or "usb dos mode" or whateever turned on in your BIOS?

      --
      -73, de n1ywb
      www.n1ywb.com
    3. Re:Still on 2.4 here by dozer · · Score: 1

      Unless you say what hardware you have, your complaint nothing more than a meaningless troll. You realize, of course, that complaining on Slashdot is not quite as effective as asking on linux-usb or filing a bug in the kernel bugzilla?

    4. Re:Still on 2.4 here by wolf31o2 · · Score: 3, Informative

      Try a Gentoo 2004.3-r1 LiveCD. We have had exactly ZERO bug reports of people's USB not working with our CD, and we don't have any special USB patches added from vanilla 2.6.9, so it should work perfectly for you.

    5. Re:Still on 2.4 here by Anonymous Coward · · Score: 0

      The reason I didn't say what hardware I have is because "complaining on Slashdot is not quite as effective as asking on linux-usb or filing a bug in the kernel bugzilla" -- I may investigate the matter further when I have more time (and when I do so it won't be on slashdot). Sorry I didn't mean to troll (but still posted AC since I knew I was close to being one ;-).

    6. Re:Still on 2.4 here by Anonymous Coward · · Score: 0
      I can't see any such options in my BIOS, here is 'lspci -vv' output from my machine (USB works fine in 2.4 but not in 2.6 with similar options chosen):

      0000:00:00.0 Host bridge: Silicon Integrated Systems [SiS] SiS 645xx (rev 02)
      Subsystem: Silicon Integrated Systems [SiS] SiS 645xx
      Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
      Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
      Latency: 32
      Region 0: Memory at e0000000 (32-bit, non-prefetchable) [size=64M]
      Capabilities: [c0] AGP version 2.0
      Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3- Rate=x1,x2,x4
      Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP+ GART64- 64bit- FW- Rate=x4

      0000:00:01.0 PCI bridge: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI bridge (AGP) (prog-if 00 [Normal decode])
      Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B-
      Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
      Latency: 64
      Bus: primary=00, secondary=01, subordinate=01, sec-latency=32
      Memory behind bridge: e4000000-e5ffffff
      Prefetchable memory behind bridge: d0000000-dfffffff
      BridgeCtl: Parity- SERR+ NoISA+ VGA+ MAbort- >Reset- FastB2B-

      0000:00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS85C503/5513 (LPC Bridge) (rev 04)
      Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
      Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
      Latency: 0

      0000:00:02.3 FireWire (IEEE 1394): Silicon Integrated Systems [SiS] FireWire Controller (prog-if 10 [OHCI])
      Subsystem: Micro-Star International Co., Ltd.: Unknown device 703d
      Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
      Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
      Latency: 32 (1000ns min, 3000ns max)
      Interrupt: pin B routed to IRQ 17
      Region 0: Memory at e7015000 (32-bit, non-prefetchable) [size=4K]
      Expansion ROM at <unassigned> [disabled] [size=128K]
      Capabilities: [64] Power Management version 2
      Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=55mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
      Status: D0 PME-Enable- DSel=0 DScale=0 PME-

      0000:00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (prog-if 80 [Master])
      Subsystem: Silicon Integrated Systems [SiS] SiS5513 EIDE Controller (A,B step)
      Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
      Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
      Latency: 128
      Interrupt: pin ? routed to IRQ 17
      Region 4: I/O ports at 4000 [size=16]
      Capabilities: [58] Power Management version 2
      Flags: PMEClk- DSI- D1- D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold+)
      Status: D0 PME-Enable- DSel=0 DScale=0 PME-

      0000:00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] Sound Controller (rev a0)
      Subsystem: Micro-Star International Co., Ltd.: Unknown device 7031
      Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
      Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
      Latency: 32 (13000ns min, 2750ns max)
      Interrupt: pin C routed to IRQ 18
      Region 0: I/O ports at d800 [size=256]
      Region 1: I/O ports at dc00 [size=128]
      Capabilities: [48] Power Management version 2
      Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=55mA PME(D0-,D1-,D2-,D3hot+,D3cold+)
      Status: D0 PME-Enable- DSel=0 DScale=0 PME-

      0000:00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) (

    7. Re:Still on 2.4 here by Anonymous Coward · · Score: 0

      OK, I suck, I copied over my 2.4 config and did a 'make oldconfig', played about in menuconfig a little and hey, presto I am now running 2.6.9 :-). The Ubuntu Live CD is still broken though.

  4. uptime... by Anonymous Coward · · Score: 0, Informative

    Linux mu 2.6.0-gentoo-r1 #2 SMP Sat Jul 17 14:53:56 CDT 2004 i686 Intel(R) Pentium(R) M processor 1200MHz GenuineIntel GNU/Linux
    12:16:12 up 365 days, 6 users, load average: 2.07, 2.17, 2.03

    1. Re:uptime... by hawkbug · · Score: 1

      That's awesome - hopefully that thing is behind a firewall or two, because hasn't there been several exploits since then?

    2. Re:uptime... by bersl2 · · Score: 1

      Intel(R) Pentium(R) M processor 1200MHz

      So you've had a laptop up for one year? Or is uname -a just screwed up?

  5. Burning, burning, burning... by PhotoJim · · Score: 1

    /me buys a lovely gift for the kernel that finally let him burn on IDE burners. That ide-scsi trick on 2.4 and earlier confounded (and continues to confound) me...

    1. Re:Burning, burning, burning... by gorre · · Score: 1

      You can burn on IDE burners without the "ide-scsi trick" on 2.4 too, you just need a new enough version of cdrecord.

      --
      "Madness is something rare in individuals - but in groups, parties, peoples, ages it is the rule." -- Nietzsche
    2. Re:Burning, burning, burning... by PhotoJim · · Score: 1

      Maybe Debian doesn't have a new enough version (although I'm running Sarge), but I haven't been able to get it to work yet...

    3. Re:Burning, burning, burning... by chgros · · Score: 1

      Maybe Debian doesn't have a new enough version (although I'm running Sarge), but I haven't been able to get it to work yet...
      I haven't been able to get it to work on 2.6...

  6. Great, wonderful, blah, blah, blah... by jo42 · · Score: 1

    Great, wonderful, blah, blah, blah...

    Now let's get a kernel fix for recent 2.6.9 series kernels that allows you to boot off of SATA drives hanging off of a NFORCE2 or NFORCE3 chipset's SATA ports. Nothing more annoying than having to take out your 10K RPM Raptor for a 7.2K RPM IDE plow horse...

    1. Re:Great, wonderful, blah, blah, blah... by Anonymous Coward · · Score: 0

      Let's not forget that some of the most popular USB chipsets still don't work without crashing 2.6.

    2. Re:Great, wonderful, blah, blah, blah... by Anonymous Coward · · Score: 0

      allows you to boot off of SATA drives hanging off of a NFORCE2

      I love this shit!!

  7. in china... by radon28 · · Score: 1

    ..birthdays are always positive!

  8. ATARAID by satanami69 · · Score: 1

    I have el cheapo Promise Fasttrak 133 (PDC20276) with two other el cheapo 30GB harddrives in a raid. It works fine with 2.4, but I still see no way of upgrading to 2.6. Will there eventually be an ATARAID workaround, or do I need to change my system setup to get on 2.6

    --
    I really hate Dan Patrick.
  9. Happy birthday, 2.6 by GreatBunzinni · · Score: 2, Insightful

    Now I hope that the linux kernel people learned their lesson and that the project's next stable release is really stable, which wasn't by far the 2.6 case.

    Don't get me wrong. I love linux and I'm very gratefull for the work that group of people invests into the project. Still, 2.6 wasn't by far near the stable status it got and that misslabelling can be very counterproductive. After all, the common idea is that linux is difficult, not ready for serious work and incredibly buggy and a buggy release just helps to perpetuate those ideas.

    --
    Slashdot, fix your code or at least hire someone who is competent at it to do it for you.
  10. bullshit! by b374 · · Score: 2, Informative
    Linux mu 2.6.0-gentoo-r1 #2 SMP Sat Jul 17 14:53:56 CDT 2004 i686 Intel(R) Pentium(R) M processor 1200MHz GenuineIntel GNU/Linux
    12:16:12 up 365 days, 6 users, load average: 2.07, 2.17, 2.03


    That's bullshit since the output shows that your kernel was compiled in July 2004, not in December last year.