But the output is file systems not disks.
"fdisk" and "divvy" will display/change disks and partitions.
Raid configurations are available only if the manufacturer of the controller provided a program to display the structure.
All RAID controllers come with a DOS or stand alone (built into a ROM) program to build the raid system before the operating system is installed.
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)
First of all, hello there!!!
Well, I' ve got one question:
How may I get the size of the HD, I mean, wich command do I have to type?
Thanks in advance, (6 Replies)
Hi Engg. ! :mad:
I have a harddisk on which SCO UNIX Open Server was installed. There was some data (in .dbf format) on it. Present condition of HDD is that it is not booting. Now I want to mount this HDD through other HDD on which SCO UNIX Open Server is installed by attaching... (0 Replies)
Hi!
Sorry, but I am'not spesialist in SCO OpenServer. I need to add hard disk from SCO Open Server ( "a") in my SCO OpenServer 5.6. I need data from "a". When I added, I see only swap disk, and didn't see root file system. I need to add IDE and SCSI
Please, help me. How right to add disk?... (0 Replies)
anyone know where I can download or get a boot disk for sco unix v/386? I have an old PC running sco unix v/386 3.2. I dont have an install or boot disk. I need to reset the root password. I have looked all over the internet and cannot find it anywhere. any help would be greatly appreciated.... (5 Replies)
Hi,
I am using SCO Unix 3.12 and Informix database. When we tried to use "du -a" command to check disk space, it showed:
342122 ./usr
30092 ./etc
6244 ./dev
4778 ./bin
2674 ./tcb
1234 ./lost+found
698 ./lib
532 ./shlib
46 ./tmp
6 ./messages
4 ./opt
4 ./var
2 ./mnt
2 ./install... (1 Reply)
Hi, i'm from Argetina and my english is very poor.
I'm trying to copy disk with sco unix 5.0.5 -60Gb IDE
Disk- (7476, 255, 63) to other disk -IDE 80Gb- and g4u v2.3.
After the copy, i'm trying the 80Gb disk and the roblem is the partition /u/disco is empty.
Note: /u/disco is the... (0 Replies)
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)
Hello,
in one default UFS filesystem we have 8K block size (bsize) and 1K fragmentsize (fsize). At this scenary I thought all "FileSytem IO" will be 8K (or greater) but never smaller than the fragment size (1K). If a UFS fragment/blocksize is allwasy several ADJACENTS sectors on disk (in a ... (4 Replies)
Discussion started by: rarino2
4 Replies
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