Tiny Core Linux

Tiny Core Base => TCB Q&A Forum => Topic started by: tinypoodle on August 15, 2010, 05:54:34 PM

Title: Practices to run multiple virtual terminals
Post by: tinypoodle on August 15, 2010, 05:54:34 PM

What are the options, parameters and good practices to run multiple virtual terminals, when TC doesn't make use of running getty's?
What i do at the moment is:

Code: [Select]

sudo openvt -c N su - tc

Thoughts?

Title: Re: Practices to run multiple virtual terminals
Post by: gerald_clark on August 16, 2010, 12:17:06 PM

Edit /etc/inittab and enable additional virtual consoles.
Add /etc/inittab to /opt/.filetool.lst
Add
kill -1 1
to /opt/bootlocal.sh
If you use noautologin boot option add
kill -1 -sh
to /opt/bootlocal.sh

run "filetool.sh backup"

Title: Re: Practices to run multiple virtual terminals
Post by: tinypoodle on August 17, 2010, 07:19:36 PM

what do 'kill -1 1' or 'kill -1 -sh' exactly do in context?

I had considered modifying inittab (and have done so on other systems in past to change number of available VT's).
However, once that TC doesn't run any getty's by default, i would highly prefer to be able to open (and deallocate) VT's dynamically on the fly, according to needs of given moments (avoiding to have getty's running).

Background for starting this thread:
There are 2 apps of extensions which show some erratic behaviour here on console at times. I intend to report them as bugs, but wanted to troubleshoot first and also exclude that my way of opening VT's (as seen in first post) could play any role.

Title: Re: Practices to run multiple virtual terminals
Post by: gerald_clark on August 17, 2010, 09:13:01 PM

kill -1 1 = signal init to re-read inittab.
kill -1 -sh = signal initial shell to enable new login on tty1.