From: "Latchesar Ionkov" <lucho@gmx.net>
To: weigelt@metux.de,
"Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] What do I need for a small 9P2000 server @ Linux ?
Date: Sat, 30 Jun 2007 11:05:32 -0700 [thread overview]
Message-ID: <f158dc670706301105m3ea183e5i64a7304906e9f88@mail.gmail.com> (raw)
In-Reply-To: <20070630005123.GA22285@nibiru.local>
There is nothing wrong with iounit being set to zero.
Lucho
On 6/29/07, Enrico Weigelt <weigelt@metux.de> wrote:
> * Kris Maglione <bsdaemon@comcast.net> wrote:
>
> Hi,
>
> > That's strange. I've never tried it with u9fs servers, but it
> > works fine for me with libixp, lib9p, and Inferno servers.
>
> I've tracked it down a little bit. Seems the iounit in the fid
> is zero (no idea why). And that leads ixp_read() to do actually
> nothing, but return immediately. So the files get opened, but
> not a bit is read.
>
>
> cu
> --
> ---------------------------------------------------------------------
> Enrico Weigelt == metux IT service - http://www.metux.de/
> ---------------------------------------------------------------------
> Please visit the OpenSource QM Taskforce:
> http://wiki.metux.de/public/OpenSource_QM_Taskforce
> Patches / Fixes for a lot dozens of packages in dozens of versions:
> http://patches.metux.de/
> ---------------------------------------------------------------------
>
>
next prev parent reply other threads:[~2007-06-30 18:05 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 13:31 Enrico Weigelt
2007-06-28 14:28 ` Eric Van Hensbergen
2007-06-28 15:20 ` ron minnich
2007-06-28 17:36 ` Enrico Weigelt
2007-06-28 17:40 ` erik quanstrom
2007-06-28 17:49 ` Kris Maglione
2007-06-28 18:45 ` Enrico Weigelt
2007-06-28 18:49 ` Kris Maglione
2007-06-28 19:01 ` Enrico Weigelt
2007-06-28 19:10 ` Kris Maglione
2007-06-28 19:37 ` Enrico Weigelt
2007-06-28 19:50 ` Kris Maglione
2007-06-28 20:12 ` Enrico Weigelt
2007-06-30 0:51 ` Enrico Weigelt
2007-06-30 0:55 ` Kris Maglione
2007-06-30 11:39 ` Enrico Weigelt
2007-06-30 16:16 ` Kris Maglione
2007-06-30 17:39 ` Enrico Weigelt
2007-06-30 17:45 ` Kris Maglione
2007-06-30 18:15 ` Latchesar Ionkov
2007-06-30 19:32 ` Kris Maglione
2007-06-30 20:34 ` geoff
2007-06-30 20:39 ` Kris Maglione
2007-06-30 21:18 ` geoff
2007-06-30 18:05 ` Latchesar Ionkov [this message]
2007-06-28 20:17 ` Kris Maglione
2007-06-28 18:52 ` ron minnich
2007-06-28 18:57 ` Kris Maglione
2007-06-28 19:03 ` Enrico Weigelt
2007-06-28 19:15 ` Kris Maglione
2007-06-29 1:05 ` Roman Shaposhnik
2007-06-29 1:22 ` ron minnich
2007-06-29 4:31 ` Kris Maglione
2007-06-29 5:37 ` Uriel
2007-06-29 11:56 ` Enrico Weigelt
2007-06-29 12:37 ` Eric Van Hensbergen
2007-06-29 14:12 ` Enrico Weigelt
2007-06-29 14:25 ` Charles Forsyth
[not found] ` <c0ae573a0daa29e787cf87aa9deaae79@terzarima.net>
2007-06-29 20:13 ` Enrico Weigelt
2007-06-29 20:30 ` Francisco J Ballesteros
2007-06-29 21:32 ` Enrico Weigelt
2007-06-29 21:40 ` ron minnich
2007-07-11 18:52 ` Jack Johnson
2007-06-29 21:53 ` Francisco J Ballesteros
2007-06-30 12:03 ` Enrico Weigelt
2007-06-28 16:51 ` Uriel
2007-07-11 18:16 ` Eric Van Hensbergen
2007-06-29 0:56 ` Roman Shaposhnik
2007-06-29 1:07 ` Kris Maglione
2007-06-29 1:10 ` ron minnich
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=f158dc670706301105m3ea183e5i64a7304906e9f88@mail.gmail.com \
--to=lucho@gmx.net \
--cc=9fans@cse.psu.edu \
--cc=weigelt@metux.de \
/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).