Howard, >I agree absolutely. > >One of my biggest problems is configuring /etc/printcap remotely. As a >config file /etc/printcap is a bloody disaster. So, use printtool I hear >you say; but I don't run X over the Internet for security and performance >reasons. > I also ran into this problem in my younger (!) days as a simple RedHat newbie, trying to configure a ethernet interface remotely over a ppp link. I didn't know (at the time) how to set up an interface using just vi and cp. :-) >When is someone going to come up with a simple ncurses equivalent of >printtool? > Printtool uses ghostscript to do the dirty work of printing. Apsfilter (with LPRng as an optional extra :-) comes very, very close with it's excellent "apsfilterconfig" script. I even used it to hand-hack my printcap to have both color and black-and-white printers in there. (Just so my sisters don't go mad printing *&(*^(&^&*&^ Dawson's Creek pictures and other such crap) And the other bonus is that you can run apsfilter remotely, and scare the people on site by printing 5 test pages with "Kill them all. Now." (ala X-Files) and then denying any knowledge when they call you. *BOFH Cackle* > -- > Howard. > ____________________________________________________ > LANNet Computing Associates <http://lannetlinux.com> > "...well, it worked before _you_ touched it!" -- Steve "Would you really trust a language without pointers, but still manages to have a null pointer exception?" -- SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/ More Info: http://slug.org.au/lists/listinfo/slug
