On Sun, Sep 13, 2015 at 05:20:25PM +0200, Edward Bartolo wrote:
> Hi all,
>
> By automatic connections I understood netman using the available
> essids for which it knows the password to connect. This means, it does
> not attempt to connect if no essid file is found under
> /etc/network/wifi.
>
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
Am 12.09.2015 um 06:54 schrieb Franco Lanza:
> Thanks for your patience, in few hours the devuan repositories will be
> up&running.
Jep, repo is working again.
Thanks for fixing the issue!
Regards
Thomas
___
Dng mailing list
Dng@lists.dyne.org
https:
Hi,
Once it connects, netman will not try to change connection unless it
fails. The backend first reads the available signal strengths, then it
reads what essids are installed, and finally, it tries to connect by
first trying the strongest wifi source if that is available in the
essid files. This
On 2015-09-13 23:44, k...@aspodata.se wrote:
Shraptor:
When I check on Arch linux the only dependency they explicitly
states is xorg-server-xnest is dependent on libsystemd.
I do not have this package installed.
When I try to run my os Xorg complains about missing libsystemd
There is some pack
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
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 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
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 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
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 -
Le 12/09/2015 06:54, Franco Lanza a écrit :
Hi all,
after the last days issues with devuan repositories,
...
Thanks for your patience, in few hours the devuan repositories will be
up&running.
Thanks very much Franco.
I could install devuan-jessie alpha2 amd64 yesterday evening on an
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
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
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
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
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
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
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
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
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
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
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
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
shraptor:
> On 2015-09-13 23:44, k...@aspodata.se wrote:
...
> > I got xorg to work on a funtoo box and that without any udev nor
> > libudev. I.e. there is no dependancy.
...
> Was there libsystemd on your funtoo setup?
No, none.
> The dependency I found was on systemd-login.
> The udev dependen
Isaac:
...
> I've redone that function without udev but using my own library libsysdev,
> which I mentioned earlier this summer.
> Repositories that you'd need to build that:
>
> -https://github.com/idunham/libsysdev
> -https://github.com/idunham/xf86-input-evdev (branch sysdev)
$ git remote -v
o
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
On 9/14/15, k...@aspodata.se wrote:
...
> How do I get the sysdev branch ?
git checkout remotes/origin/sysdev sysdev
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
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.
On Mon, Sep 14, 2015 at 10:54:53AM +0200, aitor_czr wrote:
> Hi Katolaz,
>
> I tried it but it doesn't work:
>
> aitor@gnuinos:~/netman/backend_src/src$ gcc -g -I../include
Try with the actual path to the include. With a -I option it isn't clear what
home
directory the -I is relative to.
I r
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
If there's a better place to report this, let me know.
On a fully updated Wheezy system, I installed
debuan-baseconf-0.6.4+devuan3_all.deb. That sets up the Devuan repositories
and then puts some instructions on the screen. When you select OK, those
instructions disappear. It would be nice i
On Mon, Sep 14, 2015 at 02:26:10PM -0400, Rob Owens wrote:
[cut]
>
> Another 'apt-get update' still produces the 'ignoring provides line' warnings.
>
> 'apt-get upgrade' tells me that systemd and systemd-sysv are going to be
> installed. Additionally, for some reason samba is going to be inst
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,
>>
>>
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
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
On Mon, Sep 14, 2015 at 07:35:34PM +0100, KatolaZ wrote:
> On Mon, Sep 14, 2015 at 02:26:10PM -0400, Rob Owens wrote:
>
> [cut]
>
> >
> > Another 'apt-get update' still produces the 'ignoring provides line'
> > warnings.
> >
> > 'apt-get upgrade' tells me that systemd and systemd-sysv are goin
Hleb:
> On 9/14/15, k...@aspodata.se wrote:
> ...
> > How do I get the sysdev branch ?
>
> git checkout remotes/origin/sysdev sysdev
$ git checkout remotes/origin/sysdev sysdev
error: pathspec 'sysdev' did not match any file(s) known to git.
Didn't work.
Regards,
/Karl Hammar
---
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
I correct a mistake near the end of my original email. 'apt-get dist-upgrade'
is what causes systemd, samba, and qemu to get installed. And just to be clear,
I did 'apt-get upgrade' first, then 'apt-get dist-upgrade' later in the process.
This is how I am accustomed to doing Debian upgrades.
---
- Original Message -
> On Mon, Sep 14, 2015 at 07:35:34PM +0100, KatolaZ wrote:
>> On Mon, Sep 14, 2015 at 02:26:10PM -0400, Rob Owens wrote:
>> > Another 'apt-get update' still produces the 'ignoring provides line'
>> > warnings.
>> >
>> > 'apt-get upgrade' tells me that systemd and syst
On 9/14/15, k...@aspodata.se wrote:
> $ git checkout remotes/origin/sysdev sysdev
> error: pathspec 'sysdev' did not match any file(s) known to git.
>
> Didn't work.
Swap sysdev and remotes/origin/sysdev or try just git checkout sysdev
Hint: man git-checkout :)
__
Le 14/09/2015 21:48, Rob Owens a écrit :
I only chose ceres because that was the default when I installed
devuan-baseconf. Which would be a more sensible upgrade path from Wheezy?
Should I have chosen ascii?
Up to now, Debian has never supported skipping one or two versions
in dist-upgrade.
- Original Message -
> From: "Didier Kryn"
> Le 14/09/2015 21:48, Rob Owens a écrit :
>> I only chose ceres because that was the default when I installed
>> devuan-baseconf. Which would be a more sensible upgrade path from Wheezy?
>> Should I have chosen ascii?
> Up to now, Debian ha
On Mon, 9/14/15, Didier Kryn wrote:
Subject: Re: [DNG] upgrade wheezy to devuan jessie instead of ceres
To: dng@lists.dyne.org
Date: Monday, September 14, 2015, 2:58 PM
Le 14/09/2015 21:48, Rob Owens a écrit :
> I only chose ceres because that was the default when I installed
> devuan-basec
On Mon, Sep 14, 2015 at 03:10:30PM -0400, Hendrik Boom wrote:
[cut]
>
> I'm wondering whether things are ready to upgrade my server to devuan
> jessie. I'll take the usual precautions to be able to back out if it
> doesn't work, (i.e. doing the upgrade on a copy of the working
> system) but
In my opinion, the best way to update the system is (as KatolaZ says)
"apt-get dist-upgrade".
Aitor.
El 14/09/15 a las 21:33, Rob Owens escribió:
Hi Rob,
I don't know if it is related, and maybe my comment is just silly, but
in order to upgrade from Wheezy I believe you should give an "apt-g
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
On Mon, Sep 14, 2015 at 10:36:45PM +0100, KatolaZ wrote:
> On Mon, Sep 14, 2015 at 03:10:30PM -0400, Hendrik Boom wrote:
>
> [cut]
>
> >
> > I'm wondering whether things are ready to upgrade my server to devuan
> > jessie. I'll take the usual precautions to be able to back out if it
> > doesn
Hleb:
> On 9/14/15, k...@aspodata.se wrote:
> > $ git checkout remotes/origin/sysdev sysdev
> > error: pathspec 'sysdev' did not match any file(s) known to git.
> >
> > Didn't work.
>
> Swap sysdev and remotes/origin/sysdev or try just git checkout sysdev
?? co sysdev worked, I'm clueless
Th
Hi all,
Although at the moment I am occupied with other commitments, I would
to discuss how support for uncommon systems with more than one wifi
adaptor and/or with more than one wired network adaptor.
The main drawback supporting such systems is that the GUI has to
account for them and this make
Hi all,
Obviously, the major disadvantage of using my proposed 'solution', is
users must decide which physical network interfaces to use and stick
with their decision afterwards.
Edward
On 15/09/2015, Edward Bartolo wrote:
> Hi all,
>
> Although at the moment I am occupied with other commitment
53 matches
Mail list logo
