From mboxrd@z Thu Jan  1 00:00:00 1970
From: Lucas James <Lucas.James@ldjcs.com.au>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Ideas for an printer filesystem
Date: Sat,  1 Dec 2007 09:40:39 +1100
User-Agent: KMail/1.9.7
References: <8ccc8ba40709070144y42f8c81andeb54dde4588f968@mail.gmail.com>
	<20071130123249.GB14203@nibiru.local>
	<68631093-437F-4904-A7CB-8ADB71B3A580@kix.in>
In-Reply-To: <68631093-437F-4904-A7CB-8ADB71B3A580@kix.in>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200712010940.39305.Lucas.James@ldjcs.com.au>
Topicbox-Message-UUID: 0f8c05b0-ead3-11e9-9d60-3106f5b1d025

On Sat, 1 Dec 2007 03:46:46 Anant Narayanan wrote:
> How about simply:
>
> $ echo "print <printing-options> <printer-options>" > /printers/ctl
> $ cat myfile > /printers/data
>
> Skipping either the printing/printer options while writing to ctl
> will result in default options being applied.
>
> --
> Anant

That's only good for single machine/single user setup.  

If you have more than one person/program trying to print to different 
printers/options, you would get mixed results.  Picture a second print job 
starting in between the write to /printers/ctl and /printers/data, and you'll 
see the difficulties in keeping it all together.

Lucas

-- 
Modern man is the missing link between apes and human beings.