From: Tim Small <tim@seoss.co.uk>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Narendra K <Narendra_K@dell.com>,
netdev@vger.kernel.org, linux-hotplug@vger.kernel.org,
linux-pci@vger.kernel.org, matt_domsch@dell.com,
charles_rose@dell.com, jordan_hargrave@dell.com,
vijay_nijhawan@dell.com
Subject: Re: [PATCH] Use firmware provided index to register a network interface
Date: Thu, 23 Sep 2010 06:34:20 +0000 [thread overview]
Message-ID: <4C9AF4EC.7020408@seoss.co.uk> (raw)
In-Reply-To: <20100922151645.649d3d7a@nehalam>
Stephen Hemminger wrote:
>>> http://marc.info/?l=linux-netdev&m\x125510301513312&w=2
>> Out of interest, that link says that doing it in usespace was rejected,
>> but doesn't give any references... I'd be interested to know why this
>> wasn't viable - since this seemed like the best fit at first glance -
>> most people will never use this, so no need to grow their kernel size
>> and complexity?
>>
>>
>
> This proposal was to ad changes into every application that
> knows about network names (iproute, iptables, snmp, quagga, openswan, ...)
> to do aliasing at the application layer.
>
OK, that's bonkers, but what I was refering to was the line in the
linked post which said "Achieve the above in userspace only using udev"
- which I assumed meant to do it once in a udev rename rule by adapting
/etc/udev/rules.d/70-persistent-net.rules , /lib/udev/write_net_rules
etc. - which is what I've used to enforce this sort of convention myself
from time to time.
Tim.
--
South East Open Source Solutions Limited
Registered in England and Wales with company number 06134732.
Registered Office: 2 Powell Gardens, Redhill, Surrey, RH1 1TQ
VAT number: 900 6633 53 http://seoss.co.uk/ +44-(0)1273-808309
next prev parent reply other threads:[~2010-09-23 6:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 18:31 [PATCH] Use firmware provided index to register a network interface Narendra K
2010-09-22 19:22 ` [PATCH] Use firmware provided index to register a network Greg KH
2010-09-23 15:22 ` [PATCH] Use firmware provided index to register a network interface Narendra_K
2010-09-23 15:27 ` [PATCH] Use firmware provided index to register a network Greg KH
2010-09-23 15:51 ` [PATCH] Use firmware provided index to register a network interface Narendra_K
2010-09-23 16:33 ` [PATCH] Use firmware provided index to register a network Greg KH
2010-10-07 14:26 ` Narendra_K
2010-10-07 14:27 ` [PATCH] Use firmware provided index to register a network interface Tim Small
2010-10-07 14:31 ` [PATCH] Use firmware provided index to register a network Greg KH
2010-09-22 22:07 ` [PATCH] Use firmware provided index to register a network interface Tim Small
2010-09-22 22:16 ` [PATCH] Use firmware provided index to register a network Stephen Hemminger
2010-09-23 6:34 ` Tim Small [this message]
2010-09-23 15:25 ` [PATCH] Use firmware provided index to register a network interface Narendra_K
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=4C9AF4EC.7020408@seoss.co.uk \
--to=tim@seoss.co.uk \
--cc=Narendra_K@dell.com \
--cc=charles_rose@dell.com \
--cc=jordan_hargrave@dell.com \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matt_domsch@dell.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=vijay_nijhawan@dell.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).