> > equery b /etc/init.d/net.lo
>
> sys-apps/baselayout-1.13.0_alpha2-r1 (/etc/init.d/net.lo ->
> ../../lib64/rcscripts/sh/net.sh)
Hrm, that's new.
My net.lo is not a symlink.
> > equery l baselayout
>
> sys-apps/baselayout-1.13.0_alpha2-r1
But I'm still on baselayout-1.12
> > equery k baselayout
>
> 113 out of 150 files good, with a list of "has wrong mtime"
You can confirm those are all configuration files? If not, please provide
the list...
They are all in /etc/ (including many init.d) except for:
/sbin/runscript.sh
/sbin/functions.sh
/lib64/rcscripts/sh/net.sh
/sbin/depscan.sh
Some of them show incorrect md5sum instead of wrong mtime.
> > grep -Ev '^[[:space:]]*(#.*)?$' /etc/conf.d/net
>
> modules="wpa_supplicant"
> wpa_supplicant_ath0="-Dmadwifi"
> config_ath0=( "192.168.0.3 netmask 255.255.255.0 broadcast
> 192.168.0.255" ) routes_ath0=( "default via 192.168.0.1" )
> essid_ath0="network2"
> modules_ath0=( "!plug" )
It's possible, albeit unlikely, that the two modules lines are conflicting,
try removing both of them and adding:
modules_ath0=( "wpa_supplicant" "!plug")
above your config_ath0 line.
I changed that with no luck.
This may also be some behavior that is wpa_supplicant specific and I've
never used that particular piece of software.
> > grep -Ev '^[[:space:]]*(#.*)?$' /etc/conf.d/net
Sorry, that should have been:
grep -Ev '^[[:space:]]*(#.*)?$' /etc/conf.d/wireless
I actually don't have that file at all.
> > if /etc/init.d/net.ath0 status | grep -q started; then
> > /etc/init.d/net.ath0 restart
> > else
> > /etc/init.d/net.ath0 start
> > fi
>
> How can I execute this from the command line?
You should just be able to type it in or cut/copy and paste from my
original email. bash (and indeed most shells) don't interpret the input
from the command line significantly different than the content of a script
file.
If I use spaces instead of line breaks so I can put it all on one line
it doesn't seem to work out. I'm missing something here.
- Grant
> Please also let me know if you see anything that looks like it might
> be preventing net.ath0 from connecting. It's been slowly getting less
> and less reliable, and now it won't connect no matter how many times I
> ask. net.ath0 on my laptop connects perfectly every time.
:(
Sorry, I'm just not that wireless savvy, but everything looks fine to me.
Again, keep in mind that I've never used wpa_supplicant so I don't know if
that changes things.
--
[email protected] mailing list
