From: Eric Van Hensbergen <ericvh@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] mount acme on plan9port
Date: Sun, 24 Jan 2010 10:54:55 -0600 [thread overview]
Message-ID: <a4e6962a1001240854m1021a70fy6dc36d9be9376881@mail.gmail.com> (raw)
In-Reply-To: <80c99e791001240502v3e7c955ek130ded319bb03ef5@mail.gmail.com>
On Sun, Jan 24, 2010 at 7:02 AM, Lorenzo Bolla <lbolla@gmail.com> wrote:
> I'm trying to use "9 mount" to mount acme's socket (in `namespace`/acme) to
> some directory in /mnt (let's say /mnt/acme). I'm using ArchLInux:
> $> uname -a
> Linux eee 2.6.32-ARCH #1 SMP PREEMPT Sat Dec 26 08:26:17 UTC 2009 i686
> Intel(R) Atom(TM) CPU N280 @ 1.66GHz GenuineIntel GNU/Linux
> The simple command:
> mount -t 9p -o unix,trans=unix,name=lollo,uname=lollo,noextend,nodev
> /tmp/ns.lollo.:0/acme /home/lollo/acme
> and I've traced down the offending option to be "trans=unix".
> Any suggestions?
you shouldn't need -o unix,trans=unix -- just trans=unix.
Double check the 9pnet module is installed as well as the 9p module
(it should be automagically in the kernel version you are running).
Also, a good tip when trying to figure out whats going south when v9fs
is involved is to add debug=0xffff into your mount options and post
the respective sections of your /var/log/messages.
Just tried it on 2.6.33-rc4 and it mounted fine
mount -t 9p /tmp/ns.root.localhost:10/acme /mnt -o trans=unix,uname=root
-eric
next prev parent reply other threads:[~2010-01-24 16:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-24 13:02 Lorenzo Bolla
2010-01-24 16:54 ` Eric Van Hensbergen [this message]
2010-01-24 17:55 ` Lorenzo Bolla
2010-01-24 19:27 ` Russ Cox
2010-01-24 20:09 ` David Leimbach
2010-01-24 21:51 ` Russ Cox
2010-01-27 11:44 ` Ethan Grammatikidis
2010-01-27 13:23 ` Lorenzo Bolla
2010-01-27 13:40 ` roger peppe
2010-01-27 14:12 ` erik quanstrom
2010-01-27 14:35 ` roger peppe
2010-01-27 21:20 ` erik quanstrom
2010-01-27 21:35 ` Eric Van Hensbergen
2010-01-27 21:49 ` ron minnich
2010-01-27 22:47 ` Charles Forsyth
2010-01-28 6:24 ` Russ Cox
2010-01-28 10:43 ` roger peppe
2010-01-27 17:27 ` Eric Van Hensbergen
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=a4e6962a1001240854m1021a70fy6dc36d9be9376881@mail.gmail.com \
--to=ericvh@gmail.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).