From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <906a85070a784fabc9457db2fc3f4706@proxima.alt.za> References: <13426df10906282241i40f9e9f0x2276057be26ac4d9@mail.gmail.com> <906a85070a784fabc9457db2fc3f4706@proxima.alt.za> Date: Mon, 29 Jun 2009 10:03:23 -0500 Message-ID: From: Eric Van Hensbergen To: lucio@proxima.alt.za, Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] 9p on Yeeloong (gNewSense Linux) Topicbox-Message-UUID: 10f47732-ead5-11e9-9d60-3106f5b1d025 On Mon, Jun 29, 2009 at 3:49 AM, wrote: >> cat /proc/filesystems > > Returns > > =A0 =A0 =A0 =A0nodev 9p > > but "mount -t 9p" returns "Protocol not supported". =A0Is the problem > not within "mount"? > There are actually several modules which work together to provide 9p, there is the 9p file system, the 9p network module (which includes as a default the socket transport), and then additional transport plugins (for KVM, infiniband, etc.) Its possible you have the file system module, but not the network module -- however, I thought the dependencies have been setup to fix that for some time. The best thing to do is to turn on debug with your mount and look at the /var/log/messages. Linux errno error codes don't give the best error and protocol not supported could actually mean one of several things, the /var/log/messages with debug on will clarify the problem. So add -o debug=3D0xffff to your mount line and post the /var/log/messages output and we'll see what we can do to help you. Thanks, -eric