Date: Sun, 27 Jun 1999 19:13:00 -0400 (EDT) From: aa8vb@ipass.net To: FreeBSD-gnats-submit@freebsd.org Cc: aa8vb@ipass.net Subject: kern/12420: console fails to register tty size changes Message-ID: <199906272313.TAA01194@stealth.ipass.net.>
next in thread | raw e-mail | index | archive | help
>Number: 12420
>Category: kern
>Synopsis: console fails to register tty size changes
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sun Jun 27 16:20:01 PDT 1999
>Closed-Date:
>Last-Modified:
>Originator: Randall Hopper
>Release: FreeBSD 3.2-RELEASE i386
>Organization:
self
>Environment:
Stock 3.2-RELEASE.
>Description:
The FreeBSD console does not pick up row/column size changes as
3.0-RELEASE did when console mode changes are effected before
login. This causes full-screen applications like /usr/bin/more and
less to fail to work correctly.
>How-To-Repeat:
Insert these commands into rc.local and reboot (80x50 and other
modes probably exhibit the same problem):
vidcontrol < /dev/ttyv0 -f 8x8 cp866-8x8
vidcontrol < /dev/ttyv0 132x43
vidcontrol < /dev/ttyv1 132x43
vidcontrol < /dev/ttyv2 132x43
Then log into the console, and run:
% stty size
On 3.2-RELEASE, this results in the incorrect:
25 80
On 3.0-RELEASE, it gives the right answer:
43 132
Strangely, if you rexecute the vidcontrol mode set commands
manually from the console prompt, then the the new window size is
properly registered ("stty size" returns "43 132", and full-screen
apps now work).
>Fix:
Unknown.
>Release-Note:
>Audit-Trail:
>Unformatted:
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?199906272313.TAA01194>