On 2012-01-11 02:14, Andrew Benton wrote:
>> FWIW: libnl-3.2.3 proved quite an interesting 'change', I've needed to
>> tweak several packages (hostapd to name one) to deal with the move of
>> header files :-(
>
> Could you tell me how you built hostapd with libnl-3.2.3? I've just
> taken the easy
On Wed, Jan 11, 2012 at 10:43:12PM +, Matt Burgess wrote:
> On Tue, 2012-01-10 at 02:22 +, Ken Moffat wrote:
> > For those who saw me moaning on lfs-book about libnl-2.0 (for me,
> > NetworkManager doesn't build against it), a summary of what is going
> > to happen:
> >
> > in LFS - nothi
On Tue, 2012-01-10 at 02:22 +, Ken Moffat wrote:
> For those who saw me moaning on lfs-book about libnl-2.0 (for me,
> NetworkManager doesn't build against it), a summary of what is going
> to happen:
>
> in LFS - nothing! Matt spotted that iproute2 only uses the
> headers, it doesn't link a
Markku Pesonen wrote
>iproute2 doesn't even use the headers. See this commit in upstream:
>http://git.kernel.org/?p=linux/kernel/git/shemminger/iproute2.git;a=commit;h=13603f6a9e46f08576f6284a0ef1ce1fbf94ffe0
Nice! I'll try a libnl-less build tonight with relevant seds to prevent
iproute2 from
On 10.1.2012 4:22, Ken Moffat wrote:
> For those who saw me moaning on lfs-book about libnl-2.0 (for me,
> NetworkManager doesn't build against it), a summary of what is going
> to happen:
>
> in LFS - nothing! Matt spotted that iproute2 only uses the
> headers, it doesn't link against the lib.
On Tue, 10 Jan 2012 17:15:19 +0100
Olaf wrote:
> FWIW: libnl-3.2.3 proved quite an interesting 'change', I've needed to
> tweak several packages (hostapd to name one) to deal with the move of
> header files :-(
Could you tell me how you built hostapd with libnl-3.2.3? I've just
taken the easy
Ken,
> in BLFS, I'll be adding libnl-3.2.3 when I (eventually) merge
> Wayne's gnome-3 changes. The headers in -3 have moved one level
> deeper, and a quick attempt to use them for iproute2 by editing the
> includes in ip2/ipl2tpc from netlink/ to libnl3/netlink/ failed
> because the first of t
For those who saw me moaning on lfs-book about libnl-2.0 (for me,
NetworkManager doesn't build against it), a summary of what is going
to happen:
in LFS - nothing! Matt spotted that iproute2 only uses the
headers, it doesn't link against the lib. For that, 2.0 is fine.
With only 2.0 installe
Ken Moffat wrote:
> On Mon, Jan 09, 2012 at 05:49:20PM -0600, Bruce Dubbs wrote:
>> No, I don't edit /etc files daily, but I certainly do when I'm setting
>> it up. Occasionally, I want to change things in /etc/dircolors,
>> /etc/profile.d/, /etc/vimrc, etc :)
>>
>> Actually libnl-3 has several
On Tue, 10 Jan 2012, Ken Moffat wrote:
OK. What sort of things do you change in /etc ? For me, mostly
building desktops (with shared /home), the idea of having to tweak
files in /etc to get it working properly is uncommon.
For me, mostly maintaining kind of servers, pretty sure the majority of
On Mon, Jan 09, 2012 at 05:49:20PM -0600, Bruce Dubbs wrote:
>
> No, I don't edit /etc files daily, but I certainly do when I'm setting
> it up. Occasionally, I want to change things in /etc/dircolors,
> /etc/profile.d/, /etc/vimrc, etc :)
>
> Actually libnl-3 has several executables to manage
On Tue, Jan 10, 2012 at 12:41:47AM +0100, Uwe Düffert wrote:
>
> Well, I'm not sure whether this was the original intention, but to
> me this kind of distinction does make sense. Maybe not from the
> perspective of a user of a *LFS system, but for a user of *LFS, i.e.
> a system builder/maintainer
Ken Moffat wrote:
> On Sun, Jan 08, 2012 at 10:01:21PM -0600, Bruce Dubbs wrote:
>> 4. I don't really like /etc for the /etc/libnl/{pktloc,classid} files.
>> that's not the kind of thing a user would change, especially with an
>> editor. I'd suggest /var/lib.
>>
> I'm perhaps too late to the
On Mon, 9 Jan 2012, Ken Moffat wrote:
On Sun, Jan 08, 2012 at 10:01:21PM -0600, Bruce Dubbs wrote:
4. I don't really like /etc for the /etc/libnl/{pktloc,classid} files.
that's not the kind of thing a user would change, especially with an
editor. I'd suggest /var/lib.
Why do you think user
On Sun, Jan 08, 2012 at 10:01:21PM -0600, Bruce Dubbs wrote:
>
> 4. I don't really like /etc for the /etc/libnl/{pktloc,classid} files.
> that's not the kind of thing a user would change, especially with an
> editor. I'd suggest /var/lib.
>
I'm perhaps too late to the party here, but (in t
Matt Burgess wrote:
> On Sun, 2012-01-08 at 22:01 -0600, Bruce Dubbs wrote:
>> 4. I don't really like /etc for the /etc/libnl/{pktloc,classid} files.
>> that's not the kind of thing a user would change, especially with an
>> editor. I'd suggest /var/lib.
>
> Agreed. Does it warrant a comma
On Sun, 2012-01-08 at 22:01 -0600, Bruce Dubbs wrote:
> I took a look at libnl2 and libnl3. Here's a couple of issues:
>
> 1. The book lists directories:
> /usr/include/netlink,
> /usr/include/netlink/genl,
> /usr/include/netlink/netfilter,
> /usr/include/netlink/route
>
> but I
I took a look at libnl2 and libnl3. Here's a couple of issues:
1. The book lists directories:
/usr/include/netlink,
/usr/include/netlink/genl,
/usr/include/netlink/netfilter,
/usr/include/netlink/route
but I think we really only need to list /usr/include/netlink, not all
the su
18 matches
Mail list logo
