From: "Bruce Ellis" <bruce.ellis@gmail.com>
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 15:54:06 +1100 [thread overview]
Message-ID: <775b8d190711302054g12c4868cv2575ab16c718a43c@mail.gmail.com> (raw)
In-Reply-To: <13426df10711302042x78d36291n54f50beb964aa068@mail.gmail.com>
i wrote a clonefs that changes a walk to the directory created for
the server to an attach with ctl. it saves a lot of replicated code.
i wonder what happened to it. it's not too hard.
brucee
On Dec 1, 2007 3:42 PM, ron minnich <rminnich@gmail.com> wrote:
> On Sep 6, 2007 6:56 PM, Enrico Weigelt <weigelt@metux.de> wrote:
>
> > /next-id spits out an new (random) job-id
>
> it's the wrong place. I think you need /jobs directory, with a /jobs/clone.
>
> You open /jobs/clone, it's a ctl file. You copy the file to that dir.
> you attach the job to the printer much the way you attach a protocol
> stack to an interface.
>
> i suggest your best bet is to try to put something together and see
> what feels right. Abstract design is no substitute for prototyping and
> experience with prototypes.
>
>
> >
> > View to an single job:
> >
> > * /myjob
> > /id unique key
> > /priority
> > /owner
> > /logfile the job's logfile
> > /status job's status, writable to alter status
> > values: new, processing, printing, done, kill
> > /size.total
> > /size.done
> > /pages.total
> > /pages.done
> > /colorspace (ie. rgb,cmyk,pantone,mono,greyscale)
> > /papersize
> > /orientation
> > /options/<opt> extended options (ie. for folding, etc)
> > /content.ps whole content as postscript
>
> you'll almost certainly not cover all the info you need with all the
> file names. Why not do as the network stack does and have status,
> which returns this info as a set of tuples -- want to guess what
> format I'd like? (hint -- it's NOT XML)
>
>
> > * Cloning a printer (to have multiple instances w/ separate options):
> > choose some name and write it to ./clone
>
> options should attach to jobs, not to printers. Else you have the
> possibility of a nice combinatorial explosion.
>
>
> > * Creating a new job:
> > + fetch a new job-id
>
> cat /job/clone
>
> > + mkdir a new job queue entry (with fetched key)
> no no no. :-)
>
> > + all necessary structures will appear automatically
> > + upload the postscript data to ./content.ps
> > + do appropriate changes (ie. papersize, orientation, colorspace, ...)
> > + write "new" to ./status
>
> eek. Have a ctl file.
> >
> > * Abort an job
> > + look for the job's dir and write "abort" to ./status
> no. ctl file.
>
>
> > What do you think about this ?
>
> Study the network devices, they're pretty nice.
>
> ron
>
next prev parent reply other threads:[~2007-12-01 4:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 23:56 Enrico Weigelt
2007-09-07 8:44 ` Francisco J Ballesteros
2007-09-07 10:08 ` erik quanstrom
2007-09-07 10:17 ` Francisco J Ballesteros
2007-09-07 10:54 ` erik quanstrom
2007-11-30 7:19 ` Aki Nyrhinen
2007-11-30 3:37 ` Enrico Weigelt
2007-11-30 9:42 ` Francisco J Ballesteros
2007-11-30 12:32 ` Enrico Weigelt
2007-11-30 13:06 ` Rodolfo =?unknown-8bit?Q?Garc=EDa?=
2007-11-30 13:38 ` Enrico Weigelt
2007-11-30 16:56 ` Rodolfo =?unknown-8bit?Q?Garc=EDa?=
2007-11-30 16:46 ` Anant Narayanan
2007-11-30 22:40 ` Lucas James
2007-12-01 4:42 ` ron minnich
2007-12-01 4:54 ` Bruce Ellis [this message]
2007-12-11 13:30 ` roger peppe
2007-12-11 20:36 ` Bruce Ellis
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=775b8d190711302054g12c4868cv2575ab16c718a43c@mail.gmail.com \
--to=bruce.ellis@gmail.com \
--cc=9fans@cse.psu.edu \
/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).