SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hello all, I am a computer sales and service guy in a small town in KY. I have started to grow a small Slackware Linux community here and so far have been able to resolve any customer requests doing a search here on Linuxquestions, but just today I got one I could not fix this way. First off let me say that I AM A LINUX NEWBY! I know where most stuff is located..or how to use Locate if not. I can Jed a little and rebuild a kernel if I need to. That's about it so answers in plain simple is best A customer asked me if there was a way to A. Hide all the loading text that scrolls by at startup. B. Have it boot to an account selection window (like windows). For myself, I hardly ever use items like this..My mentor is training me in the use of the command prompt only at this stage, but the end users like pretty GUI pics and seem to freeze at the first sign of a text prompt of any sort. So there you go. I know I can set it to autostart KDE (or your xWindow of choice) after login. I do that on my wifes account, but that is not what I was looking for. Any help is appreciated even if it is just a link to a hint
There might be a way to disable text output on boot. But I strongly advise against it ... very very strongly against it. What if you get a kernel panic and you don't know what it says. Now that would suck !
If they want pretty GUIs ... guess they should try Ubuntu or somethin
Last edited by H_TeXMeX_H; 04-16-2007 at 10:11 PM.
LOL, While I understand that, my customers wouldn't. Noone here had even known there were OSs other than windows. I agree about no text output being a Bad Bad thing. But you know end users. The want fluff and they want to point click and never see any text that isn't surrounded by some form of colored graphic.
bootsplash (& Co.) is what will hide the startup text. It's not easy to implement under Slackware, though.
You can hide the messages from the kernel itself by including 'quiet' in you boot command options. And the rest could be hidden by commenting out echo commands in the init scripts.
Well, I guess you could try, but make sure there is some way to actually read errors if something goes wrong. I dunno, if the kernel panics, will it spit out errors that you can read that bypass the 'quiet' option ? I know most times when kernel panics ... it's time to press the reset button, cuz the kernel won't respond.
I just tend to see what might go wrong ... cuz you know it will. I'm a strong believer of Murphy's laws
Last edited by H_TeXMeX_H; 04-17-2007 at 10:29 AM.
Yeah, that's a good idea. Have the normal startup use the quiet option, and then add another entry to the bootloader, for the same kernel, where you can actually see what's happening (no quiet option).
A. Hide all the loading text that scrolls by at startup.
Pass the quiet boot parameter to the kernel when booting from GRUB or LILO. If you later want to read the boot output results, open /var/log/dmesg. Don't worry about kernel panics as they will override the quiet option and let you know if things stall.
B. Have it boot to an account selection window (like windows).
Modify /etc/inittab to boot to init 4. Or, you can pass the init 4 option as a boot parameter. Or you can do both:
Don't worry about kernel panics as they will override the quiet option and let you know if things stall.
That's good to know. (and something I didn't know )
But you know end users. The want fluff and they want to point click and never see any text that isn't surrounded by some form of colored graphic.
Don't be so pompous and condescending. Especially when you admit to being a newbie. Were you born with perfect knowledge?
I think, for the most part, it is very true. That's what most end users want. I don't think it is pompous or condescending to say that, cuz it's also true. If it weren't true .... maybe we would all be using Linux ...
Last edited by H_TeXMeX_H; 04-17-2007 at 10:51 PM.