Patent EP0770966A2 successfully refreshed from Google Patents.
← Back to Patent Explorer
EP0770966A2 Expired / Lapsed EP ⏱️ 0.0 years remaining

Advanced file server

Assignee: NCR International Inc
•
Filing: 1996-10-23
•
Granted: —
•
Expires: 2016-10-23
📄 Original PDF 🌐 Google Patents 🔄 Sync Now

Abstract

Abstract An apparatus and method for enabling users of network which have computers (100, 420, 430, 440, 450) running several different operating systems to access each others files easily. An algorithm is used to create legitimate, meaningful filenames by combining both a filename from a host (100) computer's "native" name space and a unique "inode" number from the host computer's file system (223) assigned for this file. The preliminary information necessary to apply the algorithm can be obtained rather easily, since the host computer's filename and inode number are returned by a well-known UNIX operating system call "getdents(2)". Client computers whose operating systems do not support a particular filename can both see and access a particular file via a special filename that is computed-on-the-fly; this name is not actually stored on the host computer (100) in either the file system or in a file, thereby eliminating a need for storing any additional information in the system. Using an inode number for computing the mapping of a long filename improves the uniqueness of resulting filenames, which is crucial if a client is dealing with large directories of files with similar names.

Inventors

  • 👤 Eric J. Bauer
  • 👤 Elena Nesvetaeva

Bibliographic Details

Application Number —
Jurisdiction EP
Data Source google_patents
Last Synchronized 2026-11-08 02:25
CPC Classifications
G; G06; G06F; G06F16/00; G06F16/10; G06F16/16; G06F16/164; G06F16/166; Y; Y10; Y10S; Y10S707/00; Y10S707/99931

Claims Analysis

Total Claims: 6
Claim 1
Independent Claim 124 words
A method of computing unique filenames for computer files shared among users of a computer network (100, 420, 430, 440, 450), said network including a file server in a host computer (100) running a host operating system and at least one client computer (420, 430, 440, 450) which may utilize a client operating system different from said host operating system, characterized by the steps of: providing a filename of a file (200) from said file server, said filename being native to said host computer (100); accessing an inode number assigned to said file by said file server of; and combining said filename and said inode number to create said unique filename, wherein said unique filename is a valid filename for said client operating system.
Claim 2
Dependent Claim 43 words
The method according to Claim 1, characterized in that said step of combining includes the steps of: formatting said filename to eliminate any characters unacceptable to said client operating system; and truncating said filename to a length acceptable by said client operating system.
Claim 3
Dependent Claim 36 words
The method according to Claim 1, characterized in that said step of combining includes the step of: appending, and overwriting if necessary, characters of said filename with a hashed inode number derived from said inode number.
Claim 4
Dependent Claim 25 words
The method according to Claim 3, characterized in that said hashed inode number is a three digit decimal representation of said inode number modulus 1000.
Claim 5
Dependent Claim 35 words
The method of Claim 1, characterized in that said unique filename is computed on-the-fly by said file server during the reporting and accessing of files, whereby storage of static alternative filename references is not required.
Claim 6
Dependent Claim 124 words
A file server apparatus for storing computer files shared among users of a computer network, (100, 420, 430, 440, 450) said network including a host computer (100) containing said file server and running a host operating system, and client computers (420, 430, 440, 450) which may utilize a client operating system different from said host operating system, characterized by comprising: means for providing a filename of a file from said file server apparatus, said filename being native to said host computer (100); means for accessing an inode number assigned to said file by said host computer; and means for combining said filename and said inode number to create said unique filename, wherein said unique filename is a valid filename for said client operating system.

References Cited (Backward Citations)

No citation records indexed.

USPTO Annuity & Maintenance Windows

Maintenance schedule is calculated for granted US utility patents.

Assigned Categories & Tags

No categories assigned to this patent yet.

Assign Category Tag