I recieved MANY responses and they were all great. The consenses seems
to be "pick up a copy of JetAdmin from HP."
The other popular answer was to use admintool. I chose to go the
JetAdmin route.
Some specific responses will placed on the end of this summary.
Here is what I did.
ftp://ftp.hp.com/html/sol2_x.html#software
sol_pkgadd.d0037 -- For Solaris 2.3, 2.4
su
pkgadd -d <filename> all
Commented back in tftp into my inetd.conf
And did a mkdir /tftpboot
>From this point.. Simply run jetadmin and set up a new printer.
Thank you to everyone who responded:
The respondants that I have heard from so far:
David Evans <djve@deakin.edu.au>
Michael Price <mprice@cch.com.au>
Petros Michalis <michalis@dpg.rnb.com>
"Sanjiv K. Bhatia" <sanjiv@aryabhat.cs.umsl.edu>
Jim McBride <jim@fleshwound.org>
Martin Huber <hu@garfield.m.eunet.de>
"Marks, Evan R" <A700102@aetna.com
Justin Young <justiny@cluster.engr.subr.edu>
Kenneth Simpson <ken_simpson@tmai.com>
Guntram Wolski <gwolsk@sei.com>
Sahir Siddiqui <sahirns@menger.eecs.stevens-tech.edu>
John Eliopoulos <johne@echo-on.net>
Brian Desmond <brian@ben.psych.unimelb.edu.au>
"Michael R. Zika" <zika@oconto.tamu.edu>
Mike Ellis <mellis@mmscolwy.demon.co.uk>
Michael Sullivan <mike@trdlnk.com>
Robert Pasken <pasken@thunder.slu.edu>
Tommy Lindqvist <lindqt@space.se>
Christian Masopust <Christian.Masopust@emndev.siemens.co.at>
Glenn Satchell - Uniq Professional Services
Martin Achilli <martin@gea.hsr.it>
Oliver Landsmann <shark@geo.sbg.ac.at>
cwaters@emh-1.submepp.navy.mil
ray <rtrzaska@uk.mdis.com>
boyd0009@mc.duke.edu
Mary Verge <mary@datacube.com>
u00y0115@hsc.hac.com
"Lyle E. Miller" <lyle@ocs.com>
Sameer Vadakke-Kuruppath <sameer@sdt.com>
"S. D. Raffensberger 500622500" <sdr@rdga3.att.com>
--------------------------------------------------
From: Keith M Willenson <keith@oz.health.state.mn.us>
To: jboerne@uswest.com
Subject: Re: Setting up network printers...
I had the same problem and am very frustrated with the documentation!!!!
On solaris 2.4
#lpadmin -p printer2 -s system1!printer1
will create printer2 on your local system that goes to printer1 on
system1.
See the man page for lpadmin.
On SunOS 4.1.1, edit your /etc/printcap. rm = remote machine, rp =
remote
printer, sd = spool directory
printer2|LaserWriter|ps|postscript|laser|PostScript:\
:lp=:\
:rm=system1:\
:rp=printer1:\
:sd=/var/spool/printer1:
#
will create printer2 on your local system that goes to printer1 on
system1.
Make sure you create the /var/spool/printer1 directory.
HTH
K
keith.willenson@health.state.mn.us Sr. Systems Analyst
(612) 623-5661 Minnesota Department of Health
--------------------------------------------------
From: Nicholas J Brealey <nick.brealey@aeat.co.uk>
You probably need HP's JetDirect software which is available by anonymous
ftp
from:
ftp-boi.external.hp.com
It is very easy to install and setup.
The only problem I have found is that man -t and lp -Ttroff do not work
after
HP's procedure and Sun's Postscript filters may not be installed.
The following extract from my notes shows how I got man -t and lp -Ttroff
to work on my systems for two ptrinters lj and pj after I had installed
HP's
JetDirect Software:
To: log
Subject: INSTALLED HP printers properly
I installed the HP printers properly so that man -t and lp -Ttroff work.
On the server I added all the postscript filters as per the Solaris
documentation:
# cd /etc/lp/fd
# for f in `ls | sed 's/.fd$//'`
> do
> lpfilter -f $f -F $f.fd
> done
I then changed the lj and pj filters so that they accept postscript,
simple,
hpgl2 and pcl input instead of any input:
# lpfilter -f lj -
Input types: postscript simple hpgl2 pcl
^D
# lpfilter -f pj -
Input types: postscript simple hpgl2 pcl
^D
(I could have changed the lj.fd and pj.fd files before installing the
filters).
To list the filters do:
# lpfilter -f all -l
Nick
--------------------------------------------
From: Ric Anderson <ric@rtd.com>
Get Solaris Advanced System Administrator's Guide, ISBN 1-56276-131-5
by Janice Windsor (pub: Ziff Davis Press).
Chapter 11 covers printer setup.
I used the admintool printer thing to select a remote printer
with BSD spooling and make it the default. That sets up most of
the junk. Or you can do the following to set up an HP laserjet
4M+ named treekiller on lw1 (most from memory, so salt well)...
lpsystem -t bsd treekiller
This adds a line to /etc/lp/systems. Note that "treekiller" and
"treekiller.your.domain" aren't the same, so use the proper
notation for your environment.
lpadmin -p lw1 -s treekiller
Binds lw1 to "treekiller"
lpadmin -p lw1 -T PS
sets the printer type to "postscript",
lpadmin -p lw1 -I postscript
says the printer only accepts postscript data (don't ask...).
cd /etc/lp/fd
sh
for f in download dpost postio postior postprint postreverse
do
lpfilter -f $f -F $f.fd
done
This sets up filters so ascii files sent to the printer get a
postscript wrapper put on them.
accept lw1
enables queuing
enable lw1
enables sending data to the printer
lpadmin -p lw1 -D "HP LaserJet 4M+"
sets the printer description.
If (and only if) this is to be the default printer, then do
lpadmin -d lw1
Lastly, check things with
lpstat -p lw1 -l
and get some output. Mine says..
printer lw1 faulted. enabled since .... available.
------------^^^^^^^
** THIS IS NORMAL FOR JETDIRECT PRINTERS. Its in power save status.
JetDirect lpd: no entries
Content types: postscript
Printer types: PS
Description: HP LaserJet 4M+
Users allowed:
(all)
Forms allowed:
(none)
Banner not required
Character sets:
Default pitch:
Default page size: 80 wide 66 long
Then do
lpstat -t
and check the output of that against what you think you set up.
You can
lp file
if you made lw1 the default or
lp -p lw1 file
if you didn't make it the default but still want to print to it.
Good luck,
Ric (<ric@rtd.com> "Ric Anderson", using RTD's public internet access)
-------------------------------------------
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:51 CDT