home *** CD-ROM | disk | FTP | other *** search
- > [.. in reply to a letter to Mike about "ofiles" ..]
- >
- > Well, I recently ran across a posting of something called "ofiles" for
- > BSD, and remembering your message, I decided to see if it ported
- > easily to the Unix PC. It did, and here it is, although it doesn't
- > seem to exactly fit your description. It seems to be just a "fuser"
- > program with slightly fancier output.
- >
- > Here's the BSD version and the Unix PC version. If you can track down
- > the program you were talking about, I'd like to see it.
- >
- > -=] Ford [=-
- >
- > "The number of Unix installations (In Real Life: Mike Ditto)
- > has grown to 10, with more expected." ford@kenobi.cts.com
- > - The Unix Programmer's Manual, ...!sdcsvax!crash!elgar!ford
- > 2nd Edition, June, 1972. ditto@cbmvax.commodore.com
-
- I hacked on this to produce a version which runs on SCO Xenix/386 2.2.3.
- The biggest changes involved dealing with the floating structures in UNIX
- for the 3B1. Strange machine ...
-
- I added code to locate the inode for the text table entry, if the process
- structure indicated one existed. This prints as an 'x' character. I also
- added setuid() calls around the opens of the device files which required
- root privilege. Yes, it was possible to install this program as SUID root
- and have anyone be able to determine the status of any file on the system,
- even if the user would not normally have access to that file. Not exactly
- a good idea ...
-
- The code has had all of the 3B1 dependent things removed and a little
- spring cleaning applied.
-
- - John.
- --
- John F. Haugh II UUCP: ...!cs.utexas.edu!rpp386!jfh
- "A friend of BIFF'S for a fifth of a year" Domain: jfh@rpp386.cactus.org
-