Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rice!sun-spots-request
From: chuck@trantor.harris-atd.com (Chuck Musciano)
Newsgroups: comp.sys.sun
Subject: Re: question on SunOS 4.1 TFS...
Keywords: Miscellaneous
Message-ID: <5773@brazos.Rice.edu>
Date: 14 Mar 90 13:08:32 GMT
Sender: root@rice.edu
Organization: Sun-Spots
Lines: 30
Approved: Sun-Spots@rice.edu
X-Refs:  Original: v9n75, Replies: v9n79
X-Sun-Spots-Digest: Volume 9, Issue 81, message 8

Larry McVoy (lm@sun.com) writes:
> You've misunderstood TFS (Translucent File System).  It's a stacked file
> system - it sits on top of another file system and requests for files are
> satisfied from the top file system if the files exist in that system and
> from the bottom file system otherwise.  The example is an obviuos use: if
> a use has some program (that is broken because: ) that insists on living
> in /usr/local/bin (like mh) and you can't write in /usr/local/bin (like
> me) then you can put your program in an otherwise empty file system and
> mount that file system over /usr/local/bin.

Ah, those who forget history are condemned to repeat it!  Older Sun users
will recognize Translucent File Systems to be a snappy new name for a very
old idea.  Go back, way back, to 1964, and IBM's OS/360.  People who know
the difference between an 026 and an 029 keypunch might recognize

	//SYSIN    DD   HOSAJM.FIRST.DATASET
	//         DD   HOSAJM.NEXT.DATASET

as the way you created "translucent" file systems, concatenating multiple
datasets into one logical dataset.  A very handy concept, one missing from
Unix for a long time.  A new idea?  No way.  A good idea?  Yes.  I'm glad
it will be in 4.1.

Chuck Musciano				ARPA  : chuck@trantor.harris-atd.com
Harris Corporation 			Usenet: ...!uunet!x102a!trantor!chuck
PO Box 37, MS 3A/1912			AT&T  : (407) 727-6131
Melbourne, FL 32902			FAX   : (407) 727-{5118,5227,4004}

I'm glad you asked, son.  Being popular
	is the most important thing in the world.	-- Homer Simpson