home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!iggy.GW.Vitalink.COM!cs.widener.edu!ukma!gatech!concert!rutgers!njitgw.njit.edu!hertz.njit.edu!dic5340
- From: dic5340@hertz.njit.edu (David Charlap)
- Newsgroups: comp.os.os2.misc
- Subject: Re: Links in HPFS
- Message-ID: <1992Nov11.210240.18923@njitgw.njit.edu>
- Date: 11 Nov 92 21:02:40 GMT
- References: <1992Nov11.171548.7211@midway.uchicago.edu>
- Sender: news@njit.edu
- Organization: New Jersey Institute of Technology, Newark, N.J.
- Lines: 17
- Nntp-Posting-Host: hertz.njit.edu
-
- In article <1992Nov11.171548.7211@midway.uchicago.edu> sip1@midway.uchicago.edu writes:
- >There's certainly the provision for such things as links at the file
- >system level. It would be relatively easy to imagine such a system
- >operating with extended attributes...
-
- Much simpler than that. HPFS uses directory entries that are simply
- pointers to an F-node structure that contains all the file's
- information. These F-nodes are comparable to Unix's inode structure.
- All that needs to be done is add a reference count to the F-node
- structure and allow multiple directory entries to point to the same
- F-node. That's all there is to a hard link. I think it could be done
- in about one day, given the specs for HPFS.
- --
- |) David Charlap | .signature confiscated by FBI due to
- /|_ dic5340@hertz.njit.edu | an ongoing investigation into the
- ((|,) | source of these .signature virusses
- ~|~
-