From: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
To: Alan Cox <laughing@shared-source.org>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.8-ac12
Date: Mon, 27 Aug 2001 09:35:29 +0200 [thread overview]
Message-ID: <20010827093529.A31359@emma1.> (raw)
In-Reply-To: <20010826171335.A9362@lightning.swansea.linux.org.uk>
In-Reply-To: <20010826171335.A9362@lightning.swansea.linux.org.uk>; from laughing@shared-source.org on Sun, Aug 26, 2001 at 05:13:35PM +0100
On Sun, 26 Aug 2001, Alan Cox wrote:
>
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/alan/linux-2.4/
>
> Intermediate diffs are available from
> http://www.bzimage.org
>
> 2.4.8-ac12
> o Merge the majority of 2.4.9 except
> - min/max mess
> - fat/isofs changes
> - drm changes (some collisions with other
> fixes)
> - vm/buffer handling changes
> - emu10k1
> - vfs directory type changes
> - nfs/nfsd/sunrpc
> I'm trying to make sure I can keep this testable
> as 2.4.9 vanilla isnt being stable on my test sets
> This is basically a merge of all the "boring" bits.
2.4.9 is somewhat stable for me, here's where it bit me:
- init occasionally hangs on boot
- bridge (with netfilter patches from bridge.sf.net) kills NFS (I have
been told bridge and fragmented traffic don't go together well and I'd
have to change rsize/wsize to prevent fragmentation)
Is 2.4.8-ac12 "testable" or rather "stable"?
next prev parent reply other threads:[~2001-08-27 7:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-26 16:13 Linux 2.4.8-ac12 Alan Cox
2001-08-26 23:55 ` Linux 2.4.8-ac12 not all there Hugh Dickins
2001-08-27 0:02 ` Alan Cox
2001-08-27 7:35 ` Matthias Andree [this message]
2001-08-27 11:00 ` Linux 2.4.8-ac12 Alan Cox
2001-08-27 11:51 ` Matthias Andree
-- strict thread matches above, loose matches on Subject: below --
2001-09-26 19:07 Samium Gromoff
2001-09-26 20:22 Samium Gromoff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010827093529.A31359@emma1. \
--to=matthias.andree@stud.uni-dortmund.de \
--cc=laughing@shared-source.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox