No. There is no way currently. This is from experience in kernels up to
2.4.18, and I've not seen any dev notes on newer kernels to say it supports
them.
I've also not seen any userspace tools to allow you to interact with SCO
filesystems and divions.
bkx
.. by the same token, I could be wrong ..
Filesystems-HOWTO (section 9) reports that there may be some commercial
drivers available from a compnay called 'Crosstor' ({ftp,www}.crosstor.com).
Unfortunately both web and FTP servers were down, so I was not able to get
any further details.
bkx
"Stuart J. Browne" <stu...@promed.com.au> wrote in message
news:apa05m$eee$1...@perki.connect.com.au...
what you can do is set up a new fs that both OS's can access.
linux can read some sco fs's via the "sysv" kernel module.
I do not think it works for HTFS or DTFS, but I do know it works for
XENIX
probably it works for at least one of the newer FS's than xenix but I
haven't checked it out. linux and sco can both read/write DOS fs too.
the main thing to be aware of is, linux can't pick out a divvy
partition.
you need to make either a DOS or one of the older Unix fs's on a
whole-partition or whole-drive device. then linux can mount it.
example:
in unix:
mkfs -f XENIX /dev/rdsk/1s0
this example is the 2nd scsi hard drive, the whole drive, not a
partition that takes up the whole drive.
Both XENIX and DOS are kind of terrible filesystems to use though, so
I'd try
HTFS (don't include any "-f xxx" and you get htfs)
EAFS, S51KB, and AFS in place of XENIX
also, sco doesn't usually install xenix fs support by default, but it
is very easy to add, just "mkdev xenix"
under sco mount it with:
mount /dev/dsk/1s0 /mnt
under linux, (try to) mount it with:
insmod sysv
mount -t sysv /dev/sdb /mnt
to use a primary partition instead of a whole drive, replace the
following device names from above. Note: SCO "fdisk" numbers the 4
primary partitions backwards from the way DOS and Linux do. I will
show two examples to show how this affects the numbers & names you
need to use in each OS.
To use the 2nd primary partition as seen from DOS or Linux's fdisk
programs:
sco: /dev/dsk/1s3
lnx: /dev/sdb2
To use the 1st primary fdisk partition as seen from sco's fdisk
program:
sco: /dev/dsk/1s1
lnx: /dev/sdb4
under sco the same devices are also known by some shorter handier
names but I prefer to use these names as it's more clear to me exactly
what physical device is being refered to than the /dev/hd00 and
/dev/hd10 etc kinds of names. Just feels a little less risky to me
when it comes time to mkfs.
handy trick to be more sure before doing mkfs, if you have drive
lights for each drive (like in a raid array or hot-swap bay) just dd
if=/dev/dsk/1s0 of=/dev/null and see which drive light lights up.
delete key after a few seconds of course, no need to let it read the
whole drive :)
working with raid cards I have managed often enough to get mkdev hd to
create multiple, different device nodes that all go to the same
physical device, or that go to physical devices that are all part of
the same logical device. *dangerous*, so I check with dd before
allowing mkfs to run.