From: Charles Forsyth <forsyth@terzarima.net>
To: Philo565@tuol.org, 9fans@cse.psu.edu
Subject: Re: [9fans] Another new user question
Date: Sun, 2 Mar 2008 20:32:02 +0000 [thread overview]
Message-ID: <16a4c7f5c088b5c3081a141bcd6a187d@terzarima.net> (raw)
In-Reply-To: <20080302113221.6D542581@resin17.mta.everyone.net>
> 1) Is there a way one can write to a mounted filesystem?
>
> Just for example, if I wanted to put an executable in /bin...how would
> that be done?
/bin is an empty directory that is then populated by a sequence of binds (you
can find them in /lib/namespace and your own lib/profile). so first you work
out which one of those you'd like to hold the file (ie, global or just your own private bin).
it will typically be one of /$objtype/bin or $home/bin/$objtype for compiled programs
and /rc/bin or $home/bin/rc for rc scripts. copy the new command to one of those.
in general, given a union mount, files are created in the top-most bind or mount that
was bound or mounted using the -c option to allow creation. none of the files
bound to /bin have that option so the resulting directory disallows creation.
having typed all that in i see that pietro gagliardi has already answered but i'll send this anyway.
> 2) To mount a cdrom I know I can start 9660srv...
> but how would I mount another HD? I did not see any other
> filesystem servers.
if a program's primary purpose is to act as a file server, it can be found in section 4 of
the manual, so have a browse through that. some others, including those in ndb(8)
provide a service by serving some files, but that's just the interface so they are documented
wherever the service would naturally belong. (section 8 is admin, which must surely include DNS.)
next prev parent reply other threads:[~2008-03-02 20:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-02 19:32 Phil Kassner
2008-03-02 20:05 ` Pietro Gagliardi
2008-03-02 20:32 ` Charles Forsyth [this message]
2008-03-02 20:58 philo
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=16a4c7f5c088b5c3081a141bcd6a187d@terzarima.net \
--to=forsyth@terzarima.net \
--cc=9fans@cse.psu.edu \
--cc=Philo565@tuol.org \
/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).