George, I print to remote printers all the time! This is what you do: YaST -> System administration -> Network configuration -> Administrate remote printers and then set it up from there. Alternatively, you may just add the necessary lines to /etc/printcap manually. The ones for one of my machine are: next|remote printer on next.ensu.ucalgary.ca:\ :sd=/var/spool/lpd/next:\ :rm=next.ensu.ucalgary.ca:\ :rp=Local_Printer:\ :bk:sh:mx#0: The printer is connected to a NeXTStation, with the hostname next.ensu.ucalgary.ca . On that machine, the printer is called Local_Printer . If you want to know more about what the other "names" like sd, bk, etc. means, check 'man printcap'. Believe me, it doesn't cause any brain damage, if you want to edit /etc/printcap manually! But figuring out how to make the NeXTStep a print server, may lead one to the physchiatrist's office. :-) The lines above should work for any type of printer. You don't have to know what type of printer that is. At least, I don't think so and in my experience, I have never had to know the type of printer on the remote machine at all. If the remote printer is a non-PostScript laser printer, like the HP LaserJet 5L, for example, the remote machine will run the print job through the print filter before sending it to the printer. Essentially, what happens is that the local machine passes the print job to the remote machine which will run it through the print filter. Regards, Kenneth Tan ------------------------------------------------------------------------------ C. J. Kenneth Tan E-mail: cjtan@acm.org Telephone: 1-403-220-8038 cjtan@ieee.org 1-403-606-4257 URL: <A HREF="http://www.cuug.ab.ca/~tanc"><A HREF="http://www.cuug.ab.ca/~tanc</A">http://www.cuug.ab.ca/~tanc</A</A>> Facsimile: 1-403-284-1980 "An engineer made programmer is one who attempts to solve a problem, A programmer made engineer is one who knows how to solve a problem." ------------------------------------------------------------------------------ On Thu, 23 Jul 1998, George Sexton wrote:
I agree with Paul. DHCP support for the client side is a must.
One other thing that I found annoying is their is no way to add a remote printer under YAST. RedHat does this very easily. I know that if I were a true Linux junkie I would figure out how to edit the files but frankly I don't need the brain damage. Right now I print to a postscript file and FTP it into my print server (Intel NetPort).
George Sexton MH Software, Inc. Voice: 303 438 9585 Fax: 303 469 9679 URL: <A HREF="http://www.mhsoftware.com"><A HREF="http://www.mhsoftware.com</A">http://www.mhsoftware.com</A</A>>
-----Original Message----- From: owner-suse-linux-e@suse.com [<A HREF="mailto:owner-suse-linux-e@suse.com]On">mailto:owner-suse-linux-e@suse.com]On</A> Behalf Of Paul Hostetler Sent: Thursday, July 23, 1998 2:19 PM To: suse-linux-e@suse.com Subject: Re: [S.u.S.E. Linux] DHCP client in 5.3 (was Re: 5.3 (looks incredible))
I hope this is fixed in 5.3. SuSE's lack of DHCP client support is a show stopper.
Paul Hostetler
Arun K. Khan wrote:
I see that there is a DHCP package in 5.3. Does this include both the
client and server?
Thx, Arun Khan - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
DHCP - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e