Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's 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 just would like to ask about the ways the one can follow to achieve the following
creating Setup box to only run one application same as kiosks in malls and airport , i have application which is auto launch once the device boot in addition to follow remove all ubuntu desktop elements , protect terminal launching by password / custom key combination
That's a moderately large thing, notwithstanding that you may wish to remove the mouse cursor also as part of that.
Short answer is to run the XServer, but not a window manager. This is one part of how I've done that in the past.
There are various settings in the XServer config to do things like rotate the screen, turn off cursors, and so forth. Your application needs also to be able to be full screen with no borders or window styles. This is why it is better to not use a Window manager because all that styling usually does come from the window manager.
There are some situations where you can have your application write directly to the frame buffer, and thus not use even the XServer, but I've never been successful unless I purchased a commercially tuned version of Linux where they have staged this as part of the sale for the specific project.
Other than that, I've said this is a large task. I can offer guidance by way of some former experience with it, however you'll need to go down the path a bit yourself to determine what things work for you as well as what is adequate considering some of it may be a lot of difficult to find settings, which are small and subtle, just not blatantly explained in any documentation.
Thanks for your reply , do you have any documentation , web links for something similar so we can start with it
Quote:
Originally Posted by rtmistler
Hi and welcome to LQ.
That's a moderately large thing, notwithstanding that you may wish to remove the mouse cursor also as part of that.
Short answer is to run the XServer, but not a window manager. This is one part of how I've done that in the past.
There are various settings in the XServer config to do things like rotate the screen, turn off cursors, and so forth. Your application needs also to be able to be full screen with no borders or window styles. This is why it is better to not use a Window manager because all that styling usually does come from the window manager.
There are some situations where you can have your application write directly to the frame buffer, and thus not use even the XServer, but I've never been successful unless I purchased a commercially tuned version of Linux where they have staged this as part of the sale for the specific project.
Other than that, I've said this is a large task. I can offer guidance by way of some former experience with it, however you'll need to go down the path a bit yourself to determine what things work for you as well as what is adequate considering some of it may be a lot of difficult to find settings, which are small and subtle, just not blatantly explained in any documentation.
Thanks for your reply , do you have any documentation , web links for something similar so we can start with it
I do not. Habitual posted a link which leads to additional links and they have some of the details that come to mind about this topic. For instance I neglected to note the dpms and xset s to shut off screen dimming and power saving. However I know of them.
That first level link says about exactly what I say, "It's not for the faint of heart."
General recommendations are:
Be prepared to redo multiple times from scratch
Learn to establish backups and detail all that you've done, be that successful versus not
Study information you can find, such as the link offered by Habitual and other things you can find on the web, key terms are Linux and Kiosk
Have additional things there while you configure and have a second system which you are not setting up, but is there for you to do your general web searching or fetching of information. The additional things are a keyboard, mouse, screen for the system even if you are not going to have a keyboard once it is all set up
Learn how to build and install from source, learn how to write scripts, learn how the system initializes itself and how to create, configure, remove startup daemons or services
Be prepared to tune the system to contain only the services and capabilities you need and only be running the application you need
Learn to use dd to get a backup image of your whole system and then be capable of restoring from a former backup.
You can "do" something like this in an afternoon, however it really depends how far, how secure, how extensive, and how well tested this all needs to be. If it's for an assignment, "get it working" and then tweak it, but show it to your instructor and find out if you've gone far enough. If it's for a museum, government, any form of commercial use, test, test, test it like crazy and then test it some more. Fix all you can find. Have a certified idiot/genius test it for you and then fix all the stuff they find. If they find nothing, you didn't find a good tester, or a you didn't find a "helpful" tester.
And you're asking us if we have documentation or a guide. Haven't you looked this up? How did you come to understand the concept in the first place?
And note that I've already told you a key thing. Kiosk computers typically have touch screens. Even though you won't have a mouse, you'll likely have a mouse cursor. That is NOT convenient on a kiosk. I forget the various ways I've suppressed or removed the mouse cursor, a glimmer tells me it is an XServer setting, another memory (a very old one) tells me I used a "remove the mouse cursor" application of some type. Once again, this also depended on whether I used an actual window manager or just the XServer.
I feel your final solution is going to be a culmination of numerous sources and it will be custom to your needs, or the needs of this project.
There is no single die to cut exactly a kiosk computer that will work perfectly for you in very short order, unless your goals and needs are very loose and the system doesn't have to be tested and hardened to any serious level.
Will this kiosk have a keyboard attached? If so, then you'll probably want to do something to prevent the keyboard escape sequences to switch to console and reset X. I happen to remember a recent thread solving this problem:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.