public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: johnrobertbanks@fastmail.fm
Cc: linux-kernel@vger.kernel.org, dhlii@comcast.net,
	linux-fsdevel@vger.kernel.org
Subject: Re: REISER4 FOR INCLUSION IN THE LINUX KERNEL.
Date: Mon, 09 Apr 2007 15:12:12 -0400	[thread overview]
Message-ID: <461A900C.40400@tmr.com> (raw)
In-Reply-To: <1176092219.12458.1183612420@webmail.messagingengine.com>

johnrobertbanks@fastmail.fm wrote:

>> I actually beleive that Hans made a reasonable case that 
>> Reiser4 had gone about as far as it could reasonably go with regard 
>> to testing, robustness, ... without the broader base of use that 
>> even an experimental filesystem in distribution tree would get.
> 
> Of course, this is an entirely reasonable request of Reiser's.
> One meet with an array of unreasonable actions, but mainly STALLING 
> which has led to REISER4 never becoming part of the main kernel.
> 
> It has also lead to many false claims about REISER4. Claims that are
> never backed up with solid statistics, but used to keep REISER4 out of
> the kernel and tar its reputation.
> 
Keep that last sentence in mind for four lines...

>>     I for one would at least play with it if it were in the distribution
>> tree.
> 
> I AM SURE THERE ARE A HUGE NUMBER OF PEOPLE WHO WOULD GIVE IT A TRY.
>  
"Claims that are never backed up with solid statistics, ..."

>>     As far as I could tell Hans pretty much everything else that 
>> was demanded. Hans eventually caved and provided - albeit with much 
>> pissing and moaning, and holy than thou rhetoric.
> 
> It was not his pissing and moaning, etc,... these were just excuses to
> keep REISER4 from succeeding. The truth is, that any excuse would do.
> 
> The real reasons are financial and backed by big money (sometimes, big
> egos).
> 
Yes all of the people who make millions on the other filesystems! 
Wait... identify who makes a penny more or less with or without Reiser4.

[ snip ]

Until Namesys is stable there's no support team. It's not my impression 
that there's much support otherwise.

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

      parent reply	other threads:[~2007-04-09 19:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-09  4:16 REISER4 FOR INCLUSION IN THE LINUX KERNEL johnrobertbanks
2007-04-09  4:39 ` johnrobertbanks
2007-04-09  4:59   ` Jeff Garzik
2007-04-09  9:27   ` Pekka Enberg
2007-04-09 14:02   ` Valdis.Kletnieks
2007-04-09  4:42 ` Jeff Garzik
2007-04-09  5:11 ` Gene Heskett
2007-04-09 10:55 ` Troll Of The Year (Was: REISER4 FOR INCLUSION IN THE LINUX KERNEL.) Ronni Nielsen
2007-04-09 15:47   ` Phillip Susi
2007-04-09 16:41   ` Troll Of The Year Jan Engelhardt
2007-04-09 16:47     ` Valdis.Kletnieks
2007-04-09 13:56 ` REISER4 FOR INCLUSION IN THE LINUX KERNEL Valdis.Kletnieks
2007-04-09 14:35 ` Matthew Wilcox
2007-04-09 19:12 ` Bill Davidsen [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=461A900C.40400@tmr.com \
    --to=davidsen@tmr.com \
    --cc=dhlii@comcast.net \
    --cc=johnrobertbanks@fastmail.fm \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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