From mboxrd@z Thu Jan 1 00:00:00 1970 Message-Id: <200306200705.h5K758709088@augusta.math.psu.edu> To: 9fans@cse.psu.edu Subject: Re: [9fans] The new ridiculous license In-Reply-To: Your message of "Fri, 20 Jun 2003 02:54:52 EDT." <200306200654.h5K6sq709001@augusta.math.psu.edu> From: Dan Cross Date: Fri, 20 Jun 2003 03:05:08 -0400 Topicbox-Message-UUID: d254258a-eacb-11e9-9e20-41e7f4b1d025 > We could finally set up a reasonable print > spooler on some old recycled machine (usually an older model Sun running > one of the BSD's) and have the Solaris machines point to that. It, in > turn, would fan out to the network printers using the above mentioned > setup. Clunky though the whole thing was, it was more reliable than the > Solaris implementation of System V printing. Err, I should qualify this. Prior to Solaris 2.6, we used the native Solaris system V stuff to try and spool jobs to a machine running `normal' lpd. However, it was terribly unreliable; it would frequently crash, and jobs would just sort of mysteriously disappear. Eventually, we took to using my ports of Berkeley lpd under Solaris, but that was difficult to maintain (you had to be careful when applying patches that you wouldn't accidentally overwrite the locally modified printing system with part of the system's printing system that had been updated, but that you had already replaced). Also, there was the problem of the system printing tools no longer working. It was easy enough to provide replacements for command line use, but any time they were embedded in a command, it could get ugly. /etc/printers.conf really was a big improvement. - Dan C.