From: David Masover <ninja@slaphack.com>
To: Clay Barnes <clay.barnes@gmail.com>
Cc: "Maciej Sołtysiak" <pysiak.satriani@wp.pl>, reiserfs-list@namesys.com
Subject: Re: Another article abour Reiser4 on linux.com
Date: Sat, 05 Aug 2006 21:39:39 -0400 [thread overview]
Message-ID: <44D5485B.5070208@slaphack.com> (raw)
In-Reply-To: <20060806004442.GQ17805@HAL_5000D.tc.ph.cox.net>
Clay Barnes wrote:
> I think the core thing we have to have to win this argument is
> a) A word that isn't *instantly* associated with banned things.
That'd be nice.
> b) The ability to point to the technology to point to the design
> and say look, "Look, it's *impossible* to use this design to put
> binary modules into the kernel." Even if it's as hard as ATI or
> nVidia modules to put it in, that'll be enough to put up a fight
> against inclusion.
Why?
Why does it have to be impossible to do binary things with the kernel?
I mean, if Linus hates GPL3 because it limits what people do with the
kernel...
Besides, you can't make it impossible, you can only make it about as
hard as it is now. The license is the issue here.
> The *only* way to win a polical/personal fight
> is to remove any possible objection until resistance looks purely
> stupid and wholly unsubtantiated.
I agree. That's why we not only need a new name, we also need a
cut'n'paste argument that just makes this look stupid.
And it has to be short enough that cut'n'paste isn't bad, because if we
refer people to the FAQ, they won't read it.
> I was just saying to my roomate that I was losing hope for Reiser4
> because I didn't see an end to the politics any time soon.
Yes, it can look pretty hopeless.
> There's only one possible way I see to get in. You must ask for an
> absolute list of things that are objectionable. You should then
> ask *before you start work* about removal of any items that are
> either a) impossible, or b) illogical. Once you've gotten the
> official stamp of approval of the (posibly recvised) absolute list
> of objections, you have to do it, completely and exactly. If they
> agreed that that is everything they find wrong and promised that
> they would include Reiser4 if those issues were resolved, then they
> really *have* to put it in then.
The problem is, they don't. There have been some fairly definitive
lists in the past, that were done, but maybe not quite the way they were
expected.
> The core of all this is that rather than leaving an open-ended task
> that can be expanded at will, they are given limits to how long the
> objections can be spread out.
Problem is, dictators can do whatever they want, even if they said
something else before.
And that's all assuming you can get them to agree to such a list, and
agree to abide by it. They either wouldn't go for it, or they would
come up with a list that effectively kills Reiser4, turning it into ext3.
next prev parent reply other threads:[~2006-08-06 1:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-05 12:55 Another article abour Reiser4 on linux.com Tassilo Horn
2006-08-05 14:55 ` David Masover
2006-08-05 16:17 ` Maciej Sołtysiak
2006-08-05 16:22 ` Maciej Sołtysiak
2006-08-05 18:07 ` Clay Barnes
2006-08-05 21:40 ` David Masover
2006-08-06 0:44 ` Clay Barnes
2006-08-06 1:39 ` David Masover [this message]
2006-08-06 2:14 ` TongKe Xue
2006-08-06 2:51 ` David Masover
2006-08-06 4:07 ` TongKe Xue
2006-08-06 8:20 ` Hans Reiser
2006-08-06 11:04 ` Bernd Schubert
2006-08-06 12:41 ` Lexington Luthor
2006-08-06 13:15 ` Bernd Schubert
2006-08-06 17:06 ` Lexington Luthor
2006-08-06 19:17 ` David Masover
2006-08-06 19:21 ` TongKe Xue
2006-08-09 8:07 ` Hans Reiser
2006-08-06 9:19 ` Hans Reiser
2006-08-06 16:26 ` Clemens Eisserer
2006-08-06 22:55 ` Bruce Byfield
2006-08-09 8:28 ` Hans Reiser
2006-08-09 9:47 ` Andreas Schäfer
2006-08-09 15:51 ` David Masover
2006-08-09 18:38 ` Bruce Byfield
2006-08-09 17:37 ` Hans Reiser
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=44D5485B.5070208@slaphack.com \
--to=ninja@slaphack.com \
--cc=clay.barnes@gmail.com \
--cc=pysiak.satriani@wp.pl \
--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.