From: Hans Reiser <reiser@namesys.com>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2003@gmx.net>,
Kristian Koehntopp <kris@koehntopp.de>,
ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: Strange directories after reisferfsck
Date: Tue, 04 Nov 2003 18:32:11 -0800 [thread overview]
Message-ID: <3FA8612B.3070809@namesys.com> (raw)
In-Reply-To: <20031105021644.GB32687@matchmail.com>
Mike Fedyk wrote:
>
>
>Does that mean there is no generation number, or random hash in the 3.6
>format, or anything else that changes on each fs image that could be keyed
>upon?
>
>
>
>
Right. The V3 kernel code was written before we had experience with
running fsck for real. We learn. We get older. We release new
versions.;-)
--
Hans
next prev parent reply other threads:[~2003-11-05 2:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 6:59 Strange directories after reisferfsck Kristian Koehntopp
2003-11-04 13:54 ` Vitaly Fertman
2003-11-05 1:08 ` Kristian Koehntopp
2003-11-05 2:07 ` Carl-Daniel Hailfinger
2003-11-05 2:15 ` Hans Reiser
2003-11-05 2:16 ` Mike Fedyk
2003-11-05 2:32 ` Hans Reiser [this message]
2003-11-05 16:35 ` Kristian Koehntopp
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=3FA8612B.3070809@namesys.com \
--to=reiser@namesys.com \
--cc=c-d.hailfinger.kernel.2003@gmx.net \
--cc=kris@koehntopp.de \
--cc=mfedyk@matchmail.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.