Bug#599813: [PATCH 2/3] Add information about network-manager vs ifupdown
Bug#606268
Bug#599813
Signed-off-by: Julien Cristau <jcristau@debian.org>
---
en/issues.dbk | 25 +++++++++++++++++++++++++
1 files changed, 25 insertions(+), 0 deletions(-)
diff --git a/en/issues.dbk b/en/issues.dbk
index f24fe02..a7ee531 100644
--- a/en/issues.dbk
+++ b/en/issues.dbk
@@ -627,6 +627,7 @@ shipped in &oldreleasename; to the version in &releasename;, you can find more i
<ulink url="http://library.gnome.org/misc/release-notes/2.30/";>GNOME 2.30 Release
Notes</ulink>. Specific issues are listed below.
</para>
+
<section>
<title>GDM 2.20 and 2.30</title>
<para>
@@ -643,6 +644,7 @@ standard desktop system, however, simply installing <systemitem
role="package">gdm3</systemitem> should be enough.
</para>
</section>
+
<section>
<title>Device and other administrative permissions</title>
<para>
@@ -662,6 +664,29 @@ way to give a user administrative rights is to add it to the
</para>
</section>
+<section>
+ <title>network-manager and ifupdown interaction</title>
+ <para>
+ Upon upgrading the <systemitem role="package">network-manager</systemitem>
+ package, interfaces configured in
+ <filename>/etc/network/interfaces</filename> to use
+ <acronym>DHCP</acronym> with no other options will be disabled in that
+ file, and handled by NetworkManager instead. Therefore the
+ <command>ifup</command> and <command>ifdown</command> commands will not
+ work. These interfaces can be managed using the NetworkManager frontends
+ instead, see <ulink
+ url="http://live.gnome.org/NetworkManager/SystemSettings";>the
+ NetworkManager documentation</ulink>.
+ </para>
+ <para>
+ Conversely, any interfaces configured in
+ <filename>/etc/network/interfaces</filename> with more options will be
+ ignored by NetworkManager. This applies in particular to wireless
+ interfaces used during the installation of Debian (see bug <ulink
+ url="&url-bts;606268">#606268</ulink>).
+ </para>
+</section>
+
</section>
<section id="graphics">
--
1.7.2.3
Reply to: