★ wanayoo — archive 1999 http://kernelnotes.org/kpatch20.htmlNouvelle recherche | Portail wanayoo

Linux 2.0 Kernel Patches

[Home] [Linux 2.0] [Linux 2.1] [Information] [Software] [Distributions] [Links]

About the Kernel Patch Summaries

These summaries are written after each kernel release by examining the chunks of each patch file and figuring out what has changed. Occasionally, they are supplemented by notes that Linus (and others) posted to the linux-kernel mailing list.

The summaries from 2.0.0 to 2.0.30 were put together by Mark Evans <mevans@ecsnet.com>.

The summaries from 2.0.31 onwards were put together by Myrdraal@deathsdoor.com -- originally appearing on the Cutting Edge Linux website.


*Linux 2.0.38 patch - patch-2.0.38.gz (25-Aug-99)
    [Patch Browser]

*Linux 2.0.37 patch - patch-2.0.37.gz (14-Jun-99)
    [Patch Browser]

*Linux 2.0.36 patch - patch-2.0.36.gz (15-Nov-98)
    [Patch Browser]


From: Linus Torvalds <torvalds@transmeta.com>
Subject: Linux-2.0.36..

Is out there.

I won't claim any false credit for this: all the 2.0.x work was done by Alan Cox as the maintainer, and the 2.0.36 that is out there is exactly the same as Alan's "pre-22" version that he asked people to check out. He just asked me to "sprinkle some holy penguin-pee on it" to bless it and make it official. This I have done (*).

2.0.36 is a lot of updates, mostly to various drivers. ISDN, various SCSI drivers and network cards have been updated quite heavily. ISDN to the degree that you need to make sure you have the most recent tools in order to play well with it.

Have fun,

      Linus

(*) This, btw, is not something I would suggest you do in your living room. Getting a penguin to pee on demand is _messy_. We're talking yellow spots on the walls, on the ceiling, yea verily even behind the fridge.

However. I would also advice against doing this outside - it may be a lot easier to clean up, but you're likely to get reported and arrested for public lewdness. Never mind that you had a perfectly good explanation for it all.


*Linux 2.0.35 patch - patch-2.0.35.gz (13-Jul-98)
    [Patch Browser]

*Linux 2.0.34 patch - patch-2.0.34.gz (3-Jun-98)
    [Patch Browser]

*Linux 2.0.33 patch - patch-2.0.33.gz (16-Dec-97)
    [Patch Browser]


Hi everybody,

it turns out that we needed yet another 2.0.x kernel, hopefully the final one. This one fixes the following things:

So go forth, and populate the earth with 2.0.33-based machines.

Linus


*Linux 2.0.32 Patch - patch-2.0.32.gz (17-Nov-97)

*Linux 2.0.31 Patch - patch-2.0.31.gz (17-Oct-97 15:25)


Ok, enought beating about the bush, it's up there now.

Linux-2.0.31 is available at

ftp://ftp.kernel.org/pub/linux/kernel/v2.0/

both as full source and as a huge patch against pristine 2.0.30. You don't want the patch, but it's there for completeness.

The people who have been testing out pre-patches (thanks to you all) can find a patch against p10 in pub/linux/kernel/testing, it's pretty small. I promised patches from p9 too, and yes, it's there, but you have to apply it in a two-stage process, getting the p9-p10 patch and then the p10-real patch.

If there are problems, I don't even want to know.

Linus


*Linux 2.0.30 Patch - patch-2.0.30.gz (08-Apr-97)

*Linux 2.0.29 Patch - patch-2.0.29.gz (08-Feb-97)

*Linux 2.0.28 Patch - patch-2.0.28.gz

*Linux 2.0.27 Patch - patch-2.0.27.gz

In the 2.0.x series, the largest diff is the smbfs update. This one should fix a lot of race conditions found with the new users of 2.0.x, hopefully it's stable. The patches also fix the Teles ISDN driver compilation problem and update a few SCSI drivers a bit.

Check it out, send me comments, and dance joyously in the streets,

Linus

*Linux 2.0.26 Patch - patch-2.0.26.gz

*Linux 2.0.25 Patch - patch-2.0.25.gz

I released 2.0.25 yesterday (but ftp.funet.fi was down, so it showed up there only an hour ago). The 25 release fixes along with some other minor stuff (mostly some ide tape filemark condition stuff).

*Linux 2.0.24 Patch - patch-2.0.24.gz

*Linux 2.0.23 Patch - patch-2.0.23.gz

*Linux 2.0.22 Patch - patch-2.0.22.gz

*Linux 2.0.21 Patch - patch-2.0.21.gz    Linux 2.0.21 Full Source Tree - linux-2.0.21.tar.gz

On Fri, 20 Sep 1996, Alan Cox wrote:
>
> Yep. I think this is another manifestation of the file locking
> stuff that locks SMP in 2.0.20, but in a differently annoying guise.
> Linus posted some changes to avoid this problem so hopefully
> .21 will fix it

Yep, 2.0.21 is out, and now SMP should be stable again thanks to the file locking fixes (thanks to everybody who was testing things out). This also does the "make depend" stage in C (everybodys fabourite gripe), and it's a lot faster now. Whee.

2.0.21 also fixes a deadlock with the LOOP devices thanks to Ray Van Tassle who has been working on this for some time.

The 3c509 driver also has a longer timeout that seems to be needed on some setups, so if you had sporadic problems with detection of the 3c509 they should hopefully be gone now. The wd7000 scsi driver is also updated, please check it out.

Linus "on to 2.1, I think" Torvalds

*Linux 2.0.20 Patch - patch-2.0.20.gz

I just made a 2.0.20 that fixes the module problems (you've seen most of the patch on this list already, there have been a few other minor patches to it since then). I had a corrupted version out on the ftp-sites for about 5 minutes, so if you got it early, check that the correct files are

 length   md5sum

 5997693  71f79e8d40eaa636ec30beee96a25a46  linux-2.0.20.tar.gz
   10786  841be676a69c7a369b6a5d78b4218536  patch-2.0.20.gz

Hope you find these satisfactory,

Linus

*Linux 2.0.19 Patch - patch-2.0.19.gz

There is a problem with 2.0.19 where two entry points are not exported by the kernel. See the Unofficial Patch Page for a patch to fix this problem.

*Linux-2.0.18.patch - patch-2.0.18.gz

*Linux-2.0.17.patch - patch-2.0.17.gz

NOTE: You must back-out the pre-patch-2.0.17 before applying this patch. Use patch -R <pp17 if you have applied pre-patch-17.

On Sun, 25 Aug 1996, I wrote:
>
> As people have been wondering about 2.1, here is my current plan:
>
> I'm leaving for the US tomorrow (Mon Aug 26), and I'll be away for a week.
> Before leaving, I'll make a 2.0.15 that fixes a rather nasty thing in
> "remove_from_wait_queue()" (and has the SEOI interrupt controller changes as
> they actually do seem to make a difference for some people).
>
> I hope to start up a 2.1.x tree more-or-less immediately when I get back.

Ok, I just made a 2.0.17, which fixes:

I'll calm this down now, and if everything goes well I'll "open 2.1" by just changing the version number in about a week..

How does 2.0.17 look?

Linus

*Linux-2.0.16.patch - patch-2.0.16.gz

Linus has released a patch to fix a problem with FTAPE support in 2.0.16. Check the Unofficial Patch List for more details.

*Linux-2.0.15.patch - patch-2.0.15.gz

Linus has released a second test patch to fix problems that are un-covered in Linux 2.0.15 - Check the Unofficial Patch List for more info.

*Linux-2.0.14.patch - patch-2.0.14.gz

*Linux-2.0.13.patch - patch-2.0.13.gz

*Linux-2.0.12.patch - patch-2.0.12.gz

I've made a 2.0.12, as some people started complaining about having free CPU time but no patches to compile ;-)

2.0.12 contains

As usual, I expect you all to test it out and shout loudly with joy when you notice that you have survived yet another kernel upgrade (and shout even louder in the unlikely case something breaks, but we all know that that never happens, don't we?).

    Linus

*Linux-2.0.11.patch - patch-2.0.11.gz

I just released Linux-2.0.11, which mainly contains various device driver patches, notably the IDE patches. With 2.0.11, I (and I'm sure Mark will underwrite that too) sincerely hope that the IDE driver now works for everybody. I hope people will try this out, and make really sure that is indeed the case.

The 2.0.11 kernel also contains the ELF fixes that make it work on the alpha (and potentially other architectures too). As such, you should be able to use a standard kernel with the upcoming ELF/alpha release.

A big thanks to Mark who worked overtime on the IDE problems, and everybody who tested and have been doing other things..

Btw, people have been complaining about the chaos of 2.0.x. I can only say that most of the problems are simply because people don't try out pre-releases. I _tried_ to get people to try out the "pre-2.0" kernels (the only reason I did the numbering change was the psychological angle on people who wouldn't otherwise have tried it out), but 2.0 obviously had more users still.

With more users comes more problem reports, and it takes a while to fix them. I'm not making excuses, quite the reverse: I urge you all to update your kernels so that we _can_ get the problems fixed. Send in problem reports, and we'll slowly get a kernel that hopefully works for everybody.

Linus

*Linux-2.0.10.patch - patch-2.0.10.gz

*Linux-2.0.9.patch - patch-2.0.9.gz

Patch 2.0.9 will not compile the IDE modules correctly unless you enable CMD 640 chipset support. Please see the Unoffical Patches section for a fix.

*Linux-2.0.8.patch - patch-2.0.8.gz

I put out 2.0.8 which should fix the axp checksum routines (there are obviously other fixes there too, ppp fragmentation etc), but it seems ftp.funet.fi isn't feeling too well today and it has lost my password or something so I'm unable to upload it there. It's on ftp.cs.helsinki.fi, though.

I also noticed that my harddisk on "linux.cs.helsinki.fi" (which is where I keep the primary development sources) seems to be going, so keep your fingers crossed. I thought I'd better upload what I have now, rather than notice that I lost everything when I get back to work on Monday..

(Only wimps use tape backup: _real_ men just upload their important stuff on ftp, and let the rest of the world mirror it ;)

Linus

*Linux-2.0.7.patch - patch-2.0.7.gz

*Linux-2.0.6.patch - patch-2.0.6.gz

*Linux-2.0.5.patch - patch-2.0.5.gz

*Linux-2.0.4.patch - patch-2.0.4.gz

I made 2.0.4 - it contains some minor fixes, and I hoped it would fix the sound stuff, but I already got my first patch for a missing semi-colon in sb_common.c. Damn, I hate it when that happens. As you can probably all guess, I don't use the sound support at all - I consider it nice but not relevant to what I do, and the way the config is set up I can't really test it without going bananas so I have to rely on Hannu and you others out there.

Anyway, 2.0.4 looks largish, but a lot of that is just ppc-specific updates that don't touch anything else (so that I later will have an easier time keeping in sync). There are various minor driver updates in there too, along with a few very small POSIX.1 patches.

If you have problems with the sound driver, you'll get a rather obvious parse error compiling it - just add a ";" at the end of the appropriate line. Sorry about that, I was hoping that these silly problems would be gone by now.

Thanks to all testing it out,

Linus

*Linux-2.0.3.patch - patch-2.0.3.gz

*Linux-2.0.2.patch - patch-2.0.2.gz

Well, 2.0.2 is out, and the patches are much more reasonably sized this time. Some of the 2.0.1 patches got revoced, and some of them got just re-massaged to a better format.. This kernel should make the serial lines behave again, and it also fixes a few long-standing networking problems (why, oh why, do these problems always have to be found just after releasing a new kernel? ;)

2.0.2 also changes some file descriptor handling: our behaviour when we ran out of file descriptors was not very nice: open(.., O_TRUNC|O_CREAT) could return EMFILE and still make changes to the filesystem despite that. Oops. Thanks for the people at Unifix for pointing this out (and you can blame any problems at me, I made a different patch than theirs..)

Also some smbfs fixes from Yuri, long filenames should be stabler. TCP fix from Alexey, and Ted's secure TCP numbers are in too (I thought they were just a nice feature, but Alan tells me they actually fixed a bug too ;)

*Linux-2.0.1.patch - patch-2.0.1.gz

NOTE! The POSIX.1 patches in 2.0.1 is _not_ the complete set of patches, and I still have some stuff to integrate yet. As such we can't say that 2.0.1 is POSIX.1 conformant yet, but the patches really aren't very large (the original POSIX patches were less then 2000 lines, and around half of them are integrated in one form or another).

Also note that the POSIX requirements for "rename()" meant that I had to change the VFS interface to the low-level devices. That's rather unfortunate, as it means that binary kernel modules will mostly not work across the 2.0.0->2.0.1 upgrade. However, the new interface should be stable now, and I'd rather have break it now rather than have problems with POSIX.1..


[Home] [Up] [Search] [FeedBack]

Copyleft © The LinuxHQ Project. Licensed under the GNU Public License.