From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Brownell Date: Mon, 07 Jan 2002 17:59:38 +0000 Subject: Re: ifdown on unregister for debian system Message-Id: List-Id: References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org That sounds about right. My understanding -- please correct if appropriate! -- is that for the moment, distros have "agreed to disagree" about details of network administration, at this level, So I believe that logic along the lines of "if [ distro is X] ..." is unfortunately appropriate in these cases. Maybe in a few years we'll have more convergence, which hotplug can be a part of ... :) - Dave ----- Original Message ----- From: "Fumitoshi UKAI" To: "Bill Nottingham" Cc: Sent: Monday, January 07, 2002 9:41 AM Subject: Re: ifdown on unregister for debian system > At Mon, 7 Jan 2002 12:36:05 -0500, > Bill Nottingham wrote: > > > > Fumitoshi UKAI (ukai@debian.or.jp) said: > > > On debian system, ifup/ifdown keep status of interface status (up/down) > > > in ifstate database, so ifdown is necessary when network interface > > > unregistered. Unless ifdown is called, next registering net device > > > will fail because it was already up in ifstate database. > > > > This patch: > > a) refers to a debian-specific package > > b) refers to debian-specific ifdown behavior > > > > Is there any chance it could be cleaned up, or kept as a debian-specifc > > diff? > > debian's ifup/ifdown uses /etc/network/ifstate for status database. > How about checking the /etc/network/ifstate file existance to run ifdown? > > Regards, > Fumitoshi UKAI > _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel