Sponsored Content
Operating Systems SCO SCO OpenServer 5.0.6 media needed Post 303040184 by brantleyallen on Thursday 24th of October 2019 02:11:52 PM
Old 10-24-2019
SCO OpenServer 5.0.6 media needed

My media disk is unusable.
Can someone provide me an ISO for Openserver 5.0.6?



Thank you.
Brantley Allen
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

SCO Openserver 6.0

Hi guys, I just got this new 6.0 version and i'm trying to setup a remote office to telnet to this server running sco 6.0, in previous version all i have to do is add this file under /etc/rc2.d call S99route and put the gate in that file and that was it, for some reason in 6.0 it does not... (1 Reply)
Discussion started by: josramon
1 Replies

2. SCO

Looking for openserver 5.0.5 media kit

Hello We are running a pretty old system here which needs to be re-installed. Unfortunately even if all my licences are okay, my install CD are missing in the box. I contacted sco in order to get these media kit, with no luck (product discontinued) I was wondering if some good pal would... (5 Replies)
Discussion started by: qube001
5 Replies

3. SCO

OpenServer 5.0.6 Media Needed

I have a client with 5.0.6 who wants to migrate to new hardware. We have in our posession all appropriate paper software licenses. Over the years the media has vanished Can anyone assist with locating an ISO or actual CD containing OpenServer 5.0.6, please? Thank you (9 Replies)
Discussion started by: theantisco
9 Replies

4. SCO

openserver 5.0.6 media need

I am looking for openserver 5.0.6 media. I need build a new production server and we only have the 5.0.5 media. If anybody can help that be awesome. (9 Replies)
Discussion started by: stlwindadmin
9 Replies

5. SCO

SCO Unix OpenServer 5.0.5 Media Kit

My client has lost the SCO OS 5.0.5 install media. However, they do have a working SCO 5.0.5 system, but is crumbling apart. Where can I find the SCO OS 5.0.5 install media? Or can I get a copy of the SCO CD as a ISO file? Your help is much appreciated. (7 Replies)
Discussion started by: chedlee88-1
7 Replies

6. SCO

SCO Openserver 5.0.4Eb binaries needed

Hello, I'm a system administrator of Russian bowling club located in Tomsk. As a server for our management system we use SCO OpenServer 5.0.4Eb. I know that it's old and so on, but we use it because we, some time ago, bought all the bowling system in used condition, and it works well for years. ... (2 Replies)
Discussion started by: mr_Well
2 Replies

7. SCO

SCO 5.0.6 Media needed

Hi, can anyone provide me the sources for sco 5.0.6 as iso? Thanks! (26 Replies)
Discussion started by: VoidCeroOne
26 Replies

8. SCO

SCO OpenServer 5.0.4 Media Needed

Greetings, I've recently been given responsibility for a legacy server running SCO OpenServer 5.0.4 and upon taking inventory I discovered we have all the license documents but no installation media. Can anyone assist me with where I might download these? Thanks Kevin (9 Replies)
Discussion started by: Kevin Harris
9 Replies

9. SCO

Sco media needed for openserver 5.0.6

Hello, i need if possible media for sco openserver 5.0.6 and also want to know if is possible to upgrade from 5.0.2 to 5.0.6. Best regards, Paolo (1 Reply)
Discussion started by: elnino981
1 Replies

10. SCO

Need SCO 5.0.6 openserver media kit

hello everyone i need a copy of sco 5.0.6 iso for isntall a new server crash I read in a post that someone uploaded to an ftp an iso but I did not find the ftp any can helpme? (7 Replies)
Discussion started by: mjgeddo
7 Replies
voldiskadm(8)						      System Manager's Manual						     voldiskadm(8)

