This article is from a FAQ concerning SCO operating
systems. While some of the information may be applicable to any OS,
or any Unix or Linux OS, it may be specific to SCO Xenix, Open
Desktop or Openserver.
There is lots of Linux, Mac OS X and general Unix info elsewhere on
this site: Search this site is the best
way to find anything.
Here's a clever VMWare solution: SCO 3.2v4.0 hard disk image in VMware
See also fsrd read sco filesystem. Last I checked (Sept. 2009), that was still available.
Brian K. White wrote:
I know I read a readme and downloaded a patch that applied to some way back 2.0 or even 1.x kernel that claimed to allow mounting of divvy slices, but I never tried it and don't remember where I found it now. I think it's out there to be had, but you have to search it out. For some reason it's just not being accepted into the kernel tree proper. For now you can do the following: simply create a SCO filesystem on a raw partition manually, Linux will be able to mount that filesystem, and so will SCO. "mdev hd" is a script that runs fdisk, then divvy, then mkfs (among other things) The easiest way to go would be to run mkdev hd to add a new hard drive, (this creates the /dev/hdxxx device files for you) then determine the device name for your new raw partition (or whole drive for that metter, you actually do not need any partitions at all, not even one that takes up the whole drive) then dd if=/dev/zero of=/dev/hd10 (for whole 2nd ide drive for instance) then mkfs -f HTFS /dev/hd10 then mkdir /d2 then mount -f HTFS /dev/hd10 /d2 then to copy your "u" filesystem, cd /u; tar cf - . | (cd /d2 ;tar xf -) then in Linux: mkdir /d2 modprobe sysv mount -t sysv /dev/hdb /d2 Note: if Linux can't read the HTFS filesystem, you may need to try substituting one of the following until it works. I know for a fact Linux reads Xenix just fine, but Xenix fs has yucky limitations like 14 character name length AFS Acer Fast Filesystem DTFS Desktop Filesystem EAFS Extended Acer Fast Filesystem HTFS High Throughput Filesystem S51KB AT&T UNIX(R) System V 1KB Filesystem XENIX XENIX(R) filesystem
Brian also tells us:
Linux doesn't understand divvy, so to mount a xenix fs under linux, you just need to have created the filsystem under xenix by writing to a whole fdisk partition or whole-disk device, _not_ the normal way where divvy divides up a fdisk partition into divvy partitions and then writes filesystems to those. This means using for example /dev/hd11 as the mkfs target in xenix for the 1st fdisk partition on the 2nd drive. IE: if migrating an old xenix box and there is no room to make cpio/tar files, then add a 2nd drive, make at least one fdisk partition that is only 512 Megs since a xenix filesystem cannot exceed 512 megs anyways. Then, in linux, you also have to know that linux and xenix count the fdisk oartitions backwards from each other. Fdisk partition 1 (counting from 1) in xenix, is fdisk partition 4 in linux. xenix: /dev/hd11 linux: /dev/hdb4 Then again, if you are going to go to the trouble of adding a disk and moving it to a linux box, you could just cpio the whole system, including all mounted filesystems, (which might exceed 512 megs) directly to the whole-disk device or a larger-than-512meg fdisk partition and skip creating a filesystem.
And see http://aplawrence.com/Bofcusm/2644.html for more details on that.
If you are trying to access a crashed SCO drive with Linux, keep these things in mind:
See Linux drivers for SCO HTFS filesystems also
/SCOFAQ/FAQ_scotec1linuxfs.html copyright 1997-2003 (various) All Rights Reserved
Have you tried Searching this site?
Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.
Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.
Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.
We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.
Click here to add your comments
Don't miss responses! Subscribe to Comments by RSS or by Email
Click here to add your comments
If you want a picture to show with your comment, go get a Gravatar