Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #821
Difficulty: Easy
HTML5 is a software solution stack that defines the properties and behaviors of web page content by implementing a markup based pattern to it.
True or False?
Linux & Unix Commands - Search Man Pages

lp(4) [bsd man page]

LP(4)							     Kernel Interfaces Manual							     LP(4)

lp - line printer SYNOPSIS
/sys/conf/SYSTEM: NLP lp_printers # Line Printer LP_MAXCOL 132 # Maximum number of columns on line printers /etc/dtab: #Name Unit# Addr Vector Br Handler(s) # Comments lp ? 177514 200 4 lpintr # lp-11 line printer major device number(s): raw: 5 minor device encoding: bit 01 specifies 64-character set (instead of 96-character set) bits 06 are reserved bits 0370 specify line printer unit: <lp_unit> * 8 DESCRIPTION
Lp provides the interface to any of the standard DEC line printers on an LP-11 parallel interface. When it is opened or closed, a suitable number of page ejects is generated. Bytes written are printed. The unit number of the printer is specified by the minor device after removing the low 3 bits, which act as per-device parameters. Cur- rently only the lowest of the low three bits is interpreted: if it is set, the device is treated as having a 64-character set, rather than a full 96-character set. In the resulting half-ASCII mode, lower case letters are turned into upper case and certain characters are escaped according to the following table: { ( } ) ` ' | ! ~ ^ The driver correctly interprets carriage returns, backspaces, tabs, and form feeds. Lines longer than the maximum page width are trun- cated. The page width is specified via the LP_MAXCOL definition, set to 132 in the GENERIC distribution. FILES
/dev/lp /dev/MAKEDEV script to create special files /dev/MAKEDEV.local script to localize special files SEE ALSO
lpr(1), dtab(5), autoconfig(8) DIAGNOSTICS
None. BUGS
Although the driver supports multiple printers this has never been tried. 3rd Berkeley Distribution January 28, 1988 LP(4)

Check Out this Related Man Page

TM(4)							     Kernel Interfaces Manual							     TM(4)

tm - TM-11/TE-10 magtape interface SYNOPSIS
/sys/conf/SYSTEM: # Setting AVIVTM configures the TM driver for the AVIV 800/1600/6250 # controller. For more details, see /sys/pdpuba/tm.c. NTM tm_drives # TM11 AVIVTM YES # AVIV 800/1600/6250 controller /etc/dtab: #Name Unit# Addr Vector Br Handler(s) # Comments tm ? 172520 224 5 tmintr # tm11 driver major device number(s): raw: 7 block: 1 minor device encoding: bits 0003 specify TS drive bit 0004 specifies no-rewind operation bits 0030 specify recording density: 0000: 800BPI 0010: 1600BPI (AVIVTM and some other controllers) 0020: 6250BPI (AVIVTM only) DESCRIPTION
The tm-11/te-10 combination provides a standard tape drive interface as described in mtio(4). The standard DEC tm-11 operates only at 800 bpi. Other controllers of this type may also allow operation at 1600 bpi, under software control or by switching manually. FILES
/dev/MAKEDEV script to create special files /dev/MAKEDEV.local script to localize special files SEE ALSO
mt(1), tar(1), tp(1), mtio(4), ht(4), ts(4), mt(4), dtab(5), autoconfig(8) DIAGNOSTICS
te%d: no write ring. An attempt was made to write on the tape drive when no write ring was present; this message is written on the termi- nal of the user who tried to access the tape. te%d: not online. An attempt was made to access the tape while it was offline; this message is written on the terminal of the user who tried to access the tape. te%d: can't change density in mid-tape. An attempt was made to write on a tape at a different density than is already recorded on the tape. This message is written on the terminal of the user who tried to switch the density. te%d: hard error bn%d er=%b. A tape error occurred at block bn; the tm error register is printed in octal with the bits symbolically decoded. Any error is fatal on non-raw tape; when possible the driver will have retried the operation which failed several times before reporting the error. te%d: lost interrupt. A tape operation did not complete within a reasonable time, most likely because the tape was taken off-line during rewind or lost vacuum. The controller should, but does not, give an interrupt in these cases. The device will be made available again after this message, but any current open reference to the device will return an error as the operation in progress aborts. BUGS
If any non-data error is encountered on non-raw tape, it refuses to do anything more until closed. 3rd Berkeley Distribution January 28, 1988 TM(4)

Featured Tech Videos