From: Hans Reiser <reiser@namesys.com>
To: hanasaki <hanasaki@hanaden.com>
Cc: reiserfs-list@namesys.com
Subject: Re: v3.6 vs v4? and how to migrate?
Date: Thu, 29 Jun 2006 13:03:45 -0700 [thread overview]
Message-ID: <44A43221.1080204@namesys.com> (raw)
In-Reply-To: <44A42FFB.2000307@hanaden.com>
hanasaki wrote:
>Is Reiser v4 production ready?
>What is the procedure for migrating 3 => 4?
>What are the reasons to migrate 3 => 4?
>What are the reasons to stay on 3?
>
>TIA
>
>
>
>
I suggest running the badblocks program before migrating....
4 is faster.....
prev parent reply other threads:[~2006-06-29 20:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 19:54 v3.6 vs v4? and how to migrate? hanasaki
2006-06-29 20:03 ` Hans Reiser [this message]
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=44A43221.1080204@namesys.com \
--to=reiser@namesys.com \
--cc=hanasaki@hanaden.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.