All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Chan <chrisfz@netvigator.com>
To: reiserfs-list@namesys.com
Subject: Re: hans' case
Date: Tue, 31 Oct 2006 17:39:23 +0800	[thread overview]
Message-ID: <454719CB.70205@netvigator.com> (raw)
In-Reply-To: <45471396.70608@slaphack.com>

David Masover wrote:
> Christopher Chan wrote:
> 
>> Then again, the quietness of the list could very well be a sign of the 
>> robustness of reiserfs :D
> 
> I only wish.
> 
> Partly out of respect, and partly out of cowardice, I've avoided posting 
> anything, especially bug reports. I'm attempting to solve the issues as 
> best I can, and maybe I'll have a pile of logs for Hans if he gets back.
> 
> Also, I'm afraid of referring to Hans in the past tense, but the impulse 
> to do that is strong enough that I know I'll do it unconsciously unless 
> I avoid posting.

If Hans is reiser4 then I see little hope on the filesystem side of 
things in Linux.

> 
> Also, I don't often start threads, and nobody's talking right now.
> 
> Personally, I wish Hans the best, and I'd be praying for an acquittal if 
> I was religious. But regardless of the outcome, I'll continue to use 
> Reiser4 as long as I can -- I'm not afraid of a "tainted name". What I 
> am afraid of is whether the FS will be properly maintained. There's a 
> reason I use Linux instead of the more obscure OSes -- Linux has 
> horrible design, but it's actively supported.
> 
> I don't mean to imply that my data is more important than Hans' 
> situation, but I can't neglect my data, and I don't know what I can do 
> to help Hans.

Hans and his family have had it rough. One wonders whether all the 
resistance involved in getting reiserfs/reiser4 into Linux was partly to 
blame.

      parent reply	other threads:[~2006-10-31  9:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-31  0:15 hans' case Maciej Sołtysiak
2006-10-31  2:50 ` Christopher Chan
     [not found]   ` <45471396.70608@slaphack.com>
2006-10-31  9:39     ` Christopher Chan [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=454719CB.70205@netvigator.com \
    --to=chrisfz@netvigator.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.