DamnSmallLinuxThis forum is for the discussion of DamnSmallLinux.
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.
I'm trying to breathe some life back into my gf's machine. It's old... a Pentium 133 with 16MB of RAM. Oh, and it's a laptop. :-/
It predates USB... hell, predates MMX. But it does have a PCMCIA slot. So we got a PCMCIA USB card. That's all well. Got a USB wifi stick. That works too.
The pain comes with not knowing DSL well enough. I'm trying to rig it up so that the wifi stick connects (via WPA) automatically when she boots.
I've got a script, suid root. suid'd /etc/init.d/networking. suid'd ifconfig (need to bring up wlan0), suid'd wpa_supplicant. Installed and suid'd dhcpd. Put said script at the bottom of .xinitrc so that the whole thing runs at startup.
The problem (aside from it being really ugly) is that it won't aquire a DHCP address. Grr.
Setuid root scripts don't work. Making a bunch of stuff setuid root "just because" is one bad habit you need to drop. If you want to do root stuff in DSL you can use sudo.
Quote:
Originally Posted by headrift
(..) won't aquire a DHCP address (..) won't shut down.
Setuid root scripts don't work. Making a bunch of stuff setuid root "just because" is one bad habit you need to drop.
I wouldn't call it a "habit"... just seemed like a solution to a problem. I've never actually suid root a script until now. I'm trying to make this run without user intervention. She's not going to use the machine if she has to open a terminal and run a bunch of commands just to get online. This needs to be painless on her.
If you know how to do what I'm doing without the evil suid root thing, please let me know.
If you know how to do what I'm doing without the evil suid root thing, please let me know.
If you run 'sudo -l' as unprivileged user in DSL it will read something like "User X may run these commands: (root) NOPASSWD: ALL". Meaning you already have the capabilities to run stuff as root. And as far as I know DSL runs networking stuff on boot in /etc/init.d with the configs from /etc/network/, so what you would need to do once is make the wireless device connect to the network w/o probs. Once the modules are loaded, the device configuration and network settings are OK and iwconfig and dhclient have run this should "just work" and without intervention.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.