| slovo | definícia |
file system
(encz) | file system, n: |
file system
(wn) | file system
n 1: a system of classifying into files (usually arranged
alphabetically) [syn: file system, filing system] |
file system
(foldoc) | file system
filing system
(FS, or "filesystem") 1. A system for
organizing directories and files, generally in terms of
how it is implemented in the disk operating system. E.g.,
"The Macintosh file system is just dandy as long as you
don't have to interface it with any other file systems".
2. The collection of files and directories stored on a given
drive (floppy drive, hard drive, disk partition, logical
drive, RAM drive, etc.). E.g., "mount attaches a named file
system to the file system hierarchy at the pathname location
directory [...]" -- Unix manual page for "mount(8)".
As an extension of this sense, "file system" is sometimes used
to refer to the representatation of the file system's
organisation (e.g. its file allocation table) as opposed the
actual content of the files in the file system.
Unix manual page: fs(5), mount(8).
(1997-04-10)
|
| | podobné slovo | definícia |
andrew file system
(foldoc) | Andrew File System
AFS
(AFS) The distributed {file
system} of the Andrew Project, adopted by the OSF as part
of their Distributed Computing Environment.
{Frequently Asked Questions
(http://transarc.com/Product/AFS/FAQ/faq.html)}.
(1994-11-24)
|
attributed file system
(foldoc) | Attributed File System
AtFS
(AtFS) The basis of the Shape_VC toolkit.
Cooperative work within projects is supported by a status
model controlling visibility of version objects, locking, and
"long transactions" for synchronising concurrent updates. The
concept of object attributes provides a basis for storing
management information with versions and passing this
information between individual tools. This mechanism is
useful for building integrated environments from a set of
unrelated tools.
(2000-02-24)
|
common internet file system
(foldoc) | Common Internet File System
CIFS
(CIFS) An Internet file system protocol,
based on Microsoft's SMB. Microsoft has given CIFS to the
Internet Engineering Task Force (IETF) as an Internet Draft.
CIFS is intended to complement existing protocols such as
HTTP, FTP, and NFS.
CIFS runs on top of TCP/IP and uses the Internet's {Domain
Name Service} (DNS). It is optimised to support the slower
speed dial-up connections common on the Internet.
CIFS is more flexible than FTP. FTP operations are carried
out on entire files whereas CIFS is aimed at routine data
access and incorporates high-performance multi-user read and
write operations, locking, and file-sharing semantics.
CIFS is probably closest in functionality to NFS. NFS gives
random access to files and directories, but is stateless.
With CIFS, once a file is open, state about the current access
to that file is stored on both the client and the server.
This allows changes on the server side to be notified to the
clients that are interested.
{Microsoft Overview
(http://msdn.microsoft.com/library/en-us/fileio/base/cifs_smb_protocol_overview.asp)}.
SNIA page (http://snia.org/tech_activities/CIFS/).
{CIFS: A Common Internet File System, Paul Leach and Dan Perry
(http://microsoft.com/Mind/1196/CIFS.htm)}.
{IETF Specification. CIFS version 1
(ftp://ietf.org/internet-drafts/draft-leach-cifs-v1-spec-01.txt)}.
(2003-03-12)
|
hierarchical file system
(foldoc) | hierarchical file system
A file system in which the files are
organised into a hierarchy. The nodes of the hierarchy are
called directories while the leaves are the files
themselves.
See also root directory. Compare flat file system.
(1996-11-21)
|
high performance file system
(foldoc) | High Performance File System
HPFS
(HPFS) The native file system for IBM's
OS/2.
(1995-03-06)
|
installable file system
(foldoc) | installable file system
(IFS or "File System Driver", "FSD") An
API that allows you to extend OS/2 to access files stored
on disk in formats other than FAT and HPFS, and access
files that are stored on a network file server.
For example an IFS could provide programs running under OS/2
(including DOS and Windows programs) with access to files
stored under Unix using the Berkeley fast file system.
The other variety of IFS (a "remote file system" or
"redirector") allows file sharing over a LAN, e.g. using
Unix's Network File System protocol. In this case, the
IFS passes a program's file access requests to a remote file
server, possibly also translating between different file
attributes used by OS/2 and the remote system.
Documentation on the IFS API has been available only by
special request from IBM.
An IFS is structured as an ordinary 16-bit DLL with entry
points for opening, closing, reading, and writing files, the
swapper, file locking, and Universal Naming Convention. The
main part of an IFS that runs in ring 0 is called by the
OS/2 kernel in the context of the caller's process and
thread. The other part that runs in ring 3 is a utility
library with entry points for FORMAT, RECOVER, SYS, and
CHKDSK.
EDM/2 article (http://edm2.com/0103/).
(1999-04-07)
|
macintosh file system
(foldoc) | Macintosh file system
data fork
desktop database
resource fork
A file on the Macintosh consists of two parts,
called forks. The "data fork" contains the data which would
normally be stored in the file on other operating systems.
The "resource fork" contains a collection of arbitrary
attribute/value pairs, including program segments, icon
bitmaps, and parametric values. Yet more information
regarding Macintosh files is stored by the Finder in a
hidden file, called the "Desktop Database".
Because of the complications in storing different parts of a
Macintosh file in non-Macintosh file systems that only handle
consecutive data in one part, it is common to only send the
Data fork or to convert the Macintosh file into some other
format before transferring it.
(1996-03-03)
|
network file system
(foldoc) | Network File System
NFS
(NFS) A protocol developed by
Sun Microsystems, and defined in RFC 1094, which allows a
computer to access files over a network as if they were on its
local disks. This protocol has been incorporated in
products by more than two hundred companies, and is now a {de
facto} standard. NFS is implemented using a {connectionless
protocol} (UDP) in order to make it stateless.
See Nightmare File System, WebNFS.
(1994-12-12)
|
nightmare file system
(foldoc) | Nightmare File System
Pejorative hackerism for Sun's Network File System (NFS).
In any nontrivial network of Suns where there is a lot of NFS
cross-mounting, when one Sun goes down, the others often
freeze up. Some machine tries to access the down one, and
(getting no response) repeats indefinitely. This causes it to
appear dead to some messages (what is actually happening is
that it is locked up in what should have been a brief
excursion to a higher spl level). Then another machine
tries to reach either the down machine or the pseudo-down
machine, and itself becomes pseudo-down. The first machine to
discover the down one is now trying both to access the down
one and to respond to the pseudo-down one, so it is even
harder to reach. This situation snowballs very quickly, and
soon the entire network of machines is frozen - worst of
all, the user can't even abort the file access that started
the problem!
Many of NFS's problems are excused by partisans as being an
inevitable result of its statelessness, which is held to be
a great feature (critics, of course, call it a great
misfeature). ITS partisans are apt to cite this as proof
of Unix's alleged bogosity; ITS had a working NFS-like
shared file system with none of these problems in the early
1970s. See also broadcast storm.
[Jargon File]
|
nt file system
(foldoc) | NT File System
NTFS
(NTFS) The native file system of {Windows
NT}.
(1995-03-06)
|
nightmare file system
(jargon) | Nightmare File System
n.
Pejorative hackerism for Sun's Network File System (NFS). In any nontrivial
network of Suns where there is a lot of NFS cross-mounting, when one Sun
goes down, the others often freeze up. Some machine tries to access the
down one, and (getting no response) repeats indefinitely. This causes it to
appear dead to some messages (what is actually happening is that it is
locked up in what should have been a brief excursion to a higher spl
level). Then another machine tries to reach either the down machine or the
pseudo-down machine, and itself becomes pseudo-down. The first machine to
discover the down one is now trying both to access the down one and to
respond to the pseudo-down one, so it is even harder to reach. This
situation snowballs very quickly, and soon the entire network of machines
is frozen — worst of all, the user can't even abort the file access that
started the problem! Many of NFS's problems are excused by partisans as
being an inevitable result of its statelessness, which is held to be a
great feature (critics, of course, call it a great misfeature). (ITS
partisans are apt to cite this as proof of Unix's alleged bogosity; ITS had
a working NFS-like shared file system with none of these problems in the
early 1970s.) See also broadcast storm.
|
|