From mboxrd@z Thu Jan 1 00:00:00 1970 Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <20071130123249.GB14203@nibiru.local> References: <8ccc8ba40709070144y42f8c81andeb54dde4588f968@mail.gmail.com> <8607d45190b8811e23dc5426d1fbf657@quanstro.net> <8ccc8ba40709070317t600021b9jbe3715561964383e@mail.gmail.com> <20071130033720.GA2817@nibiru.local> <8ccc8ba40711300142w1ef7f32crf0371b06dd733aff@mail.gmail.com> <20071130123249.GB14203@nibiru.local> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <68631093-437F-4904-A7CB-8ADB71B3A580@kix.in> Content-Transfer-Encoding: 7bit From: Anant Narayanan Subject: Re: [9fans] Ideas for an printer filesystem Date: Fri, 30 Nov 2007 22:16:46 +0530 To: weigelt@metux.de, Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Cc: Topicbox-Message-UUID: 0f6d7b5e-ead3-11e9-9d60-3106f5b1d025 > Only copying one file is not enough, otherwise you have no chance > for giving additional parameters like colorspace, orientation, > resolution, etc, etc, etc. The application would have to handle all > this by itself and would require more detailed information about the > printer (which would tie the job to one specific printer). How about simply: $ echo "print " > /printers/ctl $ cat myfile > /printers/data Skipping either the printing/printer options while writing to ctl will result in default options being applied. -- Anant