From: Stewart Smith <stewart@flamingspork.com>
To: Vladimir Saveliev <vs@namesys.com>
Cc: Nick Vahalik <nick@nsanity.com>, reiserfs-list@namesys.com
Subject: Re: Reiserfs Data Recovery
Date: Sat, 13 Mar 2004 20:44:52 +1100 [thread overview]
Message-ID: <1079171092.16498.29.camel@willster> (raw)
In-Reply-To: <1078918871.9476.116.camel@tribesman.namesys.com>
[-- Attachment #1: Type: text/plain, Size: 454 bytes --]
On Wed, 2004-03-10 at 22:41, Vladimir Saveliev wrote:
> namesys.com had description of reiserfs internals. But now it does not.
> read source code instead
Is it possible to get all of these documents back and in a nice, central
location? Historical documents can be quite interesting, especially in
trying to understand the design process of modern file systems.
--
Stewart Smith (stewart@flamingspork.com)
http://www.flamingspork.com/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-03-13 9:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 3:07 Reiserfs Data Recovery Nick Vahalik
2004-03-10 11:41 ` Vladimir Saveliev
2004-03-10 15:08 ` Nick Vahalik
2004-03-10 15:26 ` Vladimir Saveliev
2004-03-10 16:54 ` Nick Vahalik
[not found] ` <200403111419.31982.vitaly@namesys.com>
2004-03-11 15:48 ` Nick Vahalik
2004-03-13 9:44 ` Stewart Smith [this message]
[not found] ` <200403111936.01548.vitaly@namesys.com>
[not found] ` <40509A74.6080703@nsanity.com>
[not found] ` <200403130001.57937.vitaly@namesys.com>
2004-03-15 15:48 ` Reiserfs Data Recovery (SOLVED) Nick Vahalik
2004-03-15 16:32 ` Vitaly Fertman
-- strict thread matches above, loose matches on Subject: below --
2004-03-08 14:22 Reiserfs Data Recovery Nick Vahalik
2004-03-08 14:33 ` Philippe Gramoullé
2004-03-08 14:43 ` Nick Vahalik
2004-03-08 14:59 ` Philippe Gramoullé
2004-03-08 16:06 ` Nick Vahalik
2004-03-09 9:28 ` Vitaly Fertman
2004-03-08 18:41 ` Ryan Underwood
[not found] ` <404CC8AA.9020405@nsanity.com>
2004-03-08 21:59 ` Ryan Underwood
[not found] ` <404CF46B.10000@nsanity.com>
2004-03-09 1:13 ` Ryan Underwood
2004-03-09 21:24 ` Nick Vahalik
2004-03-09 11:36 ` Hans Reiser
2004-03-09 14:42 ` Nick Vahalik
2004-03-09 15:45 ` Hans Reiser
2004-03-09 16:28 ` Nick Vahalik
2004-03-09 18:08 ` Ryan Underwood
[not found] <20030727153826-191600041>
2003-07-27 23:22 ` reiserfs data recovery Manuel Krause
[not found] ` <20030727162537-184400041>
2003-07-28 1:27 ` D. Sen
2003-07-28 1:27 ` D. Sen
2003-07-27 22:38 D. Sen
2003-07-27 22:38 ` D. Sen
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=1079171092.16498.29.camel@willster \
--to=stewart@flamingspork.com \
--cc=nick@nsanity.com \
--cc=reiserfs-list@namesys.com \
--cc=vs@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.