From: Matt Domsch <Matt_Domsch@dell.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: net device renaming 2-step, IFNAMSIZ limit
Date: Tue, 07 Dec 2010 03:54:10 +0000 [thread overview]
Message-ID: <20101207035409.GA30400@auslistsprd01.us.dell.com> (raw)
In-Reply-To: <20101129032908.GA29904@auslistsprd01.us.dell.com>
On Tue, Dec 07, 2010 at 12:45:04AM -0200, Piter PUNK wrote:
> As we talk on #udev, there is a patch that uses hash32 function inside
> libudev to create
> the intermediate name. We use the "oldname-newname" to create the hash.
> With that,
> exceeding IFNAMSIZ isn't a problem:
Thanks piterpunk.
I built udev on a Fedora 14 box, with this patch, and it works.
However, I don't see udev doing the 2-step anymore, perhaps that was
just a figment of the loglevel. Anyhow, it looks right, and doesn't
blow up.
Thanks,
Matt
--
Matt Domsch
Technology Strategist
Dell | Office of the CTO
next prev parent reply other threads:[~2010-12-07 3:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 3:29 net device renaming 2-step, IFNAMSIZ limit Matt Domsch
2010-12-07 2:45 ` Piter PUNK
2010-12-07 3:54 ` Matt Domsch [this message]
2011-01-29 15:23 ` Matt Domsch
2011-02-08 14:42 ` Kay Sievers
2011-02-08 18:07 ` Scott James Remnant
2011-02-09 16:21 ` Matt Domsch
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=20101207035409.GA30400@auslistsprd01.us.dell.com \
--to=matt_domsch@dell.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).