From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <297cd451811e1a0a78100d6c488708d0@kw.quanstro.net> References: <297cd451811e1a0a78100d6c488708d0@kw.quanstro.net> Date: Mon, 3 May 2010 12:01:09 -0700 Message-ID: From: Akshat Kumar To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [9fans] An Important Node Topicbox-Message-UUID: 190a9018-ead6-11e9-9d60-3106f5b1d025 I tried this initially, with the following in the file: exec /rc/bin/lp -H -d officejet5610 >>[2] /sys/lib/lp/log/officejet5610 however, the program runs as user none, and requires access to /dev/lp7 (which I believe is not in its namespace, in the first place). Perhaps this approach would work better if I ran usb/print on boot up - although still, the file /dev/lp7 is chmod 660 for user and group bootes. Ideas on that one? The other thing is, I wonder if the data coming in on the port is actually being piped to lp(1) - but I can do some tests to figure that out. Best, ak On Mon, May 3, 2010 at 7:05 AM, erik quanstrom wrote: >> On the Plan 9 side, then, the CPU server listens: >> >> aux/listen1 -tv tcp!*!PORT $home/bin/rc/print & > > makes more sense to put this script in /rc/bin/service/tcpPORT > > - erik > >