Please, be aware that this project is still in development although parts of it work. I am working on making the GUI frontend behave properly under all circumstances. The final version will be uploaded. However, those who want to have the code as it is at this stage, I am still coding and debugging, simply have to ask me to upload it.
Thanks. On 19/08/2015, Edward Bartolo <edb...@gmail.com> wrote: > Ooooooops, more instructions to setup sudo to allow only the backend > to run by all users or whatever you decide. > > Modify the /etc/sudoers file to include: > > ALL ALL=NOPASSWD: /path/to/backend/backend > > > On 19/08/2015, Edward Bartolo <edb...@gmail.com> wrote: >> I am uploading the sources for anyone wanting to help themselves. :) >> >> To compile the frontend Lazarus must be installed. Here, I am using >> version: >> 1.2.4+dfsg2-1 >> >> To compile the C source use: >> gcc backend.c -o backend >> >> Manual Configuration of the package: No yet post install script :( >> create a directory: >> /etc/network/wifi >> >> Move both backend and front end to the same directory. >> >> Outstanding TODO: >> Before saving to an existing interfaces file, delete the old one >> manually or edit the C source to do it for you. >> >> ENJOY and LONG LIFE DEVUAN! >> >> Compiled successfully on DEVUAN Alpha 64 bit. >> >> On 19/08/2015, Edward Bartolo <edb...@gmail.com> wrote: >>> I am coding and testing on Devuan 64 bit. >>> >>> On 19/08/2015, Steve Litt <sl...@troubleshooters.com> wrote: >>>> On Wed, 19 Aug 2015 10:41:30 -0400 >>>> Steve Litt <sl...@troubleshooters.com> wrote: >>>> >>>>> On Wed, 19 Aug 2015 14:29:02 +0100 >>>>> Edward Bartolo <edb...@gmail.com> wrote: >>>>> >>>>> > This is the completed C backend with all functions tested to work. >>>>> > Any suggestions as to modifications are welcome. >>>>> > >>>>> > The C code: >>>> >>>> Hi Edward, >>>> >>>> In the long run, you need to make the wifi device a variable instead of >>>> hard-coding wlan0. I have no idea which method of deducing the wifi >>>> device would require the least dependencies. I have a feeling it would >>>> be to spawn /sbin/iwconfig, which you already have due to using iwlist. >>>> Armed with the output of /sbin/iwconfig, finding the wifi device is a >>>> very simple parsing task, *unless* there are multiple wifi-enabled >>>> devices. >>>> >>>> LOL, I have to find a USB wifi dongle to continue testing your program. >>>> Without any wifi device, when I did ./a.out opScan, I got a segfault. >>>> >>>> This thing is great. As far as I can tell, it's distro independent. >>>> If you have Linux, it works. I'm going to use it on **all** my laptops, >>>> and kick NetworkManager, Wicd and my homegrown wpa_supplicant helpers >>>> to the curb. >>>> >>>> I wish all Linux software worked like this. >>>> >>>> Thanks, >>>> >>>> SteveT >>>> >>>> Steve Litt >>>> August 2015 featured book: Troubleshooting: Just the Facts >>>> http://www.troubleshooters.com/tjust >>>> _______________________________________________ >>>> Dng mailing list >>>> Dng@lists.dyne.org >>>> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng >>>> >>> >> > _______________________________________________ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng