From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: Leif Sawyer <lsawyer@gci.com>,
Ben Greear <greearb@candelatech.com>,
abraham@2d3d.co.za, "Randy.Dunlap" <rddunlap@osdl.org>,
Chris Friesen <cfriesen@nortelnetworks.com>,
linux-kernel@vger.kernel.org
Subject: Re: ethtool documentation
Date: Wed, 7 Aug 2002 11:53:04 +0100 [thread overview]
Message-ID: <20020807115304.B14073@kushida.apsleyroad.org> (raw)
In-Reply-To: <Pine.LNX.3.95.1020806214553.26399A-100000@chaos.analogic.com>; from root@chaos.analogic.com on Tue, Aug 06, 2002 at 09:51:19PM -0400
Richard B. Johnson wrote:
> This is not about 'freedom'. This is about modifying some hardware
> to make it pretend that it's something that it is not. It's completely
> unlike IP addresses or anything like that. It is supposed to uniquely
> identify a piece of hardware. It's like the "frequency of a radio station"
> where the IP address is like the "call sign".
That right, and it's very useful. How else would I have the freedom to
connect different computers onto the cable modem at home when our router
dies? (The cable service only allows a single registered MAC address)
And how else would I have the freedom to replace the old ISA NIC at
work, and continue to run the MAC-locked licensed compiler?
If nobody restricted freedoms by keying to the MAC address, I'd never
want to change it. But they do. And if the NICs didn't allow for
reprogramming it, I'd guess that there would be a Linux flag to run the
cards in promiscuous mode to simulate a fake MAC address in software..
-- Jamie
next prev parent reply other threads:[~2002-08-07 10:51 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 20:57 Leif Sawyer
2002-08-07 1:51 ` Richard B. Johnson
2002-08-07 10:53 ` Jamie Lokier [this message]
-- 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 15:41 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
2002-08-07 8:02 ` Abraham vd Merwe
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=20020807115304.B14073@kushida.apsleyroad.org \
--to=lk@tantalophile.demon.co.uk \
--cc=abraham@2d3d.co.za \
--cc=cfriesen@nortelnetworks.com \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lsawyer@gci.com \
--cc=rddunlap@osdl.org \
--cc=root@chaos.analogic.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
all inboxes | Powered by JetHome®