> Hi all!
>
> I'd like to announce a new, much needed, printing
> project: PPD Cache
> Management. I am attaching a draft of the design
> document for your
> review. This is a small project which we hope to
> complete within the
> next month. In a nutshell, this will allow a PPD
> file to be added to
> the system, and the new printer information reflected
> in the cache file
> used by the printmgr to display available printer
> information the user.
...
> One additional note to be made is that the Free
> Standards Group (FSG)
> OpenPrinting Group is working on standardizing some
> installation locations
> for PPD files and print drivers so that printer
> vendors and driver suppliers
> have a common place to install regardless of print
> service or OS distribution.
> As of the writing of this document, the following
> would be the location of
> PPD files:
>
> /usr/share/ppd/{supplier}/{language}/{manufacturer}/{m
> anufacturer}-{model}[-{extra}]-{language}.ppd
If you do not allow for an additional directory outside of /usr to be
considered as an addition to the PPD cache, adding 3rd party PPD files in a
sparse zone will not function.
When a sparse zone is created, it is not possible to write to /usr, because it
is mounted read-only (inherited) from the global zone via lofs(7FS), which
would mean that 3rd party .PPD packages would have to be installed in a global
zone.
Also according to SVID and to Sun microsystems, 3rd parties are actually not
supposed to write to /usr under any circumstances.
So my suggestion would be to come up with an alternative directory in /var/
that allows for 3rd parties to add the PPD files inside of a sparse zone.
/var/opt/ppd/.../.../ might do the trick.
This message posted from opensolaris.org
