Re: cu -l /dev/nmdm not setting rows and columns
On 11/27/14 02:02, Craig Rodrigues wrote: On Wed, Nov 26, 2014 at 3:44 PM, John-Mark Gurney j...@funkthat.com wrote: So, what exactly is the problem again? https://lists.freebsd.org/pipermail/freebsd-virtualization/2014-November/003173.html Set the correct $TERM and set also rows and columns. Something like this, will suffice: TERM=xterm; export TERM stty rows 80 stty columns 80 Then the system you are connecting to, will know what to send back to your terminal. HTH, Nikos ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: cu -l /dev/nmdm not setting rows and columns
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 ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: cu -l /dev/nmdm not setting rows and columns
On Wed, Nov 26, 2014 at 3:44 PM, John-Mark Gurney j...@funkthat.com wrote: So, what exactly is the problem again? https://lists.freebsd.org/pipermail/freebsd-virtualization/2014-November/003173.html ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
cu -l /dev/nmdm not setting rows and columns
Hi, I am configuring bhyve VM's with serial consoles directing to /dev/nmdm[n]. I am using cu -l /dev/nmdm[n]B to connect to the console. However, cu does not properly set the value of the rows and columns of my screen. For example, before connecting: # stty -a speed 9600 baud; 30 rows; 91 columns; # echo $TERM xterm # cu -l /dev/nmdm0B Inside the VM which is FreeBSD 10.1: # 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. Thanks. -- Craig ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
Re: cu -l /dev/nmdm not setting rows and columns
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. Having an xterm attached to the other end of an nmdm device isn't too different from swapping say a vt100 with a vt420 or some other terminal with a different resolution on a real serial line. There's no way for the serial driver to know this has happened. The only way to fix the changing-size problem is to have a paravirtualized tty device that has a way of reading the terminal window size and being informed of changes. The virtio-serial specification has this ability, however, the FreeBSD driver for this can't operate in polled mode so can't be the main console port, and in any event there's no bhyve backend for it currently. Or, you can network-login to the guest in which case xterm works fine :) later, Peter. ___ freebsd-virtualization@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to freebsd-virtualization-unsubscr...@freebsd.org
