SlackwareThis Forum is for the discussion of Slackware Linux.
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.
EDIT: Haha I wrote "in linux" in the thread, but what else could I be talking about.
I know I can put dirty words in rc.local to see them when I boot up. Though I want to have two dirty words that I can choose from. Do I need to insert some code into the rc.local and prompt myself for user input, or am I required to create some sort of second file?
Is it going to look like something like this?
Code:
omgerror:
PRINT PLZ TYPE
WAITFORHIMTOTYPE
If (HE TYPES 1)
echo poop
If (HE TYPES 2)
echo vagina
ELSE
goto omgerror
I used the click here to find similar threads, and I could search multiple posts on dual boot systems, but instead I posted. Thanks in advance.
You CAN use rc.local, but personally, I would write a seperate script, and call it from rc.local (easier to change/edit things).
For example, I made a script for running NAT and a DHCP server in a rc.nat script, then called it from rc.local. When I didn't need routing/DHCP server anymore, I just commented out the line in rc.local
You CAN use rc.local, but personally, I would write a seperate script, and call it from rc.local (easier to change/edit things).
For example, I made a script for running NAT and a DHCP server in a rc.nat script, then called it from rc.local. When I didn't need routing/DHCP server anymore, I just commented out the line in rc.local
Hmm, good idea. However, I'm looking for a specific choice between my hidden SSID wifi network at home and my schools PEAP network. While comments *would* work. I'd like some sort of menu. As it is I've either got to do things with iwconfig or do things with wpa_supplicant. I could just throw them all in the rc.local, but that seems like the kind of thing that would cause trouble.
Look in rc.wlan and rc.wireless. You can setup different networks using the config files for them. For example: I have two wireless networks in my house, one for the lan, one for vpn for work. I can choose between them using the config scripts and wireless tools in KDE.
I'm kind of baffled. It seems like those only allow normal configuration and don't let me specify a wpa_supplicant config file. If there is anyway I can just run what lines I need to run to connect to my home network or run what lines I need to run to connect to my school network. I'd really rather do that than deal with the config files at all.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.