From: Gadre Nayan <gadrenayan@gmail.com>
To: kernelnewbies@lists.kernelnewbies.org
Subject: Re: rules for interface naming for on-board cards
Date: Tue, 03 May 2016 04:28:30 +0000 [thread overview]
Message-ID: <CAKJ7aR47Y7EQ_C9mOiSnceeygwTixxUSwj4upqtJKqM4r4sj3w@mail.gmail.com> (raw)
In-Reply-To: <CAC+QLdTcFSqump4hD4mP67zWJSqcNVJR0aL+aDx0MqL_conCqw@mail.gmail.com>
Hi,
Thanks. I see that in my system for onboard devices I get a sysfs
attribute "acpi_index", which is not available for removable cards.
So currently existence and non existence of this file will be
sufficient to detect.
Thanks.
On Mon, May 2, 2016 at 10:22 PM, Mandeep Sandhu
<mandeepsandhu.chd@gmail.com> wrote:
>>
>> If the name contains a %d format string, the first available device
>> name with the given base is used; assigned numbers start at zero.
>>
>> On my base machine, I have 1 NIC card which is onboard, rest I can
>> remove and plug.
>> For the onboard card I get the interfaces as em1-4, while all the
>> other cards I get names as p1p2, p3p4 etc.
>
> This looks like systemd's way of naming network interfaces (aka
> predictable network interface names). Are you running a systemd
> enabled system?
>
> If so, look at this systemd guide for the naming convention:
>
> https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
>
> HTH,
> -mandeep
>
>
>>
>> Does Udev know the difference.
>>
>> How are these names given, definitely there must be some configuration
>> which is used to distinguish on-board card vs removable.
>>
>> Thanks.
>>
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies@kernelnewbies.org
>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2016-05-03 4:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 12:56 rules for interface naming for on-board cards Gadre Nayan
2016-05-02 16:52 ` Mandeep Sandhu
2016-05-03 4:28 ` Gadre Nayan [this message]
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=CAKJ7aR47Y7EQ_C9mOiSnceeygwTixxUSwj4upqtJKqM4r4sj3w@mail.gmail.com \
--to=gadrenayan@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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 read-only IMAP folder(s) and NNTP newsgroup(s).