Pushed libpqxx++ to GitLab:
https://gitlab.com/aitor_czr/libpqxx/tree/master
It uses command line parameters :)
Aitor.
El 04/09/15 a las 20:44, Edward Bartolo escribió:
I will use command line parameters for the GUI frontend so that it may
be started to automatically scan for available wifis
On arch linux xf86-input-evdev is reported to have a dependency on
systemd.
I thought the dependency is on udev and that is usually reported on arch
like
systemd(udev).
I downloaded xf86-input-evdev for recompilation but could not find any
switches
to compile without systemd though some evid
Good afternoon,
On Sat, Sep 05, 2015 at 01:49:14PM +0200, shraptor wrote:
> On arch linux xf86-input-evdev is reported to have a dependency on systemd.
>
> I thought the dependency is on udev and that is usually reported on arch
> like
> systemd(udev).
>
> I downloaded xf86-input-evdev for recom
On Sat, Sep 05, 2015 at 03:39:17PM +0200, Teodoro Santoni wrote:
> Good afternoon,
>
> On Sat, Sep 05, 2015 at 01:49:14PM +0200, shraptor wrote:
> > On arch linux xf86-input-evdev is reported to have a dependency on systemd.
> >
> > I thought the dependency is on udev and that is usually reported
Edward Bartolo writes:
> I am not putting in doubt what you are telling me.
You are. And you are - pardon my frankness - very much confused
regarding how 'processes and process relationships' work on UNIX(*)/
Linux. I'll try to clear this up but you might want to consider getting
yourself a good
vdev is currently not providing its own pkg-config file, so if you want to try
building evdev against it, you should take the .pc file from either systemd or
eudev.
On Sat, Sep 05, 2015 at 09:50:13AM -0400, Hendrik Boom wrote:
> On Sat, Sep 05, 2015 at 03:39:17PM +0200, Teodoro Santoni wrote:
> >
Edward,
A rather thorough reference is "The Linux Programming Interface"
available from: http://www.man7.org/tlpi/ and other retailers.
HTH,
- Nate
--
"The optimist proclaims that we live in the best of all
possible worlds. The pessimist fears this is true."
Ham radio, Linux, bikes, and m
On Sat, Sep 05, 2015 at 01:49:14PM +0200, shraptor wrote:
> On arch linux xf86-input-evdev is reported to have a dependency on systemd.
>
> I thought the dependency is on udev and that is usually reported on arch
> like
> systemd(udev).
>
> I downloaded xf86-input-evdev for recompilation but coul
On Sat, Sep 05, 2015 at 06:38:27PM +0300, Jack L. Frost wrote:
> vdev is currently not providing its own pkg-config file, so if you want to try
> building evdev against it, you should take the .pc file from either systemd or
> eudev.
>
Or hacking the... whatever the eff evdev uses to build in ord
First of all, thanks for taking the time to write to me.
Using "ps xao pid,ppid,comm", I found what I described to you:
precisely, that orphaned processes were adopted by the GUI frontend.
The frontend's pid was listed as the zombies' ppid. Now, this issue
has little effect on the code as I am usi
Edward Bartolo writes:
[...]
> Using "ps xao pid,ppid,comm", I found what I described to you:
> precisely, that orphaned processes were adopted by the GUI frontend.
There are no 'orphaned processes' in this case because execl does not
create a new process. It runs a new program in the same proc
Just to be clear my system before upgrade was using vdev in conjunction
with
xf86-input-evdev and working fine. I did not recompile that version of
evdev and it
just worked with libudev-compat.
When I upgraded to new version of both( and new kernel)
keyboard stopped working( though could be bro
I also forgot to say that on my upgraded system with vdev and
arch version of xf86-input-evdev touchpad gets detected and loaded that
I believe is
fascilitated by evdev and libudev-compat??
best regards
Scooby
On 2015-09-05 21:40, shraptor wrote:
Just to be clear my system before upgrade wa
Quote: <>
So what is the difference between an "orphaned process", i.e. a
process whose parent has exited after giving birth to a child process
and one which replaces the original process effectively giving its
parent a death sentence?
Sorry, but it looks there is only a very subtle difference be
Correction:
Sorry, but it looks there is only a very subtle difference between the
two. The only difference I see, is that, since in the case of execl,
the parent effectively is replaced, i.e. dies, the child process is awarded its
parent PID. This is not the case when a parent process creates a c
On Sat, Sep 05, 2015 at 08:54:25PM +0100, Edward Bartolo wrote:
> Correction:
>
> Sorry, but it looks there is only a very subtle difference between the
> two. The only difference I see, is that, since in the case of execl,
> the parent effectively is replaced, i.e. dies, the child process is awar
On Sat, Sep 05, 2015 at 08:52:39PM +0100, Edward Bartolo wrote:
> Quote: < process (that's done via fork and not via execve) and it's not adopted
> by the grand parent but by init.>>
>
> So what is the difference between an "orphaned process", i.e. a
> process whose parent has exited after giving
When I read jude's documentation it states
"It also ships with a "libudev-compat" library that is ABI-compatible
with libudev 219."
My system is libudev 224, does this mean it isn't ABI-compatible
anymore?
if so how to handle?
On 2015-09-05 21:49, shraptor wrote:
I also forgot to say that
.pc files are quilt patches applied.
Aaitor.
El 05/09/15 a las 21:52, dng-requ...@lists.dyne.org escribió:
@Jack Frost
I do not understand the use of .pc files although I have seen them
around. I am using your systemd-dummy package though to avoid pulling
in real systemd, Thanks for that.
___
Hi shraptor,
.pc file includes theapplied quilt patches.
Aitor.
El 05/09/15 a las 21:52, shraptor escribió:
@Jack Frost
I do not understand the use of .pc files although I have seen them
around. I am using your systemd-dummy package though to avoid pulling
in real systemd, Thanks for that.
Problem solved
when I changed so names from
libudev.so
libudev.so.1 -> libudev.so.1.0.1
libudev.so.1.0.1 -> libudev.so.1.5.1
libudev.so.1.5.1 -> libudev.so.1.6.0
libudev.so.1.6.0 -> libudev.so.1.6.4
libudev.so.1.6.4 -> libudev.so
to
libudev.so
libudev.so.1 -> libudev.so.1.0.1
libudev.so.1.0.
On Sat, Sep 05, 2015 at 08:52:39PM +0100, Edward Bartolo wrote:
> Quote: < process (that's done via fork and not via execve) and it's not adopted
> by the grand parent but by init.>>
>
> So what is the difference between an "orphaned process", i.e. a
> process whose parent has exited after giving
22 matches
Mail list logo
