public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: udev (viable) alternatives ?
Date: Fri, 26 Sep 2014 09:46:46 +0100	[thread overview]
Message-ID: <20140926094646.050282c7@digimed.co.uk> (raw)
In-Reply-To: <CADPrc80Rbi2JqzsqVP3JR932yWmYjUo3HdnTr4LoFu3_XXWaLw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]

On Fri, 26 Sep 2014 03:22:16 -0500, Canek Peláez Valdés wrote:

> > That may be true for PCI devices but not for USB ones. If you unplug a
> > USB device and plug it back into the same port, it will get a
> > different device number. The naming is more predictable, but it's not
> > there yet.  
> 
> That doesn't sound right. If unplugging a USB net device and plugging
> it again *in the same port* results in a different device *name*, then
> it is a bug and should be reported; the description of the algorithm
> in [1] sounds like it should get always the same name for the same
> port, unless I'm misunderstanding something.

It certainly was the case. I couldn't test it directly because this
laptop doesn't have support for such devices, but plugging, unplugging
and replugging a USB ethernet adaptor resulted in a change of device
number. I just switched to a different machine and it does indeed give the
same name now, so things have been fixed and the interface names are now
predictable.

Ugly as hell, hard to remember, but they are predictable.


-- 
Neil Bothwick

Make it idiot proof and someone will make a better idiot.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2014-09-26  8:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-25 15:25 [gentoo-user] udev (viable) alternatives ? James
2014-09-25 17:47 ` Dale
2014-09-25 18:17 ` Samuli Suominen
2014-09-25 19:03   ` [gentoo-user] " James
2014-09-25 19:32     ` Dale
2014-09-26  0:23     ` Walter Dnes
2014-09-26  3:27       ` Alan McKinnon
2014-09-26  8:07         ` Neil Bothwick
2014-09-26  8:22           ` Canek Peláez Valdés
2014-09-26  8:46             ` Neil Bothwick [this message]
2014-09-26  8:47             ` Samuli Suominen
2014-09-26  9:04               ` Samuli Suominen
2014-09-26 16:47                 ` David W Noon
2014-09-27  2:06                   ` Samuli Suominen
2014-09-26  5:04     ` Samuli Suominen
2014-11-10 11:04       ` Tanstaafl
2014-11-10 12:30         ` Rich Freeman
2014-11-10 13:23           ` Tanstaafl
2014-11-10 14:23             ` Rich Freeman
2014-11-10 15:48         ` Samuli Suominen
2014-11-10 16:01           ` Tanstaafl
2014-11-11  5:20           ` Walter Dnes
2014-11-11  5:33             ` Samuli Suominen
2014-11-11  5:35             ` Canek Peláez Valdés
2014-11-11 12:18             ` Rich Freeman
2014-11-13 17:08               ` Walter Dnes
2014-11-17 10:27                 ` Tom H

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=20140926094646.050282c7@digimed.co.uk \
    --to=neil@digimed.co.uk \
    --cc=gentoo-user@lists.gentoo.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