Date: Thu, 19 Feb 1998 21:27:30 -0500 (est) From: Vince Vielhaber <vev@michvhf.com> To: freebsd-bugs@FreeBSD.ORG Subject: gotcha with fsck? Message-ID: <Pine.OS2.3.96.980219211732.41N-100000@paprika.michvhf.com>
next in thread | raw e-mail | index | archive | help
It seems that on those not so nice occasions where fsck needs to interact
with the operator it also needs /usr/libexec/getty. Here's the problem.
FreeBSD 2.2.5 (new CD from Walnut Creek) with 2 IDE drives, one is /usr
and the other is / (and everything else that goes with it). Fsck musta
had a bigger problem where it needed to ask the operator questions but
it's hung at this point.
I can probably boot from floppy or even repair the disks on another
machine but when the server's in a remote location this won't be an
easy task. There should at least be an automatic mode to get it up
enough to repair it if not just plain fix it. Hell, the majority of
the time the operator's not going to understand the gibberish that
fsck's asking it anyway. Perhaps a timeout till automatic mode kicks
in would fix it.
Any suggested workarounds? I *was* planning on putting this machine
into service this weekend at a remote location but I'm thinking I'll
hold off for now (as long as the other machine is still breathing :)
Note: I'm not on any of the FreeBSD lists at this time, so please at
least CC me on anything.
Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null
# include <std/disclaimers.h> TEAM-OS2
Online Searchable Campground Listings http://www.camping-usa.com
"I'm just not a fan of promoting stupidity!
We have elected officials for that job!" -- Rock
==========================================================================
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.OS2.3.96.980219211732.41N-100000>