From: 9nut@9netics.com
To: 9fans@cse.psu.edu
Subject: [9fans] directories in server registry (#s)
Date: Sun, 7 Mar 2004 09:36:32 -0800 [thread overview]
Message-ID: <bbdb78cd9c061241d2fade2c3822ad4b@9netics.com> (raw)
Would supporting subdirectories in /srv be a bad idea? It seems
because of '#s's global nature, it would be useful if an application (or its
user) could confine itself to a subdirectory. Perhaps too much kernel
overhead for the convenience it provides? I think I just talked myself
out of it.
next reply other threads:[~2004-03-07 17:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-07 17:36 9nut [this message]
2004-03-07 16:40 ` David Presotto
2004-03-07 17:59 ` 9nut
2004-03-08 8:40 ` Fco.J.Ballesteros
2004-03-08 10:45 ` 9nut
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=bbdb78cd9c061241d2fade2c3822ad4b@9netics.com \
--to=9nut@9netics.com \
--cc=9fans@cse.psu.edu \
/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).