From: "T. A." <tkhoadfdsaf@hotmail.com>
To: "Ville Herva" <vherva@mail.niksula.cs.hut.fi>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Which kernel (Linus or ac)?
Date: Fri, 12 Oct 2001 05:25:32 -0400 [thread overview]
Message-ID: <OE26nfAMxUtDjTZZTTu0000e302@hotmail.com> (raw)
In-Reply-To: <XFMail.20011011094548.jkp@riker.nailed.org> <3BC5E152.3D81631@bigfoot.com> <3BC5E3AF.588D0A55@lexus.com> <OE22ITtCsuSYkbAY0Jp0000df3f@hotmail.com> <20011012095618.R22640@niksula.cs.hut.fi>
>
> Of course, you can get most of the IDE chipset support, fs support
(reiserfs
> 3.5, ext3) and LFS support as patches for 2.2:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/hedrick/ide-2.2.19/
Have used this and has worked great on the machines I've had to use it
on. Though I'm a bit leery about using it since I figure the generic
2.2.x.preX kernels get a lot more testing that those with this patch
installed. Also heard of problems using this patch on a VIA PIII SMP
system. :-( And just went I had been planning to use it on a dual PIII VIA
chipset board too.
>
>
ftp://ftp.namesys.com/pub/reiserfs-for-2.2/linux-2.2.19-reiserfs-3.5.34-patc
h.bz2
I actually was going to start using this until I learned that 2.2.x
reiser patched kernels couldn't use reiserfs partitions made with 2.4.
:-( Ended up having to redo an entire system when a downgrade to 2.2.x
became imperitive. Also the 2.2.x reiser patch lacks the large file support
(on the reiser filesystems created under 2.2.x) and maybe other goodies and
I don't get that back easily by just switching kernels.
> ftp://ftp.kernel.org/pub/linux/kernel/people/sct/ext3/
Might give this a try now that it appears to be release quality.
> http://moldybread.net/patch/kernel-2.2/linux-2.2.19-lfs-1.0.diff.gz
I'll look into this the next time > 2GB files support becomes needed on
a system. pre 2.4.x I had been using FreeBSD for such tasks.
next prev parent reply other threads:[~2001-10-12 9:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 14:45 jkp
2001-10-11 17:42 ` Robert Love
2001-10-11 17:52 ` Tim Connors
2001-10-11 18:11 ` Tim Moore
2001-10-12 2:01 ` Horst von Brand
[not found] ` <001901c152ca$0b42c080$0600000a@petersohn.net>
2001-10-12 18:32 ` Tim Moore
2001-10-11 18:13 ` Tim Moore
2001-10-11 18:23 ` J Sloan
2001-10-11 18:56 ` Tim Moore
2001-10-11 19:59 ` [OT] " J Sloan
2001-10-12 4:42 ` T. A.
2001-10-12 6:07 ` J Sloan
2001-10-12 9:14 ` T. A.
2001-10-12 9:59 ` Luigi Genoni
2001-10-12 17:35 ` J Sloan
2001-10-12 22:59 ` J . A . Magallon
2001-10-11 23:50 ` Oden Eriksson
2001-10-11 23:56 ` Arnaldo Carvalho de Melo
2001-10-12 0:09 ` J Sloan
2001-10-12 4:37 ` T. A.
2001-10-12 6:56 ` Ville Herva
2001-10-12 9:25 ` T. A. [this message]
2001-10-12 10:02 ` Ville Herva
2001-10-12 11:35 ` Andrea Arcangeli
2001-10-11 19:43 ` M. R. Brown
2001-10-11 22:05 ` Luigi Genoni
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=OE26nfAMxUtDjTZZTTu0000e302@hotmail.com \
--to=tkhoadfdsaf@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vherva@mail.niksula.cs.hut.fi \
/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
all inboxes | Powered by JetHome®