[Pkg-utopia-maintainers] Bug#419049: Bug#419049: CIFS and use cases

[Raphael Champeimont (Almacha)]

Michael Biebl wrote:
> Raphael Champeimont (Almacha) wrote:
>> Hi,
>>
> 
> Hi
> 
>> Solution 1:
>> Modify network-manager so that it does not bring down network interfaces
>> it manages when it exits. With that solution, when the network-manager
> 
> Yeah, that would be a possibility, which I had considered myself.
> 
>> daemon stops, it leaves the interfaces up, so then the umounts on
>> CIFS/NFS can happen properly, and at the end the "Deconfiguring network
>> interfaces..." step will finally put down the interfaces (as it would
>> have happened if network-manager was not installed). I known there is
> 
> Hm, that's not so easily possible. The ifupdown init script you are
> talking about, only (de)configures network interfaces which were brought
> up by ifupdown. That means, they have to have a configuration in
> /etc/network/interfaces and a state in /etc/network/run/ifstate.
> ifupdown won't manage an interface which is handled by NM.
> 
>> the WPA problem, but network-manager could at least leave up wired
>> interfaces.
>>
>> Solution 2:
>> Make it possible to have, even if network-manager is installed,
>> interfaces that are DHCP-configured at boot but that are NOT managed by
>> network-manager. In that case this possibility should be documented in
>> network-manager's README.Debian (I think of an option tu put in
>> /etc/network/interfaces on the concerned interfaces), it could also be
>> said somewhere "You should not use network-manager on interfaces you use
>> to mount network shares, but you can still use DHCP on these interfaces
>> by using option blabla."
> 
> That should already be possible, sort of. Just add a dummy config line
> "managed-by-nm no" (you can pick whatever you want)
> 
> auto eth0
> iface eth0 inet dhcp
>     managed-by-nm no
> 
> If NM finds a custom configuration for an interface, it [1] skips those
> interface and doesn't handle it. (See the README.Debian)
> ifupdown will simply ignore this fictitious "managed-by-nm" directive.
> 
> Hope that helps.

It works, thanks.

If lenny is going to have a version of NM that has this bug, then this
trick should probably be documented in NM's README.Debian, because it
may not be obvious to users (well, it was not obvious to me, at least)
that an inexistant option can be put in /etc/network/interfaces without
causing harm.

But if lenny is released with NM 0.7 which behaves differently, then
this does not apply of course.

Almacha