TIP: Click on subject to list as thread! ANSI
echo: os2lan
to: PETER KNAPPER
from: ROY J. TELLASON
date: 1998-04-08 20:36:00
subject: Multi CD/ 1 Dir letter

Peter Knapper wrote in a message to Roy J. Tellason:
 PK> Hi Roy,
 PK> Made it here........;-)
So I see...    :-)
 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 other 
 PK> logical drives (potentially spread over other systems) in a 
 PK> manner similar to the *nix file system and MOUNT commands. It 
 PK> can be very useful for building a huge logical drive, however 
 PK> performance can be poor if you build and use the resulting 
 PK> drive in an inappropriate manner...........pk.
 RJT> This still sounds rather interesting,  and I'd like to know 
 RJT> more about what is meant by your last statement there,
 PK> TVFS implements a Logical drive under OS/2 that confirms to a 
 PK> UNIX style file system but to do this it needs to "massage" 
 PK> things so that the differences between the UNIX world and the 
 PK> other environments the files can come from do not cause 
 PK> problems. One of theother nice things about TVFS is that in a 
 PK> LAN environment, different platforms on the LAN can provide 
 PK> various file systems as segmetns of the overall TCFS logical 
 PK> drive, and this is hidden from whoever is accessing the drive.
 PK> EG, a file stored on an OS/2 HPFS partition is stored as case 
 PK> retentive, but NOT case dependant. 
An interesting distinction,  and one that I've not seen before.
 PK> A UNIX file system is case retentive and is also case 
 PK> dependant, 
So I've found.  
 PK> so immediately you have a potential conflict, depending on WHO 
 PK> is accessing the file and what they expect to happen. Consider 
 PK> also a FAT partition where filenames are 8.3 and all 
 PK> upper-case. With TVFS you MUST supply the 8.3 name in all upper 
 PK> case to be able to access it. Ov course because FAT was never 
 PK> designed to have UNIX access rights applied to it, TVFS has to 
 PK> fudge around it, the same with other file systems and of course 
 PK> whatever LAN environments is sharing the component of the TVFS.
I don't plan on having much in the way of FAT partitions around when I'm done 
here...  
 PK> Pick up a copy of it and read the DOC,s it makes you think 
 PK> about sharing files over a LAN in a completely new 
 PK> way........;-)
I just looked in a handy file list and found the following:
TVFS.ZIP      461599 01/15/97  THE TORONTO VIRTUAL FILE SYSTEM IS AN
                               INSTALLABLE FILE SYSTEM THAT COMBINES VM AND
                               UNIX (XX) FILE SYSTEM CONCEPTS. VERSION 2.10
(Dunno why that description is all caps...)
Hopefully that's it,  I've sent off a request to the appropriate fileserv, so 
I oughta have this in a day or so.
Some doc files can be informative like that.  I read the one for PRESIZ (a 
dos program to fiddle with partitions) that explained the heck out of 
paritioning to me way better than it's been done before,  for example...
email: roy.j.tellason%tanstaaf@frackit.com 
--- 
---------------
* Origin: TANSTAAFL BBS 717-432-0764 (1:270/615)

SOURCE: echomail via exec-pc

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.