All of lore.kernel.org
 help / color / mirror / Atom feed
From: kenny gorman <kgorman@panix.com>
To: Oleg Drokin <green@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: Reiserfs versions
Date: Mon, 18 Nov 2002 23:46:19 -0800	[thread overview]
Message-ID: <3DD9EC4B.70907@panix.com> (raw)
In-Reply-To: 20021119093526.A32026@namesys.com

I poked around suse's site, and found the 'certified kernel' with:

2.4.16-64gb smp
reiserfs-3.x.0k_pre10-8

See any reason why this combination is not a good idea?

How do the version numbers work? I am confused about the 3.x notation 
and the 3.6 notation you used below...I upgraded my reiserfsprogs to 
3.6.4 just in case, but the filesystem rpm is still 3.x.0k_pre10-8 right?

Thanks!!!

-kg


Oleg Drokin wrote:
> Hello!
> 
> On Mon, Nov 18, 2002 at 03:30:57PM -0800, kenny gorman wrote:
> 
> 
>>I guess I want to get what would be considered the most stable 
>>combination of code vs. something bleeding edge, but also not old like 
>>what I have now (and thus prone to bugs...).  I really like reiserfs, 
>>but I have heard of (and experienced it now) about corruption problems.
>>Currently, I am running (no laughing..):
>>Suse 2.4.7-64GB-SMP
> 
> 
> Upgrade this to vanilla 2.4.19 or if you prefer SuSE stuff - to
> SuSE's errata 2.4.16 kernel.
> Actually you might try more recent 2.4.20-pre (or rc) stuff if you want, too
> if you do not feel it is too bleeding edge for you.
> 
> 
>>lvm-0.9.1_beta7-10
> 
> 
> Do not know about that.
> 
> 
>>reiserfs-3.x.0j-17
> 
> 
> This should be upgraded to latest reiserfsprogs which is 3.6.4.
> 3.x.0j is way too unstable.
> 
> Bye,
>     Oleg
> 
> .
> 




  reply	other threads:[~2002-11-19  7:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-18 23:30 Reiserfs versions kenny gorman
2002-11-19  6:35 ` Oleg Drokin
2002-11-19  7:46   ` kenny gorman [this message]
2002-11-19  7:51     ` Oleg Drokin
2002-11-19 15:05       ` kenny gorman
2002-11-19 15:08         ` Oleg Drokin
2002-11-19 16:22           ` Dieter Nützel
2002-11-19 16:26             ` Oleg Drokin
2002-11-19 16:38               ` Dieter Nützel
2002-11-19 16:41               ` kenny gorman

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=3DD9EC4B.70907@panix.com \
    --to=kgorman@panix.com \
    --cc=green@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.