From: "Michael Teichgräber" <mt@wmipf.in-berlin.de>
To: weigelt@metux.de, Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] plan9port -> ftpfs
Date: Thu, 10 Jul 2008 23:44:35 +0200 [thread overview]
Message-ID: <487682C3.50700@wmipf.in-berlin.de> (raw)
In-Reply-To: <20080710193756.GC13259@nibiru.local>
> did anyone already port ftpfs to plan9port ?
>
> thx
Last year I tried to port it, see the tarball
containing ftpfs and the mercurial history
of my changes:
http://wmipf.in-berlin.de/ftpfs-p9p-hg.tar.gz
It works basically, but some problems remain (from the readme):
- "mv" does not work, so one can't rename anything.
Ftpfs complains
about wstat not being implemented. Is there a difference to
Plan 9?
- Sometimes a "Software caused connection abort" appears,
making ftpfs exit. I don't know whether this is ftpfs's fault,
or is just the normal behaviour of an FTP server.
(Might be solved already:)
- Perhaps ftpfs should not use rfork on plan9port, but rather
proccreat for io(), since the `dying' variable seems not to
work as probably intended.
Michael
prev parent reply other threads:[~2008-07-10 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 19:37 Enrico Weigelt
2008-07-10 21:44 ` Michael Teichgräber [this message]
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=487682C3.50700@wmipf.in-berlin.de \
--to=mt@wmipf.in-berlin.de \
--cc=9fans@9fans.net \
--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).