From owner-freebsd-bugs  Tue Jan  9 15:43:54 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id PAA18813
          for bugs-outgoing; Tue, 9 Jan 1996 15:43:54 -0800 (PST)
Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA18804
          for <bugs@freebsd.org>; Tue, 9 Jan 1996 15:43:49 -0800 (PST)
Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <14417(9)>; Tue, 9 Jan 1996 15:43:13 PST
Received: by crevenia.parc.xerox.com id <177478>; Tue, 9 Jan 1996 15:40:06 -0800
From: Bill Fenner <fenner@parc.xerox.com>
To: bugs@freebsd.org
Subject: console output for fixit floppy goes to vty2
Message-Id: <96Jan9.154006pst.177478@crevenia.parc.xerox.com>
Date: Tue, 9 Jan 1996 15:39:56 PST
Sender: owner-bugs@freebsd.org
Precedence: bulk

Two bugs to report here:

1. Perhaps mount should say ", perhaps the filesystem is not clean?" when
it gets an "Operation not permitted" error.  I had no clue why the fixit
floppy was refusing to let me mount my root filesystem.

2. Perhaps the fixit sh should be started on vty2; I had no reason to
expect that I had to switch to vty2 to see the

WARNING: R/W mount of / denied. Filesystem is not clean - run fsck.

message that appeared there.

Sigh.

  Bill

(P.S. Maybe it's 3 bugs that I'm reporting here -- the whole reason I needed
to boot the fixit floppy is because the 2.1 upgrade installed the MD5 password
system over my 2.0.5 system that was set up for crypt...)