Date: Mon, 11 Mar 2019 05:49:38 +0100 From: Bernd Walter <ticso@cicely7.cicely.de> To: Ian Lepore <ian@freebsd.org> Cc: bob prohaska <fbsd@www.zefox.net>, freebsd-arm@freebsd.org Subject: Re: Editing on the serial console Message-ID: <20190311044937.GB51206@cicely7.cicely.de> In-Reply-To: <580addeeb90cc317cc65f69bdc39c549a5852806.camel@freebsd.org> References: <20190307035427.GA42903@www.zefox.net> <580addeeb90cc317cc65f69bdc39c549a5852806.camel@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Mar 07, 2019 at 07:46:57AM -0700, Ian Lepore wrote: > On Wed, 2019-03-06 at 19:54 -0800, bob prohaska wrote: > > Editing files in single-user mode on the serial console > > is non-trivial. Both vi and ee have problems displaying > > the file, ed doesn't really try so it works but isn't > > much fun. Is there a better option? When the machine > > boots single-user it reports "can't read /etc/termcap", > > is something misconfigured? > > > > I'm dealing with Raspberry Pi, but am not sure if that's > > the source of the difficulty. > > > > Thanks for reading, > > > > bob prohaska > > > > > > A lot of things work together (or fail to) to cause trouble for apps > that do full-screen terminal stuff. A big part of it is what you're > using as a terminal program. Using cu(1) from an xterm window works > well if you set TERM=xterm in the env (of course you need a termcap > file as you noted). > > Another thing that causes problems is when your terminal window size > isn't known to vi or whatever app is running. You can fix that by > manually doing 'stty rows NN cols NN' to set the right values. I usually don't waste time to setup all that stuff and just use ed(1). It only makes sense to do so if you have to spend more time on the serial console. -- B.Walter <bernd@bwct.de> http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190311044937.GB51206>