From owner-freebsd-current  Sun Oct 12 08:39:06 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id IAA27809
          for current-outgoing; Sun, 12 Oct 1997 08:39:06 -0700 (PDT)
          (envelope-from owner-freebsd-current)
Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA27654;
          Sun, 12 Oct 1997 08:35:55 -0700 (PDT)
          (envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1])
	by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id RAA14759;
	Sun, 12 Oct 1997 17:35:27 +0200 (CEST)
To: Rick Lotoczky <rickl@ic.net>
cc: current@FreeBSD.ORG, sos@FreeBSD.ORG
Subject: Re: possible sc0 problem 
In-reply-to: Your message of "Sun, 12 Oct 1997 10:11:17 EDT."
             <XFMail.971012101450.rickl@ic.net> 
Date: Sun, 12 Oct 1997 17:35:27 +0200
Message-ID: <14757.876670527@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

In message <XFMail.971012101450.rickl@ic.net>, Rick Lotoczky writes:
>
>Hi
>
>Did I miss something or did the virtual terminal capability go away using
>sc0?  It was working fine with the -current kernel from a few days ago.
>It seems to have broken this morning (10/12/97) with the latest cvsup changes.

I saw the same thing.  Use the right ALT key as a workaround...

Soren ???

--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."