netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rick Jones <rick.jones2@hp.com>
To: Phil Dibowitz <phil@ipom.com>
Cc: jamal <hadi@cyberus.ca>,
	netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
	Jeff Garzik <jeff@garzik.org>
Subject: Re: reminder, 2.6.18 window...
Date: Wed, 24 May 2006 14:04:38 -0700	[thread overview]
Message-ID: <4474CA66.5020401@hp.com> (raw)
In-Reply-To: <20060524204800.GH22881@ipom.com>

Phil Dibowitz wrote:
> Well, I can show you support on my home switch (cabletron) - the network guys
> will be a little unhappy if I clear stats on our production network (cisco)
> without warning them:

Isn't that last bit an example of why it might not be good to play-out 
that rope?-)

> Does having the ability to boot into single user mode break networking? No, it
> *allows* you to break networking. Does the _support_ of rmmod break the
> kernel? No, but it *allows* you to.

Are SNMP traps generated by going into single-user mode?  Rather like 
what I was saying to Brian earlier.   I suspect though that an rmmod 
doesn't generate an SNMP trap - unless perhaps that to do the rmmod one 
has to first ifdown the interface and that might?

rick jones

  reply	other threads:[~2006-05-24 21:04 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-24  1:22 reminder, 2.6.18 window David Miller
2006-05-24  8:01 ` Phil Dibowitz
2006-05-24 18:21   ` jamal
2006-05-24 18:23   ` Jeff Garzik
2006-05-24 18:34     ` Rick Jones
2006-05-24 18:56     ` Phil Dibowitz
2006-05-24 19:05       ` Jeff Garzik
2006-05-24 19:14         ` Phil Dibowitz
2006-05-24 20:01           ` Brent Cook
2006-05-24 20:08             ` Jeff Garzik
2006-05-25  7:23               ` Bill Fink
2006-05-25 13:05                 ` Brent Cook
2006-05-25 16:12                   ` Bill Fink
2006-05-25 17:59                   ` Phil Dibowitz
2006-05-25 18:41                     ` Brent Cook
2006-05-25 19:22                       ` Phil Dibowitz
2006-05-25 20:29                         ` David Miller
2006-05-25 21:04                           ` Phil Dibowitz
2006-05-25 21:07                             ` David Miller
2006-05-26  9:52                   ` Andi Kleen
2006-05-25 13:34                 ` Dave Dillow
2006-05-26  9:46               ` Andi Kleen
2006-05-24 20:10           ` jamal
2006-05-24 20:25             ` Rick Jones
2006-05-25 15:27               ` jamal
2006-05-25 16:43                 ` Rick Jones
2006-05-26 22:06                   ` Rick Jones
2006-05-24 20:44             ` Brian Haley
2006-05-24 21:01               ` Rick Jones
2006-05-26  6:48               ` Phil Dibowitz
2006-05-24 20:48             ` Phil Dibowitz
2006-05-24 21:04               ` Rick Jones [this message]
2006-05-24 21:10                 ` Ben Greear
2006-05-25  5:01                   ` Phil Dibowitz
2006-05-25  7:18                     ` Ben Greear
2006-05-25  7:55                     ` Bill Fink
2006-05-25 12:17                     ` Francois Romieu
2006-05-25  9:53       ` Pekka Savola
2006-05-24 20:53     ` Andy
2006-05-26  9:43   ` Andi Kleen

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=4474CA66.5020401@hp.com \
    --to=rick.jones2@hp.com \
    --cc=davem@davemloft.net \
    --cc=hadi@cyberus.ca \
    --cc=jeff@garzik.org \
    --cc=netdev@vger.kernel.org \
    --cc=phil@ipom.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;
as well as URLs for NNTP newsgroup(s).