From: hiro <23hiro@googlemail.com>
To: weigelt@metux.de, Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9P via serial links or USB
Date: Fri, 27 Nov 2009 08:24:53 +0100 [thread overview]
Message-ID: <f4d8fa40911262324n5a658013gd6f49163a340d3e4@mail.gmail.com> (raw)
In-Reply-To: <20091126225334.GA25437@nibiru.local>
There was some stuff available even before 2004
I think I've used once one of these:
http://intr.overt.org/gphotofs/
http://www.hep.phy.cam.ac.uk/~lester/gphoto2-fuse-fs/
On Thu, Nov 26, 2009 at 11:53 PM, Enrico Weigelt <weigelt@metux.de> wrote:
> * hiro <23hiro@googlemail.com> wrote:
>> There already is a gphoto2 fs for fuse if I remember correctly.
>
> Last time I heared, it was just planned.
> Perhaps I'm not up2date and you've got a pointer for me ?
>
>> Though I haven't heard of any camera with 9p yet.
>
> Yep, that would be the next step: provide a toolkit for embedded
> developers and encourage them to use it instead of the bogus
> pptp+proprietary stuff.
>
>
> Meanwhile I've made up another front:
> I'm negotiating with an developer/producer of power meters and
> similar products, which log their data to SD cards and have an
> ethernet/IP interface.
>
> At this point I'm thinking about an more thin approach for those
> devices: put 9P on the lowest level possible, no IP, but a very
> thin protocol (eg. somethink like IL, but directly ontop of eth ?),
> just enough to carry 9P messages. Just an error-correcting (not
> necessarily in-order) datagram protocol, which does not need an
> explicit address assignment (eg. builtin 64bit device addresses ?).
> These devices essentially just speak 9P - multiple devices on
> the same network interface are represented within the fs hierachy.
>
>
> cu
> --
> ----------------------------------------------------------------------
> Enrico Weigelt, metux IT service -- http://www.metux.de/
>
> phone: +49 36207 519931 email: weigelt@metux.de
> mobile: +49 174 7066481 icq: 210169427 skype: nekrad666
> ----------------------------------------------------------------------
> Embedded-Linux / Portierung / Opensource-QM / Verteilte Systeme
> ----------------------------------------------------------------------
>
>
prev parent reply other threads:[~2009-11-27 7:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 18:01 Enrico Weigelt
2009-11-25 1:08 ` hiro
2009-11-25 2:28 ` Latchesar Ionkov
2009-11-26 22:54 ` Enrico Weigelt
2009-11-26 23:14 ` Latchesar Ionkov
2009-11-26 23:37 ` Enrico Weigelt
2009-11-26 23:51 ` Latchesar Ionkov
2009-11-26 22:53 ` Enrico Weigelt
2009-11-27 7:24 ` hiro [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=f4d8fa40911262324n5a658013gd6f49163a340d3e4@mail.gmail.com \
--to=23hiro@googlemail.com \
--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).