Unix, Xenix and ODT General FAQ
The original HTFS driver module for Linux was written back in 2001 by Andrzej Dereszowski. I knew that I had seen it before, but I think you're correct that there's no opensource driver available at the moment. I very much doubt the reason for the absence of this driver is technical, but rather due to the threat of legal action from the litigious bastards at SCO. Apparently SCOG licenced this tech to a company called CrosStor, who developed a closed module for Linux, but I think they've since gone out of business (maybe little/no demand for that particular proprietary product? ;-)
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.
If you are trying to access a crashed SCO drive with Linux, keep these things in mind:
- Linux uses partitions for one filesystem; SCO puts multiple file systems on an fdisk partition. You might be able to use dd to pull out what you want, but you'll need to know how big the partitions are. Linux mount lets you specify an offset, so if you know where the filesystem starts, you might be able to do it that way.
- A crashed fs will need to be cleaned- standard Linux fsck may not understand SCO filesystems- and if it *thinks* it does, it could destroy data.
(OLDER) <- More Stuff -> (NEWER) (NEWEST)
Printer Friendly Version