Hello,
I thought I might reply to my own query with an answer, since no one else
seems to have been able to provide one. It still has some warts, which I would
greatly appreciate help with, should anyone be able to provide it.
Following a post here:
http://markmail.org/message/goi6cxt7qdcy57up#query:solaris%20startup%20wificonfig+page:1+mid:goi6cxt7qdcy57up+state:results
And using this post as a reference:
http://www.eall.com.br/blog/?p=111
I added the attached service manifest, followed by 'svccfg import
wificonfig.xml', then 'svcadm enable wificonfig' and now wifi connects
automatically on reboot.
One ugliness is that I have to assign the profile name for 'wificonfig
connect' in the xml service manifest file. Using 'wificonfig autoconf' fails
becuase the profile has a WEP password (although I understand why that should
be the case). The failure of the autoconf subcommand has nothing to do with
the environment - it fails from the command line as well, so this is a problem
with wificonfig, not with the service manifest itself. The other snag is that
on boot I get an error:
"svc:/network/wificonfig:default Method "wificonfig connect home" failed with
exit status 1.
This is likely because I have not made the service dependent on bringing up
the ath0 interface. Luckily, SMF retries (and succeeds) in executing the
wificonfig service before it ultimately brings up the dhcp link. So, although
it reports an error initially, it ultimately works.
Any ideas about how to correct these two blemishes would be welcomed.
Thanks.
Erik
--
This message posted from opensolaris.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wificonfig.xml
Type: application/octet-stream
Size: 1580 bytes
Desc: not available
URL:
<http://mail.opensolaris.org/pipermail/opensolaris-help/attachments/20100227/395ba398/attachment.obj>
