public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: »Q« <boxcars@gmx.net>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: udev-197 and /etc/udev/rules.d/
Date: Tue, 22 Jan 2013 20:29:20 -0600	[thread overview]
Message-ID: <20130122202920.47216203@fuchsia.remarqs.net> (raw)
In-Reply-To: 20130122185159.1cbd90a0@marcec.hunte.us

On Tue, 22 Jan 2013 18:51:59 +0100
Marc Joliet <marcec@gmx.de> wrote:

> Am Tue, 22 Jan 2013 14:23:57 +0000
> schrieb Neil Bothwick <neil@digimed.co.uk>:
> 
> > ISTR a change in udev that prevented renaming devices. Put it all as
> > symlinks instead of renaming and trying to symlink back to %k. It
> > seems that all the replies with working examples do it this way too.

That works, thanks.

[snip]
 
> So currently you can only change network interface names, and nothing
> else.
> 
> [0] I haven't searched extensively, but found a related Email from
> Greg K-H (search for "rename") that points out that device node
> renaming has problematic/fragile behaviour:
> http://lkml.indiana.edu/hypermail/linux/kernel/1010.1/00427.html.
> 
> [1]
> https://www.kernel.org/doc/htmldocs/device-drivers/API-device-rename.html
> (documentation generated from linux-3.0-rc7). Relevant quote: "Device
> nodes are not renamed at all, there isn't even support for that in
> the kernel now."

Thanks for the discussion (snipped) and the links.  Something Greg K-H
said about kernel names reminded me that I've been meaning to stop
using them in fstab as well.

I've been a Gentoo user for twelve years, and I've learned a lot --
including some bad habits, heh.



      reply	other threads:[~2013-01-23  2:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-22  3:56 [gentoo-user] udev-197 and /etc/udev/rules.d/ »Q«
2013-01-22  6:07 ` [gentoo-user] " Hartmut Figge
2013-01-22  8:55 ` [gentoo-user] " Marc Joliet
2013-01-22 14:23 ` Neil Bothwick
2013-01-22 17:51   ` Marc Joliet
2013-01-23  2:29     ` »Q« [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=20130122202920.47216203@fuchsia.remarqs.net \
    --to=boxcars@gmx.net \
    --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