Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 26 Nov 2014 18:24:25 +0100
From:      Willem Jan Withagen <wjw@digiware.nl>
To:        Peter Grehan <grehan@freebsd.org>, Craig Rodrigues <rodrigc@FreeBSD.org>
Cc:        "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org>
Subject:   Re: cu -l /dev/nmdm not setting rows and columns
Message-ID:  <54760CC9.1060902@digiware.nl>
In-Reply-To: <54729224.3060402@freebsd.org>
References:  <CAG=rPVdfnsNpAOLUbTH2r5gufJDOg_0-yYeGVouOBx6aj0ZObw@mail.gmail.com> <54729224.3060402@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 24-11-2014 3:04, Peter Grehan wrote:
> Hi Craig,
> 
>> # stty -a
>> speed 9600 baud; 0 rows; 0 columns;
>> # echo $TERM
>> dialup
>>
>> Any idea how I can fix this?  The console inside the VM
>> is quite unusable when it does not have the correct
>> rows/colums set.
> 
>  Not sure how you're getting 'dialup' as the terminal type: the default
> ttys file for 10.1 shouldn't need to be edited, and has
> 
> ttyu0   "/usr/libexec/getty std.9600"   vt100   onifconsole secure
> 
>  The rows/columns is always 0 for uart-style serial lines since it's not
> possible to know what's on the other end. That's why $TERM has to be set
> correctly for these.
> 
>  Or, you can network-login to the guest in which case xterm works fine :)

Or, like in the old days, just assign a TERM env value in your
shell-login script based on the device the shell is connected too.
That'll give you a basic working setup.

Resizing will probably still not automagically work, and will require
extra intervention.

--WjW






Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54760CC9.1060902>