Sign me up for testing.
On Sat, Jan 30, 2016, 5:16 PM Prof Brucee wrote:
> Any objections to me rewriting rc in go without all known bugs?
> On 31/01/2016 3:36 AM, wrote:
>
>> in the rc shell, when one has exec statement and the exec fails, rc tries
>> to
>> continue interpreting statements aft
> Any objections to me rewriting rc in go without all known bugs?
None from me, although you may want to rename it. And benchmark it,
for what that is worth.
Lucio.
Any objections to me rewriting rc in go without all known bugs?
On 31/01/2016 3:36 AM, wrote:
> in the rc shell, when one has exec statement and the exec fails, rc tries
> to
> continue interpreting statements after the exec which fails with a strange
> EOF error because in the process of prepari
thanks cinap,
your advice resolved my problem.
aux/wpa is pretty wise!
> 2016/01/31 6:37、cinap_len...@felloff.net のメール：
>
> aux/wpa doesnt need to be restarted really. it uses factotum to derive
> the psk using the current essid read from the wifi drivers ifstats file.
> so to switch essid's you
aux/wpa doesnt need to be restarted really. it uses factotum to derive
the psk using the current essid read from the wifi drivers ifstats file.
so to switch essid's you can just set essid with echo essid >
/net/etherX/clone
or the ctl file. (note, you can read the ifstats file to see the list
in the rc shell, when one has exec statement and the exec fails, rc tries to
continue interpreting statements after the exec which fails with a strange
EOF error because in the process of preparing filedescriptors for exec,
the very fd thats used to read the script was closed.
burnzez provided an
