From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <80c99e791001240502v3e7c955ek130ded319bb03ef5@mail.gmail.com> References: <80c99e791001240502v3e7c955ek130ded319bb03ef5@mail.gmail.com> Date: Sun, 24 Jan 2010 10:54:55 -0600 Message-ID: From: Eric Van Hensbergen To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [9fans] mount acme on plan9port Topicbox-Message-UUID: c5dea94c-ead5-11e9-9d60-3106f5b1d025 On Sun, Jan 24, 2010 at 7:02 AM, Lorenzo Bolla 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