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.
I seem to recall that a recent Slackware release (somewhere around 12.x) changed how the logo behaved at boot. In earlier releases, if you had the logo turned on, it would stay on after booting was finished and you got the login prompt (runlevel 3, of course). If you wanted to get rid of Tux you had to log in and enter "reset".
Then, it changed where Tux would smoothly disappear right as the screen stopped scrolling and you got the login prompt. That was best in my opinion - I like the tradition of seeing the logo, but if I'm going to stay in the console I like him to go away automatically.
Now with 13.x it's back to where Tux stays on the screen after booting. I've never seen kernel options that control whether he stays or not. Anyone know what does it, or what changed in more recent Slackware kernels?
The logo disappears (and doesn't come back) when you switch to another virtual terminal or when the video mode or the font is changed.
I'd guess your 12.x was configured to set a font; this would happen right before the login prompt.
Distribution: Debian Wheezy/Jessie/Sid, Linux Mint DE
Thanks for the additional replies.
In case you think I am making a big fuss out of nothing I should explain a little bit more.
I am a die-hard Debian user. However the current Debian Testing really disappoints me in terms of stability, completeness and KDE4. This is not how Debian Testing used to be, and I am using it long enough to be able to say that.
So I am very carefully trying to install Slackware because I am impressed by the Slackware community and the way Slack users are devoted to their distro. Then it must be good, isn't it?
No I am not going to explain every detail where I run into trouble as a Debian user. Besides, it it not even that bad, and 99% of the problems I see is because of me lacking experience with Slackware.
I also should explain that I installed Slack on Virtualbox running on a Debian host. That is only for practical reasons, I do this for fun, I wanted to keep a machine on which I can do my normal stuff and didn't want to have another machine on my workbench so I had to turn my chair all the time back and forth to switch between the running and the experimental machine.
(This reminds me of another recent thread in this forum: Virtual Machines are not ideal to try out Linux or various distros)
Anyway, I am still working a lot on the command line, and the logo did not always disappear as it should. That is extremely inconvenient when browsing man pages as the pager thinks it has the full screen but part of it is overlaid by the logo. Neither did I have virtual consoles in that VM. This could all be caused by the fact that I am using a VM.
Nevertheless, I didn't see any use for the logo appearing and now it is gone I am much happier.