Sponsored Content
Operating Systems SCO Migrate SCO 5.0.6 to different hardware Post 302443085 by jgt on Friday 6th of August 2010 02:44:16 PM
Old 08-06-2010
Either use Backup Edge, or do a fresh install OS the new hardware. You cannot simply copy the partition from one style of disk controller to another.
What SCSI Controller do you expect to use?
Is there a device driver for SCO 5.0.6 available?
With Backup Edge, you have to create a target kernel on the old system.
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

How to migrate ?

Currently, I am planning a migration between machine which under True64UNIX. The new machine will run with higher version O/S. My question is, is there any solution on migrating one machine to another which with different O/S version? My goal is keeping minimum impact to the users. Excuse my... (1 Reply)
Discussion started by: coolmans
1 Replies

2. Solaris

Migrate oracle solaris 5.8 5.9

If I have an oracle 9 database environment on a san running solaris 5.8 as the os. Can I plug the san into a Solaris 5.9 environment and have the database work ? - as long as binaries are on the san (1 Reply)
Discussion started by: tim-carroll@com
1 Replies

3. Linux

Mysql Migrate

Hi , I would like to (MYSQL) migrate the all the data from solari's to linux box. I have checked whether mysql is installed or not. rpm -qa | grep -i mysql I confirmed !!!! I want to know the following points. 1) How can get to know what are mysql data files and location as well.... (4 Replies)
Discussion started by: Mani_apr08
4 Replies

4. Solaris

Hardware faulty, but which hardware?

Hi folk, I have this hardware faunty message, but dont know which hardware is this ? can you guide me ? --------------- ------------------------------------ -------------- --------- TIME EVENT-ID MSG-ID SEVERITY ---------------... (9 Replies)
Discussion started by: dehetoxic
9 Replies

5. SCO

Migrate UNIXWare from old machine to new machine (different hardware)

Good afternoon all, I'm a bit stuck... I honestly don't know very much about Unix let alone UnixWare for that matter. I have a system that's very old and could fail really at any time. I have another server I'd like to move everything to yet I don't know what's possible. The current server is... (2 Replies)
Discussion started by: rubiks015
2 Replies

6. SCO

SCO 5.0.7v VM Hardware

I run SCO 5.0.7v in ESXi 5.5 and am looking at ways to increase performance. I notice that the VM hardware is still set to 4 and wondered if there was an advantage in raising it or will this cause issues? (0 Replies)
Discussion started by: stewartg
0 Replies

7. SCO

Recommendation for hardware to run SCO OSR 5.0.7 natively

Looking for a modern server to run SCO OSR 5.0.7 without VM (native), h/w must have manufacturers warranty. Requirements would be to accommodate light loads of up to 15 users, app does not take more than 30 - 40 MB of RAM and data stored takes up to 15 - 20 GB, no internet connections... (3 Replies)
Discussion started by: migurus
3 Replies

8. Linux

How to migrate a running lvm.?

Hi all, Please explain how do i. Migrate and backup a running lvm..!! Thanks, Sent from my LG-D802 using Tapatalk (3 Replies)
Discussion started by: lordkizzo
3 Replies

9. AIX

Migrate AIX to new Hardware

Hello Friends/AIXgurus, When you have time, could you please look into below. We're planning to migrate AIX LPARs on to new Hardware. Requirement: Migrate AIX LPARs from POWER 6 to POWER 8 Hardware (*everything should run as is after the transition) Below is our thought process. Ours... (5 Replies)
Discussion started by: System Admin 77
5 Replies
SD(4)							   BSD Kernel Interfaces Manual 						     SD(4)

NAME
sd -- SCSI and ATAPI disk driver SYNOPSIS
sd* at scsibus? target ? lun ? sd3 at scsibus0 target 3 lun 0 sd* at atapibus? drive ? flags 0x0000 DESCRIPTION
The sd driver provides support for SCSI bus and Advanced Technology Attachment Packet Interface (ATAPI) disks. It allows the disk to be divided up into a set of pseudo devices called partitions. In general the interfaces are similar to those described by wd(4). Where the wd(4) device has a fairly low level interface to the system, SCSI devices have a much higher level interface and talk to the system via a SCSI host adapter (e.g., ahc(4)). A SCSI adapter must also be separately configured into the system before a SCSI disk can be config- ured. When the SCSI adapter is probed during boot, the SCSI bus is scanned for devices. Any devices found which answer as 'Direct' type devices will be attached to the sd driver. For the use of flags with ATAPI devices, see wd(4). PARTITIONING
On many systems disklabel(8) is used to partition the drive into filesystems. On some systems the NetBSD portion of the disk resides within a native partition, and another program is used to create the NetBSD portion. For example, the i386 port uses fdisk(8) to partition the disk into a BIOS level partition. This allows sharing the disk with other operat- ing systems. CONFIGURATION OPTIONS
The following config(1) options may be applied to SCSI disks as well as to other disks. SDRETRIES Set the number of retries that will be performed for operations it makes sense to retry (e.g., normal reads and writes). The default is four (4). SD_IO_TIMEOUT Set amount of time, in milliseconds, a normal read or write is expected to take. The defaults is sixty seconds (60000 mil- liseconds). This is used to set watchdog timers in the SCSI HBA driver to catch commands that might have died on the device. IOCTLS
The following ioctl(2) calls apply to SCSI disks as well as to other disks. They are defined in the header file <disklabel.h>. DIOCGDINFO Read, from the kernel, the in-core copy of the disklabel for the drive. This may be a fictitious disklabel if the drive has never been initialized, in which case it will contain information read from the SCSI inquiry commands. DIOCSDINFO Give the driver a new disklabel to use. The driver will not write the new disklabel to the disk. DIOCKLABEL Keep or drop the in-core disklabel on the last close. DIOCWLABEL Enable or disable the driver's software write protect of the disklabel on the disk. DIOCWDINFO Give the driver a new disklabel to use. The driver will write the new disklabel to the disk. DIOCLOCK Lock the media cartridge into the device, or unlock a cartridge previously locked. Used to prevent user and software eject while the media is in use. DIOCEJECT Eject the media cartridge from a removable device. In addition, the scsi(4) general ioctl() commands may be used with the sd driver, but only against the 'c' (whole disk) partition. NOTES
If a removable device is attached to the sd driver, then the act of changing the media will invalidate the disklabel and information held within the kernel. To avoid corruption, all accesses to the device will be discarded until there are no more open file descriptors referenc- ing the device. During this period, all new open attempts will be rejected. When no more open file descriptors reference the device, the first next open will load a new set of parameters (including disklabel) for the drive. FILES
/dev/sdup block mode SCSI disk unit u, partition p /dev/rsdup raw mode SCSI disk unit u, partition p DIAGNOSTICS
None. SEE ALSO
ioctl(2), intro(4), scsi(4), wd(4), disklabel(5), disklabel(8), fdisk(8), scsictl(8) HISTORY
The sd driver was originally written for Mach 2.5, and was ported to FreeBSD by Julian Elischer. It was later ported to NetBSD. BSD
January 18, 1996 BSD
All times are GMT -4. The time now is 01:15 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy