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?
I have a Dell 1850 and trying to load OS and my applications using PXE. How can I stage new servers using Network drive.
Want to move away from Tape and go towards network load.
Thx
Sean. (0 Replies)
Here is what I did . . . . I FTP'd several *.dbf zipped files from a SCO 5.0.5 server to winXP machine, and did not set the transfer mode to BIN, now when i was uncompressing these files in SCO 5.0.5 , it was giving "Bad Decode Table error. Is there a way to convert the *.dbf.Z files to Binary so... (1 Reply)
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)
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 ? (1 Reply)
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... (0 Replies)
MKNOD(8) BSD System Manager's Manual MKNOD(8)NAME
mknod -- make device special file
SYNOPSIS
mknod [-F format] name [c | b] major minor
[-F format] name [c | b] major unit subunit
name [c | b] number
name [p]
DESCRIPTION
The mknod command creates device special files. Normally the shell script /dev/MAKEDEV is used to create special files for commonly known
devices; it executes mknod with the appropriate arguments and can make all the files required for the device.
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 | p
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. All other devices are character type devices, such as terminal and pseudo devices, and are type c. To create named pipes
the type p can be used.
major The major device number is an integer number which tells the kernel which device driver entry point to use. To learn what major
device number to use for a particular device, check the file /dev/MAKEDEV to see if the device is known, or check the system depen-
dent device configuration file:
``/usr/src/sys/conf/device.architecture''
(for example device.hp300).
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), MAKEDEV(8)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