Em 25-01-2014 14:11, Armin K. escreveu:

Thanks, Armin.

> You can't use two different services to configure one network interface, 
> they'll collide. Either way, if you decided to use NM/Wicd instead of 
> LFS ifup/ifdown, you NEED to disable ifup/ifdown configuration for the 
> specific interface you want NM/Wicd to manage.


Yes, I know, since after I was trying to understand Ragnar's problem.




I only used fixed ip, so, network interface was already configured in
LFS, or just after. Then, needed to updated DHCPCD and Network Manager
for the *book*, that is why I had left DHCPCD being default in my dev
system. But always with fixed ip, for all three methods. Some of this is
described in the #4605: DHCPCD 6.2.1 ticket.




Then, started *experimenting with DHCPCD and NM*, due to *Ragnar's*
problem. However, after boot, configured by DHCPCD, I could successfully
start NM by hand and it worked, for version 6.0.5, but failed for
version 6.2.1. This is when I discovered what you wrote above, things
got more strict, thus.

Therefore, *my* issue is *solved*. I think that something about what I
accidentally discovered and you wrote should go into the *book*,
probably as note(s) in page(s). I would like help from somebody, please,
to decide if I put a note in DHCPCD, DHCP and/or NM or in all three. I
believe you could help me with this decision with some suggestion.





Next, Ragnar's issue: as far as I know, it isn't still solved (you
remember, you have already replied his post in support, I think).

For this, I have sent data that I have been reading and compiling (not
in the informatics sense), trying to understand these subjects. Last one
was an udev.so library that was introduced probably at DHCPCD-6.1.0 (I
gave the address of the commit in my previous post). The file udev.c
from which it is compiled has been modified many times, between 6.0.5
with 6.2.1.

Thanks in advance.


-- 
[]s,
Fernando
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to