El 24/10/13 09:15, Koehne Kai escribió:
> Hi,
>
> First time I post to the list, so please bear with me :) I'm a developer
> working on Qt. The Qt project just released a beta of the upcoming version
> 5.2, and to help people to test it we've been also releasing an installer
> with binaries fo
On Thu, Oct 24, 2013 at 6:50 PM, Nicholas Majeran
wrote:
> /sys/class/net/enp65s0f0/dev_id:0x0
> /sys/class/net/enp65s0f1d1/dev_id:0x1
> /sys/class/net/lo/dev_id:0x0
>
> Thanks for the pointer. As far as correcting this, should I contact the
> maintainer of the sfc driver?
Yes, the kernel shoul
On Thursday 2013-10-24 14:15, Koehne Kai wrote:
>
>I'm a developer working on Qt.[...]
>https://bugreports.qt-project.org/browse/QTBUG-34176 [is] one of the
>problems we still have[,] to fix is our libudev.so.0 dependency ...
>That is, we're building the packages on Ubuntu 11.10 and link
>against
On Thu, Oct 24, 2013 at 6:39 AM, Kay Sievers wrote:
> On Thu, Oct 24, 2013 at 3:15 PM, Laszlo Papp wrote:
>> On Thu, Oct 24, 2013 at 2:09 PM, Kay Sievers wrote:
>
>>> No, you cannot really ship your own libudev, it is coupled with the
>>> daemon. They speak a non-trivial wire protocol and write
Yep, that's definitely the case here:
[root@sunelkvm6 ~]# grep . /sys/class/net/*/dev_id
/sys/class/net/eno1/dev_id:0x0
/sys/class/net/eno2/dev_id:0x0
/sys/class/net/eno3/dev_id:0x0
/sys/class/net/eno4/dev_id:0x0
/sys/class/net/enp4s0f0/dev_id:0x0
/sys/class/net/enp4s0f1/dev_id:0x0
/sys/class/net/
> -Original Message-
> From: Kay Sievers [mailto:k...@vrfy.org]
> Subject: Re: [systemd-devel] Can apps ship their own copy of libudev?
>
> [...]
> Libudev0 and libudev1 are almost API compatible, only a few pointless
> functions are no longer provided by the new library. There should be
On Thu, Oct 24, 2013 at 3:15 PM, Laszlo Papp wrote:
> On Thu, Oct 24, 2013 at 2:09 PM, Kay Sievers wrote:
>> No, you cannot really ship your own libudev, it is coupled with the
>> daemon. They speak a non-trivial wire protocol and write udev database
>> files which are a private implementation o
On Thu, Oct 24, 2013 at 2:15 PM, Koehne Kai wrote:
> First time I post to the list, so please bear with me :) I'm a developer
> working on Qt. The Qt project just released a beta of the upcoming version
> 5.2, and to help people to test it we've been also releasing an installer
> with binaries
On Wed, Oct 23, 2013 at 9:02 PM, Nicholas Majeran
wrote:
> I have recently installed Fedora 19 on a Dell R620.
> I'm trying to grok the new device naming scheme put forth in systemd, but
> the results are a bit confusing.
>
> This box has four onboard ports -- those are all correctly labelled as
Hi,
First time I post to the list, so please bear with me :) I'm a developer
working on Qt. The Qt project just released a beta of the upcoming version
5.2, and to help people to test it we've been also releasing an installer with
binaries for Linux that is supposed to work on a variety of dis
Thanks. I did read the comments in that source before sending a message to the
mailing list -- but I am still unclear why the SolarFlare card doesn't behave
like the e1000e, and adds a device to the end of the devname.
> On Oct 24, 2013, at 2:56 AM, "Jóhann B. Guðmundsson"
> wrote:
>
>> O
On 10/23/2013 07:02 PM, Nicholas Majeran wrote:
I would expect to see enp65s0f0 and enp65s0f1, like the e1000e.
Read the source luke [1]...
JBG
1.
http://cgit.freedesktop.org/systemd/systemd/tree/src/udev/udev-builtin-net_id.c#n20
___
systemd-deve
12 matches
Mail list logo
