thomax@netmbx.UUCP (Thomas) (04/17/89)
help! i need info about the sco xenix file system for 286's and 386's. the info an the man page for 'filesystem' seems to be wrong. what i would like to know is: how is the free list stored? in /usr/include/sys/filsys.h struct filsys is defined. it is the format of the superblock. in the struct, the array s_free[] holds the first NICFREE free block numbers. in unix, s_free[0] is the link to a chain of indirect blocks containing some more free block numbers. unfortunately, this is *not* the way it works in xenix *86. the man page for 'filesystem' is the same as on a vanilla sys v system. i guess sco forgot to document their "enhancements" there. does anyone know? sco? mfg thomax -- *============================================================================* | thomax@netmbx.UUCP Thomas Kaulmann | | ...{pyramid|altger|unido}!netmbx!thomax Alexandrinenstr. 42 | | "the Killer Ducks are comming!!!" 1000Berlin61 |
peter@ontmoh.UUCP (Peter Renzland) (04/27/89)
From article <2576@netmbx.UUCP>, by thomax@netmbx.UUCP (Thomas Kaulmann):
> help! i need info about the sco xenix file system for 286's and 386's.
( Thomas says it doesn't do it the way the manual says )
Well, it sure does it the right way on any XENIX system I've seen.
(But, be careful: 286 and 386 versions have different freelist sizes --
don't mount a 286 disk on a 386 system or you can get into big trouble.)
In a recent data rescue mission I reversed 99% of the effect of someone
doing "rm -rf /", under 2.1.3, and I wouldn't have been able to it without
a reliable freelist.
Now, if only someone could tell me why XENIX destroys all the INODE contents,
except for the dates, when the last link goes ...
(and please don't say "security" -- the data itself is left intact).
--
Peter Renzland @ Ontario Ministry of Health 416/964-9141 peter@ontmoh.UUCP