05-24-2012
Thanks for the info jgt. unfortunately the system that is going to rest on the sco calls for 507. however i do have 6.o install disk. problem i have is configuring the hard drive partitions. install instructions i have for 507 (to be compatable) shows different setup screen than 6.0 when i get to the section to setup the drive.
10 More Discussions You Might Find Interesting
1. SCO
I've installed a CD-RW rom using SCO OSR 5.0.7, but I cannot open the dev to perform backup (6 Replies)
Discussion started by: tsc_hk
6 Replies
2. Programming
I am trying to access DG-100 gps logger on Mac OS X with POSIX API. The device uses a Prolific usb-serial controller, and connect to the usb port on my mac.
After I install the Prolific driver, it shows up as /dev/tty.usbserial and /dev/cu.usbserial. The vendor has published the data format. So... (1 Reply)
Discussion started by: monkeybiz
1 Replies
3. Solaris
Hi,
I attached the CDROM device in sun 2500 system , Now i want to mount this device.
From where i can find the CDROM device.
Thnx.. (2 Replies)
Discussion started by: Aamir Sahil
2 Replies
4. SCO
Looking for specifically naming convention for a tape device for SCO Unix
What full system backup command should I use for SCO UNIX (1 Reply)
Discussion started by: jedimaster
1 Replies
5. Solaris
Hi,
I've seen similar posts on this board about ejecting CDROMs but I've tried the solutions people suggested but still cannot eject the CD. It's stuck in a production box so I can't reboot it...
bash-3.00# eject -f cdrom
/vol/dev/dsk/c0t0d0/sol_10_106_sparc/s0: Device busy
bash-3.00#... (14 Replies)
Discussion started by: jimmy54321
14 Replies
6. SCO
I'm "attempting" to install SCO 5.0.7 on an HP ML370 G4 server and am ready to bash the keyboard with head now. I keep getting the error message "WARNING hd: no root disk controller found" when running the bootable install cd.
I have a raid 5 array with an online spare created using 4 36.3 GB... (2 Replies)
Discussion started by: FrictionBurn
2 Replies
7. SCO
This is my first load of SCO OpenServer v5.0.7 on a HP ProLiant ML350 G6. When it asks me to identify the source media it can't find it no matter how I respond. The SCO compatible page says it used the on board SATA DVD-ROM on Port 2 of the embedded SATA controller with "Legacy IDE emulation (as... (8 Replies)
Discussion started by: farmboy
8 Replies
8. SCO
So today I tried to upgrade a customer from a Proliant with an HPSAS controller to an Intel server with a MEGASAS controller.
First, I downloaded the megasas driver from SCO and installed it on the old system.
Then I created a new Microlite Edge emergency boot cd with the new driver on it.
I... (2 Replies)
Discussion started by: jgt
2 Replies
9. HP-UX
Hello,
I am following the HPUX 11.31 install/update guide and I am trying to install "Update-UX" from the installation media. I put the CD into the drive, and I am trying to mount the device. The instructions state:Find the DVD-ROM device file name:
ioscan -C disk -f -n -k | more
A typical... (5 Replies)
Discussion started by: bstring
5 Replies
10. SCO
Hi all,
A client has an SCO OpenServer Server 6.0, that is running on an HP ProLiant Box and they lost the root password.
Its equipped with a Doal-Core Intel Pentium Processor. They don't have any media or emergency disk anymore.
I tried to boot with the CD Rom, then "Tools", then exit to... (7 Replies)
Discussion started by: thm2222
7 Replies
SD(4) Linux Programmer's Manual SD(4)
NAME
sd - Driver for SCSI Disk Drives
SYNOPSIS
#include <linux/hdreg.h> /* for HDIO_GETGEO */ #include <linux/fs.h> /* for BLKGETSIZE and BLKRRPART */
CONFIG
The block device name has the following form: sdlp, where l is a letter denoting the physical drive, and p is a number denoting the parti-
tion on that physical drive. Often, the partition number, p, will be left off when the device corresponds to the whole drive.
SCSI disks have a major device number of 8, and a minor device number of the form (16 * drive_number) + partition_number, where drive_num-
ber is the number of the physical drive in order of detection, and partition_number is as follows:
partition 0 is the whole drive
partitions 1-4 are the DOS "primary" partitions
partitions 5-8 are the DOS "extended" (or "logical") partitions
For example, /dev/sda will have major 8, minor 0, and will refer to all of the first SCSI drive in the system; and /dev/sdb3 will have
major 8, minor 19, and will refer to the third DOS "primary" partition on the second SCSI drive in the system.
At this time, only block devices are provided. Raw devices have not yet been implemented.
DESCRIPTION
The following ioctls are provided:
HDIO_GETGEO
Returns the BIOS disk parameters in the following structure:
struct hd_geometry {
unsigned char heads;
unsigned char sectors;
unsigned short cylinders;
unsigned long start;
};
A pointer to this structure is passed as the ioctl(2) parameter.
The information returned in the parameter is the disk geometry of the drive as understood by DOS! This geometry is not the physical
geometry of the drive. It is used when constructing the drive's partition table, however, and is needed for convenient operation of
fdisk(1), efdisk(1), and lilo(1). If the geometry information is not available, zero will be returned for all of the parameters.
BLKGETSIZE
Returns the device size in sectors. The ioctl(2) parameter should be a pointer to a long.
BLKRRPART
Forces a re-read of the SCSI disk partition tables. No parameter is needed.
The scsi(4) ioctls are also supported. If the ioctl(2) parameter is required, and it is NULL, then ioctl() will return -EINVAL.
FILES
/dev/sd[a-h]: the whole device
/dev/sd[a-h][0-8]: individual block partitions
SEE ALSO
scsi(4)
1992-12-17 SD(4)