[Buildroot] Run getty on multiple ttys and Box-drawing character

[MOHAMMAD RASIM]

On 06/24/2018 04:56 PM, Carlos Santos wrote:
>> From: "MOHAMMAD RASIM" <mohammad.rasim96 at gmail.com>
>> To: "Peter Korsgaard" <peter at korsgaard.com>
>> Cc: "buildroot" <buildroot at busybox.net>
>> Sent: Friday, June 22, 2018 9:25:43 PM
>> Subject: Re: [Buildroot] Run getty on multiple ttys and Box-drawing character
>> Yes, I've already set up a post-build script that modifies the inittab, didn't
>> know about the raspberrypi script, could have saved me some time :(
>> I have two Ideas that can be used for tty:
>> 1- make a startup script in /etc/init.d/ that parses the /proc/cmdline and start
>> gettys accordingly, I've tried it and it works but obviously, It's not the
>> right way to do these things(no respawning).
>> 2- in the /init script after mounting devtmpfs and before running (exec
>> /sbin/init "$@") we add the same code from the post-build script that parses
>> /proc/cmdline and adds ttys to /etc/inittab (Didn't try this but seems like the
>> right way to do it).
> This works but is a bit dangerous. If the script fails to parse cmdline
> you may get system on which you can not log in. Ensure that you have an
> inittab file with least a line containing something like this
>
>      cons::respawn:/sbin/getty -L console 115200 vt100
>
> (or the corresponding one for BusyBox init).
>
> Notice also that /init is a script only when rootfs is in a cpio
> archive, which is selected along with initrd, but not for other
> rootfs configurations.
>
>> As for the TERM settings I've set up my TERM to 'xterm-256color' which is the
>> most capable terminal I know and the characters don't show.
>> I don't think the problem is related to the terminal, instead, I think It has
>> something to do with charset and character encoding .
> Are you using a terminal emulator (e.g. PuTTY) to access the console?
> If yes, check its character encoding configuration.
>
No, I'm not using PuTTY, I'm running the script in the 
framebuffer(/dev/console).
Actually the problem only appears when running from the framebuffer, if 
I ssh to the system and run the script I can see the box drawing 
normally (because I'm using a terminal emulator, e.g gnome-terminal).