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.
In order to have complete manual control, just make /etc/rc.d/rc.inet1 and rc.inet2 non-executable. Then, create two small scripts which run the commands you need to start and stop the network services.
Some have a Fn key or switch that can turn the wireless on and off. On my Dell 1545n, it's an Fn key; on my Asus, there's a switch on the front of the box just beneath the latch.
The OP voiced a preference to use software rather than hardware, although an Fn-Fx combination would qualify as software. On my Thinkpad T400, Fn-F5 is suppose to support that kind of option, but only directly for that proprietary system. I haven't fiddled with making that work. I probably need to write Yet Another Script and then map that script to the key combination. Supposed to control bluetooth too.
My preference is to stick with the stock slackware scripts and configs and work with that. If I have to edit rc.inet1.conf before I shut down (in order to guarantee no wifi on next boot) that is fine. I would appreciate however some tips on the least intrusive way to do this (ie. what key lines should I comment out/change/delete) and what might the greater consequences of this be.
I'm mostly running on eth0, wired lan (and run local apache servers', so I need localhost), but occasionally travel and need to use public wifi or the home routers of friends (via wifi).
Just make rc.net1 non-executable to disable it on next boot.
"most people want lo to start automatically" I never had this behavior at all until recently when I started using a wireless router. I run a lot of the time as root, so I prefer to have networking setup as a completely manual operation, to avoid security risks.