CEMENTERIO GENERAL DE GUAYAQUIL

This is the lpd FAQ version 1.2, this section is maintained by Brian McCauley.

Please send any suggestion [email protected].

114 16 EVERYTHING FOR PRINTING

16.1 General Information

16.1.1 What

the lpr/lpd package?

lpris a utility that is used to print les out to local and remote printers. As with

all networking, there are conguration les which have to be tailored to your needs. These les are concerned with access control, accounting and page setup of your printer(s). Now all control of the printer is performed by a process called lpd

lpd is a laser printer daemon (yes I know an epson isn't a laser printer but

thats besides the point). The programlpdis normally started in/etc/rc.local

in either the forground or the background. What happens is that lpd will sink

back as a daemon, only ever being invoked when a printer request is generated. lpd

itself has some options which are of possible intrest to some people chiey that of the -lag which causes lpdto log requests recieved from the network (useful for

debugging). The other option is for what port lpdshould listen for data on and is

generally not used. Note:

lpreally stands for line printer but as technology has advanced laser printer makes

more sense.

16.1.2 What is

Linux lpr/lpd?

Up until 28th May 1993, as far as there is a denitive Linux version of anything

the Linux lpr/lpd is Ross Biro's ([email protected]) port of the BSD

sources dated 20th November 1992 (so if you're used to AT&T's you'll nd some

dierences). Ross's binaries and the dis are found at tsx-11.mit.eduin/pub/-

linux/binaries/usr.bin/lpr.tar.Zand onsunsite.unc.eduinpub/Linux/system/Daemons/lpr.tar.Z

The SLS lelpr.tgzon disk b2 contains the same stu.

However this is all about to change so from now on this version will be called

the oldbinaries. As of 28th May 1993 there appears be two dierent new releases

of lpd expected RSN.

In addition to the standard BSDlprcapabilities Ross Biro's port should have

had better support for serial printers (but it didn't work in the old binaries). Ross's port was not based on the latest BSD sources (by about 3 years, '88 vs '91). His new release will also be based on these sources which can be found are at:

gatekeeper.dec.comand /afs/ir.stanford.edu/src/...

Recent BSD sources are all over the place.

ftp.uu.net: /systems/unix/bsd-sources/usr.sbin/lpr src.doc.ic.ac.uk: /unix/bsd-sources/usr.sbin/lpr

to name but two. The BSD sources have unGNU things in their Makeles so they

don't compileout of the boxbut have now been ported [email protected]

Fred van Kempen and will be available RSN (if not now) as part of the complete overhall of the Linux Net stu.

Ross agrees that Fred's version should be thought of astheLinuxlpdpackage.

I ([email protected]) have not had a chance to look at Fred's port yet

(I'm waiting for the full release of 0.99pl10 before I update anything) but most of this FAQ refers to the BSDlpdpackage or Linux in general so this is probably not

too important.

There are some other versions oflpd stu about but I have to draw the line

somewhere. If anyone whants to maintain FAQ sections on these they are welcome to do so. The other versions include plp and the ka9q lp facility. There are also romours of SysV spoolers being ported.

16.2 Installing 115

16.1.3 What are all these diretrories for? (

,

,

,

,

)

This is one to which I can't nd a staight answer.

For various reasons including the diculties of fsck'ing / some people like to

put all things that aren't needed during bootstrap in/usrso that/is as small as

possible. Also some people like all their internet stu in/etc/inet. Most Linux

gurus advise keeping it all in/etc.

If you really want this quirky layout:

cd /etc

ls -s ../usr/etc/* . ls -s inet/* .

Make sure the les in /usr/etcand /etc/inet are not already symlinks into

/etc.

If you want to spread out your conguration les for the sake of tidiness then a better solution is to have a directory tree called/confand make the les in/etc

symlinks into this tree.

To avoid the problem of your/usrlesystem lling up as a result of stu in spool

queues some poeple perfer to keep their spool queues and such like in a separate

lesystem called/var. If you don't have a/varle system then you should make

/vara symlink to /usr. If you do have a /var lesystem to may want to make

/usr/spool a symlink to ../var/spool so that any programs expecting to nd /usr/spoolwill not be dissapointed.

16.2 Installing

16.2.1 How do I get

to work properly other than for root? Where