Path: utzoo!attcan!uunet!zaphod.mps.ohio-state.edu!usc!ucsd!pacbell.com!att!cbnewsl!wag1
From: wag1@cbnewsl.att.com (d.wagley)
Newsgroups: comp.sys.mac.misc
Subject: Re: Not another NeXT defector???!!!
Summary: fsck output
Message-ID: <1990Nov8.203230.18538@cbnewsl.att.com>
Date: 8 Nov 90 20:32:30 GMT
References: <1990Nov7.015140.239@agate.berkeley.edu> <TWL.90Nov8121433@boojum.cs.brown.edu>
Organization: AT&T Bell Laboratories
Lines: 13

In article <TWL.90Nov8121433@boojum.cs.brown.edu>, twl@cs.brown.edu (Ted "Theodore" W. Leung) writes:
> So what does the novice user do when fsck starts to print all sorts of
> messages about bad cylinder groups and incorrect inode counts and bad
> superblocks? 

Does the Next machine dump this information to the screen by default?

If I remember right (and somebody correct me if I don't, it's been a while)
the AT&T Unix PC hid all of that from the user. If there was a file system
problem, it went off and fixed it without dumping the fsck output to the
screen. The point is that it wouldn't have to.

					Doug