Sponsored Content
Full Discussion: Modem problems on SCO Xenix
Top Forums UNIX for Dummies Questions & Answers Modem problems on SCO Xenix Post 31297 by jbartok on Tuesday 5th of November 2002 03:02:11 PM
Old 11-05-2002
Modem problems on SCO Xenix

Randomly receive the following message:
"Can not open line tty1a device busy error 16"
and
"/etc/getty/t60 tty1a"
What is causing this error message ?
 

10 More Discussions You Might Find Interesting

1. IP Networking

Modem Problems

*breathe in* *breathe out* Okay, I managed to get Linux installed on my 2nd harddrive with my primary running windows.. but I'm having alittle problem getting linux to 'like' my modem.. (a 3com)... it just won't let me use it. I configure my internet connection how it should (give me some credit... (9 Replies)
Discussion started by: cHiCkEn
9 Replies

2. UNIX for Dummies Questions & Answers

How to install modem in SCO OPEN SERVER VER 5.05

Hello Friends. I would like to know couple of questions. 1. How to install internal modem in unix operating system. I have a toshiba laptop with toshiba v.90 internal modem . 2. Where is hyper Terminal in Unix. 3. Where i can get the support for windows like we used to have vipex. (2 Replies)
Discussion started by: skywatcher
2 Replies

3. UNIX for Advanced & Expert Users

modem for sco opensever

i have to configur the modem for sco opensever .tell me correct details about that. (1 Reply)
Discussion started by: ashoka
1 Replies

4. Linux

Problems with the Internal modem

Hi I have a hsf Conexant modem & I have a driver for it but it works only on 2.4.* kernels . I know that there is a site called Linuxant.com which offers kernels for download ,but it gives a speed near 14 kb/s and the full feature driver offered for money and I can't buy it. My questions... (3 Replies)
Discussion started by: engshaheen
3 Replies

5. UNIX for Advanced & Expert Users

adding additional drive to sco the is xenix

I am taking an old xenix drive and installing it in a recent SCO Build Server. I have gone through the process of running mkdev hd twice since the drive is a SCSI then proceed to run mkdev fs and when I attempt to add one of the shown partitions I get the following: fsck: cannot determine... (1 Reply)
Discussion started by: justenglabs
1 Replies

6. SCO

Xenix Problems - No space on dev 1/40

Hello - I'm a newbie to these forums. Please excuse me if I am posting in the wrong area. My dilemma. The HD on our ancient Xenix system apparently is full. I receive the "no space on dev 1/40" prompt. This occurred after I attempted to purge some unwanted files. This system runs our small... (1 Reply)
Discussion started by: gmbrickley
1 Replies

7. UNIX for Dummies Questions & Answers

Help with a ext. modem on SCO 5.0.5

I am fully capable of reading a book to get the answers or looking to the web, but no one has the answer to this one. I had a Zoom 56K V34 Plus external modem (2836A) attached to my Unix box for about ten years without a flaw. This weekend I couldn't access the box remotely through the modem and... (0 Replies)
Discussion started by: scivic
0 Replies

8. SCO

network problems with sco

SCO unix 5.0.5 - Suddently network lost & has to be reboot. I try to stop TCP & start TCP. but no connection. Any idea about that. thanks (8 Replies)
Discussion started by: ajantha
8 Replies

9. SCO

SCO Xenix AR command ?

Hi I am looking for sco xenix ar command under sco unix. please help me ! (4 Replies)
Discussion started by: javad1_maroofi
4 Replies

10. SCO

load sco xenix and sco unix binary ?

Hi I have some sco xenix object, bin and archive files that operate in sco unix 5.0.7. I know that sco unix kernel can support sco xenix binary. I want to know how can I link xenix and unix archives together? (0 Replies)
Discussion started by: javad1_maroofi
0 Replies
lat_manual_setup(7)					 Miscellaneous Information Manual				       lat_manual_setup(7)

NAME
lat_manual_setup - Describes how to manually set up the Local Area Transport (LAT) DESCRIPTION
To run LAT on your system, you must configure LAT in your system's kernel (see the Network Administration manual). Optionally, you can customize your LAT setup. The customization section of the Network Administration manual includes information on gen- eral customization, setting up printers, host-initiated connections, the LAT/Telnet gateway, and creating your own service. For more information on customizing LAT, see the Network Administration manual. Setting Up LAT To set up LAT on your system manually, you must first configure your kernel for LAT (see the Network Administration manual). Then log in as superuser and perform the following steps: Create the LAT device special files. LAT supports SVR4-style and BSD-style devices. You should use SVR4-style devices. See the Network Administration manual for more information. You should use the latsetup utility to create SVR4-style devices to ensure that duplicate minor numbers are not used. You can use the mknod command to create character devices with a major number of 5. If you create SVR4 devices manually, you should observe the following rules: Start the SVR4 device numbers at /dev/lat/620. This avoids overlapping minor numbers from the BSD tty name space. Make the minor number of the SVR4 device the same as the name. For example, device /dev/lat/833 should have minor num- ber 833. The following command would create the SVR4-style LAT device /dev/lat/833: # /usr/sbin/mknod /dev/lat/833 c 5 833 Once you have created the SVR4-style device, check the permissions of the device to make sure they are what you desire. You can create BSD-style devices by running the /dev/MAKEDEV script with the LAT option. The syntax for the MAKEDEV command with the LAT option is as follows: MAKEDEV latN The N variable can be 0 to 38. The /dev/MAKEDEV script creates one BSD-style LAT device special file for each LAT terminal device. When you run the MAKEDEV script, it creates 16 BSD-style LAT device special files, and creates the LAT control device (/dev/streams/lat), if it has not already been created. The MAKEDEV script requires 16 contiguous LAT device special files to be available. (Specifying lat38 requires only 12 contiguous LAT device special files to be available.) For example, the following commands create a total of 32 BSD-style LAT device special files: # cd /dev # MAKEDEV lat0 # MAKEDEV lat1 Record the device special file information displayed by the MAKEDEV script. The special file names vary depending on the number of terminal devices already configured. The following is sample output from the MAKEDEV command: MAKEDEV: special file(s) for lat1: tty16 tty17 tty18 tty19 tty1a tty1b tty1c tty1d tty1e tty1f tty1g tty1h tty1i tty1j tty1k tty1l Edit the /etc/inittab file to include entries for the LAT device special files you created. For example: lat620:34:respawn:/usr/sbin/getty /dev/lat/620 console vt100 lat621:34:respawn:/usr/sbin/getty lat/621 console vt100 lat630:34:respawn:/usr/sbin/lattelnet lat/630 lattelnet The second field (34) specifies the run levels at which the LAT devices are spawned; in this example, the getty process is spawned at either run level 3 or 4. The first entry uses an absolute pathname for the device (/dev/lat/620). The second uses a relative pathname (lat/621). The previous example shows how to add entries to the /etc/inittab file for SVR4 LAT devices. The following example shows entries for BSD LAT devices: lat16:34:respawn:/usr/sbin/getty tty16 console vt100 lat17:34:respawn:/usr/sbin/getty tty17 console vt100 lat18:34:respawn:/usr/sbin/lattelnet tty18 lattelnet18 For more information, see the inittab(4) and getty(8) reference pages. The Network Administration manual provides additional information on SVR4 and BSD devices. Use the following command to spawn the pro- cesses for the LAT device special files that you added to the /etc/inittab file: # /sbin/init q Create the STREAMS special file required by LAT by issuing the following command: # /usr/sbin/strsetup -i Enable LAT automatic startup and shutdown by using the following command: # /usr/sbin/rcmgr set LAT_SETUP 1 When LAT automatic startup and shutdown is enabled, the /sbin/init.d/lat file automatically starts LAT upon reaching run level 3 and automatically stops LAT when exiting run level 3. Start LAT by issuing the following command: # /usr/sbin/latcp -s RELATED INFORMATION
Commands: llogin(1), netstat(1), getty(8), init(8), latcp(8), latsetup(8), MAKEDEV(8), mknod(8), rcmgr(8), strsetup(8). Files: inittab(4). Introduction: lat_intro(7). Network Administration , System Administration delim off lat_manual_setup(7)
All times are GMT -4. The time now is 06:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy