From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: ifdown on unregister for debian system
Date: Mon, 07 Jan 2002 17:59:38 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-101042655627553@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-101042335418693@msgid-missing>
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" <ukai@debian.or.jp>
To: "Bill Nottingham" <notting@redhat.com>
Cc: <linux-hotplug-devel@lists.sourceforge.net>
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
next prev parent reply other threads:[~2002-01-07 17:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-07 17:07 ifdown on unregister for debian system Fumitoshi UKAI
2002-01-07 17:36 ` Bill Nottingham
2002-01-07 17:41 ` Fumitoshi UKAI
2002-01-07 17:44 ` Bill Nottingham
2002-01-07 17:59 ` David Brownell [this message]
2002-01-07 18:05 ` David Brownell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-linux-hotplug-101042655627553@msgid-missing \
--to=david-b@pacbell.net \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).