TCP in sco unix 3.2

10 More Discussions You Might Find Interesting

1. SCO

Sco Openserver Starting TCP/IP Services

Hi all, I have a customer whose sco unix server wasnt power off correctly and when booting it up I noticed that the boot up takes a while to finish the " Starting TCP services: snmpd routed lpd". after that the server is ready for login, but you cannot ping anything from the server (apart from...

2. SCO

SCO TCP/IP 1.2.0. floppys needed

Hi, every body, I have the same problem but with the SCO TCP/IP 1.2.0. I have the 3 floppy disks but I get an error on disk 3, unreadable. I have seen the closed post regarding the sco tcp/ip. Does anybody have those disks? Thank you in advance Mariano

3. SCO

SCO TCP/IP ?

Hello! I tried to install an old version of SCO for test purposes, (3.2v4.0y), all fine, but my TCP/IP disks are "unreadable" and I cant find them on the internetz. Also, SCO doesnt respond to my request....is there any source for those images available? I have license/activation key which...

4. 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?

5. SCO

/dev/inet/tcp not listening in SCO 6.

While in SCO Openserver 5.0.7, Sybase listened to /dev/inet/tcp, the same is not working in SCO Openserver 6. The Network card is however active and pinging fine. What can be the reason? What is the way out? An early response will be appreciated. Thank you Regards TCG

6. SCO

all tcp are CLOSED on SCO Unix on VMWARE

Hi folks, First of all, sorry about my english, isn't the best and thks for advance. Here es my problem... I have virtualize an SCO unix with VMware ESX 3 and everything was going on beatifull until that i try to connect from anorther host, i can't do it so i check the connection with...

7. UNIX for Dummies Questions & Answers

SCO UNIX "TCP/IP not licensed error"

I have been running 5.0.02 for more than 10 years in its present configuration. I am running a business software package on it (text based). I am trying to use my windows machines to access it through a program like "reflections" so that I can run my software from different systems but I get...

8. IP Networking

TCP/IP in c (unix)

I have written a client receive (TCP/IP) program which is up all the time. It connects to the server during Beginning of the day and stays alert and reads a message whenever one comes in. the problem is after receiving a message, the client_receive program is getting a message with zero bytes....

9. Filesystems, Disks and Memory

SCO TCP/IP runtime System for SCO Unix

Hi everyone i have a question for all of you. It may be basic or it may be a good one. I recently aquired a copy of "SCO TCP/IP runtime System for SCO Unix" (thats what the disks say) and for the life of me i can not get it to load. i have tried opening the disk in linux and it can not determine...

10. IP Networking

TCP/IP printing on SCO 2.1.3

I am trying to set up TCP/IP printing to so we can remove the old novel server. The printer details have been added to the etc/hosts file correctly, and the printer added as a remote UNIX printer . However when a print job is issued lpstat -o displays the job, but it dosent move. Any help yould...

LEARN ABOUT MOJAVE

mknod

MKNOD(8)						    BSD System Manager's Manual 						  MKNOD(8)

NAME

     mknod -- make device special file

SYNOPSIS

     mknod [-F format] name [c | b] major minor
     mknod [-F format] name [c | b] major unit subunit
     mknod name [c | b] number
     mknod name w

DESCRIPTION

     The mknod command creates device special files.

     To make nodes manually, the required arguments are:

     name    Device name, for example ``sd'' for a SCSI disk on an HP300 or a ``pty'' for pseudo-devices.

     b | c | w
	     Type of device. If the device is a block type device such as a tape or disk drive which needs both cooked and raw special files, the
	     type is b.  Whiteout nodes are type w.  All other devices are character type devices, such as terminal and pseudo devices, and are
	     type c.

     major   The major device number is an integer number which tells the kernel which device driver entry point to use.

     minor   The minor device number tells the kernel which one of several similar devices the node corresponds to; for example, it may be a spe-
	     cific serial port or pty.

     unit and subunit
	     The unit and subunit numbers select a subset of a device; for example, the unit may specify a particular SCSI disk, and the subunit a
	     partition on that disk.  (Currently this form of specification is only supported by the bsdos format, for compatibility with the
	     BSD/OS mknod(8).)

     Device numbers for different operating systems may be packed in a different format.  To create device nodes that may be used by such an oper-
     ating system (e.g. in an exported file system used for netbooting), the -F option is used.  The following formats are recognized: native,
     386bsd, 4bsd, bsdos, freebsd, hpux, isc, linux, netbsd, osf1, sco, solaris, sunos, svr3, svr4 and ultrix.

     Alternatively, a single opaque device number may be specified.

SEE ALSO

     mkfifo(1), mkfifo(2), mknod(2)

HISTORY

     A mknod command appeared in Version 6 AT&T UNIX.  The -F option appeared in NetBSD 1.4.

NetBSD 1.4							September 11, 1998							NetBSD 1.4

SCO