CA1323448C - Method and apparatus for translucent file system - Google Patents
Method and apparatus for translucent file systemInfo
- Publication number
- CA1323448C CA1323448C CA000613984A CA613984A CA1323448C CA 1323448 C CA1323448 C CA 1323448C CA 000613984 A CA000613984 A CA 000613984A CA 613984 A CA613984 A CA 613984A CA 1323448 C CA1323448 C CA 1323448C
- Authority
- CA
- Canada
- Prior art keywords
- file
- layer
- files
- layers
- directory
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/901—Indexing; Data structures therefor; Storage structures
- G06F16/9017—Indexing; Data structures therefor; Storage structures using directory or table look-up
- G06F16/902—Indexing; Data structures therefor; Storage structures using directory or table look-up using more than one table in sequence, i.e. systems with three or more layers
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/188—Virtual file systems
- G06F16/192—Implementing virtual folder structures
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99942—Manipulating data structure, e.g. compression, compaction, compilation
Abstract
ABSTRACT OF THE DISCLOSURE
In a computer system having a hierarchical file structure, a file system is provided which permits users of the system to share a file hierarchy and also have a private hierarchy in which files are automatically copied to as they are modified. Through the system of the present invention, a directory appears to the user as a single directory but may actually comprise files originating from a number of directories which are connected to one another through search links. Each directory has a search link associated with it which contains the path name of the back layer or directory behind it. The first layerseen through the system of the present invention is the front layer, private to the user. The back layers behind the front layer and connected to the front layer through the search links are shared layers accessible to multiple users. Thus transparent to the user the directory accessible comprises multiple layers comprising shared and private files. The system further provides a copy-on-writefeature which protects the integrity of the shared files by automatically copying a shared file into the users private layer when the user attempts to modify a shared file in a back layer.
82225.P051
In a computer system having a hierarchical file structure, a file system is provided which permits users of the system to share a file hierarchy and also have a private hierarchy in which files are automatically copied to as they are modified. Through the system of the present invention, a directory appears to the user as a single directory but may actually comprise files originating from a number of directories which are connected to one another through search links. Each directory has a search link associated with it which contains the path name of the back layer or directory behind it. The first layerseen through the system of the present invention is the front layer, private to the user. The back layers behind the front layer and connected to the front layer through the search links are shared layers accessible to multiple users. Thus transparent to the user the directory accessible comprises multiple layers comprising shared and private files. The system further provides a copy-on-writefeature which protects the integrity of the shared files by automatically copying a shared file into the users private layer when the user attempts to modify a shared file in a back layer.
82225.P051
Description
~ 323448 ~A~K~iRQllND QF IHE I~Y~NTIQi~
Q F ~tl E 1~ Y ~ T LQ~;
Th~ ld ~f the Invention is computer systsms utilizing hierarchical 5 file structures, such as th~ hierarchical file stn~cture used in th~ UNIX operating system anvironment.
~RiLF ~ N_QF~lCH~Y~I~
1~ The obj~cts, faatures and advan~ages of th~ system of th~ pres~n~
invantion will be apparent from the following desonption in which:
FIG. t illustrates a hierarchical file system structur~;
FIG. 2 is a block diagram rspres~ntation of a UNlX-based comput3r system;
Fl~;. 3~a) is a block diagram illustrative of th~ location of th~ TFS
module syst~m in ons embodimant of th~ system of th~ present invantion;
~0 FIG. 3(b) is a block diagram illustrativs of Ihe location of the TFS
module syst~m in another embo~imant of the system of the pressnt invontion;
FIG. 4(a) and 4(b) illustrat~s a hierarchical fila syst~m and th~
25 resuRing structurs visibls to the us~r through the system of th~ pr~s~nt invention;
FIG.5 illustrates a hierarchical fil0 systsm employacl usin~ an embodiment of the system of the pr~sent invention including shared layers and vafiant layers; and ~ IG. 6 further illustrates the embodiment o~ th~ systen of the pres~nt inYention described with respect to Fi~. 4.
~ ,.
~RI E~A~K~E3Qulyv,~
Computer systems availabla ~oday rangs in cos~ and sophistication from low cost micro-processor p~rsonal computers ~o sophisticated, high cost mainframe computers. However, fhB computer systems can ba said to include 5 the same basic c~mponents: al least one central processin~ unit (CPU) which controls the performance of computer operations, inpuVoutput units which controlth~ input and output of informa~ion within and out of the computar system, and memory or storage space which stores information us~d by the CPU to perSorm computer operations.
The CPU is controlled by ~he operating system which dictates how certain computer operations are to bs performed. One ponion of the operating system is the file system rnodule which deterrnines and controls the file stn~ctura in ths computer syst~m.
On~ type sf file structure in use is rsferred to as a hierarchical f!le structure. In a hierarchical fiie s~n~cture filss are or~anized into a tree structure commencing with a single root node often r~ferred to as th0 ~root~. One or more nodes may then bs connsctcd to the root and one or more nodes may bs 20 conneetad to each node. Every non-leaf node of ~he fil~ system stn~cturs, that is a node which has another node connected to it, is a directory of ~1~8; and ths files at tho leaf nodes of the tree are cithar directories, regular files, or a special lyps of file such as a device file.
:
' :
Q F ~tl E 1~ Y ~ T LQ~;
Th~ ld ~f the Invention is computer systsms utilizing hierarchical 5 file structures, such as th~ hierarchical file stn~cture used in th~ UNIX operating system anvironment.
~RiLF ~ N_QF~lCH~Y~I~
1~ The obj~cts, faatures and advan~ages of th~ system of th~ pres~n~
invantion will be apparent from the following desonption in which:
FIG. t illustrates a hierarchical file system structur~;
FIG. 2 is a block diagram rspres~ntation of a UNlX-based comput3r system;
Fl~;. 3~a) is a block diagram illustrative of th~ location of th~ TFS
module syst~m in ons embodimant of th~ system of th~ present invantion;
~0 FIG. 3(b) is a block diagram illustrativs of Ihe location of the TFS
module syst~m in another embo~imant of the system of the pressnt invontion;
FIG. 4(a) and 4(b) illustrat~s a hierarchical fila syst~m and th~
25 resuRing structurs visibls to the us~r through the system of th~ pr~s~nt invention;
FIG.5 illustrates a hierarchical fil0 systsm employacl usin~ an embodiment of the system of the pr~sent invention including shared layers and vafiant layers; and ~ IG. 6 further illustrates the embodiment o~ th~ systen of the pres~nt inYention described with respect to Fi~. 4.
~ ,.
~RI E~A~K~E3Qulyv,~
Computer systems availabla ~oday rangs in cos~ and sophistication from low cost micro-processor p~rsonal computers ~o sophisticated, high cost mainframe computers. However, fhB computer systems can ba said to include 5 the same basic c~mponents: al least one central processin~ unit (CPU) which controls the performance of computer operations, inpuVoutput units which controlth~ input and output of informa~ion within and out of the computar system, and memory or storage space which stores information us~d by the CPU to perSorm computer operations.
The CPU is controlled by ~he operating system which dictates how certain computer operations are to bs performed. One ponion of the operating system is the file system rnodule which deterrnines and controls the file stn~ctura in ths computer syst~m.
On~ type sf file structure in use is rsferred to as a hierarchical f!le structure. In a hierarchical fiie s~n~cture filss are or~anized into a tree structure commencing with a single root node often r~ferred to as th0 ~root~. One or more nodes may then bs connsctcd to the root and one or more nodes may bs 20 conneetad to each node. Every non-leaf node of ~he fil~ system stn~cturs, that is a node which has another node connected to it, is a directory of ~1~8; and ths files at tho leaf nodes of the tree are cithar directories, regular files, or a special lyps of file such as a device file.
:
' :
2 ~ ~ :
f.`
In a par~icular herarchical fjIB ~ystem, the name of ths file is ths path name that describes how to locat~ the file in ~h~ syst~m hierarchy. A path name is a sRqu~nce of component nam~s s~parat~d by th~ ur characier. A full path 5 nama starts with a ~r character which specifiQs that a fila is found by starting at the fil~ system root and traversing th~ file tree, following the branches that Isad to successive paths~ For example, the path name /usr/src/cmd~wo~c follows a path such as that shown within the box in Fig. 1 and designates the two.c file label~d in th~ iree shown~
In the software devalopm~nt environm~n~, num~rous comput~r programm~rs may b~ working concurrently on a single program or a ~roup of programs which are interrelated and operate together. It is quite desirabl~ thatthe work be done simultaneously so that it may be completed in th~ shortest amount of time. Typically, each software programmer makes a copy of those fiies in the por~ion of the file structure he is working in and works on those particular ~pies to achieve his goal~ Thus, if a product consists of twenty pro~rams, ~ach programmer may have a copy of thoss twenty programs in his user area.
The probl3m with this arrang~ment is ~hat ~ach programmer must usually work with a lar~ number of files in oraisr to work on a singls file~
Consaqu~ntly, muitipla copies of th~se fil~s ~xist in numerous places on the system, raquiring a large amount of disk memory space and adàing to the complaxity of th~ arrangem~nt and the ident;fication of tha fil~s~ Furthsrrnor~, it is 2s quite ~asy to los~ track of or con~use old~r versions pro~rams with the current ~rarsions of programs~ For ~xample, programmor one may be working on certain portions of a pro3ram that has a revision date of May, and programmer two may be working on a program ~hat has a r0vision date of Jun~ Thus the chan~s mad~ b~ ~ither programmer ars con~ained in differ~nt vsrsions; and, in or~er to incorporate th~ new software developod by the pro~rammars, th~ code must be 1 323~48 incorporated into the latest version of ths code, a repetitive and cumbarsome tas~ `
~ :
: : :
, . , : . .
~;UMMARY l:)F~l~LELyDQl~l It is, therefore, an object of the present inven~ion to provide a Gomputer system which contains a fil9 structure and system compfising a private 5 fils hisrarchy and a shared nle hierarchy, th3 private hierarchy cQntaining thos~
files which only the private user has modified.
It is ~urther an objec~ of th0 present invention to provids a computer system in which shared files are writtan into a private user fil~ automatically if the 0 user attempts 10 modify the file.
It is another object of the present inv~ntion to provide a computer syst~m in which files may b~ accessed by a common nams regardless of the location of th~ file in tha file structure.
It is an additional object of the present imfention to provide a computer system in which a file directory contains both shar~d and private files~
In the computer system of the pr0sent invention, the opsratin~
20 systsm compris~s a ~ranslucent file system module (TFS) which permits users of the computer system to share a file hierarchy and also to hav~ a private fila hisrarchy in which ~lles from the sharsd hierarchy are copied into the private hl~rarchy only as they ar~ modified, a fsature rsferred to as a ~copy-on-write~
procedure. Writing is done only in the private hi~rarchy. Thus, individual users25 ara isolated from changes made by o~h~rs bocause files in the sharod hierarchy are ~uaranteed not tQ change~ In addition! fi~s are only copied whon th~y ar~
modified; until modified, the shared files ara utiliz~d. Consegu~ntly, a si~nifican~
amount of disk space is cr nserved.
i. ~
`?" . . . ~ .
1 3234~8 A directory seen through lhe TFS appears to the user as a single directory, but actually comprises listings for files for directories which may exist in a number of layers.- Each layer is a physical directory, and the layers are joinsd by what are r~ferred to as search links. Each layer has a scarch link S associated with it which contains the directory name of ths next layer behind it.
The first layer seen through the TFS is considered to be ~he front layer, and layers found ~y following the search links from this iayer are considered to be behind the front layer in what are referred to as th~ "back layers". The files show through from back layers unless ~h~ same files exist in a laysr in front to mask the 10 filss in the back layers. Therefore, it can bs said tha~ the fr~nt layer is ~ranslucent or selectively transparent, ,~ .?
1 32344~
~ETAILED ~i~lPT1ON OF TH~ I~V~lQ~I
In ths system of the present invention, a file system is providad comprising a Translucent File System module (TFS), which provides users wi~h a 5 sharQd filQ hierarchy and a pnvate hierarchy in which shar~d files edited by the user are automatioally copied into the user~s pnvate hierarchy. By msans of the TFS module, search links are formad for each directory. The ssarch link for a - directory comprises a pointer stored in the layer with a diractory ~hich points to the next directory which is in the next layar behind the directory. Therefore, files 0 can ba access~d from directories or layers which are behind the front layer by examining the layer identilied through the search links.
The physical layers may b~ located in one location of msmory or storage on one computer system or at multiple locations situated on multiple computer systems linked together through a computer network. Whenever a user or a process accessss a file, the TFS module causes the most current version of the file to be presented for access. Furthermore, if a user requests a directorylisting, the TFS module causes a directory listing to be displayed, listing only the most current versions of the files found among the directories linked toge~her 20 through search links. The files listed may be shared files looated in differ~nt back layers or 1he files may be private fil~s, private to ths ussr and located in the front layor~
On~ operating system which us~s a hi~rarchical file structure is the 2s UNIXe \ (UNIX is a ragistercd trademark of AT&T) op~ralin~ sys~m initially dsvelop~d by Bsll Laboratorics. Although the preferred 3mbodim~nt is described in a UNIX operatin~ systam enYironment, it is eviderlt that the systemof the present invention may be applied to other operatin~ systems employing a hi~rar~hical file structure.
82225~Pû51 7 .
In a lUNlX-based system, the operatin~ system interacts directly with the hardware providin~ common servicas to programs and isolatin~ ths software and users from ths hardware idiosyncrasies of a particular computsr syst~m. Viewin~ the systam as a set of layers, the operating system is commonly 5 called th0 ~system k~rnel~ or just ~kernel~, ~mphasizing its isolation from 1he user programs. Because the programs are independent of the und~rlying hardware, it is easy to move the programs between UNIX systems running on differ~nt hardware. Tha UNIX file system, located within the ksrnel, organizes ~he file structures.
The kernsl is depicted generally in Figure 2 which shows three IRVQIS: user/programs, kernel and hardware. The system call and library interface reprssents the border or interface between programs and the kernel.
The system calls are divided into those system calls that interface with the file 15 system and those that interact with the process control system. The process control system is responsible for process synchronization, interprocess communication, memory management and process scheduling. The file system manages flles, allocates files space, administers free space, controls access tofiles and retrisv~s data for users and programs.
One ~mbodiment of the system of the present invention is reali7ed in tha system illustrat~d in Figure 3(a3. The kernel 60 interfàcss to the us3rlprograms at the user level 70 and the hardware at the hardware lcval 80.
ThQ fil~ system comprises a file system interfaGe 90 which rec~ives the fils 2s system commands and datermines wh0ther the current directory to be accsssQd Is a TFS dirsctory. This is preferably achievad by storin~ a tabl0 or file accessible by the fils system intsrface 90, which identifies thoss directorias or file systems which are to bs accessed through Ih~ TFS modul0.
~;æ25~P~sl 8 .
.
One UNlX-based system is the SUNOS (Sun Op~rating Syst~m), produc~d ~y Sun MicrosystQms, Inc., Mountain View, California. This operatin~
systsm includes in its most recent versions, a Network Fila System ~hereinafter NFS). The NFS is further described in a paper entitlad C)e~iQn~n~
5 Impl~ ~atit?n nf ~e ~or~ FD~L~m, Sandberg et al, publishsd by Sun Microsystems Inc. Associated with the NFS is a Vir~ual Fila System (hsrsinaf~Qr VFS). The VFS is a file interface architecture for accomodating muitiple file systems within the SUNOS kemel. In particular, the YFS provides a fils system int~rface which supports local disk file syst~ms such as the 4.2BSD
10 file systsm, statelsss remote file systems such as NFS, stat~full r~mote fil~ systems such as AT~rs RFS, or non-UNlX file systems such as MSDOS. Tha VFS is further described in a paper entitled Vnodes: An~rchit~ re ~r ~ulti~le Fil~ ~ystem Ty~es in Sun UNIX, S. R. Kleinman, published by Sun Microsystsms, Inc.
The VFS allows the mounting of different file systsms which require different mount data. To accomplish this, in using the system mount command, the fil~ system hype, the directory which is th~ mount point, th~ dir~ctory to bs mountsd, various generic flags such as "read only," and a point~r to th~ filQ
20 system specific type dataar~ provided. Th~ mount system command accepts as one of its file system types the d~signation TFS.
Thus, th~ fil~ system may be identified to be a nTFS hype" by the user whQn the dircctory or file system is mounted. The "rnount" command 25 attachas a nam3d file system to a file system hierarchy which is identified by a path name l~a~ion (e.g. ~/usr/srcR~. For oxample, if a first file systcm ~Jaaa/bbb/ccc" is mounted on a second tile system "/usrlsrc~ ~he resulting file syst~m consists of R/usrtsrctaaa/bbb/ccc". This pathnam~ for the fil0 system to be attached is the pathnams which designat~s th~ frontmost writable dir~ctory in30 the TFS system.
a222s.Pos1 9 t 3234~8 lS the current siirectory is a TFS direc~ory, then any directory command to be executed is executed ~hrough the TFS module 95. Otherwise th~
command is executed by the non-TFS module, h~reinafter referred to as the 5 ~generic fil~ system moduls~ 120. If the command is to b~ ~xecuted through thaTFS module system 95, tha TFS modul0 under control of a TFS servar process (a user program) makes requests throu~h the generic file system module 120 which provides th~ proper command - to the hardware control system 110 for causing ths hardware 100 ~o execut~ th~ commands. The TFS module system 95, upon lO recQipt of a command, such as on~ ~or reading ~ file or for providing a listing of thQ directory, utilizes the search links from the designated direc~ory and oth~rfeatures particular to the TFS file syst~m in orcier to access the most current version of the file or files that may be located in the multipls layers in ths file system.
A second embodiment of the inv~ntion which minimizes the modi~ications to the kernel is shown in Figure 3(b). In this embodiment, ths TFSfile syst~m module is connect~d through a pre-existing file syst~m module such as the Network FjlQ System Module ~NFS) which is connected to the file system 20 interface as a server. The NFS module directs the command to the NFS serv~r that it is bcund to, and for the purpos~s of TFS, tho TFS module is the file ser~er.
Th~refor~, the system commands are dir~ctQd to the TFS moduls. Since the commands for operating th~ NFS modul~ are already in tha kernol, when the TFS
acts as an NFS S3rvQr the kernel does not have to be modifi~d. Thus, commands ~s ~elevant to a TFS file system ar~ first dirQcted to th~ NFS modul~ whera they are forwarded to be exQcuted through tha TFS ~nodul~. The TFS modul6 then provides th~ layer directories in the mann~r d~scribed.
In either cmbodiment of the invention, the user has a single private 30 front layer. The name of the directory ~or th~ front lay0r is specified at mount tims ~22~.P051 1 0 .
1 323~48 and sent to the TFS server process. The TFS servar process lhen follows the search links from the designated front layer to determine the rest of the layers.
The searchlinks are originally established by software commands ~acquire" and "preservs" in the Network Software Environment, utilities that Nn on the SUNOS;
5 obviously, o~her commands might be used in other systems. These c~rnmands are used when a file is first viewed by a user and point ~o the next back layer.
As explained, in the preferred embodiment the search links for a file system are in a file associated with a directory and id~ntily the next back 0 directory for the layer in back of a particular directery. In effect, a directory is designated as Iying in a back layer by the search links pointing to it. When thesearch links are established, the files in that back directory are designated asread-only by the TFS server process. Although it is preferred that the search link for each directory be located in a file associated with that directory, the15 search links for the entire file system might be located in a single file situated in a central location such as the root directory of the file system. The search linksidsntify the diractories of shared files located in the back layers. The files are designated ~shared" simply because of the search links which have been esta~lished.
~o When a TFS module receivss a command to be ex0cuted, such as ~list a particular tile", the TFS directory idsntifisd in th~ command, which by d~fault is the front lay~r, is ~xamined first to determina if the file requested is locat~d in the front layer. If th~ file is not located in ths front layer, the TFS
25 module taads 1he ~ile containing the search link and examines the files in the directory identifiQd in the search link. This process continuas until the last directory identified through search links is read or until the file is found. If the file requested is found, it is identified to the ussr in the same mannsr as if it wastocated in the use~s current directory, i.e. the front layer, ~ven through the flle 30 may ba located on a back layer numerous layors behind the front layer~ This 82225.Po51 - 11 sntire oparation of searching multiple layers or directories is transparen~ ~ Sh~
user.
Fi~. ~ illustra~es thr~e layars lO, 20 and 30 conn~ct~d by searoh 5 links 40 and 45 containing differsnt versil~ns of files en~.c, two.c, and thr~e.c.
Layer 30 is ths privatc layer and contains files one.c3 and thrae.c1 indicating the most current version with respect ~o the user of those files. Th~ files ons.c3 and two.cl arc private files signifying that ~ha us~r had either created the files or had modified th~ shared versions of the files. The layer directly behind the pri~ate10 layer 30, is layQr 20. This is a shared layer and contains ~he file one.c2, an earliQr version of one.c3. Fil~ ene.c~, was copi~d automatically into layer 30 when the user msdified or wrots on th~ fiie. Connected by search link 4û is shared layer 10 which is behind layer 20. Shared layer 10 contains filPS one.cl which is an earlier version of one.c2 and fil~ two.c1. Using the TFS modul~ of the l5 prasent invention, th~ resultin~ file structure, that is the file structur~ visible te and accessibla by the user is a single directory, a singls layer containing files one.c3, two.c1 and three.c~. This is illustrated in Fiy. 4(b) in which the filesone.c3 ~nd thre~.cl originated from the private layer 30 and ~ile two.c1 originated from the shared back layer 10. Thus, i~ can be seen that the compl~xities of 20 multiple layers are isolated from the user of the syst~m. Furtharrnore, the shared fil~s locat~d in the back layers ara protscted from modification by a user by the copy-on-writQ ~eature which automatically copies a fil~ into th~ user's priva~e front lay~r when the ussr attempts to modify th~ fil~.
Becaus~ the back laycrs are read only and th~ privat~ lay~r i~ the only layer which is r~ad and write acc~ssible, fll~s may only b0 deleted from the private layer. However, if the user has no naed for oertain files that are located in back layers, ths user can effcctively dslsts those flles through a "white out"
~unction. The white-out ~unction causes a flle which would othenNis3 be ~0 displayed whan a user r~vi~ws his directory, to be mask~d-ou~ and not visible or R~2~5 Posl 1 2 accessibl~ to th~ user. A file is provided in which ~he white-out antries are listed.
Tha file is referred to by the TFS module to determine whether a particular ~ile is to bs masked or "whitad out' when file sys~em operations are performed. The white out entries for a file system may be stored in a single file in the root 5 directory of the file system. Alternatively, the file containing the whiteTout entries for a dirsctory may be stored in each directory or the white-out entries may be incorporated into the same file containing the search link. In a pre~erred embodiment, commands may be included for listing the flles subject ~o the whitaout command and for removing the whiteout îndication for a particular file.
In another embodiment of the system of the present invention, conditional search links are provided. A conditional search link can point to more than one directory, wherein the directory pointed to is dependent on the variant ùsed. To accomplish this resuH, each ssarch links provides a string of 15 characters which indicate that there are variants of the search link. In use, the TFS module determines which variant to use from the ~ile system designation givan at th~ mount command, and the string is replaced by the TFS module with a proper variant name to read thc proper search link to yield the name of the nextback layer~
These conditional search links arc particularly helpful where numerous identical source filas are used for differant vcr~inns of operating systems sinc~ each version is then capable of compiling its own object code from the same source code~
Referring to Fig. 5, there are two variants, sys3 and sys4 which are used on two separate hardware architecturcs~ There are two r~visions, revision 1 and 2; and each revision has a variant layar ~or each of the sys3 and sys4 variants and a layer 210 shared batwean tho two variants. The sys3 ~nd sys4 30 variants both have layers in revision two 20û, 205 with search links to the shared a2225~P051 1 3 layer for revision iwo 21 0. The shar~d layer 210 has a conditional search link 215 to $view Rev1. In the preferred embodiment, the ~$view" is the indication used for a conditional search îink. When ~ha user looks at the sys3 variant thisconditional search iink points to the sys3 revision one layer 220 and if the user 5 looks at the sys4 variant the search link points to the sys4 revision one layer 225.
The sys3 and sys4 r~vision one layers 220, 22~ have regular, that is, unconditional search links 230, 235 to the shared lay~r for r~vision ons 240.
The conditional search links and ~h~ shared layers aliow files to b9 shared by different variants so that the source files in the shared layer will be seen in both lO sys3 and sys4 variants.
Additionally, protection is provided to prevent a user operatin~ in one variant from modifying a source file from a shared layer such that the file is c~pied to ths front layer which is varian~ specific. If this occurs, the source file is 1S no-longer ~hared because the most currant version o~ the source file is in a users front layer which is variant specific and is no longsr in the iay~r sharedamong the varianls. It is therefore preferable that the rnost current version of the source filss stay in the shared lay~r even when it is modified. This ~atura is achi~vad by providing a front layer comprising sub-layers: a sharad sub-layQr 20 and a su~-layer for each variant. Thus, any modification performed with respect to a shared or variant sub-layer is maintained in the particular sub-layer. If a flle ts found in ~ither of the two front sub-layars, the file will ba modified in that ~ub-lay~r. ~his is Tllustrated in Flg~ 6~ If fila one~o in ths revision two shared layer 205, which is the front layer, is modifi~d by a user who is operatin~ und0r ~ha ~S sys3 Yariant, the fila will not bs copi~d to th~ revision two vafiant sub-layer 210;
insi~ad the ffle will remain in th~ rsvision ~wo shared sub-lay~r 205~
Furtharmore, wh~n a file is created, it is created in the ~ront vafiant su~layerunless the file name has appsared in th0 shar~d sub-lay~r wh~reby th~ tile is crsatac~ in ths ~ront shared sub-layer. The preservation of the sub-layers also 30 appli~s to the copy on write function of back layers as well; if a file to be modified 82æ~.P051 1 4 is found in the shared sub-layer of a back layar that file will b~ copiad to thesharcd sub-layer of the front layer. It a file to bc modified is found in a vanant sub-layer, it will be copied to the varian~ sub-layer of th~ front layar.
For example, referring to Fig. 6, i~ the file two.c 215 in the r~vision one shar~d layer 2~0 is modifie~, it is copied to the shared sub-lay~r o~ revision two 205. However, if the fiie ~wo.0 is modifiad, it is copisd to the variant sub-layer o~ revision two 210. Thus, only one front wriiable layer exis~s, but the layer comprises multipl~ sub layers reflecting shared variant sub-layers.
One problem with the invention disclosed to this point is that as the numbQr of back layers increase, so do the number of search links and the amount of time to perform a ~ile system function such as listing the contents of the directory which requires reading numerous directories and s~arch link ~iles until the last back laycr is reached. Consequ~ntly, in another embodiment of th~
system o? the prasent invention, a fil~ look-up cach~, referred to as a "back tile", is utilized to accelerate file look-up and directory read tunctions.
To minirnize tha amount of time and ths number of operations 20 required to pcrform operations with respect to a multi-layered file syst~m, back files are uscd. The back file for a directory contains a list of all the rsad-only files in thQ til~ system and tha path names of the back lay~rs the fil~s are found in.Thus, to raad a directory, the TFS syst~m ne~ds only to rsad tho directory ~ntries of the front layer and the back flls for that diractory located in thc front lay~r to ~s ~etsrmine th~ nam~s and the actual locations ot th~ files in a ~l~ system.
Furthermore, a ?ile locatcd in a back layGr can be directly accessed simply by detsrmining the location through the back fil~. Thc back filo is always accurat~bccausa the back layers ars rsad only; that is, th~ s in ths back lay~r cannot changs so once a tile is placed in a back laysr, i~ remains in thc back layer.
82225.P0~1 1 5 ~ 32344~
The back files are wntten by the TFS process server when a user looks up a file in a TFS directory or reads a TFS directory; i~ at that time no back file exist for the directory, one is ereated. Normally, this is a simpl~ processbecause there is usually a back file ~r the dirsctory of the next layer back which 5 ~an ba used to construct the new back file for the front layer. Thus, usually only the first read-only layer has to be read for its contents since the looations of the rest of the read-only files can be determined from the back file in the first read-only layer.
While the invention has baan dsscribed in conjunc~ion with preferred embodiments, it is ~vident that numerous alternativas, modifications, variations and usas will be apparent to those skilled in the art in light of theforegoing description.
f.`
In a par~icular herarchical fjIB ~ystem, the name of ths file is ths path name that describes how to locat~ the file in ~h~ syst~m hierarchy. A path name is a sRqu~nce of component nam~s s~parat~d by th~ ur characier. A full path 5 nama starts with a ~r character which specifiQs that a fila is found by starting at the fil~ system root and traversing th~ file tree, following the branches that Isad to successive paths~ For example, the path name /usr/src/cmd~wo~c follows a path such as that shown within the box in Fig. 1 and designates the two.c file label~d in th~ iree shown~
In the software devalopm~nt environm~n~, num~rous comput~r programm~rs may b~ working concurrently on a single program or a ~roup of programs which are interrelated and operate together. It is quite desirabl~ thatthe work be done simultaneously so that it may be completed in th~ shortest amount of time. Typically, each software programmer makes a copy of those fiies in the por~ion of the file structure he is working in and works on those particular ~pies to achieve his goal~ Thus, if a product consists of twenty pro~rams, ~ach programmer may have a copy of thoss twenty programs in his user area.
The probl3m with this arrang~ment is ~hat ~ach programmer must usually work with a lar~ number of files in oraisr to work on a singls file~
Consaqu~ntly, muitipla copies of th~se fil~s ~xist in numerous places on the system, raquiring a large amount of disk memory space and adàing to the complaxity of th~ arrangem~nt and the ident;fication of tha fil~s~ Furthsrrnor~, it is 2s quite ~asy to los~ track of or con~use old~r versions pro~rams with the current ~rarsions of programs~ For ~xample, programmor one may be working on certain portions of a pro3ram that has a revision date of May, and programmer two may be working on a program ~hat has a r0vision date of Jun~ Thus the chan~s mad~ b~ ~ither programmer ars con~ained in differ~nt vsrsions; and, in or~er to incorporate th~ new software developod by the pro~rammars, th~ code must be 1 323~48 incorporated into the latest version of ths code, a repetitive and cumbarsome tas~ `
~ :
: : :
, . , : . .
~;UMMARY l:)F~l~LELyDQl~l It is, therefore, an object of the present inven~ion to provide a Gomputer system which contains a fil9 structure and system compfising a private 5 fils hisrarchy and a shared nle hierarchy, th3 private hierarchy cQntaining thos~
files which only the private user has modified.
It is ~urther an objec~ of th0 present invention to provids a computer system in which shared files are writtan into a private user fil~ automatically if the 0 user attempts 10 modify the file.
It is another object of the present inv~ntion to provide a computer syst~m in which files may b~ accessed by a common nams regardless of the location of th~ file in tha file structure.
It is an additional object of the present imfention to provide a computer system in which a file directory contains both shar~d and private files~
In the computer system of the pr0sent invention, the opsratin~
20 systsm compris~s a ~ranslucent file system module (TFS) which permits users of the computer system to share a file hierarchy and also to hav~ a private fila hisrarchy in which ~lles from the sharsd hierarchy are copied into the private hl~rarchy only as they ar~ modified, a fsature rsferred to as a ~copy-on-write~
procedure. Writing is done only in the private hi~rarchy. Thus, individual users25 ara isolated from changes made by o~h~rs bocause files in the sharod hierarchy are ~uaranteed not tQ change~ In addition! fi~s are only copied whon th~y ar~
modified; until modified, the shared files ara utiliz~d. Consegu~ntly, a si~nifican~
amount of disk space is cr nserved.
i. ~
`?" . . . ~ .
1 3234~8 A directory seen through lhe TFS appears to the user as a single directory, but actually comprises listings for files for directories which may exist in a number of layers.- Each layer is a physical directory, and the layers are joinsd by what are r~ferred to as search links. Each layer has a scarch link S associated with it which contains the directory name of ths next layer behind it.
The first layer seen through the TFS is considered to be ~he front layer, and layers found ~y following the search links from this iayer are considered to be behind the front layer in what are referred to as th~ "back layers". The files show through from back layers unless ~h~ same files exist in a laysr in front to mask the 10 filss in the back layers. Therefore, it can bs said tha~ the fr~nt layer is ~ranslucent or selectively transparent, ,~ .?
1 32344~
~ETAILED ~i~lPT1ON OF TH~ I~V~lQ~I
In ths system of the present invention, a file system is providad comprising a Translucent File System module (TFS), which provides users wi~h a 5 sharQd filQ hierarchy and a pnvate hierarchy in which shar~d files edited by the user are automatioally copied into the user~s pnvate hierarchy. By msans of the TFS module, search links are formad for each directory. The ssarch link for a - directory comprises a pointer stored in the layer with a diractory ~hich points to the next directory which is in the next layar behind the directory. Therefore, files 0 can ba access~d from directories or layers which are behind the front layer by examining the layer identilied through the search links.
The physical layers may b~ located in one location of msmory or storage on one computer system or at multiple locations situated on multiple computer systems linked together through a computer network. Whenever a user or a process accessss a file, the TFS module causes the most current version of the file to be presented for access. Furthermore, if a user requests a directorylisting, the TFS module causes a directory listing to be displayed, listing only the most current versions of the files found among the directories linked toge~her 20 through search links. The files listed may be shared files looated in differ~nt back layers or 1he files may be private fil~s, private to ths ussr and located in the front layor~
On~ operating system which us~s a hi~rarchical file structure is the 2s UNIXe \ (UNIX is a ragistercd trademark of AT&T) op~ralin~ sys~m initially dsvelop~d by Bsll Laboratorics. Although the preferred 3mbodim~nt is described in a UNIX operatin~ systam enYironment, it is eviderlt that the systemof the present invention may be applied to other operatin~ systems employing a hi~rar~hical file structure.
82225~Pû51 7 .
In a lUNlX-based system, the operatin~ system interacts directly with the hardware providin~ common servicas to programs and isolatin~ ths software and users from ths hardware idiosyncrasies of a particular computsr syst~m. Viewin~ the systam as a set of layers, the operating system is commonly 5 called th0 ~system k~rnel~ or just ~kernel~, ~mphasizing its isolation from 1he user programs. Because the programs are independent of the und~rlying hardware, it is easy to move the programs between UNIX systems running on differ~nt hardware. Tha UNIX file system, located within the ksrnel, organizes ~he file structures.
The kernsl is depicted generally in Figure 2 which shows three IRVQIS: user/programs, kernel and hardware. The system call and library interface reprssents the border or interface between programs and the kernel.
The system calls are divided into those system calls that interface with the file 15 system and those that interact with the process control system. The process control system is responsible for process synchronization, interprocess communication, memory management and process scheduling. The file system manages flles, allocates files space, administers free space, controls access tofiles and retrisv~s data for users and programs.
One ~mbodiment of the system of the present invention is reali7ed in tha system illustrat~d in Figure 3(a3. The kernel 60 interfàcss to the us3rlprograms at the user level 70 and the hardware at the hardware lcval 80.
ThQ fil~ system comprises a file system interfaGe 90 which rec~ives the fils 2s system commands and datermines wh0ther the current directory to be accsssQd Is a TFS dirsctory. This is preferably achievad by storin~ a tabl0 or file accessible by the fils system intsrface 90, which identifies thoss directorias or file systems which are to bs accessed through Ih~ TFS modul0.
~;æ25~P~sl 8 .
.
One UNlX-based system is the SUNOS (Sun Op~rating Syst~m), produc~d ~y Sun MicrosystQms, Inc., Mountain View, California. This operatin~
systsm includes in its most recent versions, a Network Fila System ~hereinafter NFS). The NFS is further described in a paper entitlad C)e~iQn~n~
5 Impl~ ~atit?n nf ~e ~or~ FD~L~m, Sandberg et al, publishsd by Sun Microsystems Inc. Associated with the NFS is a Vir~ual Fila System (hsrsinaf~Qr VFS). The VFS is a file interface architecture for accomodating muitiple file systems within the SUNOS kemel. In particular, the YFS provides a fils system int~rface which supports local disk file syst~ms such as the 4.2BSD
10 file systsm, statelsss remote file systems such as NFS, stat~full r~mote fil~ systems such as AT~rs RFS, or non-UNlX file systems such as MSDOS. Tha VFS is further described in a paper entitled Vnodes: An~rchit~ re ~r ~ulti~le Fil~ ~ystem Ty~es in Sun UNIX, S. R. Kleinman, published by Sun Microsystsms, Inc.
The VFS allows the mounting of different file systsms which require different mount data. To accomplish this, in using the system mount command, the fil~ system hype, the directory which is th~ mount point, th~ dir~ctory to bs mountsd, various generic flags such as "read only," and a point~r to th~ filQ
20 system specific type dataar~ provided. Th~ mount system command accepts as one of its file system types the d~signation TFS.
Thus, th~ fil~ system may be identified to be a nTFS hype" by the user whQn the dircctory or file system is mounted. The "rnount" command 25 attachas a nam3d file system to a file system hierarchy which is identified by a path name l~a~ion (e.g. ~/usr/srcR~. For oxample, if a first file systcm ~Jaaa/bbb/ccc" is mounted on a second tile system "/usrlsrc~ ~he resulting file syst~m consists of R/usrtsrctaaa/bbb/ccc". This pathnam~ for the fil0 system to be attached is the pathnams which designat~s th~ frontmost writable dir~ctory in30 the TFS system.
a222s.Pos1 9 t 3234~8 lS the current siirectory is a TFS direc~ory, then any directory command to be executed is executed ~hrough the TFS module 95. Otherwise th~
command is executed by the non-TFS module, h~reinafter referred to as the 5 ~generic fil~ system moduls~ 120. If the command is to b~ ~xecuted through thaTFS module system 95, tha TFS modul0 under control of a TFS servar process (a user program) makes requests throu~h the generic file system module 120 which provides th~ proper command - to the hardware control system 110 for causing ths hardware 100 ~o execut~ th~ commands. The TFS module system 95, upon lO recQipt of a command, such as on~ ~or reading ~ file or for providing a listing of thQ directory, utilizes the search links from the designated direc~ory and oth~rfeatures particular to the TFS file syst~m in orcier to access the most current version of the file or files that may be located in the multipls layers in ths file system.
A second embodiment of the inv~ntion which minimizes the modi~ications to the kernel is shown in Figure 3(b). In this embodiment, ths TFSfile syst~m module is connect~d through a pre-existing file syst~m module such as the Network FjlQ System Module ~NFS) which is connected to the file system 20 interface as a server. The NFS module directs the command to the NFS serv~r that it is bcund to, and for the purpos~s of TFS, tho TFS module is the file ser~er.
Th~refor~, the system commands are dir~ctQd to the TFS moduls. Since the commands for operating th~ NFS modul~ are already in tha kernol, when the TFS
acts as an NFS S3rvQr the kernel does not have to be modifi~d. Thus, commands ~s ~elevant to a TFS file system ar~ first dirQcted to th~ NFS modul~ whera they are forwarded to be exQcuted through tha TFS ~nodul~. The TFS modul6 then provides th~ layer directories in the mann~r d~scribed.
In either cmbodiment of the invention, the user has a single private 30 front layer. The name of the directory ~or th~ front lay0r is specified at mount tims ~22~.P051 1 0 .
1 323~48 and sent to the TFS server process. The TFS servar process lhen follows the search links from the designated front layer to determine the rest of the layers.
The searchlinks are originally established by software commands ~acquire" and "preservs" in the Network Software Environment, utilities that Nn on the SUNOS;
5 obviously, o~her commands might be used in other systems. These c~rnmands are used when a file is first viewed by a user and point ~o the next back layer.
As explained, in the preferred embodiment the search links for a file system are in a file associated with a directory and id~ntily the next back 0 directory for the layer in back of a particular directery. In effect, a directory is designated as Iying in a back layer by the search links pointing to it. When thesearch links are established, the files in that back directory are designated asread-only by the TFS server process. Although it is preferred that the search link for each directory be located in a file associated with that directory, the15 search links for the entire file system might be located in a single file situated in a central location such as the root directory of the file system. The search linksidsntify the diractories of shared files located in the back layers. The files are designated ~shared" simply because of the search links which have been esta~lished.
~o When a TFS module receivss a command to be ex0cuted, such as ~list a particular tile", the TFS directory idsntifisd in th~ command, which by d~fault is the front lay~r, is ~xamined first to determina if the file requested is locat~d in the front layer. If th~ file is not located in ths front layer, the TFS
25 module taads 1he ~ile containing the search link and examines the files in the directory identifiQd in the search link. This process continuas until the last directory identified through search links is read or until the file is found. If the file requested is found, it is identified to the ussr in the same mannsr as if it wastocated in the use~s current directory, i.e. the front layer, ~ven through the flle 30 may ba located on a back layer numerous layors behind the front layer~ This 82225.Po51 - 11 sntire oparation of searching multiple layers or directories is transparen~ ~ Sh~
user.
Fi~. ~ illustra~es thr~e layars lO, 20 and 30 conn~ct~d by searoh 5 links 40 and 45 containing differsnt versil~ns of files en~.c, two.c, and thr~e.c.
Layer 30 is ths privatc layer and contains files one.c3 and thrae.c1 indicating the most current version with respect ~o the user of those files. Th~ files ons.c3 and two.cl arc private files signifying that ~ha us~r had either created the files or had modified th~ shared versions of the files. The layer directly behind the pri~ate10 layer 30, is layQr 20. This is a shared layer and contains ~he file one.c2, an earliQr version of one.c3. Fil~ ene.c~, was copi~d automatically into layer 30 when the user msdified or wrots on th~ fiie. Connected by search link 4û is shared layer 10 which is behind layer 20. Shared layer 10 contains filPS one.cl which is an earlier version of one.c2 and fil~ two.c1. Using the TFS modul~ of the l5 prasent invention, th~ resultin~ file structure, that is the file structur~ visible te and accessibla by the user is a single directory, a singls layer containing files one.c3, two.c1 and three.c~. This is illustrated in Fiy. 4(b) in which the filesone.c3 ~nd thre~.cl originated from the private layer 30 and ~ile two.c1 originated from the shared back layer 10. Thus, i~ can be seen that the compl~xities of 20 multiple layers are isolated from the user of the syst~m. Furtharrnore, the shared fil~s locat~d in the back layers ara protscted from modification by a user by the copy-on-writQ ~eature which automatically copies a fil~ into th~ user's priva~e front lay~r when the ussr attempts to modify th~ fil~.
Becaus~ the back laycrs are read only and th~ privat~ lay~r i~ the only layer which is r~ad and write acc~ssible, fll~s may only b0 deleted from the private layer. However, if the user has no naed for oertain files that are located in back layers, ths user can effcctively dslsts those flles through a "white out"
~unction. The white-out ~unction causes a flle which would othenNis3 be ~0 displayed whan a user r~vi~ws his directory, to be mask~d-ou~ and not visible or R~2~5 Posl 1 2 accessibl~ to th~ user. A file is provided in which ~he white-out antries are listed.
Tha file is referred to by the TFS module to determine whether a particular ~ile is to bs masked or "whitad out' when file sys~em operations are performed. The white out entries for a file system may be stored in a single file in the root 5 directory of the file system. Alternatively, the file containing the whiteTout entries for a dirsctory may be stored in each directory or the white-out entries may be incorporated into the same file containing the search link. In a pre~erred embodiment, commands may be included for listing the flles subject ~o the whitaout command and for removing the whiteout îndication for a particular file.
In another embodiment of the system of the present invention, conditional search links are provided. A conditional search link can point to more than one directory, wherein the directory pointed to is dependent on the variant ùsed. To accomplish this resuH, each ssarch links provides a string of 15 characters which indicate that there are variants of the search link. In use, the TFS module determines which variant to use from the ~ile system designation givan at th~ mount command, and the string is replaced by the TFS module with a proper variant name to read thc proper search link to yield the name of the nextback layer~
These conditional search links arc particularly helpful where numerous identical source filas are used for differant vcr~inns of operating systems sinc~ each version is then capable of compiling its own object code from the same source code~
Referring to Fig. 5, there are two variants, sys3 and sys4 which are used on two separate hardware architecturcs~ There are two r~visions, revision 1 and 2; and each revision has a variant layar ~or each of the sys3 and sys4 variants and a layer 210 shared batwean tho two variants. The sys3 ~nd sys4 30 variants both have layers in revision two 20û, 205 with search links to the shared a2225~P051 1 3 layer for revision iwo 21 0. The shar~d layer 210 has a conditional search link 215 to $view Rev1. In the preferred embodiment, the ~$view" is the indication used for a conditional search îink. When ~ha user looks at the sys3 variant thisconditional search iink points to the sys3 revision one layer 220 and if the user 5 looks at the sys4 variant the search link points to the sys4 revision one layer 225.
The sys3 and sys4 r~vision one layers 220, 22~ have regular, that is, unconditional search links 230, 235 to the shared lay~r for r~vision ons 240.
The conditional search links and ~h~ shared layers aliow files to b9 shared by different variants so that the source files in the shared layer will be seen in both lO sys3 and sys4 variants.
Additionally, protection is provided to prevent a user operatin~ in one variant from modifying a source file from a shared layer such that the file is c~pied to ths front layer which is varian~ specific. If this occurs, the source file is 1S no-longer ~hared because the most currant version o~ the source file is in a users front layer which is variant specific and is no longsr in the iay~r sharedamong the varianls. It is therefore preferable that the rnost current version of the source filss stay in the shared lay~r even when it is modified. This ~atura is achi~vad by providing a front layer comprising sub-layers: a sharad sub-layQr 20 and a su~-layer for each variant. Thus, any modification performed with respect to a shared or variant sub-layer is maintained in the particular sub-layer. If a flle ts found in ~ither of the two front sub-layars, the file will ba modified in that ~ub-lay~r. ~his is Tllustrated in Flg~ 6~ If fila one~o in ths revision two shared layer 205, which is the front layer, is modifi~d by a user who is operatin~ und0r ~ha ~S sys3 Yariant, the fila will not bs copi~d to th~ revision two vafiant sub-layer 210;
insi~ad the ffle will remain in th~ rsvision ~wo shared sub-lay~r 205~
Furtharmore, wh~n a file is created, it is created in the ~ront vafiant su~layerunless the file name has appsared in th0 shar~d sub-lay~r wh~reby th~ tile is crsatac~ in ths ~ront shared sub-layer. The preservation of the sub-layers also 30 appli~s to the copy on write function of back layers as well; if a file to be modified 82æ~.P051 1 4 is found in the shared sub-layer of a back layar that file will b~ copiad to thesharcd sub-layer of the front layer. It a file to bc modified is found in a vanant sub-layer, it will be copied to the varian~ sub-layer of th~ front layar.
For example, referring to Fig. 6, i~ the file two.c 215 in the r~vision one shar~d layer 2~0 is modifie~, it is copied to the shared sub-lay~r o~ revision two 205. However, if the fiie ~wo.0 is modifiad, it is copisd to the variant sub-layer o~ revision two 210. Thus, only one front wriiable layer exis~s, but the layer comprises multipl~ sub layers reflecting shared variant sub-layers.
One problem with the invention disclosed to this point is that as the numbQr of back layers increase, so do the number of search links and the amount of time to perform a ~ile system function such as listing the contents of the directory which requires reading numerous directories and s~arch link ~iles until the last back laycr is reached. Consequ~ntly, in another embodiment of th~
system o? the prasent invention, a fil~ look-up cach~, referred to as a "back tile", is utilized to accelerate file look-up and directory read tunctions.
To minirnize tha amount of time and ths number of operations 20 required to pcrform operations with respect to a multi-layered file syst~m, back files are uscd. The back file for a directory contains a list of all the rsad-only files in thQ til~ system and tha path names of the back lay~rs the fil~s are found in.Thus, to raad a directory, the TFS syst~m ne~ds only to rsad tho directory ~ntries of the front layer and the back flls for that diractory located in thc front lay~r to ~s ~etsrmine th~ nam~s and the actual locations ot th~ files in a ~l~ system.
Furthermore, a ?ile locatcd in a back layGr can be directly accessed simply by detsrmining the location through the back fil~. Thc back filo is always accurat~bccausa the back layers ars rsad only; that is, th~ s in ths back lay~r cannot changs so once a tile is placed in a back laysr, i~ remains in thc back layer.
82225.P0~1 1 5 ~ 32344~
The back files are wntten by the TFS process server when a user looks up a file in a TFS directory or reads a TFS directory; i~ at that time no back file exist for the directory, one is ereated. Normally, this is a simpl~ processbecause there is usually a back file ~r the dirsctory of the next layer back which 5 ~an ba used to construct the new back file for the front layer. Thus, usually only the first read-only layer has to be read for its contents since the looations of the rest of the read-only files can be determined from the back file in the first read-only layer.
While the invention has baan dsscribed in conjunc~ion with preferred embodiments, it is ~vident that numerous alternativas, modifications, variations and usas will be apparent to those skilled in the art in light of theforegoing description.
Claims (16)
1. In a multi-user computer system comprising a central processing unit (CPU), an input/output unit and memory said CPU being controlled by an operating system, said operating system comprising a file system module, wherein the file system module organizes and controls access to files located on disks in the computer system, said file system module organizing files into file systems comprising directories and files organized in a hierarchical file structure, said directories containing the files, a translucent file system module which cooperates with the file system module, said translucent file system module comprising:
organizing means for structuring a designated file hierarchy into a plurality of layers whereby each layer contains at least one directory;
ordering means for creating an ordered set of layers which can be shared by any number of users, wherein the plurality of layers of the designated file hierarchy are arranged in time-of-creation sequence such that a layer containing a less recent revision of a file in the designated file hierarchy is placed below a layer with a more recent revision of the same file;
a first layering means for providing one or more front layers, each containing at least one directory, with each of the one or more front layers being controlled by a particular user of the system and not being shared with other users of the system, with files located in each of said one or more front layers being designated such that only the particular user can read from and write to the files in the particular user's front layer and each particular user's front layer being positioned in front of the ordered set of shared layers of the designated file hierarchy; and display means for displaying to a particular user, most recent revisions of files regardless of whether these files reside in the directory of the particular user's front layer or in the directories of the ordered set of shared layers, as if all of the files resided in the particular user's front directory.
organizing means for structuring a designated file hierarchy into a plurality of layers whereby each layer contains at least one directory;
ordering means for creating an ordered set of layers which can be shared by any number of users, wherein the plurality of layers of the designated file hierarchy are arranged in time-of-creation sequence such that a layer containing a less recent revision of a file in the designated file hierarchy is placed below a layer with a more recent revision of the same file;
a first layering means for providing one or more front layers, each containing at least one directory, with each of the one or more front layers being controlled by a particular user of the system and not being shared with other users of the system, with files located in each of said one or more front layers being designated such that only the particular user can read from and write to the files in the particular user's front layer and each particular user's front layer being positioned in front of the ordered set of shared layers of the designated file hierarchy; and display means for displaying to a particular user, most recent revisions of files regardless of whether these files reside in the directory of the particular user's front layer or in the directories of the ordered set of shared layers, as if all of the files resided in the particular user's front directory.
2. The translucent file system module of claim 1 wherein the ordering means for creating an ordered set of shared layers further comprises a connecting means for connecting a particular layer in the ordered set of shared layers to a layer below said particular layer by means of search links, and for connecting each of the one or more front layers to a topmost layer of the ordered set of shared layers using search links, wherein the search links are located in a directory of each layer, and comprise a path name of a directory of a layer behind the layer the search link file is located in, said path name identifying a location of a directory in the translucent file system.
3. The translucent file system module of claim 1 further comprising copying means for automatically copying a designated file from a layer of the ordered set of shared layers, into a particular user's front layer when the particular user attempts to execute a write command to the designated file, whereby the copy of the designated file in the particular user's front layer can be modified according to the write command which triggered the copy operation without the copy operation or the location of the modified copy of the designated file being evident to the particular user.
4. The translucent file system module of claim 2 wherein the means for connecting each of the one or more front layers and the ordered set of shared layers through search links comprises a means for establishing such search links when a new layer is created.
5. The translucent file system module of claim 1 further comprising routing means to direct any file system commands from the file system module with respect to the designated file hierarchy to the translucent file system module such that the commands are executed through the translucent file system module.
6. The translucent file system module of claim 1 further comprising designating means for identifying directories according to a type of variant of files contained in the directories; and accessing means for accessing files located in at least one directory of the one or more front layers and in the ordered set of shared layers, comprising identification means for identifying the type of variant of files to be accessed, wherein the particular user is provided access through the particular user's front layer directory to files located in the directories identified by a variant type requested by the particular user.
7. The translucent file system module of claim 6 wherein a search link file is located in at least one directory of each layer, said search link file comprising a variant type name which identifies a variant type of files contained in a directory located in a next lower layer and a path name identifying a location of a directory located in a next lower layer which contains files of a desired variant type.
8. The translucent file system module of claim 7 wherein the accessing means for accessing the particular user's front layer and the ordered set of shared layers further comprises means directing any file system commands from the file system module with respect to the designated file hierarchy to the translucent file system module such that the commands are executed through the translucent file system module.
9. The translucent file system module of claim 8 wherein each of the one or more front layers comprises at least a first and a second sub-layer, the first sub-layer comprising a directory containing those files which are not identified by a variant type and the second sub-layer comprising a directory containing those files identified by a variant type.
10. The translucent file system module of claim 9 further comprising copying means for automatically copying a selected file located in a layer of the ordered set of shared layers into a particular user's front layer when the particular user attempts to write the selected file, and for copying selected files which are not identified by a variant type into a directory of the sub-layer which is not identified by a variant type and for copying files which are identified by a variant type into a directory of the sub-layer identified by the variant type.
11. The translucent file system module of claim 1 wherein the file system module is distributed among a plurality of computer system connected together via a computer network such that different portions of the file system are located on different computer systems connected together via the computer network.
12. The translucent file system module of claim 1 further comprising masking means to eliminate access to an unwanted file located in a layer of the ordered set of shared layers without deleting the unwanted file such that the unwanted file may be accessed by others sharing the ordered set of shared layers, said masking means comprising:
marking means for establishing a white-out file in a particular user's front layer identifying unwanted files in a layer of the ordered set of shared layers to which access by the particular user will no longer be permitted from the particular user's front layer; and reading means for reading the white-out file and masking out any unwanted file listed in the white-out file when any operation is performed involving the file system such that a masked unwanted file is invisible to the particular user of the system when viewed from the layer containing the white-out file or from any layer above a layer containing the white-out file.
marking means for establishing a white-out file in a particular user's front layer identifying unwanted files in a layer of the ordered set of shared layers to which access by the particular user will no longer be permitted from the particular user's front layer; and reading means for reading the white-out file and masking out any unwanted file listed in the white-out file when any operation is performed involving the file system such that a masked unwanted file is invisible to the particular user of the system when viewed from the layer containing the white-out file or from any layer above a layer containing the white-out file.
13. In a multi-user computer system comprising a central processing unit (CPU), an input/output unit and memory, said CPU being controlled by an operating system, said operating system comprising a file system module, wherein the file system module organizes and controls access to files located on disks in the computer system, said file system module organizing files into file systems comprising directories, said directories containing files organized in a hierarchical file structure, a method for translucently providing to a user both shared and private access to current revisions of files, said method comprising the steps of:
structuring a designated file hierarchy into a plurality of layers whereby each layer contains at least one directory;
creating an ordered set of layers which can be shared by any number of users, wherein the plurality of layers of the designated file hierarchy are arranged in time-of-creation sequence such that a layer containing a less recent revision of a file in the designated file hierarchy is placed below a layer with a more recent revision of the same file;
providing one or more front layers, each containing at least one directory, with each of the one or more front layers being controlled by a particular user of the system and is not being shared with other users of the system, with files located in each of said one or more front layers being designated such that only the particular user can read from and write to the files in said particular user's front layer, and each front layer being positioned in front of the ordered set of shared layers of the designated file hierarchy;
displaying to a particular user, most recent revisions of files, regardless of whether these files reside in the directory of the particular user's front layer or in the directories of the ordered set of shared layers, as if all of the files resided in the particular user's front directory.
structuring a designated file hierarchy into a plurality of layers whereby each layer contains at least one directory;
creating an ordered set of layers which can be shared by any number of users, wherein the plurality of layers of the designated file hierarchy are arranged in time-of-creation sequence such that a layer containing a less recent revision of a file in the designated file hierarchy is placed below a layer with a more recent revision of the same file;
providing one or more front layers, each containing at least one directory, with each of the one or more front layers being controlled by a particular user of the system and is not being shared with other users of the system, with files located in each of said one or more front layers being designated such that only the particular user can read from and write to the files in said particular user's front layer, and each front layer being positioned in front of the ordered set of shared layers of the designated file hierarchy;
displaying to a particular user, most recent revisions of files, regardless of whether these files reside in the directory of the particular user's front layer or in the directories of the ordered set of shared layers, as if all of the files resided in the particular user's front directory.
14. The method of claim 13 wherein the step of creating an ordered set of shared layers further comprises a first connecting step for connecting a particular layer in the ordered set of shared layers to a layer below said particular layer by means of search links, and wherein the step for providing one or more front layers further comprises a second connecting step for connecting each of the one or more front layers to a topmost layer of the ordered set of shared layers using search links, wherein the search links are associated with a directory of each layer and comprise a path name of a directory of a layer behind the layer the search link is located in, said path name identifying the location of a directory in a file system.
15. The method of claim 13 further comprising steps for automatically copying a designated file from a layer of the ordered set of shared layers, into a particular user's front layer when the particular user attempts to execute a write command to the designated file, whereby the copy of the designated file in the particular user's front layer can be modified according to the write command which triggered the copy operation without the copy operation or the location of the modified copy of the designated file being evident to the particular user.
16. The method of claim 14 wherein the step of connecting the one or more front layers and the ordered set of shared layers through search links comprises an additional step of establishing such search links when a new layer is created.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US315,287 | 1989-02-24 | ||
| US31528789A | 1989-06-10 | 1989-06-10 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA1323448C true CA1323448C (en) | 1993-10-19 |
Family
ID=23223726
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA000613984A Expired - Fee Related CA1323448C (en) | 1989-02-24 | 1989-09-28 | Method and apparatus for translucent file system |
Country Status (3)
| Country | Link |
|---|---|
| US (1) | US5313646A (en) |
| JP (1) | JP3041528B2 (en) |
| CA (1) | CA1323448C (en) |
Families Citing this family (204)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2067633C (en) * | 1991-07-24 | 1996-10-01 | Eric Jonathan Bauer | Method and apparatus for accessing a computer-based file system |
| EP0930566A3 (en) | 1992-07-06 | 2006-07-05 | Microsoft Corporation | Method and system for composing objects |
| US6286013B1 (en) | 1993-04-01 | 2001-09-04 | Microsoft Corporation | Method and system for providing a common name space for long and short file names in an operating system |
| DE69429378T2 (en) * | 1993-04-01 | 2002-05-23 | Microsoft Corp | Common memory area for long and short file names |
| US5963962A (en) * | 1995-05-31 | 1999-10-05 | Network Appliance, Inc. | Write anywhere file-system layout |
| US7174352B2 (en) | 1993-06-03 | 2007-02-06 | Network Appliance, Inc. | File system image transfer |
| US6604118B2 (en) | 1998-07-31 | 2003-08-05 | Network Appliance, Inc. | File system image transfer |
| JPH0721034A (en) * | 1993-06-28 | 1995-01-24 | Fujitsu Ltd | Character string copying processing method |
| US5530849A (en) * | 1993-08-16 | 1996-06-25 | Cornell Research Foundation, Inc. | Method of reading dynamic, hierarchical file system directories |
| BE1007551A3 (en) * | 1993-09-24 | 1995-08-01 | Philips Electronics Nv | Method for in a calculator auto repair of consistency in a hierarchical objektstruktuur after inter action by a user and calculator with such a system for consistency auto repair. |
| US5588147A (en) * | 1994-01-14 | 1996-12-24 | Microsoft Corporation | Replication facility |
| US5483652A (en) * | 1994-01-24 | 1996-01-09 | Digital Equipment Corporation | Mechanism for locating without search discrete application resources known by common name only in a distributed network computing environment |
| JPH07302236A (en) * | 1994-05-06 | 1995-11-14 | Hitachi Ltd | Information processing system, method therefor and service providing method in the information processing system |
| US5680609A (en) * | 1994-06-10 | 1997-10-21 | Intel Corporation | Method and apparatus for synchronizing file deletions in computer systems |
| US5603019A (en) * | 1994-07-25 | 1997-02-11 | International Business Machines Corporation | Takeover technique for networked virtual filesystems |
| US5701463A (en) * | 1994-09-09 | 1997-12-23 | Cheyenne Advanced Technology Limited | Method of replacing the identity of a file with another as part of a file open request in a computer system |
| JP2912840B2 (en) * | 1994-12-07 | 1999-06-28 | 富士通株式会社 | File management system |
| US5745752A (en) * | 1994-12-13 | 1998-04-28 | Microsoft Corporation | Dual namespace client having long and short filenames |
| US5566328A (en) * | 1995-01-23 | 1996-10-15 | Tandem Computers Incorporated | Reconstructing directory pathnames from file handles in a computer system |
| US5675769A (en) * | 1995-02-23 | 1997-10-07 | Powerquest Corporation | Method for manipulating disk partitions |
| US5930831A (en) * | 1995-02-23 | 1999-07-27 | Powerquest Corporation | Partition manipulation architecture supporting multiple file systems |
| US5706472A (en) * | 1995-02-23 | 1998-01-06 | Powerquest Corporation | Method for manipulating disk partitions |
| US6108759A (en) * | 1995-02-23 | 2000-08-22 | Powerquest Corporation | Manipulation of partitions holding advanced file systems |
| US5978577A (en) * | 1995-03-17 | 1999-11-02 | Csg Systems, Inc. | Method and apparatus for transaction processing in a distributed database system |
| US5826254A (en) * | 1995-04-18 | 1998-10-20 | Digital Equipment Corporation | System for selectively browsing a large, distributed directory tree using authentication links |
| US5644736A (en) * | 1995-05-25 | 1997-07-01 | International Business Machines Corporation | System and method for selecting components of a hierarchical file structure |
| JP3335801B2 (en) * | 1995-07-05 | 2002-10-21 | 株式会社日立製作所 | Information processing system enabling access to different types of files and control method thereof |
| US5758334A (en) * | 1995-07-05 | 1998-05-26 | International Business Machines Corporation | File system remount operation with selectable access modes that saves knowledge of the volume path and does not interrupt an executing process upon changing modes |
| US5805899A (en) * | 1995-07-06 | 1998-09-08 | Sun Microsystems, Inc. | Method and apparatus for internal versioning of objects using a mapfile |
| WO1997004391A1 (en) | 1995-07-20 | 1997-02-06 | Novell, Inc. | Transaction log management in a disconnectable computer and network |
| WO1997004389A1 (en) * | 1995-07-20 | 1997-02-06 | Novell, Inc. | Transaction synchronization in a disconnectable computer and network |
| US5678015A (en) * | 1995-09-01 | 1997-10-14 | Silicon Graphics, Inc. | Four-dimensional graphical user interface |
| US5668958A (en) * | 1995-09-12 | 1997-09-16 | International Business Machines Corporation | Heterogeneous filing system with common API and reconciled file management rules |
| US5701458A (en) * | 1995-09-20 | 1997-12-23 | International Business Machines Corporation | System and method for managing arbitrary subsets of access control lists in a computer network |
| US5706510A (en) * | 1996-03-15 | 1998-01-06 | Hewlett-Packard Company | Zymbolic history management system |
| GB2311392B (en) * | 1996-03-22 | 1998-03-04 | Digital Equipment Corp | A method of maintaining information in a memory of a computer system |
| US5946490A (en) * | 1996-03-22 | 1999-08-31 | Northeastern University | Automata-theoretic approach compiler for adaptive software |
| US6601091B1 (en) * | 1996-03-28 | 2003-07-29 | Networks Associates Technology, Inc. | Method for improving the perceived performance of a computer system |
| US5968152A (en) * | 1996-04-10 | 1999-10-19 | Apple Computer, Inc. | Method and apparatus for extending key space in a plug and play ROM |
| US5974410A (en) * | 1996-06-28 | 1999-10-26 | Microsoft Corporation | Method and system for filtering in a uniform data interface |
| US6412017B1 (en) | 1996-07-01 | 2002-06-25 | Microsoft Corporation | Urgent replication facility |
| US5878434A (en) * | 1996-07-18 | 1999-03-02 | Novell, Inc | Transaction clash management in a disconnectable computer and network |
| US6049809A (en) * | 1996-10-30 | 2000-04-11 | Microsoft Corporation | Replication optimization system and method |
| CA2272708A1 (en) | 1996-11-27 | 1998-06-04 | Kurt E. Godwin | File directory and file navigation system |
| US6401099B1 (en) | 1996-12-06 | 2002-06-04 | Microsoft Corporation | Asynchronous binding of named objects |
| US6460058B2 (en) | 1996-12-06 | 2002-10-01 | Microsoft Corporation | Object-oriented framework for hyperlink navigation |
| US6148294A (en) * | 1996-12-20 | 2000-11-14 | Siemens Information And Communication Networks, Inc. | System and method for computer directory updating and presentation based on frequency of access |
| US5950198A (en) * | 1997-03-24 | 1999-09-07 | Novell, Inc. | Processes and apparatuses for generating file correspondency through replication and synchronization between target and source computers |
| US5924102A (en) * | 1997-05-07 | 1999-07-13 | International Business Machines Corporation | System and method for managing critical files |
| US5905990A (en) * | 1997-06-23 | 1999-05-18 | International Business Machines Corporation | File system viewpath mechanism |
| US5991777A (en) | 1997-09-19 | 1999-11-23 | Microsoft Corporation | System and method for performing defined actions when grafting the name space of one storage medium into the name space of another storage medium |
| US6125373A (en) | 1997-09-19 | 2000-09-26 | Microsoft Corporation | Identifying a driver that is an owner of an active mount point |
| US6260040B1 (en) | 1998-01-05 | 2001-07-10 | International Business Machines Corporation | Shared file system for digital content |
| WO1999042934A2 (en) * | 1998-02-20 | 1999-08-26 | Storm Systems, Llc | File system performance enhancement |
| US6457130B2 (en) | 1998-03-03 | 2002-09-24 | Network Appliance, Inc. | File access control in a multi-protocol file server |
| US6317844B1 (en) | 1998-03-10 | 2001-11-13 | Network Appliance, Inc. | File server storage arrangement |
| US6604236B1 (en) | 1998-06-30 | 2003-08-05 | Iora, Ltd. | System and method for generating file updates for files stored on read-only media |
| US6574591B1 (en) * | 1998-07-31 | 2003-06-03 | Network Appliance, Inc. | File systems image transfer between dissimilar file systems |
| US6356863B1 (en) | 1998-09-08 | 2002-03-12 | Metaphorics Llc | Virtual network file server |
| US6343984B1 (en) | 1998-11-30 | 2002-02-05 | Network Appliance, Inc. | Laminar flow duct cooling system |
| US7181438B1 (en) | 1999-07-21 | 2007-02-20 | Alberti Anemometer, Llc | Database access system |
| US8335775B1 (en) * | 1999-08-05 | 2012-12-18 | Oracle International Corporation | Versioning in internet file system |
| US7634453B1 (en) | 1999-08-13 | 2009-12-15 | Storage Technology Corporation | Distributed file data location |
| US6622170B1 (en) | 1999-09-10 | 2003-09-16 | International Business Machines Corporation | System and method for DEN/LDAP client database access with a backoff capability |
| US6578054B1 (en) * | 1999-10-04 | 2003-06-10 | Microsoft Corporation | Method and system for supporting off-line mode of operation and synchronization using resource state information |
| AU2336901A (en) * | 1999-12-27 | 2001-07-09 | Texar Software Corp. | Virtual resource attribute directory |
| US7028251B2 (en) * | 2000-03-02 | 2006-04-11 | Iora, Ltd. | System and method for reducing the size of data difference representations |
| US7155667B1 (en) | 2000-06-21 | 2006-12-26 | Microsoft Corporation | User interface for integrated spreadsheets and word processing tables |
| US7117435B1 (en) | 2000-06-21 | 2006-10-03 | Microsoft Corporation | Spreadsheet fields in text |
| US7624356B1 (en) | 2000-06-21 | 2009-11-24 | Microsoft Corporation | Task-sensitive methods and systems for displaying command sets |
| US7346848B1 (en) | 2000-06-21 | 2008-03-18 | Microsoft Corporation | Single window navigation methods and systems |
| JP4522650B2 (en) | 2000-06-21 | 2010-08-11 | マイクロソフト コーポレーション | System and method for integrating spreadsheet and word processing tables |
| US6874143B1 (en) * | 2000-06-21 | 2005-03-29 | Microsoft Corporation | Architectures for and methods of providing network-based software extensions |
| US6883168B1 (en) | 2000-06-21 | 2005-04-19 | Microsoft Corporation | Methods, systems, architectures and data structures for delivering software via a network |
| US6948135B1 (en) | 2000-06-21 | 2005-09-20 | Microsoft Corporation | Method and systems of providing information to computer users |
| US7191394B1 (en) | 2000-06-21 | 2007-03-13 | Microsoft Corporation | Authoring arbitrary XML documents using DHTML and XSLT |
| US7000230B1 (en) | 2000-06-21 | 2006-02-14 | Microsoft Corporation | Network-based software extensions |
| US7222132B2 (en) * | 2001-03-20 | 2007-05-22 | Swsoft Holdings, Ltd. | Common template file system tree for virtual environments and virtual servers |
| US6668264B1 (en) | 2001-04-03 | 2003-12-23 | Network Appliance, Inc. | Resynchronization of a target volume with a source volume |
| US7047257B2 (en) * | 2001-04-03 | 2006-05-16 | Qnx Software Systems | Computer file management system |
| US7433900B2 (en) * | 2001-04-03 | 2008-10-07 | Qnx Software Systems Gmbh & Co. Kg | Custom filesystem having file mappings to files of a real filesystem |
| US7440980B2 (en) * | 2001-04-03 | 2008-10-21 | Qnx Software Systems Gmbh & Co. Kg | Computer file management system |
| US7219122B1 (en) * | 2001-04-23 | 2007-05-15 | Massachusetts Institute Of Technology | Software service handoff mechanism with a performance reliability improvement mechanism (PRIM) for a collaborative client-server system |
| US20040205587A1 (en) * | 2001-08-07 | 2004-10-14 | Draper Stephen P.W. | System and method for enumerating arbitrary hyperlinked structures in which links may be dynamically calculable |
| US20030033303A1 (en) * | 2001-08-07 | 2003-02-13 | Brian Collins | System and method for restricting access to secured data |
| JP3776769B2 (en) * | 2001-08-08 | 2006-05-17 | 株式会社東芝 | File server system and control method thereof |
| KR100538659B1 (en) * | 2001-08-13 | 2005-12-26 | 콸콤 인코포레이티드 | Application level access privilege to a storage area on a computer device |
| EP1300757A1 (en) * | 2001-10-02 | 2003-04-09 | Sun Microsystems, Inc. | Shareable installation hierarchies |
| US6859812B1 (en) * | 2001-10-31 | 2005-02-22 | Hewlett-Packard Development Company, L.P. | System and method for differentiating private and shared files within a computer cluster |
| US7725490B2 (en) | 2001-11-16 | 2010-05-25 | Crucian Global Services, Inc. | Collaborative file access management system |
| US6909910B2 (en) | 2002-02-01 | 2005-06-21 | Microsoft Corporation | Method and system for managing changes to a contact database |
| US7783665B1 (en) * | 2002-03-27 | 2010-08-24 | Parallels Holdings, Ltd. | Effective file-sharing among virtual environments |
| US7293033B1 (en) * | 2002-03-27 | 2007-11-06 | Swsoft Holdings, Ltd. | System and method for providing effective file-sharing in a computer system to allow concurrent multi-user access |
| CA2481687A1 (en) * | 2002-04-11 | 2003-10-23 | Linuxcare, Inc. | Managing multiple virtual machines |
| US6857001B2 (en) * | 2002-06-07 | 2005-02-15 | Network Appliance, Inc. | Multiple concurrent active file systems |
| US7165260B2 (en) | 2002-06-12 | 2007-01-16 | Fsl, L.L.C. | Layered computing systems and methods for insecure environments |
| WO2003107221A1 (en) * | 2002-06-12 | 2003-12-24 | Fslogic, Inc. | Layered computing systems and methods |
| US7512977B2 (en) * | 2003-06-11 | 2009-03-31 | Symantec Corporation | Intrustion protection system utilizing layers |
| US7620956B2 (en) * | 2003-06-11 | 2009-11-17 | Symantec Corporation | Portable memory storage devices with application layers |
| US7970789B1 (en) | 2003-06-11 | 2011-06-28 | Symantec Corporation | Sublayered application layered system |
| US7549164B2 (en) * | 2003-06-11 | 2009-06-16 | Symantec Corporation | Intrustion protection system utilizing layers and triggers |
| US8843903B1 (en) | 2003-06-11 | 2014-09-23 | Symantec Corporation | Process tracking application layered system |
| US7461086B1 (en) | 2006-01-03 | 2008-12-02 | Symantec Corporation | Run-time application installation application layered system |
| US8010961B1 (en) | 2003-06-11 | 2011-08-30 | Symantec Corporation | Data layer prioritization in an application layered system |
| US7945897B1 (en) | 2002-06-12 | 2011-05-17 | Symantec Corporation | Method and system for running an application in a clean operating environment using a layered computing system |
| US7877413B1 (en) | 2002-06-12 | 2011-01-25 | Symantec Corporation | Path variablizing layered system |
| US7542988B1 (en) * | 2006-01-03 | 2009-06-02 | Symantec Corporation | File type associative application layered system |
| US7496931B2 (en) * | 2003-12-30 | 2009-02-24 | Symantec Corporation | Portable memory storage devices containing public context application layers |
| US7886291B1 (en) | 2003-06-11 | 2011-02-08 | Symantec Corporation | Layer typed prioritizing application layered systems |
| US7461096B1 (en) | 2003-06-11 | 2008-12-02 | Symantec Corporation | Weighted prioritizing layered computing system |
| US20040015522A1 (en) * | 2002-06-13 | 2004-01-22 | International Business Machines Corporation | Apparatus, system and method of providing a stackable private write file system |
| US7197516B1 (en) | 2002-07-22 | 2007-03-27 | Veritas Operating Corporation | Method and system for an overlay filesystem |
| US7805449B1 (en) | 2004-10-28 | 2010-09-28 | Stored IQ | System, method and apparatus for enterprise policy management |
| US8417678B2 (en) | 2002-07-30 | 2013-04-09 | Storediq, Inc. | System, method and apparatus for enterprise policy management |
| US8612404B2 (en) * | 2002-07-30 | 2013-12-17 | Stored Iq, Inc. | Harvesting file system metsdata |
| AU2003265335A1 (en) | 2002-07-30 | 2004-02-16 | Deepfile Corporation | Method and apparatus for managing file systems and file-based data storage |
| US7519910B2 (en) * | 2002-10-10 | 2009-04-14 | International Business Machines Corporation | Method for transferring files from one machine to another using adjacent desktop displays in a virtual network |
| US7415672B1 (en) | 2003-03-24 | 2008-08-19 | Microsoft Corporation | System and method for designing electronic forms |
| US7275216B2 (en) | 2003-03-24 | 2007-09-25 | Microsoft Corporation | System and method for designing electronic forms and hierarchical schemas |
| US7370066B1 (en) | 2003-03-24 | 2008-05-06 | Microsoft Corporation | System and method for offline editing of data files |
| US7296017B2 (en) * | 2003-03-28 | 2007-11-13 | Microsoft Corporation | Validation of XML data files |
| US7913159B2 (en) | 2003-03-28 | 2011-03-22 | Microsoft Corporation | System and method for real-time validation of structured data files |
| US7516145B2 (en) | 2003-03-31 | 2009-04-07 | Microsoft Corporation | System and method for incrementally transforming and rendering hierarchical data files |
| WO2004102326A2 (en) * | 2003-05-07 | 2004-11-25 | Linuxcare, Inc. | Detection and alerting of viruses in a shared read-only file system |
| US7168035B1 (en) | 2003-06-11 | 2007-01-23 | Microsoft Corporation | Building a view on markup language data through a set of components |
| US7451392B1 (en) | 2003-06-30 | 2008-11-11 | Microsoft Corporation | Rendering an HTML electronic form by applying XSLT to XML using a solution |
| US7197515B2 (en) | 2003-06-30 | 2007-03-27 | Microsoft Corporation | Declarative solution definition |
| CA2434644A1 (en) * | 2003-06-30 | 2004-12-30 | Archidata Inc. | System for the certification of plans and specifications produced by construction professionals and clients |
| US7581177B1 (en) | 2003-08-01 | 2009-08-25 | Microsoft Corporation | Conversion of structured documents |
| US7406660B1 (en) | 2003-08-01 | 2008-07-29 | Microsoft Corporation | Mapping between structured data and a visual surface |
| US7334187B1 (en) | 2003-08-06 | 2008-02-19 | Microsoft Corporation | Electronic form aggregation |
| JP4349871B2 (en) * | 2003-09-09 | 2009-10-21 | 株式会社日立製作所 | File sharing apparatus and data migration method between file sharing apparatuses |
| WO2005029333A1 (en) * | 2003-09-12 | 2005-03-31 | Levanta, Inc. | Tracking and replicating file system changes |
| US7827362B2 (en) * | 2004-08-24 | 2010-11-02 | Symantec Corporation | Systems, apparatus, and methods for processing I/O requests |
| US7472254B2 (en) * | 2003-10-10 | 2008-12-30 | Iora, Ltd. | Systems and methods for modifying a set of data objects |
| US7644376B2 (en) * | 2003-10-23 | 2010-01-05 | Microsoft Corporation | Flexible architecture for notifying applications of state changes |
| US20050091535A1 (en) * | 2003-10-24 | 2005-04-28 | Microsoft Corporation | Application identity for software products |
| US20050091658A1 (en) * | 2003-10-24 | 2005-04-28 | Microsoft Corporation | Operating system resource protection |
| US8819072B1 (en) | 2004-02-02 | 2014-08-26 | Microsoft Corporation | Promoting data from structured data files |
| US7313720B1 (en) | 2004-02-12 | 2007-12-25 | Network Appliance, Inc. | Technique for increasing the number of persistent consistency point images in a file system |
| US7430711B2 (en) | 2004-02-17 | 2008-09-30 | Microsoft Corporation | Systems and methods for editing XML documents |
| US7318063B2 (en) | 2004-02-19 | 2008-01-08 | Microsoft Corporation | Managing XML documents containing hierarchical database information |
| US7636710B2 (en) * | 2004-03-04 | 2009-12-22 | Symantec Operating Corporation | System and method for efficient file content searching within a file system |
| US7496837B1 (en) | 2004-04-29 | 2009-02-24 | Microsoft Corporation | Structural editing with schema awareness |
| US7568101B1 (en) | 2004-05-13 | 2009-07-28 | Microsoft Corporation | Digital signatures with an embedded view |
| US7281018B1 (en) | 2004-05-26 | 2007-10-09 | Microsoft Corporation | Form template data source change |
| US7774620B1 (en) | 2004-05-27 | 2010-08-10 | Microsoft Corporation | Executing applications at appropriate trust levels |
| US7516399B2 (en) | 2004-09-30 | 2009-04-07 | Microsoft Corporation | Structured-document path-language expression methods and systems |
| US7692636B2 (en) | 2004-09-30 | 2010-04-06 | Microsoft Corporation | Systems and methods for handwriting to a screen |
| US8510331B1 (en) | 2004-10-28 | 2013-08-13 | Storediq, Inc. | System and method for a desktop agent for use in managing file systems |
| US7844582B1 (en) | 2004-10-28 | 2010-11-30 | Stored IQ | System and method for involving users in object management |
| US8487879B2 (en) | 2004-10-29 | 2013-07-16 | Microsoft Corporation | Systems and methods for interacting with a computer through handwriting to a screen |
| US7712022B2 (en) | 2004-11-15 | 2010-05-04 | Microsoft Corporation | Mutually exclusive options in electronic forms |
| US7584417B2 (en) | 2004-11-15 | 2009-09-01 | Microsoft Corporation | Role-dependent action for an electronic form |
| US7721190B2 (en) | 2004-11-16 | 2010-05-18 | Microsoft Corporation | Methods and systems for server side form processing |
| US7509353B2 (en) | 2004-11-16 | 2009-03-24 | Microsoft Corporation | Methods and systems for exchanging and rendering forms |
| US7904801B2 (en) | 2004-12-15 | 2011-03-08 | Microsoft Corporation | Recursive sections in electronic forms |
| US8606830B2 (en) * | 2004-12-17 | 2013-12-10 | Microsoft Corporation | Contiguous file allocation in an extensible file system |
| US8321439B2 (en) | 2004-12-17 | 2012-11-27 | Microsoft Corporation | Quick filename lookup using name hash |
| US9639554B2 (en) * | 2004-12-17 | 2017-05-02 | Microsoft Technology Licensing, Llc | Extensible file system |
| US7873596B2 (en) | 2006-05-23 | 2011-01-18 | Microsoft Corporation | Extending cluster allocations in an extensible file system |
| US7437376B2 (en) | 2004-12-20 | 2008-10-14 | Microsoft Corporation | Scalable object model |
| US7509419B2 (en) * | 2005-01-13 | 2009-03-24 | International Business Machines Corporation | Method for providing remote access redirect capability in a channel adapter of a system area network |
| US7937651B2 (en) | 2005-01-14 | 2011-05-03 | Microsoft Corporation | Structural editing operations for network forms |
| US7574464B2 (en) * | 2005-02-14 | 2009-08-11 | Netapp, Inc. | System and method for enabling a storage system to support multiple volume formats simultaneously |
| US7725834B2 (en) | 2005-03-04 | 2010-05-25 | Microsoft Corporation | Designer-created aspect for an electronic form template |
| US7300621B2 (en) * | 2005-03-16 | 2007-11-27 | Siemens Power Generation, Inc. | Method of making a ceramic matrix composite utilizing partially stabilized fibers |
| US20060235863A1 (en) * | 2005-04-14 | 2006-10-19 | Akmal Khan | Enterprise computer management |
| US8010515B2 (en) | 2005-04-15 | 2011-08-30 | Microsoft Corporation | Query to an electronic form |
| US8332526B2 (en) | 2005-05-25 | 2012-12-11 | Microsoft Corporation | Data communication protocol including negotiation and command compounding |
| KR101130475B1 (en) * | 2005-05-25 | 2012-03-27 | 마이크로소프트 코포레이션 | Data communication protocol |
| US7543228B2 (en) | 2005-06-27 | 2009-06-02 | Microsoft Corporation | Template for rendering an electronic form |
| US8200975B2 (en) | 2005-06-29 | 2012-06-12 | Microsoft Corporation | Digital signatures for network forms |
| US7613996B2 (en) | 2005-08-15 | 2009-11-03 | Microsoft Corporation | Enabling selection of an inferred schema part |
| US8001459B2 (en) | 2005-12-05 | 2011-08-16 | Microsoft Corporation | Enabling electronic documents for limited-capability computing devices |
| US8015165B2 (en) | 2005-12-14 | 2011-09-06 | Oracle International Corporation | Efficient path-based operations while searching across versions in a repository |
| US7472140B2 (en) * | 2005-12-20 | 2008-12-30 | Oracle International Corporation | Label-aware index for efficient queries in a versioning system |
| US7533136B2 (en) * | 2005-12-22 | 2009-05-12 | Oracle International Corporation | Efficient implementation of multiple work areas in a file system like repository that supports file versioning |
| US7543004B2 (en) * | 2005-12-22 | 2009-06-02 | Oracle International Corporation | Efficient support for workspace-local queries in a repository that supports file versioning |
| US7730032B2 (en) * | 2006-01-12 | 2010-06-01 | Oracle International Corporation | Efficient queriability of version histories in a repository |
| US7779343B2 (en) | 2006-01-30 | 2010-08-17 | Microsoft Corporation | Opening network-enabled electronic documents |
| GB0623916D0 (en) * | 2006-11-30 | 2007-01-10 | Ibm | Methods, apparatus and computer programs for change management in a data processing environment |
| GB2446169A (en) * | 2006-12-01 | 2008-08-06 | David Irvine | Granular accessibility to data in a distributed and/or corporate network |
| GB2446199A (en) | 2006-12-01 | 2008-08-06 | David Irvine | Secure, decentralised and anonymous peer-to-peer network |
| US8656386B1 (en) * | 2007-03-13 | 2014-02-18 | Parallels IP Holdings GmbH | Method to share identical files in a common area for virtual machines having the same operating system version and using a copy on write to place a copy of the shared identical file in a private area of the corresponding virtual machine when a virtual machine attempts to modify the shared identical file |
| GB2450538A (en) * | 2007-06-28 | 2008-12-31 | Symbian Software Ltd | Copying computer files when manipulation is requested |
| US20110040812A1 (en) * | 2007-12-20 | 2011-02-17 | Virtual Computer, Inc. | Layered Virtual File System |
| US8688641B1 (en) | 2008-03-31 | 2014-04-01 | Symantec Operating Corporation | Per user and per process layer visibility |
| US8438196B1 (en) | 2008-03-31 | 2013-05-07 | Symantec Operating Corporation | Finer grained data organization using data sublayers |
| US8639734B1 (en) | 2008-03-31 | 2014-01-28 | Symantec Operating Corporation | Use of external information about a file to determine virtualization |
| US8315996B2 (en) * | 2008-08-13 | 2012-11-20 | International Business Machines Corporation | Efficient management of customized functionality within shared data objects |
| AU2008246236B1 (en) * | 2008-11-18 | 2009-10-01 | International Business Machines Corporation | Presentation of items arranged in a hierarchy |
| US20110061046A1 (en) * | 2008-12-18 | 2011-03-10 | Virtual Computer, Inc. | Installing Software Applications in a Layered Virtual Workspace |
| WO2011022388A1 (en) * | 2009-08-17 | 2011-02-24 | Virtual Computer, Inc. | Layered virtual file system |
| US8881140B1 (en) | 2009-09-04 | 2014-11-04 | Symantec Corporation | Systems and methods for virtualizing software associated with external computer hardware devices |
| US8621365B2 (en) * | 2010-04-06 | 2013-12-31 | Asustek Computer Inc. | File sharing method and system |
| US8631277B2 (en) | 2010-12-10 | 2014-01-14 | Microsoft Corporation | Providing transparent failover in a file system |
| US8490207B2 (en) * | 2011-05-31 | 2013-07-16 | Red Hat, Inc. | Performing zero-copy sends in a networked file system with cryptographic signing |
| EP2535826A1 (en) * | 2011-05-31 | 2012-12-19 | Research In Motion Limited | Method and system for data synchronization including file system abstraction |
| CN102296501A (en) * | 2011-06-16 | 2011-12-28 | 中国农业大学 | Seamless track rail temperature locking preprocessing system |
| US9331955B2 (en) | 2011-06-29 | 2016-05-03 | Microsoft Technology Licensing, Llc | Transporting operations of arbitrary size over remote direct memory access |
| US8856582B2 (en) | 2011-06-30 | 2014-10-07 | Microsoft Corporation | Transparent failover |
| US8788579B2 (en) | 2011-09-09 | 2014-07-22 | Microsoft Corporation | Clustered client failover |
| US20130067095A1 (en) | 2011-09-09 | 2013-03-14 | Microsoft Corporation | Smb2 scaleout |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4742450A (en) * | 1986-01-16 | 1988-05-03 | International Business Machines Corporation | Method to share copy on write segment for mapped files |
| US4887204A (en) * | 1987-02-13 | 1989-12-12 | International Business Machines Corporation | System and method for accessing remote files in a distributed networking environment |
| US5001628A (en) * | 1987-02-13 | 1991-03-19 | International Business Machines Corporation | Single system image uniquely defining an environment for each user in a data processing system |
| US4809170A (en) * | 1987-04-22 | 1989-02-28 | Apollo Computer, Inc. | Computer device for aiding in the development of software system |
| JPS6410353A (en) * | 1987-07-03 | 1989-01-13 | Hitachi Ltd | Computer file system |
| US5077658A (en) * | 1987-10-19 | 1991-12-31 | International Business Machines Corporation | Data access system for a file access processor |
| US4914569A (en) * | 1987-10-30 | 1990-04-03 | International Business Machines Corporation | Method for concurrent record access, insertion, deletion and alteration using an index tree |
| US4875159A (en) * | 1987-12-22 | 1989-10-17 | Amdahl Corporation | Version management system using plural control fields for synchronizing two versions of files in a multiprocessor system |
| US4912637A (en) * | 1988-04-26 | 1990-03-27 | Tandem Computers Incorporated | Version management tool |
-
1989
- 1989-09-28 CA CA000613984A patent/CA1323448C/en not_active Expired - Fee Related
-
1990
- 1990-02-26 JP JP2042723A patent/JP3041528B2/en not_active Expired - Fee Related
-
1991
- 1991-06-10 US US07/714,312 patent/US5313646A/en not_active Expired - Lifetime
Also Published As
| Publication number | Publication date |
|---|---|
| JPH02249043A (en) | 1990-10-04 |
| JP3041528B2 (en) | 2000-05-15 |
| US5313646A (en) | 1994-05-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA1323448C (en) | Method and apparatus for translucent file system | |
| US5649200A (en) | Dynamic rule-based version control system | |
| CN101073058B (en) | Method for isolating execution of software applications | |
| US6681382B1 (en) | Method and system for using virtual labels in a software configuration management system | |
| US6374268B1 (en) | Methods and systems for an incremental file system | |
| US5920867A (en) | Data management system having data management configuration | |
| US8522205B2 (en) | Packaging multiple groups of read-only files of an application's components into multiple shared libraries | |
| US5905990A (en) | File system viewpath mechanism | |
| CN101073059B (en) | Methods and systems for accessing, by application programs, resources provided by an operating system | |
| US7647363B2 (en) | Revision control system for large-scale systems management | |
| CA2137492C (en) | System for and method of providing delta-versioning of the contents of pcte file objects | |
| US6094654A (en) | Data management system for file and database management | |
| US5761678A (en) | Creation of clone storage area with identification of base storage area and deferred cloning of metadata | |
| US5412808A (en) | System for parsing extended file names in an operating system | |
| US6035297A (en) | Data management system for concurrent engineering | |
| US5870734A (en) | Three-dimensional file system using a virtual node architecture | |
| US5991753A (en) | Method and system for computer file management, including file migration, special handling, and associating extended attributes with files | |
| US8392477B2 (en) | Seamless remote traversal of multiple NFSv4 exported file systems | |
| US7720869B2 (en) | Hierarchical structured abstract file system | |
| US7197516B1 (en) | Method and system for an overlay filesystem | |
| EP0947932A2 (en) | File version reconciliation using hash codes | |
| US20050015674A1 (en) | Method, apparatus, and program for converting, administering, and maintaining access control lists between differing filesystem types | |
| US5274806A (en) | Hierarchical data encyclopedia | |
| JPH05135108A (en) | Method and apparatus for organizing database | |
| Korn et al. | A new dimension for the Unix® file system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| MKLA | Lapsed |