i can think of two options: - you could go for an all Plan 9 distributed solution. this will be the easiest to roll out and maintain in my opinion (security, administration, maintenance, etc). i have used this setup with over a dozen 9pi cpu's (tftp booting from a 386-based auth+fs) collecting bluetooth data (via usb) and logging it on the fs. it worked well; the collector is a simple rc script that reads files served by the bluetooth fs and writes the data to the (imported) filesystem; it all uses 9P, of course.
- you could build a 9P network on top of heterogeneous OS environments , but things get unnecessarily messy. you have to deal with authentication, log forwarding or u9fs, non-standard ways of talking to USB, or serial and needing to build your own 9P file server for each, etc. -Skip On Sat, Nov 1, 2014 at 2:41 PM, Shane Morris <[email protected]> wrote: > Hi 9fans, > > I wish to have a 9P based sensor and actuator reporting system for an > aquaponics setup I am designing. > > I was going to use a RaspberryPi running Plan 9, an "A la mode" for the > interface to the Arduino shield, and a Cooking Hacks Open Aquarium/ Open > Garden shield (so I would need two RaspberryPi's). On the control side of > things, I would have my MacBook access the namespace via Mac9P. > > Some questions: > > * Would it be better to use a RaspberryPi Plan 9 CPU image rather than a > terminal image? The only interface I will need from the RaspberryPi to the > Arduino is TTL serial > * Eventually I would create another RaspberryPi, running Linux using > 9mount, to display various statistics and data about the system. I'd be > writing the interpreter for the information from the Open Aquarium/ Open > Garden shields in Python. With what I have described, all I would need to > do is "open" the TTL serial stream file from each of the RPis and read out > the data, am I correct? > * Does anyone have any constructive thoughts on this system setup? Please > note, I am doing this to get a handle on 9P. > > Many thanks! > > Shane. > >
