From: "Wolfgang Kunz" <woku@hush.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] How to extend a fossil filesystem with a second disk?
Date: Tue, 9 Feb 2010 07:48:17 +0100 [thread overview]
Message-ID: <20100209064818.1204711803D@smtp.hushmail.com> (raw)
Your sample:
mount /srv/fossil /n/other other
works fine.
There was a typo error in my mount command.
Many thanks for your help!
-Wolfgang
On Mon, 08 Feb 2010 13:34:06 +0100 Steve Simon <steve@quintile.net>
wrote:
>> Here is what I was trying without success:
>> [snip]
>
>It looks right (from memory).
>
>> I was not able to mount the 'other' fs to /n/other.
>
>how are you doing the mount, I would expect somthing like
>
> mount /srv/fossil /n/other other
>
>i.e. you mount fossil but with the attach specifier of "other".
>
>-Steve
next reply other threads:[~2010-02-09 6:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 6:48 Wolfgang Kunz [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-02-08 12:20 Wolfgang Kunz
2010-02-08 12:34 ` Steve Simon
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=20100209064818.1204711803D@smtp.hushmail.com \
--to=woku@hush.com \
--cc=9fans@9fans.net \
/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).