From owner-freebsd-current Mon Jan 6 12:22:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA25447 for current-outgoing; Mon, 6 Jan 1997 12:22:42 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA25424 for ; Mon, 6 Jan 1997 12:22:36 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id VAA15004 for ; Mon, 6 Jan 1997 21:21:16 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA03428 for freebsd-current@freebsd.org; Mon, 6 Jan 1997 21:21:15 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id VAA04701; Mon, 6 Jan 1997 21:16:29 +0100 (MET) Message-ID: Date: Mon, 6 Jan 1997 21:16:28 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-current@freebsd.org Subject: Re: 2.2-BETA comments References: <199701060900.KAA01036@ravenock.cybercity.dk> X-Mailer: Mutt 0.55-PL10 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199701060900.KAA01036@ravenock.cybercity.dk>; from sos@freebsd.org on Jan 6, 1997 10:00:22 +0100 Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As sos@freebsd.org wrote: > > I think the ScrollLock feature used to have problems all the time, in > > particular if output data arrived while one was scrolling back. > > Erhm, could you be more specific about this one ?? I know I use it > this way often and it has newer failed on me (yet). Hit ScrollLock immediately after the interrupts got enabled, i.e. very early in /etc/rc. Browse a little back and forth through the kernel messages, hit ScrollLock again and -- you don't see any messages from /etc/rc. It takes you another return or so to finally see them. But maybe that's also another incarnation of the ``buggy pty'' behaviour only. The latter can be best observed in the Emergency Holographic Shell of a 2.2-ALPHA or -BETA installation floppy. It's simply unusable if you try entering anything while the installation is in progress. Funny, no response. If you switch back to VTY2, you won't get back to VTY4 (though the EHS is still running there), the system beeps only. Now, try again, and start another /bin/sh or /bin/csh on top of the EHS itself -- everything will work fine. (If you ask me: the ``beep if there's nothing open on that VTY'' misfeature is something i already hated in Interactive Unix. I never believed one would implement such a misfeature volunteerely. But i know, you don't ask me. :) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)