Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
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.
# Default runlevel. The runlevels used by RHS are:
# 0 - halt (Do NOT set initdefault to this)
# 1 - Single user mode
# 2 - Multiuser, without NFS (The same as 3, if you do not have networking)
# 3 - Full multiuser mode
# 4 - unused
# 5 - X11
# 6 - reboot (Do NOT set initdefault to this)
I had the same problem. I think its actually the mouse driver that appears even in text mode. Its one of the startup scripts, but I can't remember exactly which one I killed to get rid of it. Its one of the following:
gpm <-- I *THINK* it was this one
That's weird... gpm has nothing to do with X... X has its own mouse driver. gpm is for console (text mode) mouse operations.
One more thing... I have RH7.2 and I don't have the "SV:123456:respawn:/command/svscanboot" line... I am not sure what SV stands for, but in any case, you may want to check out the file /command/svscanboot. I have a RH7.2 installation (several boxes, actually) and I don't even have the /command directory/partition.
I've managed to shutdown KDM but it was more blind luck then anything else. Stopping nsflock did the trick. I'm not sure what nfslock does or did. Maybe someone can shed some light on that. However, NFS is Network Filesystem, which uses sunrpc (port 111), which coincidently was also tunred on by default. I'm gonna go out on a limb here and say KDM was turned to allow other computers w/ GUI's file share via sunrpc. BTW, the "sun" in sunrpc" comes from Sun Micosystem, who developed NFS. Just some useless information for ya.
As for the svscanboot script, I did find a path to /usr/X11R6, which I believe runs X windows, which brings us back to KDM. Do I sound like I know what I'm talking about. I hope so. Anyways, a big thank you to everyone for sticking through long thread. The mystery that is KDM has been solved...for now.