Posted by
Roblimo
on from the kernel-updates dept.
Lface writes "Linus has just announced a feature freeze for Linux 2.4. He further says: 'The feature freeze should be turning into a code freeze in another two months or so, and a release by the end of the year. And as everybody knows, our targets never slip.'"
Don't take Linus so seriously, PLEASE :-P
by
BadlandZ
·
· Score: 5
The feature freeze should be turning into a code freeze in another two months or so, and a release by the end of the year. And as everybody knows, our targets never slip.--Linus
For those of you to new to development kernel tracking, this is a JOKE, it's sarcasm. I have no doubt that Linus would like a freeze, and it COULD happen, but this is not written in stone.
Anyway, I personally don't see anything major pending. There are still various fixes that have yet to be integrated (some of the smbfs work by Bill etc), but on the whole I'd call this feature-freeze time. Have fun--Linus
As it happens, the development kernel kept going from 2.1.69 in 1-Dec-97 on to Linux 2.2.0-pre9 in 20-Jan-99, that's over a year.
Linus has a sence of humor, don't think every word out of his mouth is written in stone, this isn't Moses comeing down from the mountian with the ten commandments... . It's just a comment, and one said with tounge in cheek.
It could be "the freeze," but don't hold your breath.
There has been quite a bit of discussion about it on the linux kernel development mailing list, with many people on different sides.. Look here to see what people on the list have been saying.
-- Does Rain Man use the Autistic License for his software?
Yep, it will be in there. It might not work with everything out there, but it's a really good start. As of the latest development kernel (2.3.18), there's support for the following:
UHCI (intel PIIX4 and others) support
OHCI (compaq and some others) support
OHCI-HCD (other OHCI opt. Virt. Root Hub) support
USB hub support
USB mouse support
USB HP scanner support
USB keyboard support
USB audio parsing support
USB Communications Device Class (ACM) support
USB Printer support
USB CPiA Camera support
USB SCSI Support
EZUSB Firmware downloader
USS720 parport driver
Preliminary/proc/bus/usb support
-- Does Rain Man use the Autistic License for his software?
I wouldn't count on XFS being included, Linus said in his post that "if the changes aren't too major" From what I understand from the posts some of the SGI folks have made is that XFS is not a "plug-in" filesystem driver, it requires changes all over the place. Ofcourse I could be totally wrong:-) since I don't work for SGI and never worked on/with the XFS filesystem.
I sure would like to know what the news is with SGI porting their XFS journalling file system to Linux. This will be awsome.
From what I've heard, XFS is going to require some heavy-duty changes to the VFS layer to allow for >2GB files on 32-bit systems. (It's also the VFS layer that keeps ext2 from allowing >2GB files, so this may end up killing two birds with one stone.) I don't think the SGI engineers working on XFS for Linux have any code that's fit for public consumption yet anyway.
--Troy
-- "My life's work has been to prompt others... and be
forgotten." --Cyrano de Bergerac
Quick minor releases, long major releases...
by
Ami+Ganguli
·
· Score: 4
A (roughly) once a year release cycle is good for minor releases. There's less temptation to back-port stuff from devel into the stable kernel and therefore less chance of bugs showing up in the stable tree.
The kind of hoopla that happened with 2.2 is good, but it should be reserved for major releases every few years.
What I'm not clear on is how earth-shattering features that justify a bump in major version number and lots of hoopla will ever make it into the devel kernel. Linus is opposed to parrallel development trees (probably with good reason), but I'm not sure how else you introduce big changes withough jeapardizing the quick release cycle.
I think Linus should annoint somebody to start a "3.0 experimental" tree with major new features like clustering. Linus and the regular gang could continue work on 2.5/2.6 for another year, and then synch up with the experimental kernel for 2.7/3.0.
Of course, I'm just a lurker on Linux Kernel, so I don't really have any right to give advice. It's just my idea.
-- It is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail. - Abraham Maslow
For those of you to new to development kernel tracking, this is a JOKE, it's sarcasm. I have no doubt that Linus would like a freeze, and it COULD happen, but this is not written in stone.
I refer you to Kernel 2.1.69 notes where Linus said:
Anyway, I personally don't see anything major pending. There are still various fixes that have yet to be integrated (some of the smbfs work by Bill etc), but on the whole I'd call this feature-freeze time. Have fun--Linus
As it happens, the development kernel kept going from 2.1.69 in 1-Dec-97 on to Linux 2.2.0-pre9 in 20-Jan-99, that's over a year.
Linus has a sence of humor, don't think every word out of his mouth is written in stone, this isn't Moses comeing down from the mountian with the ten commandments... . It's just a comment, and one said with tounge in cheek.
It could be "the freeze," but don't hold your breath.
There has been quite a bit of discussion about it on the linux kernel development mailing list, with many people on different sides.. Look here to see what people on the list have been saying.
-- Does Rain Man use the Autistic License for his software?
Slashdot's first reaction to VMware
UHCI (intel PIIX4 and others) support
OHCI (compaq and some others) support
OHCI-HCD (other OHCI opt. Virt. Root Hub) support
USB hub support
USB mouse support
USB HP scanner support
USB keyboard support
USB audio parsing support
USB Communications Device Class (ACM) support
USB Printer support
USB CPiA Camera support
USB SCSI Support
EZUSB Firmware downloader
USS720 parport driver
Preliminary /proc/bus/usb support
-- Does Rain Man use the Autistic License for his software?
Slashdot's first reaction to VMware
I wouldn't count on XFS being included, Linus said in his post that "if the changes aren't too major" :-) since I don't work for SGI and never worked on/with the XFS filesystem.
From what I understand from the posts some of the SGI folks have made is that XFS is not a "plug-in" filesystem driver, it requires changes all over the place.
Ofcourse I could be totally wrong
I sure would like to know what the news is with SGI porting their XFS journalling file system to Linux. This will be awsome.
From what I've heard, XFS is going to require some heavy-duty changes to the VFS layer to allow for >2GB files on 32-bit systems. (It's also the VFS layer that keeps ext2 from allowing >2GB files, so this may end up killing two birds with one stone.) I don't think the SGI engineers working on XFS for Linux have any code that's fit for public consumption yet anyway.
"My life's work has been to prompt others... and be forgotten." --Cyrano de Bergerac
A (roughly) once a year release cycle is good for minor releases. There's less temptation to back-port stuff from devel into the stable kernel and therefore less chance of bugs showing up in the stable tree.
The kind of hoopla that happened with 2.2 is good, but it should be reserved for major releases every few years.
What I'm not clear on is how earth-shattering features that justify a bump in major version number and lots of hoopla will ever make it into the devel kernel. Linus is opposed to parrallel development trees (probably with good reason), but I'm not sure how else you introduce big changes withough jeapardizing the quick release cycle.
I think Linus should annoint somebody to start a "3.0 experimental" tree with major new features like clustering. Linus and the regular gang could continue work on 2.5/2.6 for another year, and then synch up with the experimental kernel for 2.7/3.0.
Of course, I'm just a lurker on Linux Kernel, so I don't really have any right to give advice. It's just my idea.
It is tempting, if the only tool you have is a hammer, to treat everything as if it were a nail. - Abraham Maslow