Salix Forums

Or do
to access root user PATH. Apologies for the mistake.

mimosa wrote:You should see either wlan0 or wlan1 in the output. Go back to wicd and check the settings are looking at the right one. I think this problem is more common with the ethernet (eth0 versus eth1) but it's worth checking.

I didn't even bother with the terminal. I just went to wicd and switched it from wlan1 to wlan0 to see what happened. Bingo, the wi-fi connections were all back. Really simple solution. I just had no idea what to look for. Thanks for the help.

laprjns wrote: That is because most of the commands that you use as root are not in the normal users PATH. Commands like reboot and spkg are in /sbin and when called with sudo need to have the full path. For example :

sudo /sbin/reboot

I should probably be way more embarrassed about not realizing this sooner, than I currently am. Thank you for that tip, because I'm sure I'd eventually have been banging my head for days on end trying to figure out how to remedy this! I'm still new to the concept of environment variables in general; I do a lot of "export HOME" with programs where I use multiple libraries or profiles (Firefox, Chromium, Shotwell, Calibre, etc.), but that's really the only such variable that I've had occasion to play with up to now.

laprjns wrote:That is because most of the commands that you use as root are not in the normal users PATH. Commands like reboot and spkg are in /sbin and when called with sudo need to have the full path. For example :

sudo /sbin/reboot

Wait... No. In 14.1, /sbin and /usr/sbin are in the user's PATH, if the user is in the wheel group.

Would this be something that got set up in the final release, but those of us who started with beta need to do manually? That was what I first assumed (it's just on my machine you can't do sudo iwconfig, must get round to fixing it, can't remember how).

If you have the wheel-sudo package, it's done.

gapan wrote:Wait... No. In 14.1, /sbin and /usr/sbin are in the user's PATH, if the user is in the wheel group.

You are of course correct. I made the assumption that since tab complete didn't work therefore the command itself would not work.

laprjns wrote:

gapan wrote:

laprjns wrote:Wait... No. In 14.1, /sbin and /usr/sbin are in the user's PATH, if the user is in the wheel group.

You are of course correct. I made the assumption that since tab complete didn't work therefore the command itself would not work.

Autocomplete doesn't work because the command is an argument to sudo and arguments don't autocomplete, ever. If you want autocomplete to work, you can always type the command first, without sudo, then press the Home button and add sudo in front.

I can confirm that installing the wheel-sudo package fixes it. I also needed to manually add my user to the wheel group (which would occur during installation with the final release) and reboot. No infinitives were harmed during the process.

Good tip about TAB and HOME!