public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@bfk.de>
To: Kay Sievers <kay.sievers@vrfy.org>
Cc: "Loke\, Chetan" <Chetan.Loke@netscout.com>,
	Matt Domsch <Matt_Domsch@dell.com>,
	Michael Di Domenico <mdidomenico4@gmail.com>,
	linux-net@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: nic enumeration
Date: Fri, 09 Jul 2010 08:13:18 +0000	[thread overview]
Message-ID: <827hl5hy3l.fsf@mid.bfk.de> (raw)
In-Reply-To: <AANLkTilRdnjShlB2JA1TjxMklTjw4ASl3BhwUWtKRdMW@mail.gmail.com> (Kay Sievers's message of "Fri\, 9 Jul 2010 09\:57\:14 +0200")

* Kay Sievers:

> Anyway, it's not recommended to do anything like this. On many distros
> it will cause trouble with the network scripts/services, which are run
> again for already active interfaces. Using the udevadm trigger
> 'hammer' on the running system may lead to all sorts of problems. This
> tool is usually only used at coldplug time during bootup.

There was a time when the Debian scripts were pretty robust.  But
maybe we've just been lucky.

> In general, there is no safe way, or a tool to do this. You have to
> know very well what you are doing. It's pretty common, that you
> disconnect yourself from a remote box if you try anything like this.

Yeah, but there should be a way to do this over OOB management,
without requiring a reboot. 8-(

-- 
Florian Weimer                <fweimer@bfk.de>
BFK edv-consulting GmbH       http://www.bfk.de/
Kriegsstraße 100              tel: +49-721-96201-1
D-76133 Karlsruhe             fax: +49-721-96201-99

  reply	other threads:[~2010-07-09  8:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-07 22:25 nic enumeration Michael Di Domenico
2010-07-07 22:39 ` Brian Kroth
2010-07-07 23:15 ` Steve Fink
2010-07-08  1:21 ` Matt Domsch
2010-07-08 20:36   ` Loke, Chetan
2010-07-08 20:47     ` Andrew Fong
2010-07-08 21:27       ` Kay Sievers
2010-07-08 22:07         ` Loke, Chetan
2010-07-08 21:24     ` Charlie Brady
2010-07-09  7:18     ` Florian Weimer
2010-07-09  7:57       ` Kay Sievers
2010-07-09  8:13         ` Florian Weimer [this message]
2010-07-09 16:27       ` Loke, Chetan
2010-07-09 17:10         ` Steve Fink
2010-07-09 18:23           ` Loke, Chetan
2010-07-09 21:26             ` Steve Fink
2010-07-12 16:56               ` Loke, Chetan
2010-07-12 18:27                 ` Steve Fink
2010-07-09 17:15         ` Matt Domsch
2010-07-09 18:55           ` Loke, Chetan

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=827hl5hy3l.fsf@mid.bfk.de \
    --to=fweimer@bfk.de \
    --cc=Chetan.Loke@netscout.com \
    --cc=Matt_Domsch@dell.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=mdidomenico4@gmail.com \
    /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