From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Drawterm and security
Date: Mon, 21 Feb 2005 11:20:03 -0800 [thread overview]
Message-ID: <faac09a691b7307030050e14e6b768e5@collyer.net> (raw)
In-Reply-To: <b82bcbb558aabed15b9b5a802473212e@tombob.com>
> What is the reason for ensuring an explicit service name?
As usual, one posts a service to permit (or at least encourage)
sharing. In this case, one also wants to avoid a possible
collision with an existing (bootes) /srv/factotum on a CPU server.
By creating a /srv/factotum.$user at first login, it's
then possible for later logins by $user to share the same
factotum (by just mounting /srv/factotum.$user on /mnt).
It does make one's profile (or at least my profile) a little
messier, probing for suitable existing factota in /srv and
/mnt/term/srv.
next prev parent reply other threads:[~2005-02-21 19:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-19 18:37 Brian L. Stuart
2005-02-19 18:48 ` andrey mirtchovski
2005-02-19 21:00 ` Brian L. Stuart
2005-02-19 18:58 ` Russ Cox
2005-02-19 19:15 ` blstuart
2005-02-19 19:20 ` Russ Cox
2005-02-19 20:24 ` blstuart
2005-02-19 20:34 ` andrey mirtchovski
2005-02-19 19:20 ` [9fans] Venti security in view of SHA-1 exploit Paul Lalonde
2005-02-19 19:26 ` andrey mirtchovski
2005-02-19 19:35 ` Paul Lalonde
2005-02-19 20:14 ` Tim Newsham
2005-02-20 4:24 ` Karl Magdsick
2005-02-19 20:15 ` Russ Cox
2005-02-19 22:25 ` boyd, rounin
2005-02-19 22:44 ` [9fans] Venti security in view of SHA-1 exploity William Josephson
2005-02-19 22:48 ` boyd, rounin
2005-02-20 18:08 ` William Josephson
2005-02-19 23:21 ` [9fans] Venti security in view of SHA-1 exploit Bruce Ellis
2005-02-20 1:00 ` Tim Newsham
2005-02-20 3:53 ` Karl Magdsick
2005-02-19 19:52 ` [9fans] Drawterm and security Skip Tavakkolian
2005-02-19 19:11 ` blstuart
2005-02-21 11:30 ` Robert Raschke
2005-02-21 19:20 ` geoff [this message]
[not found] <Pine.BSI.4.61.0502191055110.3971@malasada.lava.net>
2005-02-19 21:09 ` Brian L. Stuart
2005-02-19 22:42 ` Russ Cox
2005-02-19 23:37 ` Brian L. Stuart
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=faac09a691b7307030050e14e6b768e5@collyer.net \
--to=geoff@collyer.net \
--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).