goer@sophist.uucp (Richard Goerwitz) (02/06/90)
I was poking through fsanalyze to see if I could get it
running under Xenix/386. This was not a problem. It
took basically three adjustments. I defined SUPERBOFF
as 1024L, defined the OS as OS_ATT, and then I screwed
with the macro that checks to see if the file system has
been cleaned properly. Here's the question:
Fsanalyze as it stands wants to read the superblock into
a filsys structure, then check one of its fields (like
I said above) to see if the file system needs to be fsck'd.
The macro (see is_ok in fsconfig.h) looks for a field with-
in the filsys structure called s_state. This does not
exist in my Xenix superblocks. Instead, I just poked
around until I found something that looked good: s_clean.
I then rewrote the macro to be
... ((fs)->s_clean = S_CLEAN)
Was this the right decision? I notice that John Haugh simply
did away with the whole sordid affair by defining XENIX/286
as his os, and indicating that he had a command /etc/fsstat.
I don't have this command. So I had to take my best guess at
what would be a reasonable equivalent to s_clean under Xenix.
Does anyone have any suggestions on this score?
Should I define SUPERBOFF myself in one of the .h files?
-Richard L. Goerwitz goer%sophist@uchicago.bitnet
goer@sophist.uchicago.edu rutgers!oddjob!gide!sophist!goerchip@chinacat.Lonestar.ORG (Chip Rosenthal) (02/07/90)
In article <7472@tank.uchicago.edu> goer@sophist.UUCP (Richard Goerwitz) writes: >I was poking through fsanalyze to see if I could get it >running under Xenix/386. I don't understand what the problem is. I ported it to XENIX, and Michael Young incorporated the changes in the 4.1 release. If you make off of the Mkfile.xenix it works |just fine| under 2.2 and 2.3. For reference, the version I'm running is 4.1.1.3. -- Chip Rosenthal | Yes, you're a happy man and you're chip@chinacat.Lonestar.ORG | a lucky man, but are you a smart Unicom Systems Development, 512-482-8260 | man? -David Bromberg