From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cpu command and 9660srv
Date: Fri, 21 May 2004 10:02:50 +0200 [thread overview]
Message-ID: <886341aadd5c3b775fa91eba24c94991@proxima.alt.za> (raw)
In-Reply-To: <35604a989834edb77258ee76364f30a0@granite.cias.osakafu-u.ac.jp>
> In the present 9660srv command, only one user can use
> /srv/9660, and then, mount his cdrom to cpu server.
> How can I change this situation to those described above.
> ie,
You can load multiple copies of 9660srv, just specify the target /srv/
name for it (see the synopsis in the man page). I have had cause to
do this on occasion.
In general, though, you can use the same /srv/9660 for multiple
devices/images unless they can't locate the image in their namespace.
I am somewhat foggy about permissions, I have to admit.
++L
next prev parent reply other threads:[~2004-05-21 8:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-21 7:21 Kenji Okamoto
2004-05-21 8:02 ` lucio [this message]
2004-05-21 8:11 ` Charles Forsyth
2004-05-21 8:43 ` Kenji Okamoto
2004-05-21 9:16 ` Kenji Okamoto
2004-05-21 9:41 ` Kenji Okamoto
2004-05-24 1:54 ` Kenji Okamoto
2004-05-27 2:47 ` Kenji Okamoto
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=886341aadd5c3b775fa91eba24c94991@proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).