From: athiele@charter.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ource and multiple upas/fs mounts
Date: Thu, 9 Jan 2003 03:55:33 -0500 [thread overview]
Message-ID: <a1876e5e7d8fd742ebafb532cff7d857@charter.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 54 bytes --]
Thanks, I believe it was you who helped me last time
[-- Attachment #2: Type: message/rfc822, Size: 1785 bytes --]
From: "Skip Tavakkolian" <fst@centurytel.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ource and multiple upas/fs mounts
Date: Thu, 9 Jan 2003 00:48:06 -0800
Message-ID: <38a9f552b96ef90c2e45ede79106d48a@centurytel.net>
> Somebody was kind enough to give me a command that works like source in UNIX, I have since forgotten it. Anyone remember it ?
>
the . (dot) will 'source' a file.
> Question2: Multiple upas/fs mounts ?
> When I try to mount more than 1 in my
> profile, I only get the last one.
-m option might be what you need?
next reply other threads:[~2003-01-09 8:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-09 8:55 athiele [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-09 8:48 Skip Tavakkolian
2003-01-09 8:16 athiele
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=a1876e5e7d8fd742ebafb532cff7d857@charter.net \
--to=athiele@charter.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).