"Perry E. Metzger" <perry@piermont.com> writes:
> Tim Rightnour <root@garbled.net> writes:
> > On 09-Mar-99 Havard.Eidnes@runit.sintef.no spoke unto us all:
> > #   o The current sysinst is IMHO way too insistent on manual
> > #     interaction during the installation.  Requiring a keystroke for
> > #     each "user-visible" command that is executed is, um... "highly
> > #     undesirable".
> > 
> > I found this useful at first while debugging sysinst.. but I can see your point
> > now..  Perhaps an alarm function that continues after 5 seconds.  My problem is
> > the classic "newfs blows up, and then scrolls right off the screen and you
> > never get a chance to see it".
> 
> If something blows up, it will have a non-zero exit code, and you can
> stop then.

Oh, and...

1) if something doesn't have a non-zero exit code, that's a bug we can 
fix.
2) if it does help debugging anyway, we can have an option in sysinst
to turn on the pause behavior if we want it.

Perry