Hi all,

The additional ability to recognize wlan1, wlan2, wlan3, etc, in
something I will do as soon as I can.

Regarding the use of "iface wlan0 inet dhcp" in
/etc/network/interfaces, I have no other option unless someone really
versed in network configuration provides an alternative that works and
that doesn't disrupt the already working code.

I have already a germinating idea of how to implement support for
wlanN. This is by naming the essid files as wlanX_essid. This way only
the essid saving function and the frontend essid listing functions
would need to be changed. The connecting functions of the backend
would simply parse the filename to extract the device name, and it
would be done.

However, at this time of the year, I am very busy doing other work
besides programming for Devuan. At the moment, I am busy planting my
vegetables which cannot wait as that depends on the season, and a
couple of weeks makes a whole difference.

Edward

On 13/09/2015, aitor_czr <aitor_czr@???> wrote:
> Ok, I like XFCE4 of course.
>
> Aitor.
>
> El 13/09/15 a las 20:13, Edward Bartolo escribió:
>
> Hi aitor, I forgot to write that the final step is to let netman be
> automatically run as soon as a user boots into XFCE4 or desktop or
> window manager. Edward On 13/09/2015, Edward Bartolo <edbarx@???>
> wrote:
>>> >Hi aitor,
>>> >
>>> >I think, the time has come to start thinking about producing a .deb
>>> >package for netman. However, we will have to use a post installation
>>> >script to add the line:
>>> >
>>> >"iface wlan0 inet dhcp"
>>> >
>>> >to /etc/network/interfaces. The script has also to create a new
>>> >directory under /usr/bin with the name netman ie /usr/bin/netman will
>>> >hold both the frontend and the backend.
>>> >
>>> >The SUID for backend must be changed to that belonging to root. I do
>>> >this as follows:
>>> >chown root:root backend
>>> >chmod u+s backend
>>> >
>>> >A new directory under /etc/network with the name wifi must be created
>>> >i.e. /etc/network/wifi must be an existing directory.
>>> >
>>> >Then, the final steps would be to create a launcher for netman, the
>>> >frontend. To enable automatic attempts at connecting basing on
>>> >installed essid files under /etc/network/wifi, the parameter
>>> >--auto-conn must be passed to netman upon invocation. --auto-conn need
>>> >not be used and netman would not attempt to connect without user
>>> >intervention. This feature is for those who want to control what
>>> >happens on their machine.
>>> >
>>> >Edward
>>> >
>>> >
>
>