From: Rudolf Sykora <rudolf.sykora@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] have a problem with u9fs
Date: Fri, 3 Sep 2010 11:11:35 +0200 [thread overview]
Message-ID: <AANLkTinuQHGOHn3_LVJiaHOWtUiD0COyuy6D685_tmvv@mail.gmail.com> (raw)
In-Reply-To: <AANLkTindGF7JznPcfBpsLCk18_v+NvnuybC7zezQ=DDT@mail.gmail.com>
one more note:
;ls -l /etc/u9fs.key
lrwxrwxrwx 1 root root 25 2009-07-31 20:30 /etc/u9fs.key ->
/home/ruda/ruzne/u9fs.key
;ls -l /home/ruda/ruzne/u9fs.key
-r-------- 1 root root 20 2009-07-30 15:35 /home/ruda/ruzne/u9fs.key
On 3 September 2010 11:07, Rudolf Sykora <rudolf.sykora@gmail.com> wrote:
> I have, on my linux machine:
>
> /etc/services:
> u9fs 564/tcp 9fs
>
> /etc/inetd.conf:
> u9fs stream tcp nowait root /home/ruda/bin/u9fs u9fs -a p9any
>
> /etc/u9fs.key: 3 lines:
> <password>
> <login>
> local
>
> I don't remember if I had to do anything on my plan9 machine.
> And it somehow works. But I have never understood it.
> Don't know if it's of any help...
>
> Ruda
>
>
> On 4 September 2010 09:45, unknown <unknown.0x0000@gmail.com> wrote:
>> i installed u9fs on my linux machine to can use 9p server, and added lines
>> to /etc/services and to /etc/inetd.conf too and it listens to 564 port as
>> expected, but there is a problem with the authentication, when i do 9p -a
>> 192.168.1.2 ls /home , i got 9p: mount: u9fs: rhosts authentication failed ,
>> i created $HOME/.rhosts and putted in it 192.168.1.2 also tried with
>> me@192.168.1.2 all failed with the same error, what should i do?
>>
>> i
>>
>>
>
next prev parent reply other threads:[~2010-09-03 9:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-04 7:45 unknown
2010-09-03 9:07 ` Rudolf Sykora
2010-09-03 9:11 ` Rudolf Sykora [this message]
2010-09-04 8:16 ` unknown
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=AANLkTinuQHGOHn3_LVJiaHOWtUiD0COyuy6D685_tmvv@mail.gmail.com \
--to=rudolf.sykora@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).