From: John D Groenveld on 30 Apr 2010 14:08 In article <379875634294341974.202408eckert-alphanet.ch(a)news1.open-news-network.org>, Chris Eckert <eckert(a)alphanet.ch> wrote: >the appropriate cli tools, but how is this >achieved? # lpadmin -p hp1320nw -v /dev/null -m netstandard_foomatic \ -n /usr/lib/lp/model/ppd/system/foomatic/HP/HP-LaserJet_1320-Postscript.ppd.gz \ -o dest=HPHP1320NW_IP_ADDRESS:9100 -o Duplex=DuplexNoTumble \ -o banner=never -T PS -I postscript # /bin/enable hp1320nw # /usr/sbin/accept hp1320nw # lp -d hp1320nw /usr/share/ghostscript/8.64/examples/alphabet.ps John groenveld(a)acm.org
From: Richard B. Gilbert on 30 Apr 2010 16:47 John D Groenveld wrote: > In article <Ueidnawdz6oXnkbWnZ2dnUVZ_vadnZ2d(a)giganews.com>, > Richard B. Gilbert <rgilbert88(a)comcast.net> wrote: >> so, upgrade to Solaris 10. It configures printers with far greater ease > > The OP is running S10. His problem is that the printer GUI broke > when he upgraded from update 7 to update 8. > > I don't use the GUI so won't be much help to him but > the hack is to use the command line tools. > > John > groenveld(a)acm.org It's been years since I configured a printer that way. AIRC the process was poorly documented. I'd suggest that the OP back out to update 7. This sort of thing is one of the reasons that Sysadmins don't always install the "latest and greatest"! I don't want to have to fight the *~@#$ system. I want to *use* it. "Updates" should be tested to ensure that they DO NOT BREAK ANYTHING.
From: Chris Eckert on 1 May 2010 05:57
thanks a lot; will try that and report back here. chris -- Chris Eckert (mobile) |