marco@buengc.BU.EDU (Marco Zelada) (06/21/89)
Problem statement: I want to make a GPX station running Ultrix 3.0 use a PS printer that has been configured off of a decserver. Configuration steps done so far: a) I have created the PRINTCAP entry for the new printer in which I tell lpd the LAT device and LAT port on which the PS printer is connected. b) I created all needed directories under /usr/spool for the new printer queue area, accounting info, etc. c) Now I need to make a node under /dev for the new printer, however, I can not figure out how to create the node and give ultrix enough information about the LAT device and port number when I create the node. I have tried MAKEDEV and mknode, but I always get an errors from them. Besides, I do not understand where to include the LAT device address and port number if I am using these commands. Question: What am I doing wrong ? Thank you in advance. -- ___________________________________________________________________________ | Name: Marco Zelada | Tel: 617 353 9882, Fax: 353 6322 | | Group: VLSI CAD Research Laboratory | E-mail: marco@buengc.bu.edu | | Dept: Electrical & Computer Eng. | US-Mail: 44 Cummington St. | | Org: Boston University | Boston MA, 02215 | ---------------------------------------------------------------------------
thomas@mipsbx.nac.dec.com (Matt Thomas) (06/21/89)
> I want to make a GPX station running Ultrix 3.0 use a PS printer that > has been configured off of a decserver. > c) Now I need to make a node under /dev for the new printer, > however, I can not figure out how to create the node and give > ultrix enough information about the LAT device and port number > when I create the node. I have tried MAKEDEV and mknode, but I > always get an errors from them. Besides, I do not understand > where to include the LAT device address and port number if I am > using these commands. Has your kernel been build with lat support? Your config file should have the following lines in it: OPTIONS LAT psuedo-device lat psuedo-device lta To get MAKEDEV to make the lat ttys, do a 'MAKEDEV lta0'. lpd will set the DECserver's name and port from the ts and op entries in the printcap file. You don't have to do anything to the tty expect lcp -h /dev/ttyXX. -- Matt Thomas Internet: thomas@decwrl.dec.com DECnet-Ultrix Development UUCP: ...!decwrl!thomas Digital Equipment Corporation Disclaimer: This message reflects my own Littleton, MA warped views, etc.
alan@shodha.dec.com ( Alan's Home for Wayward Notes File.) (06/21/89)
In article <3264@buengc.BU.EDU>, marco@buengc.BU.EDU (Marco Zelada) writes: > Problem statement: > > I want to make a GPX station running Ultrix 3.0 use a PS printer that > has been configured off of a decserver. > > a) I have created the PRINTCAP entry for the new printer in which > I tell lpd the LAT device and LAT port on which the PS printer > is connected. In Ultrix V3.0 there are two ways of associating a terminal server port with a special device. One limits it's use to lpd and the other makes the port available for general access. They are: 1. :ts=terminal-server: and :op=port-name: This tells lpd how to connect to the port. 2. The -h option on lcp(8) will let associate a lat port with a special device file. For example: lcp -h /dev/tty00:TS1:TS1_1 This lets anything that can open /dev/tty00 write to and read from the terminal server port. > > c) Now I need to make a node under /dev for the new printer, > however, I can not figure out how to create the node and give > ultrix enough information about the LAT device and port number > when I create the node. I have tried MAKEDEV and mknode, but I > always get an errors from them. Besides, I do not understand > where to include the LAT device address and port number if I am > using these commands. The device name for LAT ttys is lta#. So for the first set of 16 LAT ports you'd use MAKEDEV lta0. If you included LAT support during the installation of V3.0 it should have created one set for you. Unless you have other comm devices on the system they will ordinarly start at tty00. You can use file(1) to determine what device a special is associated with. > > Question: > > What am I doing wrong ? In c) you mentioned getting errors from the MAKEDEV. What were the errors?