9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: mirtchov@cpsc.ucalgary.ca
To: 9fans@cse.psu.edu
Subject: Re: [9fans] import-ing files instead of directories
Date: Thu, 22 Jan 2004 22:19:59 -0700	[thread overview]
Message-ID: <61d3bfcb68eceb6c1ebf33b9aa14a8f4@plan9.ucalgary.ca> (raw)
In-Reply-To: <c066960cb963aa1c9882c56a1000b372@plan9.bell-labs.com>

> The problem is exportfs.  It limits what it exports by chdir'ing to the
> directory being exported and only exporting from there down.  Is exporting
> a single file important to you or would you accept me just changing the
> man page?

would've been an easy solution to importing parts of remote namespaces
without taking in the entire /srv of the machine.

changing the man page is the way to go -- after all nobody uses import
differently :)



      reply	other threads:[~2004-01-23  5:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-23  3:18 mirtchov
2004-01-23  4:34 ` David Presotto
2004-01-23  5:19   ` mirtchov [this message]

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=61d3bfcb68eceb6c1ebf33b9aa14a8f4@plan9.ucalgary.ca \
    --to=mirtchov@cpsc.ucalgary.ca \
    --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).