Norm Jacobs wrote: > Milan Jurik wrote: >> NIS is not Solaris specific feature and fully supported naming service >> with no EOL plans. Why should admins mantain another naming just for >> printing? >> > NIS is not Solaris specific, but our printers.conf.byname NIS map is. > The name service support in CUPS is more dynamic and actually > requires less admin work than NIS does for printing under Solaris.
Architecturally, though, if it went through the name service switch rather than linking directly with the protocol-specific libraries, it should work fine with NIS, LDAP, or any other NSS-supported feature. -- James Carlson 42.703N 71.076W <carlsonj at workingcode.com>
