Successfully connected to wifi with the frontend and backend
communicating. But there are still problems regarding text capture.

It will take more tedious debugging time... but in the end, it should
work, hopefully.

> On 18/08/2015, Edward Bartolo <edbarx@???> wrote:
>> A) I am at the stage of trying to understand these:
>> a) iw_sockets_open
>> b) iw_get_range_info
>> c) iw_scan
>>
>> The goal is to avoid to have the least number of dependencies.
>>
>>
>> B) I have yet another tempting idea. This is to use only one file for
>> the essids and corresponding passwords. However, this would force me
>> to somehow trick ifup into thinking it is being passed an interfaces
>> file instead of the output from an executable.
>>
>> I found it. But this does work. :)
>> cat /etc/network/interfaces | ifup wlan0
>>
>> What do you think?
>>
>> Now I can use only one file for all the wifi hotspots. I think, it
>> should be a text file only writable by root. As wifi passwords are
>> effective only near their respective wifi hot spots, I shouldn't
>> think, I need to use encryption to make the file unreadable.
>>
>> P.S.
>> Before the actual uploading of the source, I will need direction and
>> help. I will need to know which developer tools I will need to use to
>> import my pascal project together with the other C source files. I
>> will also need to know what to include so that the source would be
>> compatible with dpkg-buildpackage.
>>
>>
>> Edward
>>
>>
>> On 18/08/2015, Edward Bartolo <edbarx@???> wrote:
>>> A) I am at the stage of trying to understand these:
>>> a) iw_sockets_open
>>> b) iw_get_range_info
>>> c) iw_scan
>>>
>>> The goal is to avoid to have the least number of dependencies.
>>>
>>>
>>> B) I have yet another tempting idea. This is to use only one file for
>>> the essids and corresponding passwords. However, this would force me
>>> to somehow trick ifup into thinking it is being passed an interfaces
>>> file instead of the output from an executable.
>>>
>>> Here is the command:
>>> ifup wlan0 -i $(tricky-executable(essid))
>>>
>>> tricky-executable would pass a series of text lines as they would
>>> appear in a dedicated interfaces file.
>>>
>>> I found it: it is not the above as that does not work. But this does
>>> work.
>>> :)
>>> cat /etc/network/interfaces | ifup wlan0
>>>
>>> What do you think.
>>>
>>> On 18/08/2015, Steve Litt <slitt@???> wrote:
>>>> On Tue, 18 Aug 2015 11:49:40 +0100
>>>> Edward Bartolo <edbarx@???> wrote:
>>>>
>>>>> At the moment I am stuck trying to use sudo to run ifup from within my
>>>>> frontend.
>>>>
>>>> I think the backend should do the ifup. ifup is part of the apps core
>>>> responsibility, not a way of presenting to the user. Just have the
>>>> front end tell the back end to do whatever's necessary (ifup, ifdown,
>>>> rewrite a config file and ifup, etc).
>>>>
>>>>
>>>>
>>>> SteveT
>>>>
>>>> Steve Litt
>>>> August 2015 featured book: Troubleshooting: Just the Facts
>>>> http://www.troubleshooters.com/tjust
>>>>
>>>
>>
>