d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
51e25af386
freebsd-dev/etc/printcap

55 lines
2.0 KiB
Plaintext
Raw Normal View History

Initial import of 386BSD 0.1 othersrc/etc
1993-06-20 13:41:45 +00:00
# @(#)printcap 5.3 (Berkeley) 6/30/90
$Id$ -> $FreeBSD$
1999-08-27 23:37:10 +00:00
# $FreeBSD$
Initial import of 386BSD 0.1 othersrc/etc
1993-06-20 13:41:45 +00:00
Uncomment the "raw" lp entry in /etc/printcap. We start lpd by default, so there's no use in running it without any printer definition in printcap. Also added a bunch of hints about the printer setup, to guide the admin about the printer setup (handbook, "apsfilter"), and a commented-out sample setup for a remote printer. In the same line, add /var/spool/lpd/output to BSD.var.dist since it is referred to by the "lp" entry in printcap.
1996-10-13 16:52:40 +00:00
#
# This enables a simple local "raw" printer, hooked up to the first
fixes: a) the configured default printer entry might turn out to become a security hole Although lpd isn't enabled by default in FreeBSD 4 and later versions bad things might happen because of a simple copy and paste failure: - fill up root-fs, if /dev/lpt0 doesn't exist - fill up the spool dir (either root-fs or var-fs) if machine hadn't been designed as print server Therefore best decision: if people want printing, then configure both 1. /etc/rc.conf 2. /etc/printcap the default entry wouldn't have served well all tastes and needs anyway... design of most of our config files is, to have commented out suggestions if a service is not active. b) [Garance] fix old and wrong documentation: input filters are possible even if you print to a remote printer this makes FreeBSDs implementation of lpd currently the best without having to switch to port monster LPRng ... c) fix pointer to wrong handbook section for a longer time .. so I doesn't fix the number I'm only referring to the printing section, otherwise this would have to be fixed several times, if the chapters should be reordered again ... d) typo: chose -> choose Submitted by: me and some suggestions by Garance Approved by: Eivind and Garance A Drosihn <drosih@rpi.edu> in private e-mail
2000-11-01 13:30:24 +00:00
# parallel port. No kind of filtering is done, so everything you pass
# to the "lpr" command will be printed unmodified.
Uncomment the "raw" lp entry in /etc/printcap. We start lpd by default, so there's no use in running it without any printer definition in printcap. Also added a bunch of hints about the printer setup, to guide the admin about the printer setup (handbook, "apsfilter"), and a commented-out sample setup for a remote printer. In the same line, add /var/spool/lpd/output to BSD.var.dist since it is referred to by the "lp" entry in printcap.
1996-10-13 16:52:40 +00:00
#
fixes: a) the configured default printer entry might turn out to become a security hole Although lpd isn't enabled by default in FreeBSD 4 and later versions bad things might happen because of a simple copy and paste failure: - fill up root-fs, if /dev/lpt0 doesn't exist - fill up the spool dir (either root-fs or var-fs) if machine hadn't been designed as print server Therefore best decision: if people want printing, then configure both 1. /etc/rc.conf 2. /etc/printcap the default entry wouldn't have served well all tastes and needs anyway... design of most of our config files is, to have commented out suggestions if a service is not active. b) [Garance] fix old and wrong documentation: input filters are possible even if you print to a remote printer this makes FreeBSDs implementation of lpd currently the best without having to switch to port monster LPRng ... c) fix pointer to wrong handbook section for a longer time .. so I doesn't fix the number I'm only referring to the printing section, otherwise this would have to be fixed several times, if the chapters should be reordered again ... d) typo: chose -> choose Submitted by: me and some suggestions by Garance Approved by: Eivind and Garance A Drosihn <drosih@rpi.edu> in private e-mail
2000-11-01 13:30:24 +00:00
# Remember, for further print queues you're going to add, you have
# to choose different spool directories (the "sd" capability below),
Uncomment the "raw" lp entry in /etc/printcap. We start lpd by default, so there's no use in running it without any printer definition in printcap. Also added a bunch of hints about the printer setup, to guide the admin about the printer setup (handbook, "apsfilter"), and a commented-out sample setup for a remote printer. In the same line, add /var/spool/lpd/output to BSD.var.dist since it is referred to by the "lp" entry in printcap.
1996-10-13 16:52:40 +00:00
# otherwise you will greatly confuse lpd.
#
# For some advanced printing, have a look at the "apsfilter" package.
# It plugs into the lpd system, allowing you to print a variety of
# different file types by converting everything to PostScript(tm)
fixes: a) the configured default printer entry might turn out to become a security hole Although lpd isn't enabled by default in FreeBSD 4 and later versions bad things might happen because of a simple copy and paste failure: - fill up root-fs, if /dev/lpt0 doesn't exist - fill up the spool dir (either root-fs or var-fs) if machine hadn't been designed as print server Therefore best decision: if people want printing, then configure both 1. /etc/rc.conf 2. /etc/printcap the default entry wouldn't have served well all tastes and needs anyway... design of most of our config files is, to have commented out suggestions if a service is not active. b) [Garance] fix old and wrong documentation: input filters are possible even if you print to a remote printer this makes FreeBSDs implementation of lpd currently the best without having to switch to port monster LPRng ... c) fix pointer to wrong handbook section for a longer time .. so I doesn't fix the number I'm only referring to the printing section, otherwise this would have to be fixed several times, if the chapters should be reordered again ... d) typo: chose -> choose Submitted by: me and some suggestions by Garance Approved by: Eivind and Garance A Drosihn <drosih@rpi.edu> in private e-mail
2000-11-01 13:30:24 +00:00
# format. For more information about apsfilter visit
Uncomment the "raw" lp entry in /etc/printcap. We start lpd by default, so there's no use in running it without any printer definition in printcap. Also added a bunch of hints about the printer setup, to guide the admin about the printer setup (handbook, "apsfilter"), and a commented-out sample setup for a remote printer. In the same line, add /var/spool/lpd/output to BSD.var.dist since it is referred to by the "lp" entry in printcap.
1996-10-13 16:52:40 +00:00
#
fixes: a) the configured default printer entry might turn out to become a security hole Although lpd isn't enabled by default in FreeBSD 4 and later versions bad things might happen because of a simple copy and paste failure: - fill up root-fs, if /dev/lpt0 doesn't exist - fill up the spool dir (either root-fs or var-fs) if machine hadn't been designed as print server Therefore best decision: if people want printing, then configure both 1. /etc/rc.conf 2. /etc/printcap the default entry wouldn't have served well all tastes and needs anyway... design of most of our config files is, to have commented out suggestions if a service is not active. b) [Garance] fix old and wrong documentation: input filters are possible even if you print to a remote printer this makes FreeBSDs implementation of lpd currently the best without having to switch to port monster LPRng ... c) fix pointer to wrong handbook section for a longer time .. so I doesn't fix the number I'm only referring to the printing section, otherwise this would have to be fixed several times, if the chapters should be reordered again ... d) typo: chose -> choose Submitted by: me and some suggestions by Garance Approved by: Eivind and Garance A Drosihn <drosih@rpi.edu> in private e-mail
2000-11-01 13:30:24 +00:00
# http://www.apsfilter.org/
Uncomment the "raw" lp entry in /etc/printcap. We start lpd by default, so there's no use in running it without any printer definition in printcap. Also added a bunch of hints about the printer setup, to guide the admin about the printer setup (handbook, "apsfilter"), and a commented-out sample setup for a remote printer. In the same line, add /var/spool/lpd/output to BSD.var.dist since it is referred to by the "lp" entry in printcap.
1996-10-13 16:52:40 +00:00
#
fixes: a) the configured default printer entry might turn out to become a security hole Although lpd isn't enabled by default in FreeBSD 4 and later versions bad things might happen because of a simple copy and paste failure: - fill up root-fs, if /dev/lpt0 doesn't exist - fill up the spool dir (either root-fs or var-fs) if machine hadn't been designed as print server Therefore best decision: if people want printing, then configure both 1. /etc/rc.conf 2. /etc/printcap the default entry wouldn't have served well all tastes and needs anyway... design of most of our config files is, to have commented out suggestions if a service is not active. b) [Garance] fix old and wrong documentation: input filters are possible even if you print to a remote printer this makes FreeBSDs implementation of lpd currently the best without having to switch to port monster LPRng ... c) fix pointer to wrong handbook section for a longer time .. so I doesn't fix the number I'm only referring to the printing section, otherwise this would have to be fixed several times, if the chapters should be reordered again ... d) typo: chose -> choose Submitted by: me and some suggestions by Garance Approved by: Eivind and Garance A Drosihn <drosih@rpi.edu> in private e-mail
2000-11-01 13:30:24 +00:00
# If you don't have a PostScript(tm) printer, don't panic, but do
# also install the latest "ghostscript" package for best printer support.
Suppress banner pages by default and add a note describing how to turn them back on. PR: 5226
1998-01-04 17:59:24 +00:00
#
fixes: a) the configured default printer entry might turn out to become a security hole Although lpd isn't enabled by default in FreeBSD 4 and later versions bad things might happen because of a simple copy and paste failure: - fill up root-fs, if /dev/lpt0 doesn't exist - fill up the spool dir (either root-fs or var-fs) if machine hadn't been designed as print server Therefore best decision: if people want printing, then configure both 1. /etc/rc.conf 2. /etc/printcap the default entry wouldn't have served well all tastes and needs anyway... design of most of our config files is, to have commented out suggestions if a service is not active. b) [Garance] fix old and wrong documentation: input filters are possible even if you print to a remote printer this makes FreeBSDs implementation of lpd currently the best without having to switch to port monster LPRng ... c) fix pointer to wrong handbook section for a longer time .. so I doesn't fix the number I'm only referring to the printing section, otherwise this would have to be fixed several times, if the chapters should be reordered again ... d) typo: chose -> choose Submitted by: me and some suggestions by Garance Approved by: Eivind and Garance A Drosihn <drosih@rpi.edu> in private e-mail
2000-11-01 13:30:24 +00:00
# Do also refer to the "printing" section of the handbook.
#
Update the handbook printing section URL so that it points to the correct location.
2003-03-25 18:03:11 +00:00
# http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/printing.html
fixes: a) the configured default printer entry might turn out to become a security hole Although lpd isn't enabled by default in FreeBSD 4 and later versions bad things might happen because of a simple copy and paste failure: - fill up root-fs, if /dev/lpt0 doesn't exist - fill up the spool dir (either root-fs or var-fs) if machine hadn't been designed as print server Therefore best decision: if people want printing, then configure both 1. /etc/rc.conf 2. /etc/printcap the default entry wouldn't have served well all tastes and needs anyway... design of most of our config files is, to have commented out suggestions if a service is not active. b) [Garance] fix old and wrong documentation: input filters are possible even if you print to a remote printer this makes FreeBSDs implementation of lpd currently the best without having to switch to port monster LPRng ... c) fix pointer to wrong handbook section for a longer time .. so I doesn't fix the number I'm only referring to the printing section, otherwise this would have to be fixed several times, if the chapters should be reordered again ... d) typo: chose -> choose Submitted by: me and some suggestions by Garance Approved by: Eivind and Garance A Drosihn <drosih@rpi.edu> in private e-mail
2000-11-01 13:30:24 +00:00
#
# A local copy can be found under
#
# /usr/share/doc/handbook/handbook.{html,latin1}.
#
# Banner pages are now suppressed by default. Remove the :sh: capability
# to turn them back on.
#
#lp|local line printer:\
# :sh:\
# :lp=/dev/lpt0:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs:
Uncomment the "raw" lp entry in /etc/printcap. We start lpd by default, so there's no use in running it without any printer definition in printcap. Also added a bunch of hints about the printer setup, to guide the admin about the printer setup (handbook, "apsfilter"), and a commented-out sample setup for a remote printer. In the same line, add /var/spool/lpd/output to BSD.var.dist since it is referred to by the "lp" entry in printcap.
1996-10-13 16:52:40 +00:00
#
# Sample remote printer. The physical printer is on machine "lphost".
fixes: a) the configured default printer entry might turn out to become a security hole Although lpd isn't enabled by default in FreeBSD 4 and later versions bad things might happen because of a simple copy and paste failure: - fill up root-fs, if /dev/lpt0 doesn't exist - fill up the spool dir (either root-fs or var-fs) if machine hadn't been designed as print server Therefore best decision: if people want printing, then configure both 1. /etc/rc.conf 2. /etc/printcap the default entry wouldn't have served well all tastes and needs anyway... design of most of our config files is, to have commented out suggestions if a service is not active. b) [Garance] fix old and wrong documentation: input filters are possible even if you print to a remote printer this makes FreeBSDs implementation of lpd currently the best without having to switch to port monster LPRng ... c) fix pointer to wrong handbook section for a longer time .. so I doesn't fix the number I'm only referring to the printing section, otherwise this would have to be fixed several times, if the chapters should be reordered again ... d) typo: chose -> choose Submitted by: me and some suggestions by Garance Approved by: Eivind and Garance A Drosihn <drosih@rpi.edu> in private e-mail
2000-11-01 13:30:24 +00:00
# You can perform any kind of local filtering directly. If you need
# local filters (e.g. LF -> CR-LF conversion for HP printers), create
# a filter script that sends the proper escape sequence to the printer
# and then concatenates stdin to stdout.
Uncomment the "raw" lp entry in /etc/printcap. We start lpd by default, so there's no use in running it without any printer definition in printcap. Also added a bunch of hints about the printer setup, to guide the admin about the printer setup (handbook, "apsfilter"), and a commented-out sample setup for a remote printer. In the same line, add /var/spool/lpd/output to BSD.var.dist since it is referred to by the "lp" entry in printcap.
1996-10-13 16:52:40 +00:00
#
#remote|sample remote printer:\
Suppress banner pages by default and add a note describing how to turn them back on. PR: 5226
1998-01-04 17:59:24 +00:00
# :sh:\
fixes: a) the configured default printer entry might turn out to become a security hole Although lpd isn't enabled by default in FreeBSD 4 and later versions bad things might happen because of a simple copy and paste failure: - fill up root-fs, if /dev/lpt0 doesn't exist - fill up the spool dir (either root-fs or var-fs) if machine hadn't been designed as print server Therefore best decision: if people want printing, then configure both 1. /etc/rc.conf 2. /etc/printcap the default entry wouldn't have served well all tastes and needs anyway... design of most of our config files is, to have commented out suggestions if a service is not active. b) [Garance] fix old and wrong documentation: input filters are possible even if you print to a remote printer this makes FreeBSDs implementation of lpd currently the best without having to switch to port monster LPRng ... c) fix pointer to wrong handbook section for a longer time .. so I doesn't fix the number I'm only referring to the printing section, otherwise this would have to be fixed several times, if the chapters should be reordered again ... d) typo: chose -> choose Submitted by: me and some suggestions by Garance Approved by: Eivind and Garance A Drosihn <drosih@rpi.edu> in private e-mail
2000-11-01 13:30:24 +00:00
# :rm=lphost:sd=/var/spool/output/lphost:lf=/var/log/lpd-errs:\
# :if=/usr/local/libexec/if-script:
Add commented out example of Russian output filter usage
1998-02-04 12:09:06 +00:00
#
# Simple Russian printer with hardware CP866 character set, output filter
# used for KOI8-R -> CP866 conversion
#
#lp|Russian local line printer:\
# :sh:of=/usr/libexec/lpr/ru/koi2alt:\
# :lp=/dev/lpt0:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs:
Reference in New Issue Copy Permalink