gheet wrote:
> Hi Joel,
>
> Thanks for raising this! I believe Norm has answered most of your
> queries below.
>
> Starting any ipp service causes gdm start up is a bug. You can log a
> bug against jds/gnome/session if you wish, I can see that being
> assigned to the appropriate product.
>
> I find CUPS interesting while was putting together the Linux version
> of JDS. There are good GUI support for example, like the
> gnome-cups-manager which essentailly provides one GUI to do what
> currently gnome-dtprintinfo and solaris-print-manager does. Of course
> you also got the web based interface as part of CUPS.
>
> There is one thing that was really bad is that CUPS store your
> password in plain text file and doesn't integrate with your LDAP/NIS
> that well.
>
> One thing which I would like see working towards with is to see
> whether when a user want to add access to a print queue that he/she
> can do it without having the root password or print privileges. That
> would simplify many thing as I believe.
>
The Solaris print commands are name service aware and the PAPI print
commands are as well. On Solaris, they use the name service switch for
printer name resolution, so you can store data in
${HOME}/.printers
/etc/printers.conf
NIS (printers.conf.byname)
NIS+ (printers.org_dir)
LDAP
The PAPI print commands also run on Linux and should run on most systems
with POSIX interfaces. They are print service and protocol independent
and name service aware. They contain code that emulates the name
service switch for
/etc/printers.conf
/etc/printcap
NIS (printers.conf.byname)
At some point, it would be nice to expand this to include
${HOME}/.printers and LDAP for non-Solaris systems, but as far as
Solaris and OpenSolaris are concerned, we already have them.
The ${HOME}/.printers provides users a means of limitting their view of
the available printers and adding access to remote print queues anywhere.
Configuring local print queues for direct attached printers should be
handled as hands off as possible through hot-plug event handling.
Network attached printers should be handled similiarly (if possible). I
would like to componentize the print managers so that we can call
specific, targeted functionality for things like hot-plug events.
-Norm