NAME
voldiskadm - Menu interface for LSM disk administration SYNOPSIS
/usr/sbin/voldiskadm DESCRIPTION
The voldiskadm script is an interactive tool that presents a menu of possible operations to the user. When an operation is selected, the script guides the user through the necessary steps, and prompts for data needed to complete the operation. The voldiskadm interface is intended mainly for beginning users and for those who prefer a simple method for doing common operations. The interface uses query-based prompts to gather input, with defaults supplied when possible. Context-sensitive help is available at every prompt by typing ?. Also, a list option can be used to get information on available target disks for an operation. For operations that require a device name, one or more names can be specified using a space-separated list. Names in the list can have the form dskn or rdskn (for an entire disk) or dsknp or rdsknp (for a specific disk partition). Disk names relate directly to device names in the /dev/disk and /dev/rdisk directories. The file, /etc/vol/disks.exclude, may be used to exclude disks from use by voldiskadm. Each line of the file specifies the name of a disk to exclude (for example, dsk5). The voldiskadm menu includes the following options: Add or initialize one or more disks This option prompts for one or more disk device addresses. The specified disks can be added to an existing disk group, added to a new disk group, added to a disk group as spares, or initialized but not added to a disk group (reserved for use as replacement disks). After specifying the disks, the user is prompted for a disk group (rootdg by default) and a disk name. If no name is specified, a default disk name is assigned (diskn for disks in the rootdg disk group and diskgroupn for disks in other disk groups). The disks are then checked to ensure that there is no information already on them. If there is, the user is given the option of encapsulating the disks. Encapsulate one or more disks This option prompts for one or more disk addresses. It then calls volencap to encapsulate the specified partitions. Remove a disk This option prompts for a disk, by disk media name. The disk is checked to ensure that no subdisks reside on the disk. If the disk is in use, the operation fails with a recommendation to first move all volumes off the disk. If this disk is the last disk in a disk group, the user is prompted for whether the disk group should be removed from the system, as well. The operation proceeds by calling voldg rmdisk to remove the disk from its disk group. If this is the last disk in its disk group, voldg deport is used, instead, to remove the disk group from use. Remove a disk for replacement This option prompts for a disk, by disk media name. The disk is checked for volumes that would lose all mirrors as a result of the operation. If such volumes exist, they are listed and the user is prompted to ensure that the operation should proceed. The operation proceeds by calling voldg -k rmdisk to dissociate the media record from the physical disk. If some formatted disks are under LSM control but not assigned to a disk group, the user is prompted for whether one of these disks should be used as a replacement. Replace a failed or removed disk This option prompts for a disk media name. The named media record must be dissociated from a disk. If the media record is not in the removed state, unused disks are scanned for matching disk IDs. If a disk with a matching disk ID is found, the user is prompted for whether that disk should be reattached. If a matching disk is not used, the user is prompted for a new disk, by device name. If the named replacement disk has a valid disk header, but is not allocated to a disk group, the user is prompted for whether the disk should be reinitialized. If the named replacement disk is listed as allocated to a disk group or to another host, the user is prompted to ensure that the operation should proceed. If the device is to be initialized, a new disk label is written to the disk to reflect its private and public regions. Given an initialized disk, the operation proceeds by replacing the disk in a disk group with voldg -k adddisk. Mirror volumes on a disk This option prompts for a disk, by disk media name. It then prompts for a destination disk within the same disk group, also by disk media name. Specifying no destination disks indicates that any disk is suitable. The operation proceeds by calling volmirror to mirror the volumes. Mirroring volumes from the boot disk will produce a disk that can be used as an alternate boot disk. This is done by calling the volrootmir command. Move volumes from a disk This option prompts for a disk, by disk media name. It then prompts for a possible list of destination disks, also by disk media name. Specifying no destination disks indicates that any disk is suitable. The operation proceeds by calling volevac to move sub- disks off the disk. Enable access to (import) a disk group This option prompts for a disk, by device address. The operation proceeds by calling voldg import to import the disk group stored on that disk. Disable access to (deport) a disk group This option prompts for a disk group name. The prompt display lists alternate disk groups and the disks (media name and access name) that they contain. The operation proceeds by calling voldg deport. Enable (online) a disk device This option prompts for a disk device. The prompt display allows for a display of disks on the system. The operation only func- tions for disks currently in an offline state. It then proceeds to make the disk accessible. Disable (offline) a disk device This option prompts for a disk device. The prompt display allows for a display of disks on the system. The operation only func- tions for disks currently in an online state but not part of any disk group. It then proceeds to mark the disk as offline such that the Logical Storage Manager makes no further attempt at accessing the disk. Mark a disk as a spare for a disk group This option sets up a disk to be used as a spare device for its disk group. A spare disk can be used to automatically replace a disk that has failed. No space can be used on a disk that is marked as a spare. Turn off the spare flag for a disk This option removes a disk from those that can be used as a spare and returns its space to the general pool of available space. Recover plexes and volumes after replacement This operation performs plex attachment, RAID-5 subdisk recovery, and resynchronize operations for the named volumes, or for volumes residing on the named disks (media name). If no media name or volume operands are specified, the operation applies to all volumes (or to all volumes in the specified disk group). ERRORS
See the voldiskadd(8) reference page for a description of errors related to the initialization operation. FILES
A list of disks to exclude from use by voldiskadm. SEE ALSO
disklabel(8), volintro(8), voldg(8), voldisk(8), voldiskadd(8), voldisksetup(8), volrootmir(8) voldiskadm(8)
All times are GMT -4. The time now is 10:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy