From: Oleg Drokin <green@namesys.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Jure Pecar <pegasus@nerv.eu.org>, reiserfs-list@namesys.com
Subject: Re: Red Hat Enterprise Linux AS (v. 2.1) and > 2 GB files
Date: Fri, 27 Jun 2003 10:59:18 +0400 [thread overview]
Message-ID: <20030627065918.GA20771@namesys.com> (raw)
In-Reply-To: <3EFB1F97.3020205@namesys.com>
Hello!
On Thu, Jun 26, 2003 at 08:30:15PM +0400, Hans Reiser wrote:
> >Because RedHat never bothered to update reiserfs code in their e kernels.
> >Your best bet is to get a newer kernel, perhaps 2.4.21, and if you cannot
> >afford that, trim your app to not create files that big.
> >There are rumors that 2.4.18 based e kernel is in the testing ...
> You mean RedHat is STILL shipping 2.4.9 based kernels? Oh no wonder
> there are people with stability problems.....
No, I believe there was kernel update last month that upgraded RHAS kernel up to
2.4.18.
Anyway RHAS 2.4.9 kernel does not have that much in common with vanilla 2.4.9.
Bye,
Oleg
next prev parent reply other threads:[~2003-06-27 6:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-26 13:53 Red Hat Enterprise Linux AS (v. 2.1) and > 2 GB files Trond Hagen
2003-06-26 13:58 ` Jure Pecar
2003-06-26 16:30 ` Hans Reiser
2003-06-27 6:59 ` Oleg Drokin [this message]
2003-06-27 8:50 ` Alexander Lyamin
2003-06-27 11:51 ` Nikita Danilov
2003-06-27 12:48 ` Chris Mason
2003-06-27 16:10 ` Russell Coker
2003-06-27 22:07 ` [OT] Distro names ending with 'ix' and Linux forks Was [Re: Red Hat Enterprise Linux AS (v. 2.1) and > 2 GB files] Philippe Gramoullé
2003-06-26 15:42 ` Red Hat Enterprise Linux AS (v. 2.1) and > 2 GB files Oleg Drokin
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=20030627065918.GA20771@namesys.com \
--to=green@namesys.com \
--cc=pegasus@nerv.eu.org \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.