From: David Masover <ninja@slaphack.com>
To: "Markus Törnqvist" <mjt@nysv.org>
Cc: reiserfs-list@namesys.com
Subject: Re: "Metas"
Date: Sat, 24 Apr 2004 23:38:05 -0500 [thread overview]
Message-ID: <408B40AD.2050701@slaphack.com> (raw)
In-Reply-To: <20040423203515.GK19049@nysv.org>
>
>What's so terribly bad about having the name for it in /proc or /sys
>or wherever and having it global from the kernel config?
>
>
Imagine if I had to do
cd `cat /sys/names/parent_directory`
instead of
cd ..
Or even
cd $parent_directory
or
cd $parent
The fact is, for the usability to be sane in a text world, you're going
to have to stomp on somebody's namespace. If we were talking about
scripts, it'd be different, but we're talking about something that I
know I'd find a _manual_ use for. Even if you say that I can set it to
'...' myself, there's the problem of everyone having different
definitions of that. Imagine if, before I could even 'cd ..', I had to
make sure that '..' was really '..'? Or I might accidentally 'rm -rf
../something' and have it mean something entirely different, because I'm
on a different machine?
Note that in creating /proc/sys/names, I may have stomped on somebody
anyway. And here we have the chicken-and-egg thing of
cd `cat /sys/\`/sys/names\``
and so on...
I vote for '...' if Hans/Linus/the Powers that Be will allow it.
>This is such a waste of time, really.
>
>
Not really. We already have 'metas' working, and now people want to
change it. There are a few choices here, if we wanted to "not waste time":
Change it to the most popular idea, then change it again, and again,
until people stop bickering. They won't, and this is just confusing to
users.
Leave it the same until someone comes up with a generally accepted idea.
Hans arbitrarily picks an idea.
Option #2 is what appears to be happening, and is the right thing to do
-- make something that works (somewhat) so that other development may
continue, then don't waste any more coding time on it until the design
is solid.
Or, if you mean that bickering is a waste of time, get used to it --
we're human. On top of that, if reiser4 is successful, no one may
remember us, but they will use what we create here every day.
I appologize -- I shouldn't have said "we create". I do little more
than bicker.
next prev parent reply other threads:[~2004-04-25 4:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-05 0:12 "Metas" Christian Iversen
2004-04-05 0:32 ` "Metas" Alexander G. M. Smith
2004-04-05 0:36 ` "Metas" Christian Iversen
2004-04-05 15:17 ` "Metas" Marcelo Pacheco
2004-04-13 16:51 ` "Metas" Hans Reiser
2004-04-13 18:03 ` "Metas" Narcoleptic Electron
2004-04-13 18:06 ` "Metas" Hans Reiser
2004-04-16 18:11 ` "Metas" James H. Cloos Jr.
2004-04-16 19:20 ` "Metas" Narcoleptic Electron
2004-04-16 20:44 ` "Metas" Grant Miner
2004-04-18 3:33 ` "Metas" Narcoleptic Electron
2004-04-18 5:28 ` "Metas" Zygo Blaxell
2004-04-21 16:17 ` "Metas" Hans Reiser
2004-04-21 17:14 ` "Metas" Grant Miner
2004-04-25 5:05 ` "Metas" David Masover
2004-04-25 5:44 ` "Metas" Hubert Chan
2004-04-23 20:35 ` "Metas" mjt
2004-04-25 4:38 ` David Masover [this message]
2004-04-25 10:09 ` "Metas" mjt
2004-04-26 22:30 ` "Metas" Valdis.Kletnieks
2004-04-16 22:16 ` "Metas" David Masover
2004-04-18 3:31 ` "Metas" Narcoleptic Electron
2004-04-21 16:42 ` "Metas" John D. Heintz
2004-04-21 17:00 ` "Metas" Hans Reiser
2004-04-21 18:15 ` "Metas" John D. Heintz
2004-04-05 0:47 ` "Metas" Hubert Chan
-- strict thread matches above, loose matches on Subject: below --
2004-04-21 16:19 "Metas" Burnes, James
[not found] <no.id>
2004-04-17 2:55 ` "Metas" The Amazing Dragon
2004-04-28 5:06 ` "Metas" The Amazing Dragon
2004-04-28 6:49 ` "Metas" Hubert Chan
2004-04-28 9:32 ` "Metas" mjt
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=408B40AD.2050701@slaphack.com \
--to=ninja@slaphack.com \
--cc=mjt@nysv.org \
--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.