Hi all,
This morning I reviewed the C code for the backend to gracefully
account for error situations. At the moment I am using the latest
edited version to test whether it behaves so that I may git push the
latest changes.
As I am approaching the completion of this present and first project
for
Hi Aitor,
Yes.
Edward.
On 25/02/2032, aitor_czr wrote:
> So, the content of "/etc/netman.conf" would be:
>
> backend=/usr/lib/netman/bin/backend
>
> Isn't it?
>
> Aitor.
>
> On 17/09/15 16:28, Edward Bartolo wrote:
>> Hi Aitor,
>>
>> Agreed. Shall I also remove the ability to have the backend p
So, the content of "/etc/netman.conf" would be:
backend=/usr/lib/netman/bin/backend
Isn't it?
Aitor.
On 17/09/15 16:28, Edward Bartolo wrote:
Hi Aitor,
Agreed. Shall I also remove the ability to have the backend placement
set in an /etc/netman.conf file?
By itself the frontend is unable to
Hi Aitor,
Agreed. Shall I also remove the ability to have the backend placement
set in an /etc/netman.conf file?
By itself the frontend is unable to give root privileges to whatever
is pointed to in that file. So, I see no problem in having an
/etc/netman.conf file. But I stand to being corrected
This is the case, for example, of Qt. Qtchooser chooses between Qt4 or
Qt5 depending on the installed package: qt4-default, or qt5-default.
But i think this is not our case... So, i will use the directory
suggested by Tilt, if you agree.
Aitor.
On 17/09/15 10:21, Edward Bartolo wrote:
Also
Hi Aitor and Tilt,
As it is, the frontend can use an /etc config file for the location
and name of the backend but the GUI does NOT provide any means to
alter the config file.
Do you, Tilt, still think that I have to remove the use of a config
file even though users have to edit it by hand? The o
Hi Aitor and Tilt,
I think, Tilt has a point, if you agree, I can remove the use of an
/etc config file.
Edward
On 17/09/2015, Edward Bartolo wrote:
> Hi Aitor,
>
> Now, you should be able to place backend wherever you want and to name
> it what you like but you have to use a config file under
Hi Aitor,
Now, you should be able to place backend wherever you want and to name
it what you like but you have to use a config file under /etc.
New file name:
/etc/netman.conf
Contents of /etc/netman.conf
backend=/usr/lib/netman/bin/backend
Edward
On 17/09/2015, Edward Bartolo wrote:
> Hi Ait
Hi Aitor,
I am understanding you are giving me the go-ahead to let netman use an
/etc/netman.conf file. In this case, the location of the backend would
only be dictated by the path specified in the /etc/netman.conf file.
Changes implemented to use an /etc/netman.conf file.
Edward
On 24/02/2032,
Hi Aitor & Edward,
i don't think an /etc config file describing a location of a
backend executable is required in the first release.
What would be the motivation for a user to mess with
intrinsics of the software architecture?
Please keep in mind that the backend is a dangerous setuid
executable
Ok, thanks.
On 17/09/15 10:21, Edward Bartolo wrote:
Hi Aitor,
I think avoiding to use two links for the backend would help to keep
the project as simple as possible. Also using the version as a
directory would indicate that more than one concurrent version of
netman would be installed.
The fr
Hi Aitor,
I think avoiding to use two links for the backend would help to keep
the project as simple as possible. Also using the version as a
directory would indicate that more than one concurrent version of
netman would be installed.
The frontend, netman, expects to find the backend named as bac
Thanks Edward, i will try it.
I am considering locating netman-backend in the following path:
"/usr/lib/netman/0.1.0/"
doing after that the following simbolic links:
# ln -s /usr/lib/netman/0.1.0/netman-backend /etc/alternatives/
# ln -s /etc/alternatives/netman-backend /usr/bin/
What
Hi Aitor,
Try this command:
fpc -MObjFPC -Scghi -Tlinux -vewnhi -Filib/x86_64-linux
-Fl/opt/gnome/lib
-Fu/usr/lib/lazarus/1.2.4/lcl/units/x86_64-linux/gtk2
-Fu/usr/lib/lazarus/1.2.4/lcl/units/x86_64-linux
-Fu/usr/lib/lazarus/1.2.4/components/lazutils/lib/x86_64-linux
-Fu/usr/lib/lazarus/1.2.4/pa
Lazbuild doen't exit as a package, but it would be more appropiate
fp-compiler (freepascal) than lazarus.
Aitor.
On 16/09/15 05:51, Edward Bartolo wrote:
Hi Aitor,
Lazarus IDE may not be a hard dependency as it can be avoided by
directly building netman using lazbuild.
The version number sho
Hi Aitor,
Lazarus IDE may not be a hard dependency as it can be avoided by
directly building netman using lazbuild.
The version number should appropriately be 0.1.0 as this is the first
version and still needs maturation to become proper version 1.0
Edward
On 15/09/2015, aitor_czr wrote:
> The
The only error hurled by lintian is:
"Could not find a profile matching "{VENDOR}/main" for vendor devuan
at /usr/bin/lintian line 979."
On the other hand, what about the number version of the package?
0.1.0 ??
1.0 ??
Aitor.
On 15/09/15 15:30, aitor_czr wrote:
I think that the dependenc
I think that the dependencies of netman are the following:
Build-Depends: debhelper (>= 7.0.50), gcc, lazarus, dh-python,
python-all-dev
"netman-gui" deps -> netman-backend, libatk1.0-0, libgdk-pixbuf2.0-0,
libglib2.0-0, libpango-1.0-0, libx11-6
"netman-backend" deps -> libc-bin
Aitor.
No
Wow =-O
El 14/09/15 a las 21:33, Rainer Weikusat
escribió:
NB: I'm (professionally) maintaining 57 Debian packages, 33 of these
being completely 'original' developments.
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin
aitor_czr writes:
> Good job !
>
> Now i must to hit with the correct dependencies. All the rest is
> done. So, now i need some time to build it into a chroot jail using
> pbuilder, etc...
For a native package (as this), you really only need to invoke dh_make
in a suitable way and edit some of th
To all those trying to install netman,
Please note that now the directories for installation have changed to
comply with the usual placement of executables. /usr/bin is required
to contain only executables, creating a directory in it may disrupt
the behaviour of unrelated programs.
The new place
Good job !
Now i must to hit with the correct dependencies. All the rest is done.
So, now i need some time to build it into a chroot jail using pbuilder,
etc...
Regards,
Aitor.
On 14/09/15 20:51, Edward Bartolo wrote:
Hi Aitor,
Hopefully, now the BUG has been removed. On my computer disco
Hi Aitor,
Hopefully, now the BUG has been removed. On my computer disconnecting
now is respected even in auto-connect mode. Now, you can continue
packaging netman.
Edward
On 14/09/2015, KatolaZ wrote:
> On Mon, Sep 14, 2015 at 10:28:09AM -0400, Steve Litt wrote:
>
> [cut]
>
>>
>> KatolaZ,
>>
>>
On Mon, Sep 14, 2015 at 10:28:09AM -0400, Steve Litt wrote:
[cut]
>
> KatolaZ,
>
> Back in the day I used to do #include "/path/absolute" all the time.
> I'm pretty sure #include #include "../path/relative" would work too.
>
> I prefer to annunciate the include in the source file so I don't ha
On Mon, 14 Sep 2015 09:39:55 +0100
KatolaZ wrote:
> On Mon, Sep 14, 2015 at 10:26:25AM +0200, aitor_czr wrote:
> > Hi Edward,
> >
> > I thick you must change all the headers like:
> >
> > #include "paths.h"
> > #include "automated_scanner.h"
> > #include "core_functions.h"
> > #include "caller.
I'm not getting that with the build you uploaded a few hours ago. But I
didn't get it with yesterday's build, either. When I disconnect after
auto-connect, it stays disconnected. Could that be because I only have one
essid saved?
-fsr
On Mon, Sep 14, 2015 at 7:45 AM, aitor_czr wrote:
> Ok, tha
Ok, thank you.
On 14/09/15 13:10, Edward Bartolo wrote:
Hi Aitor,
I discovered that disconnecting immediately calls auto-connect
restoring the connection. I will 'git push' the necessary changes to
netman after making sure this behaviour is rectified. However, this
afternoon I am too busy to co
I added 'iface wlan0 inet dhcp' while there was a static ip configuration
in place.
With the dhcp line before the static configuration or with the dhcp line
in a separate file under interfaces.d, boot hangs for a short time while
it's trying dhcp, then boot completes, and it's connected with the s
Hi Aitor,
I discovered that disconnecting immediately calls auto-connect
restoring the connection. I will 'git push' the necessary changes to
netman after making sure this behaviour is rectified. However, this
afternoon I am too busy to continue working on the computer. I will
make myself availabl
Hi Aitor,
Don't forget that we also need to create a subdirectory, 'wifi', in
/etc/network. The full path to the new directory will be:
/etc/network/wifi
Together with the above, /etc/network/interfaces should have this line
added if not already included.
iface wlan0 inet dhcp
Without it ifdown
Having 'iface wlan0 inet dhcp' in /etc/network/interfaces causes no
problem if there is no wireless interface, but it might cause a problem if
someone already has wlan0 configured. I guess I should test that, too.
(Need to reboot for that.)
If netman is going to inject that line into the interface
Ok :-)
On 14/09/15 12:23, Edward Bartolo wrote:
Hi Aitor,
I pushed the necessary changes in netman. The changes are only in
backend.pas to account for the new placement of backend.
Please, note that the two executables will be placed according to
Tilt's suggestion so that we comply with where
Hi Aitor,
I pushed the necessary changes in netman. The changes are only in
backend.pas to account for the new placement of backend.
Please, note that the two executables will be placed according to
Tilt's suggestion so that we comply with where executables should be
placed.
Thanks.
Edward.
On
I've got the same resulting "/lib/i386-linux/netman.compiled" building
*in the command line*. So, appearently, is enough with:
$ lazbuild -B netman.lpr
Aitor.
On 14/09/15 12:02, aitor_czr wrote:
The content of the resulting "/lib/i386-linux/netman.compiled" *with
Lazarus* is:
It
The content of the resulting /lib/netman.compiled with Lazarus is:
It will track us for the needed parameters :-)
Aitor.
On 14/09/15 11:57, Edward Bartolo wrote:
Hi Aitor,
I tried "lazbuild -B netman.lpr" in the netman directory and it
worked. There were some complaints but the exe
Hi Aitor,
I tried "lazbuild -B netman.lpr" in the netman directory and it
worked. There were some complaints but the executable was produced.
By the way, thanks for teaching me something new about Lazarus.
Edward.
On 14/09/2015, aitor_czr wrote:
> Hi,
>
> I'm adding:
>
> lazbuild -B netman.lp
Hi,
I'm adding:
lazbuild -B netman.lpr
to the debian/rules. Is it enough to build the frontend? I've never used
Lazarus.
Thanks in advance,
Aitor.
On 14/09/15 10:52, Edward Bartolo wrote:
Hi,
My experience using gcc directly corroborates what KatolaZ said. This
command works on my comput
I will rectify this issue in my libpqxx++ project.
https://gitlab.com/aitor_czr/libpqxx/tree/master
Thanks.
Aitor.
On 14/09/15 11:00, aitor_czr wrote:
On 14/09/15 10:39, KatolaZ wrote:
I think you guys must rather specify an appropriate "-I" flag to gcc
in the Makefile. I have never ever se
Sorry, sorry !!
I didn't undo some changes. How foolish failure :-(
Now it works.
Aitor.
On 14/09/15 10:54, aitor_czr wrote:
Hi Katolaz,
I tried it but it doesn't work:
aitor@gnuinos:~/netman/backend_src/src$ gcc -g -I../include
core_functions.c file_functions.c backend.c essid_encoder.c -
Hi Katolaz,
I tried it but it doesn't work:
aitor@gnuinos:~/netman/backend_src/src$ gcc -g -I../include
core_functions.c file_functions.c backend.c essid_encoder.c -o backend
core_functions.c:29:36: fatal error: include/core_functions.h: No existe
el fichero o el directorio
#include "include
Hi,
My experience using gcc directly corroborates what KatolaZ said. This
command works on my computer without the need to edit the .c files as
you suggested.
The gcc command:
gcc -lm -I../include core_functions.c file_functions.c backend.c
essid_encoder.c automated_scanner.c -o backend
Edward
Hi Aitor,
I will include the relative path as you instructed. Thanks.
The compiler command is this:
gcc -lm core_functions.c file_functions.c backend.c essid_encoder.c
automated_scanner.c -o backend
Edward.
On 14/09/2015, aitor_czr wrote:
> Hi Edward,
>
> I thick you must change all the hea
On Mon, Sep 14, 2015 at 10:26:25AM +0200, aitor_czr wrote:
> Hi Edward,
>
> I thick you must change all the headers like:
>
> #include "paths.h"
> #include "automated_scanner.h"
> #include "core_functions.h"
> #include "caller.h"
>
> etc... in the *.c files of the backend of netman by:
>
> #inc
Hi Edward,
I thick you must change all the headers like:
#include "paths.h"
#include "automated_scanner.h"
#include "core_functions.h"
#include "caller.h"
etc... in the *.c files of the backend of netman by:
#include "../include/paths.h"
#include "../include/automated_scanner.h"
#include "../i
Hi Edward,
I thick you must change all the headers like:
#include "paths.h"
#include "automated_scanner.h"
#include "core_functions.h"
#include "caller.h"
etc... in the *.c files of the backend of netman by:
#include "../include/paths.h"
#include "../include/automated_scanner.h"
#include "../i
Hi,
I tested my installation, Devuan 64 bit, for unwanted behaviour when
/etc/network/interfaces contains lines as follows but which point to
inexistent physical devices:
iface wlan1 inet dhcp
The OS didn't complain and I was able to use netman as usual without
the least of issues. Needless to s
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 a
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
wrote:
>Hi aitor,
Vintage :-)
El 13/09/15 a las 20:10, Edward Bartolo escribió:
Edward Bartolo wrote:
Oooops, I have a new pair of spectacles that is playing tricks on me,
especially, since it is the first near-sight spectacles. Before, I
didn't use any.
You just turned 40, didn't you?
As I rememb
Hi,
On 09/13/2015 08:10 PM, Edward Bartolo wrote:
> 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.
Is that really necc
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 wrote:
> Hi aitor,
>
> I think, the time has come to start thinking about producing a .deb
> package for n
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 nam
52 matches
Mail list logo
