Hi Roy,
Made it here........;-)
 CA>         Toronto Virtual File System will do what you want.
 RJT> What is that?
 PK> An IBM Employee writting product that allows you to build 1
 PK> HUGE OS/2 drive on a single driver letter, from multiple
 PK> other logical drives (potentially spread over other systems)
 PK> in a manner similar to the *nix file system and MOUNT
 PK> commands. It can be very useful for building a huge logical
 PK> drive, however performance can be poor if you build and use
 PK> the resulting drive in an inappropriate manner...........pk.
 RJT> This still sounds rather interesting,  and I'd like to 
 RJT> know more about what is meant by your last statement 
 RJT> there,
TVFS implements a Logical drive under OS/2 that confirms to a UNIX style file 
system but to do this it needs to "massage" things so that the differences 
between the UNIX world and the other environments the files can come from do 
not cause problems. One of theother nice things about TVFS is that in a LAN 
environment, different platforms on the LAN can provide various file systems 
as segmetns of the overall TCFS logical drive, and this is hidden from 
whoever is accessing the drive.
EG, a file stored on an OS/2 HPFS partition is stored as case retentive, but 
NOT case dependant. A UNIX file system is case retentive and is also case 
dependant, so immediately you have a potential conflict, depending on WHO is 
accessing the file and what they expect to happen. Consider also a FAT 
partition where filenames are 8.3 and all upper-case. With TVFS you MUST 
supply the 8.3 name in all upper case to be able to access it. Ov course 
because FAT was never designed to have UNIX access rights applied to it, TVFS 
has to fudge around it, the same with other file systems and of course 
whatever LAN environments is sharing the component of the TVFS.
Pick up a copy of it and read the DOC,s it makes you think about sharing 
files over a LAN in a completely new way........;-)
--- Maximus/2 3.01
---------------