From: Eric Van Hensbergen <ericvh@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] inferno from hg does not build out of the box
Date: Fri, 2 Oct 2009 13:39:49 -0500 [thread overview]
Message-ID: <0A38B1B3-1D12-4B81-944E-EC3BE38F0FAC@gmail.com> (raw)
In-Reply-To: <84bb117e7f2be0bbb9f39875c9d6b4e4@terzarima.net>
On Oct 2, 2009, at 1:31 PM, Charles Forsyth wrote:
>> committing a ".emptydir" file in each directory would be easier.
>
> why bother making it .emptydir (ie, with the dot) when that makes it
> invisible on broken host systems (with the ls bug) but visible under
> inferno itself.
> more important, and the reason i didn't do that,
> if it's visible under inferno itself, it breaks the point of some of
> those directories being there, and empty: you're supposed to be able
> to enumerate
> services by listing names subsequently bound to them.
>
Perhaps a rule in the mkfile which would check/create empty directories?
Certainly makes sense for <arch>/lib and whatnot, less certain it
makes perfect
sense for other common empty directories.
-eric
next prev parent reply other threads:[~2009-10-02 18:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 4:27 [9fans] corrections to /sys/src/cmd/8l/l.h lucio
2009-10-01 10:22 ` sqweek
2009-10-01 13:23 ` [9fans] kencc, inferno hg, v9fs is big?, porting Sam Watkins
2009-10-01 13:48 ` Abhishek Kulkarni
2009-10-01 17:09 ` C H Forsyth
2009-10-01 16:59 ` Russ Cox
2009-10-02 1:27 ` jrm8005
2009-10-01 18:19 ` ron minnich
2009-10-01 18:23 ` David Leimbach
2009-10-01 18:25 ` David Leimbach
2009-10-01 18:26 ` Eric Van Hensbergen
2009-10-01 18:34 ` Vinu Rajashekhar
2009-10-02 4:52 ` [9fans] inferno from hg does not build out of the box Sam Watkins
2009-10-02 8:44 ` roger peppe
2009-10-02 10:44 ` C H Forsyth
2009-10-02 15:03 ` David Leimbach
2009-10-02 17:03 ` Tim Newsham
2009-10-02 18:31 ` Charles Forsyth
2009-10-02 18:39 ` Eric Van Hensbergen [this message]
2009-10-02 21:07 ` Charles Forsyth
2009-10-03 15:12 ` Sam Watkins
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=0A38B1B3-1D12-4B81-944E-EC3BE38F0FAC@gmail.com \
--to=ericvh@gmail.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).