9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Christoph Paschke <c.paschke@me.com>
To: 9fans@9fans.net
Subject: [9fans] hardware device line -> what about the "file resource hardware devices" that are supported
Date: Tue, 13 Mar 2012 17:21:17 +0100	[thread overview]
Message-ID: <A14DFD63-53A3-46D7-86D3-2861B3762B95@me.com> (raw)

I'm a newbe at Plan 9 and I got Inferno and Octopus just running. I writing first limbo programs and I like it.

+ Made in plane C
+ resource is a file and not complicated proprietary drivers
+ it can be run such easy and small with emu at each system (I have Mac)
+ interconnect of resources

And when in one example it is explained, that you just send command "snap" to a cam input stream and you catch the file later by /image folder I thought:

Ok, let's google if there is any description for a CAM or a USB-Scanner what can be addressed such way with Plan 9. I found nothing.

So, my question: Doesn't it makes sense that some hardware like CAMs or USB-Scanners are working with Plan 9. I mean: There is a good system but as I understand there is absolutely no device what I can buy and connect to it.
There not need be 1000 CAMs supported, I would be happy if already only 1 CAM, 1 Scanner, 1 Printer would be supported and usable with Plan 9.

Example: I want write some Limbo programs and I would also support for example some printing functions (one laser printer, one label printer) and a barcode scanner for example.
And if I mean printing, I will say that it need work and not absolutely catastrophic results.

So think about Apple: There is also not 1000 of hardware what you buy, you stay in the Apple Line. Ok, today it is growing fast and more and more companies offer the matching Mac drivers now.
But I remember that before it was always VERY LESS that was supported. Most was only a small Apple supported line of hardware, in most cases high value.

So, for me, who wants start programing at Plan 9 base would be very interesting to find a good "Plan 9 Line of Hardware" that work with the file resource concept.
+ One Laser Printer, maybe one Inkjet
+ One Label Printer
+ One Barcode Reader, maybe one RFID reader
+ One digital camera
+ maybe One Meshing device like Zigbee / Digimesh
+ One USB-Scanner
+ One Hardware for a fax system

So, only one supported hardware line would be already enough and I already could start with some nice user programs.

Is this a stupid question? Sure I could now spend endless times in trying to reach such aim myself, but I believe there are so much tec freaks out there, that can do such things much better and faster and I could concentrate more at starting user programs?

- Chris




             reply	other threads:[~2012-03-13 16:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13 16:21 Christoph Paschke [this message]
2012-03-13 17:24 ` Nemo
2012-03-13 17:27   ` erik quanstrom
2012-03-13 21:54 ` [9fans] hardware device (...) Tristan
2012-03-13 22:09   ` erik quanstrom
2012-03-13 22:27     ` John Floren
2012-03-13 22:55       ` Tristan
2012-03-14  1:38   ` Jeff Sickel
2012-03-14 13:02     ` erik quanstrom
2012-03-14 13:13       ` erik quanstrom

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=A14DFD63-53A3-46D7-86D3-2861B3762B95@me.com \
    --to=c.paschke@me.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).