From: mjt@nysv.org
To: David Masover <ninja@slaphack.com>
Cc: Hans Reiser <reiser@namesys.com>,
Claudio Martins <ctpm@ist.utl.pt>,
reiserfs-list@namesys.com, Marcel Hilzinger <marcel@hilzinger.hu>
Subject: Re: reiser acceptance (was Re: Atomic filesystem or not)
Date: Wed, 21 Jul 2004 11:25:51 +0300 [thread overview]
Message-ID: <20040721082551.GZ4990@nysv.org> (raw)
In-Reply-To: <40FDFAB1.9050300@slaphack.com>
On Wed, Jul 21, 2004 at 12:10:09AM -0500, David Masover wrote:
>Wrong. sys_reiser5 could require a totally different set of arguments
>than sys_reiser4. Suppose it's like this:
You are right.
>If only, if only. But we discussed libraries, and it seems Hans wants
>apps patched to use sys_reiser4 directly. Right?
Is there a performance reason behind this?
Also, one less library dependancy is one less library dependancy...
Beside the fact that direct patching is a stronger vote for
standardizing.
>Imagine if Tesla had been able to play that game. This is why democracy
>currently sucks -- the honest people won't be able to play the game, so
>of course there are mostly dishonest politicians!
So we have the Free Software movement that can't play the corporate
software game. But revolutions have been known to happen.
>Oops, offtopic :X
A strong maybe.
>Why, when it's automated, stable, and ultimately makes your box faster?
The time that goes to compiling may even save the 1% speedup that
the new binaries bring along. Remember, that Debian has different packages
with different optimizations where it actually matters.
And I can make my own packages with apt-get source --build if I need.
So I just don't like to sit on my arse for hours while something compiles
just so I can have a next-to-imaginary speed-up :)
>And I abhor the notion of having packages excluded because someone else
>doesn't like the license.
Amen to that. cf. DFSG/Debian.
>But I wasn't trying to sell Gentoo as a distro to actually use, only one
>to send patches to.
And I think it's a good point, Gentoo users are most likely very good
testers.
>Just tell them that you are a (woody|sarge|sid)-based very unstable
>reiser4-powered distro.
This is a bit like defeating the purpose of Debian stable, and it
takes a bit of time to make all these packages. But sure, there may
be some automatization to build these backports easily; if there isn't
I'd have to invent one, and still no-one would be forced to use it.
So, now we have the strategy, now let's wait for the call to arms.
--
mjt
next prev parent reply other threads:[~2004-07-21 8:25 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-15 12:34 Atomic filesystem or not Marcel Hilzinger
2004-07-15 12:54 ` Claudio Martins
2004-07-15 13:25 ` Marcel Hilzinger
2004-07-15 19:43 ` David Masover
2004-07-15 19:52 ` Hans Reiser
2004-07-16 1:46 ` David Masover
2004-07-19 8:33 ` Hans Reiser
2004-07-19 9:23 ` Toby Dickenson
2004-07-19 21:03 ` reiser acceptance (was Re: Atomic filesystem or not) David Masover
2004-07-19 22:07 ` John D. Heintz
2004-07-20 5:58 ` Hans Reiser
2004-07-20 7:28 ` David Masover
2004-07-20 5:27 ` Hans Reiser
2004-07-20 7:04 ` David Masover
2004-07-20 6:52 ` mjt
2004-07-20 7:39 ` David Masover
2004-07-20 8:03 ` mjt
2004-07-21 5:10 ` David Masover
2004-07-21 8:25 ` mjt [this message]
2004-07-22 8:08 ` Hans Reiser
2004-07-20 14:30 ` reiser acceptance Hubert Chan
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=20040721082551.GZ4990@nysv.org \
--to=mjt@nysv.org \
--cc=ctpm@ist.utl.pt \
--cc=marcel@hilzinger.hu \
--cc=ninja@slaphack.com \
--cc=reiser@namesys.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.