Sponsored Content
Operating Systems SCO SCO TCP/IP 1.2.0. floppys needed Post 302608441 by edfair on Saturday 17th of March 2012 01:51:51 PM
Old 03-17-2012
I have no experience with tcpip on earlier SCo systems (moved to enterprise 5before needing it) so this is a question in the dark.

OP requested disk 3 (of 3) of the 1.2.0 package. I've provided disk 3 of my 1.2.0 set but there are 4 runtime disks in the package (plus LL driver and 2 maintenance disks). Were there multiple versions of 1.2.0 provided that might account for this seeming discrepancy?
 

10 More Discussions You Might Find Interesting

1. IP Networking

TCP/IP printing on SCO 2.1.3

I am trying to set up TCP/IP printing to so we can remove the old novel server. The printer details have been added to the etc/hosts file correctly, and the printer added as a remote UNIX printer . However when a print job is issued lpstat -o displays the job, but it dosent move. Any help yould... (2 Replies)
Discussion started by: eel_king
2 Replies

2. Filesystems, Disks and Memory

SCO TCP/IP runtime System for SCO Unix

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)
Discussion started by: Cerberus
0 Replies

3. SCO

all tcp are CLOSED on SCO Unix on VMWARE

Hi folks, First of all, sorry about my english, isn't the best and thks for advance. Here es my problem... I have virtualize an SCO unix with VMware ESX 3 and everything was going on beatifull until that i try to connect from anorther host, i can't do it so i check the connection with... (5 Replies)
Discussion started by: martocapo
5 Replies

4. SCO

/dev/inet/tcp not listening in SCO 6.

While in SCO Openserver 5.0.7, Sybase listened to /dev/inet/tcp, the same is not working in SCO Openserver 6. The Network card is however active and pinging fine. What can be the reason? What is the way out? An early response will be appreciated. Thank you Regards TCG (2 Replies)
Discussion started by: thecobolguy
2 Replies

5. SCO

TCP in sco unix 3.2

Hi every body. I am looking for TCP package under sco unix 3.2 or sco xenix system. would you please help me? (7 Replies)
Discussion started by: javad1_maroofi
7 Replies

6. SCO

SCO TCP/IP ?

Hello! I tried to install an old version of SCO for test purposes, (3.2v4.0y), all fine, but my TCP/IP disks are "unreadable" and I cant find them on the internetz. Also, SCO doesnt respond to my request....is there any source for those images available? I have license/activation key which... (5 Replies)
Discussion started by: doc_holiday
5 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 Starting TCP/IP Services

Hi all, I have a customer whose sco unix server wasnt power off correctly and when booting it up I noticed that the boot up takes a while to finish the " Starting TCP services: snmpd routed lpd". after that the server is ready for login, but you cannot ping anything from the server (apart from... (2 Replies)
Discussion started by: CharlL
2 Replies

9. SCO

Sco 5.0.6 installer needed

Hi I m sorry but to post this again. Does anyone have installer of sco 5.0.6 and instruction to reinstall the current system? This is urgent so Any help is appreciated. Thousand thanks (25 Replies)
Discussion started by: OrangeKenny
25 Replies

10. 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
CCD(4)							   BSD Kernel Interfaces Manual 						    CCD(4)

NAME
ccd -- Concatenated disk driver SYNOPSIS
pseudo-device ccd [count] DESCRIPTION
The ccd driver provides the capability of combining one or more disks/partitions into one virtual disk. This document assumes that you're familiar with how to generate kernels, how to properly configure disks and pseudo-devices in a kernel con- figuration file, and how to partition disks. Note that the 'raw' partitions of the disks must not be combined. Each component partition should be offset at least one cylinder from the beginning of the component disk. This avoids potential conflicts between the component disk's disklabel and the ccd's disklabel. The kernel will only allow component partitions of type FS_CCD. But for now, it allows partition of all types since some port lacks support of an on- disk BSD disklabel. The partition of FS_UNUSED may be rejected because device driver of component disk will refuse it. In order to compile in support for the ccd, you must add a line similar to the following to your kernel configuration file: pseudo-device ccd 4 # concatenated disk devices The count argument is how many ccds memory is allocated for at boot time. In this example, no more than 4 ccds may be configured. A ccd may be either serially concatenated or interleaved. To serially concatenate the partitions, specify the interleave factor of 0. If a ccd is interleaved correctly, a ``striping'' effect is achieved, which can increase performance. Since the interleave factor is expressed in units of DEV_BSIZE, one must account for sector sizes other than DEV_BSIZE in order to calculate the correct interleave. The kernel will not allow an interleave factor less than the size of the largest component sector divided by DEV_BSIZE. Note that best performance is achieved if all component disks have the same geometry and size. Optimum striping cannot occur with different disk types. Also note that the total size of concatenated disk may vary depending on the interleave factor even if the exact same components are concate- nated. And an old on-disk disklabel may be read after interleave factor change. As a result, the disklabel may contain wrong partition geometry and will cause an error when doing I/O near the end of concatenated disk. There is a run-time utility that is used for configuring ccds. See ccdconfig(8) for more information. WARNINGS
If just one (or more) of the disks in a non-mirrored ccd fails, the entire file system will be lost. FILES
/dev/{,r}ccd* ccd device special files. SEE ALSO
config(1), MAKEDEV(8), ccdconfig(8), fsck(8), mount(8), newfs(8) HISTORY
The concatenated disk driver was originally written at the University of Utah. BSD
March 5, 2004 BSD
All times are GMT -4. The time now is 04:32 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy