From: Hans Reiser <reiser@namesys.com>
To: Valdis.Kletnieks@vt.edu
Cc: Perry Kundert <perry@kundert.ca>, reiserfs-list@namesys.com
Subject: Re: Reiser4 changes meaning of ENOENT/EACCES, breaking gcc?
Date: Fri, 30 Jul 2004 22:22:48 -0700 [thread overview]
Message-ID: <410B2CA8.6070905@namesys.com> (raw)
In-Reply-To: <200407302057.i6UKvLAu000714@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
>On Fri, 30 Jul 2004 11:57:35 PDT, Hans Reiser said:
>
>
>
>>> By the way, his suggested workaround was effective...
>>>
>>>
>>Can you talk the glibc guys into adopting it? That would be best.
>>
>>
>
>Somebody should also check the POSIX spec and see if it requires a
>particular semantic there.
>
>Also, pushing it off to the glibc people is quite possibly the wrong
>way to go about it. Do you *really* want to sit there and tell every
>other app that turns up with a similar problem that they have to fix
>it to run on one particular filesystem, when every OTHER filesystem
>doesn't need help? That doesn't sound like a good plan - if 4 or 5
>apps turn up, it will turn people away "because stuff breaks if you
>use reiser4"....
>
>
>
That is the cost of progress. Just look at all the confusion caused by
phasing out horse whips and using gas pedals instead.....
We are adding functionality. The standards will adjust to that in 5
years. I am 40, 5 years seems like not so long....
prev parent reply other threads:[~2004-07-31 5:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-29 23:54 Reiser4 changes meaning of ENOENT/EACCES, breaking gcc? Perry Kundert
2004-07-30 18:57 ` Hans Reiser
2004-07-30 20:57 ` Valdis.Kletnieks
2004-07-31 5:22 ` Hans Reiser [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=410B2CA8.6070905@namesys.com \
--to=reiser@namesys.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=perry@kundert.ca \
--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.