From: Denis Vlasenko <vda.linux@googlemail.com>
To: Hans Reiser <reiser@namesys.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: reiser4: maybe just fix bugs?
Date: Wed, 2 Aug 2006 21:53:30 +0200 [thread overview]
Message-ID: <200608022153.30788.vda.linux@googlemail.com> (raw)
In-Reply-To: <44CEBCBC.9070707@namesys.com>
On Tuesday 01 August 2006 04:30, Hans Reiser wrote:
> Denis Vlasenko wrote:
> > * Are there plans for making reiserfsck interface compatible with fsck?
> > I mean, making it so that reiserfsck can be symlinked to fsck.reiser
> > and it will work? Currently, there seems to be some incompatibility
> > in command-line switches. (I will dig out details and send separately
> > when I'll get back to my Linux box.)
>
> Not sure what you mean. Forgive me, I have not supervised fsck as
> closely as other things.
I just tested. reiserfsck from latest reiserfsprogs is compatible with
fsck. That is, I symlinked reiserfsck to fsck.reiserfs and on reboot
fsck -a ran "fsck.reiserfs <device>" for all my reiser3 partitions.
So this problem doesn't exist anymore. Thanks!
P.S. My fsck is from e2fsprogs-1.34.
--
vda
next prev parent reply other threads:[~2006-08-02 19:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 9:26 reiser4: maybe just fix bugs? Denis Vlasenko
2006-07-31 12:38 ` Adrian Bunk
2006-07-31 16:17 ` Horst H. von Brand
2006-07-31 20:06 ` Denis Vlasenko
2006-08-01 15:22 ` Theodore Tso
2006-08-01 2:30 ` Hans Reiser
2006-08-01 10:37 ` Pavel Machek
2006-08-01 13:59 ` Scott J. Harmon
2006-08-02 6:22 ` Jan Engelhardt
2006-08-02 19:53 ` Denis Vlasenko [this message]
2006-08-01 8:31 ` Andrew Morton
2006-08-01 2:18 ` Hans Reiser
2006-08-01 11:24 ` Vladimir V. Saveliev
2006-08-01 14:33 ` Andrew Morton
2006-08-01 15:07 ` Vladimir V. Saveliev
2006-08-01 16:55 ` David Masover
2006-08-01 19:26 ` Nate Diller
2006-08-02 3:54 ` David Masover
2006-08-03 7:46 ` Theodore Tso
2006-08-04 21:09 ` David Masover
2006-08-01 19:14 ` Nate Diller
2006-08-01 11:43 ` Christoph Hellwig
2006-08-01 11:52 ` Nick Piggin
2006-08-01 14:54 ` Andrew Morton
2006-08-01 19:32 ` Andi Kleen
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=200608022153.30788.vda.linux@googlemail.com \
--to=vda.linux@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox