loop back broken in 2.2.14
I think that was suggested a while ago, in the 2.2 days. It didn't fly! There was however a general consensus that for small bugs that are found in a 'stable' release there should be fixes for just the bug as the next release. I.E. 2.2.15 should be released with just the one fix. Linus didn't seem to go for that as well as some other developers .
If 2.5 was open this kind of thing would probably not happen, but that is not to say that there would not be other issues in 2.4
If someone has the web space, they could as you say, post these 2.4.14.fixme kernels and then also maintain the patches between the official Linus kernel and the fixme kernels.
J
Quoted 1 line · Michael Peddemors
Well, the loopback bug is a pain.. but we have had these pains on quite
a few releases in the 2.4.x series...
I wonder if maybe a new method of distributing kernels should happen.. 2.4.14 should become 2.4.14-stable meaning that it never ever changes after release, and 2.4.14-fixed means that these tiny typos, gotchas, and backport driver fixes can get into 2.4.14-fixed which may change from day to day, but not get any enhancements, only minor fixes..
People could try 2.4.14-stable, and if they have a problem, they could just try the 2.4.14-fixed to see if their problem is already addressed...
The idea is that at least every major release kernel should compile, and it would reduce the noise levels from people trying out *stable* kernel versions..
Just a thought..
Quoted 2 lines · On Mon, 2001-11-12 at 12:27, [email protected] wrote:
I thought that the -pre would be the developer kernels, and that an actual release (2.4.14) would have been somewhat tested. I fully understand that a 'runtime' bug in the vm or some other system could arrise and that is one thing. I also understand when a 'less used' driver like NTFS or VFAT breaks, but to see bugs in the loop device in a 'stabilizing' kernel is something that I thought I'd never see.
Signature · 9 lines
"Catch the Magic of Linux..." -------------------------------------------------------- Michael Peddemors - Senior Consultant LinuxAdministration - Internet Services NetworkServices - Programming - Security Wizard IT Services http://www.wizard.ca Linux Support Specialist - http://www.linuxmagic.com -------------------------------------------------------- (604)589-0037 Beautiful British Columbia, Canada
Yes, I seriously considered the feasibility of having 2.4.14-fixed kernels around, but I could just imagine trying to deal with millions of people trying to download known good kernels on our bandwidth...
It would be good to be able to point people to a stable kernel.. instead of having to recommend kernels in the pre-series..
But for now, fixing the 2.4.14. loopback bug has given us a kernel we are most comfortable with..
Just wish that 2.4.14 was that kernel..
Quoted 5 lines · On Wed, 2001-11-14 at 10:17, [email protected] wrote:
I think that was suggested a while ago, in the 2.2 days. It didn't fly! There was however a general consensus that for small bugs that are found in a 'stable' release there should be fixes for just the bug as the next release. I.E. 2.2.15 should be released with just the one fix. Linus didn't seem to go for that as well as some other developers .
If 2.5 was open this kind of thing would probably not happen, but that is not to say that there would not be other issues in 2.4
If someone has the web space, they could as you say, post these 2.4.14.fixme kernels and then also maintain the patches between the official Linus kernel and the fixme kernels.
Signature · 9 lines
"Catch the Magic of Linux..." -------------------------------------------------------- Michael Peddemors - Senior Consultant LinuxAdministration - Internet Services NetworkServices - Programming - Security Wizard IT Services http://www.wizard.ca Linux Support Specialist - http://www.linuxmagic.com -------------------------------------------------------- (604)589-0037 Beautiful British Columbia, Canada
Quoted 7 lines · On 20011115 Michael Peddemors wrote:
Yes, I seriously considered the feasibility of having 2.4.14-fixed kernels around, but I could just imagine trying to deal with millions of people trying to download known good kernels on our bandwidth...
It would be good to be able to point people to a stable kernel.. instead of having to recommend kernels in the pre-series..
...
Quoted 3 lines · On Wed, 2001-11-14 at 10:17, [email protected] wrote:
Quoted 2 lines
I think that was suggested a while ago, in the 2.2 days. It didn't fly! There was however a general consensus that for small bugs that are found in a 'stable' release there should be fixes for just the bug as the next release. I.E. 2.2.15 should be released with just the one fix. Linus didn't seem to go for that as well as some other developers .
Well, Linus could post a 'errata' patch...
Layout now in ftp space is (reverse date order):
test-kernels ChangeLog-2.4.14 LATEST-IS-2.4.14 linux-2.4.14.tar.bz2
A couple files could be posted, named Errata-2.4.14 and linux-2.4.14-errata.bz2, first being a description of what the second (the patchs) cures...with names like that so the listing gets them visible near the main tarball...
Signature · 4 lines
J.A. Magallon # Let the source be with you... mailto:[email protected] Mandrake Linux release 8.2 (Cooker) for i586 Linux werewolf 2.4.15-pre4-beo-2 #1 SMP Thu Nov 15 13:02:43 CET 2001 i686
Well I think it is a good idea to do this and have errata patches or something. I don't think Linus wants the extra work. I'd do it myself, but I don't have the ftp storage space, the time or the bandwidth. I am now keeping seperate trees on my box. One that is the default kernel and then my tree which has fixes to that tree. I'll be working out a
system of testing and migration now ..................
Quoted 7 lines
Well, Linus could post a 'errata' patch...
Layout now in ftp space is (reverse date order):test-kernels ChangeLog-2.4.14 LATEST-IS-2.4.14 linux-2.4.14.tar.bz2