public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: erik@debill.org
To: linux-kernel@vger.kernel.org
Subject: Re: ethtool documentation
Date: Wed, 7 Aug 2002 15:16:42 -0500	[thread overview]
Message-ID: <20020807201642.GA11100@debill.org> (raw)
In-Reply-To: <Pine.LNX.3.95.1020807070841.28061A-100000@chaos.analogic.com>

On Wed, Aug 07, 2002 at 07:18:17AM -0400, Richard B. Johnson wrote:
> 
> That capability is not permanent. If you let users write to the
> SEEPROM, permanently changing the IEEE Station Address, you have
> let users permanently break their network boards. I do protest
> when this capability is in the kernel.

Don't forget the old sun workstations that keep MAC addresses in
nvram, where it's setable via the boot prom.  I had one with a bad
battery that I had to reset the MAC address on by hand if I unplugged
it for too long.

They DID implement a check to make sure the first few bits were
correct for the product, though.  I couldn't pick completely random
MACs (though C0FFEE fit nicely at the end).

Given a working nvram, this change was "permanent", and the only tools
needed came with the system.



Erik

-- 
Ask not what your computer can do for you.  Ask what you can do for
  your computer.

  parent reply	other threads:[~2002-08-07 20:13 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-06 15:41 ethtool documentation Randy.Dunlap
2002-08-06 19:24 ` Richard B. Johnson
2002-08-06 19:40   ` Chris Friesen
2002-08-06 19:44     ` Randy.Dunlap
2002-08-06 20:03     ` Richard B. Johnson
2002-08-06 20:04       ` Randy.Dunlap
2002-08-06 20:36         ` Ben Greear
2002-08-06 21:15       ` Tim Hockin
2002-08-07  1:42         ` Richard B. Johnson
2002-08-07  3:33           ` Tim Hockin
2002-08-06 21:58       ` Alan Cox
2002-08-06 20:42         ` Randy.Dunlap
2002-08-06 22:27           ` Alan Cox
2002-08-19 19:00             ` Mark H. Wood
2002-08-07  1:57         ` Richard B. Johnson
2002-08-07 11:47           ` Alan Cox
2002-08-07  2:54   ` Ryan Anderson
2002-08-07  5:32   ` Dax Kelson
2002-08-07  6:30     ` Jonathan Lundell
2002-08-07 11:47       ` Alan Cox
2002-08-08  1:07         ` Peter Samuelson
2002-08-07 11:18     ` Richard B. Johnson
2002-08-07 12:05       ` Abraham vd Merwe
2002-08-07 18:44       ` Bernd Eckenfels
2002-08-07 20:16       ` erik [this message]
2002-08-07  8:02 ` Abraham vd Merwe
  -- strict thread matches above, loose matches on Subject: below --
2002-08-08  9:18 Helge Hafting
2002-08-07 18:16 Leif Sawyer
2002-08-06 20:57 Leif Sawyer
2002-08-07  1:51 ` Richard B. Johnson
2002-08-07 10:53   ` Jamie Lokier
2002-08-05 11:46 Abraham vd Merwe
2002-08-05 15:42 ` Jeff Garzik
2002-08-05 19:06   ` Tim Hockin
2002-08-05 19:16     ` Jeff Garzik
2002-08-05 19:30       ` Jonathan Lundell
2002-08-05 20:20         ` Jeff Garzik
2002-08-06 10:17     ` Abraham vd Merwe
2002-08-06 10:07       ` David S. Miller

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=20020807201642.GA11100@debill.org \
    --to=erik@debill.org \
    --cc=linux-kernel@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