Return to Filing4d.n CVS log

Up to [CSRG BSD Unix] / 43BSDTahoe / new / xns / man

Annotation of 43BSDTahoe/new/xns/man/Filing4d.n, revision 1.1

1.1     ! root        1: .TH "FILING4D" 1 "3-Feb-87" "Xerox (WRC)"
        !             2: .\" $Header: Filing4d.n,v 1.2 87/04/01 13:53:59 ed Exp $
        !             3: .SH NAME
        !             4: Filing4d - XNS Filing version 4 service
        !             5: .SH DESCRIPTION
        !             6: .I Filing4d
        !             7: is a service for the XNS Courier Filing protocol version 4.
        !             8: This service implements a subset of the Filing Protocol which is similar
        !             9: to the XNS FilingSubset Protocol; however, extensions to this subset
        !            10: provide additional functionality as well as compatibility for use with 
        !            11: XDE FileTool and Xerox Network Services/IBM PC.
        !            12: .PP
        !            13: The service is forked from the XNS courier daemon,
        !            14: .IR xnscourierd , 
        !            15: upon connection requests for version 4 of the Filing Protocol.
        !            16: .SH "PROCEDURE SUPPORT"
        !            17: The Filing Protocol defined procedures 
        !            18: .IR Logon , 
        !            19: .IR Logoff , 
        !            20: .IR Continue , 
        !            21: .IR Open , 
        !            22: .IR Close ,
        !            23: .IR Create ,
        !            24: .IR Delete ,
        !            25: .IR GetAttributes ,
        !            26: .IR ChangeAttributes ,
        !            27: .IR Copy ,
        !            28: .IR Move ,
        !            29: .IR Store ,
        !            30: .IR Retrieve ,
        !            31: .IR Replace ,
        !            32: .IR Serialize ,
        !            33: .I Deserialize
        !            34: and
        !            35: .I List
        !            36: are supported. The extent of support is
        !            37: consistent with the FilingSubset Protocol with extensions added to provide
        !            38: additional functionality and interoperability.
        !            39: .SH "ATTRIBUTE SUPPORT"
        !            40: Attribute support within the service is also consistent with the FilingSubset
        !            41: Protocol. All attributes defined as mandatory in the FilingSubset Protocol
        !            42: are supported (\fIcreatedOn\fR, 
        !            43: .IR dataSize , 
        !            44: .IR isDirectory , 
        !            45: .IR modifiedOn , 
        !            46: .IR pathname, 
        !            47: .IR type ).
        !            48: Additional attributes (\fIcreatedBy\fR, 
        !            49: .IR fileID , 
        !            50: .IR name ,
        !            51: .IR readOn , 
        !            52: .IR version)
        !            53: are supported
        !            54: and/or allowed to provide interoperability. 
        !            55: .PP
        !            56: Additional Viewpoint related attributes are uninterpreted by the 
        !            57: file service; however, they are retained and returned to the client when
        !            58: retrieved.
        !            59: .PP
        !            60: The \fIOpen\fR procedure allows files to be identified through the use of the
        !            61: .IR fileID ,
        !            62: .I name
        !            63: or 
        !            64: .I pathname
        !            65: attributes.
        !            66: .PP
        !            67: .I Filing4d
        !            68: maintains the file type attribute in a manner consisten with the storage of
        !            69: the file locally. Files are stored locallay as described in 
        !            70: \fIViewpointfiles(5N)\fR. Uninterpreted attributes are
        !            71: retained with the file content so that they may be returned when asked for.
        !            72: .PP
        !            73: Since the service does not maintain the file types explicitly within the Unix
        !            74: file system
        !            75: .I Filing4d
        !            76: will make an educated guess of the file type based on the contents and/or
        !            77: stored attributes of the file, when a client requests the type of a file.
        !            78: .SH "FILE TRANSFERS"
        !            79: .I Filing4d
        !            80: currently makes a distinction between  
        !            81: .I tText 
        !            82: and other file types for use during file transfer. Files of type
        !            83: .I tText
        !            84: undergo a translation of contents for compatibility with existing Filing
        !            85: implementations; Unix EOL characters
        !            86: (\\n) are translated to and from Xerox EOL characters (\\r), Xerox left
        !            87: arrow characters are translated to underscore, etc.
        !            88: All other files are treated as a binary stream with no translation incurred.
        !            89: .SH AUTHENTICATION
        !            90: The Filing Protocol (version 4) allows clients to supply a set of primary
        !            91: credentials and accompanying verifier. Since the credentials and verifier
        !            92: are encrypted in a form recognizable by the network Authentication service,
        !            93: there is no mechanism available for supplying a verifier to be used by the
        !            94: host system for verification.
        !            95: .PP
        !            96: .I Filing4d
        !            97: uses the following assumptions for user validation. Credentials and verifiers
        !            98: must be of type
        !            99: .IR simple .
        !           100: The
        !           101: .I Logon
        !           102: will be rejected if 
        !           103: .I nullCredentials 
        !           104: or 
        !           105: .I strong 
        !           106: credentials are supplied. The credentials and verifier will be validated 
        !           107: against the network Authentication service and rejected if not successful.
        !           108: The object name supplied in the credentials will then be used as the user
        !           109: name for validation against the Unix /etc/passwd file. If the name does
        !           110: not exist, the procedure will be rejected. If the user is valid, the 
        !           111: .I Logon
        !           112: will be successful with no ensuing Unix password verification. (The assumption
        !           113: is that a valid network user that has an account on the host is also a valid
        !           114: host user.) 
        !           115: .PP
        !           116: In some situations, the credentials supplied may contain a full Clearinghouse
        !           117: name rather than a more convenient Clearinghouse alias (i.e., \*(lqJohn Q.
        !           118: Public:Computer Science:Cornell-Univ\*(rq). In these instances, the supplied
        !           119: name obviously will not pass as a Unix user name.
        !           120: .I Filing4d
        !           121: therefore, will strip the last name of the object field (i.e., Public)
        !           122: and attempt to use this as the user name for the Unix host. An additional
        !           123: conversion to all lower case characters will take place if the original
        !           124: attempt fails.
        !           125: .SH "SEE ALSO"
        !           126: Filing5d(1N), Filing6d(1N), FilingSubset1d(1N), Viewpointfiles(5N)
        !           127: .br
        !           128: Filing Protocol, \s8XNSS\s0 108507 (July 1985)
        !           129: .br
        !           130: Filing Protocol, \s8XNSS\s0 108605 (May 1986)
        !           131: .br
        !           132: FilingSubset Implementor's Guide, \s8XNSG\s0 098609 (September 1986)
        !           133: .SH NOTES
        !           134: A limited subset of the full Filing Protocol is actually implemented.
        !           135: Procedures dealing with controls, access lists or random access are not yet
        !           136: implemented.
        !           137: .PP
        !           138: .I ChangeAttributes
        !           139: only allows the \fIname\fR attribute to be modified.
        !           140: .PP
        !           141: Service related attributes (\fIaccessList\fR,
        !           142: .IR checksum ,
        !           143: .IR childrenUniquelyNamed ,
        !           144: .IR defaultAccessList ,
        !           145: .IR numberOfChildren ,
        !           146: .IR ordering ,
        !           147: .IR parentID ,
        !           148: .IR position ,
        !           149: .IR subtreeSize ,
        !           150: .IR subtreeSizeLimit )
        !           151: are not implemented within this service.
        !           152: .SH BUGS
        !           153: When used with FileTool, Delete from within FileTool will not work correctly.
        !           154: This is because the Unix XNS implementation does not allow a single Filing
        !           155: session to occur over multiple transport (SPP) connections.
        !           156: .PP
        !           157: For the same reason, wildcard operations within FileTool will not work also.
        !           158: .PP
        !           159: If a connection is left open by FileTool for an extended period of time, a
        !           160: Session Problem or Courier Error may occur. This is caused by the fact that the 
        !           161: Unix service has destroyed the session after a period of inactivity and the  
        !           162: client is responsible for maintaining the open session via a Continue procedure.
        !           163: Unfortunately, FileTool doesn't issue the Continue to keep the session
        !           164: alive.
        !           165: .PP
        !           166: When used in conjunction with the Network Services IBM PC/XNS, the PC user 
        !           167: should specify fully qualified filenames for each command. The \*(lqcd\*(rq
        !           168: command will work but subsequent attempts to access files will result in an 
        !           169: error since \fIFiling4d\fR cannot open files by \fIfileID\fR without a
        !           170: specified directory (i.e., Unix inodes are available only in a specific
        !           171: directory).
        !           172: .SH AUTHOR
        !           173: Ed Flint

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.