...'t going away any time soon for me...) You have two problems here: 1) Accessing plan 9's plumber from unix 2) Accessing unix files (attachments) from plan 9 1 isn't too difficult, a listen1 with exportfs -r /mnt/plumb combined with an ssh port forward (-L or -R, can't remember which applies here) will give you access to the plumber via p9p's 9p (probably in combination with srv -a ...

... text via noproc). for the later, likely just remove the ! from /rc/bin/service/!tcp515 if you're already running aux/listen (as on a cpu server); otherwise inspect its contents for handing to aux/listen1. I'm now trying to set the thing up so it works across the network; I *think* it's listening on port 515, and I get the following in my /sys/lib/lp/log/lpdaemonl file when I try ...

... via noproc). for the later, likely just remove the ! from /rc/bin/service/!tcp515 if you're already running aux/listen (as on a cpu server); otherwise inspect its contents for handing to aux/listen1. Well, I ran out of paper testing, finding, and fixing a problem (needed to set auto-CR), but I think the printer should be able to print now. No postscript, which is annoying, but it's ...

... if it's a dot-matrix printer, you almost certainly will want some other device class for your dot-matrix printer (unless ghostscript knows how to drive it, you're likely just going to get text via noproc). for the later, likely just remove the ! from /rc/bin/service/!tcp515 if you're already running aux/listen (as on a cpu server); otherwise inspect its contents for handing to aux/listen1.

since it was mentioned, (and not that anyone cares), found an interpretation of netpipes i wrote for testing the myricom driver. /n/sources/contrib/quanstro/hose.c it turns out that aux/listen1 is enough to replace faucet. sink%% aux/listen1 -v 'tcp!*!6666' /bin/rc -c '/bin/cat plan9.iso' source%% hose sink < plan9.iso - erik

... there should be a simple way to take stdin/stdout and generate a srv file -- such that I could aux/listen1 tcp!*!someport srvit -b somesrvname aux/listen1 tcp!*!someport rc -c 'echo -n 0 /srv/somesrvname' Guess I was getting too hung up on stdin and stdout being different fd's like a ...

On 4/5/07, Eric Van Hensbergen <ericvh@gmail.com> wrote: Probably a stupid question -- there seems like there should be a simple way to take stdin/stdout and generate a srv file -- such that I could aux/listen1 tcp!*!someport srvit -b somesrvname aux/listen1 tcp!*!someport rc -c 'echo -n 0 /srv/somesrvname' Russ

Probably a stupid question -- there seems like there should be a simple way to take stdin/stdout and generate a srv file -- such that I could aux/listen1 tcp!*!someport srvit -b somesrvname import -B sorta does this, but it does too much, it shoves authentication down my throat and also wants to mount it to some mount point instead of giving me a nice srv file. Is there some more simple ...