Some notes on problems in A/UX

[David W. Berry]

In article <271 at oglvee.UUCP> jr at oglvee.UUCP (Jim Rosenberg) writes:
>From article <6836 at well.UUCP>, by pokey at well.UUCP (Jef Poskanzer):
>> When I was using pre-release A/UX, I would typically reboot once or twice
>> a day.  fsck would find and fix a problem about on about half of these
>> reboots.  Maybe once in two weeks, it would do a double reboot as you
>> describe above.  And twice in N months, it went into continuous reboots.
>> fsck would claim to have fixed the problem, reboot, and then do exactly
>> the same thing again.  When I showed this to a wizard he mumbled something
>> about fsck not flushing all its buffers -- sounds pretty dangerous to me!
>
>I probably shouldn't stick my nose into this, since I don't have a Mac II and
>don't run A/UX.  But it seems to me that the better part of wisdom in dealing
>with fsck is to know how to boot a "lifeboat" UNIX system from a floppy, and
>fsck your "raw" hard disk root file system while it's *UNMOUNTED*.  This would
>allow any number of passes through fsck without any auto reboots.
	Well, on A/UX it's pretty simple.  You boot the Mac OS, run sash
and instead of launching unix, you run the standalone fsck.  The standalone
environment allows you to run many of the common utilities (dd, cp, mv, rm,
ed, fsck, fsdb, and more)  It's not a bootable floppy based unix, but it
does solve most of the problems.
>-- 
>Jim Rosenberg                        pitt
>Oglevee Computer Systems                 >--!amanue!oglvee!jr
>151 Oglevee Lane                      cgh
>Connellsville, PA 15425                                #include <disclaimer.h>




Opinions:  MINE, ALL MINE! (greedy evil chuckle)

David W. Berry
apple!dwb at sun.com	dwb at apple.com	973-5168 at 408.MaBell