Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a problem that I can't resolve for a long time, maybe you can help me. I have a console application written in dialog, this is a couple of simple function for users. I would like to run this dialog inside virtual terminal called fbiterm, but this virtual terminal needs to be run on system startup and inside them i want to run this dialog application.
I read something about change inittab entries but don't know exactly how run this application inside fbiterm.
To generalize your question: you want to start an interactive text-mode application on system boot, but there is no text terminal in which to run the application until after the system has booted and someone has logged in. This is a somewhat common problem. The one workaround that I have used is very messy, and I would be happy if someone could come up with a better solution.
I start up a Gnu screen session. Using some scripting in rc.local, I stuff commands into the screen session, to start up my application(s). Screen is started in multi-user mode, so anyone sufficiently privileged can later connect to the session. The terminal that screen uses initially is an xterm, which uses the virtual X server, xvfb, which is started up before xterm & screen. Much of this would be unnecessary, but for a bug in screen, which causes it to disregard any stuff commands until such time as it has entered the 'attached' state. It can be started in 'detached' mode, and even receive commands in 'detached' mode, but must first have entered the 'attached' state in order to receive any stuff commands. In order to 'attach' during boot time, it requires the terminal, which requires a tty....
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.