All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev.rules behavior changed ?
Date: Sat, 12 Jun 2004 12:19:24 +0000	[thread overview]
Message-ID: <1087042764.2337.7.camel@pim> (raw)
In-Reply-To: <200406111803.10401.vapier@gentoo.org>

On Fri, 2004-06-11 at 18:03 -0400, Mike Frysinger wrote:
> a while back i asked a question about how to disable device nodes from being 
> created ... a good example is the tty stuff.  by default, 64 tty's are 
> created (0-63) and the only solution is to either edit the kernel (not useful 
> across many different machines and kernel upgrades) or to 'trick' the 
> udev.rules file as so (this is what was suggested and what *used* to work):
> KERNEL="tty[0-9]",    NAME="vc/%n",  SYMLINK="%k"
> KERNEL="tty[0-9]*",   NAME=""
> 
> here you can see that tty0 - tty9 would have the nodes created while 
> tty10-tty63 should disappear ... however, now with udev-026 at least (it's 
> the first time i noticed because i was debugging that tty/666/660 mode bug), 
> i get all the vc nodes in /dev/vc/ with their tty symlinks in /dev/
> 
> is there a 'better' way to do what i want or is this a 'bug' ? :)
> -mike

Your rules are working as expected on my box:

[root@pim kay]# ls -la /udev/tty*
crw-------  1 root root 5,  0 Jun 12 14:09 /udev/tty
lrwxrwxrwx  1 root root     4 Jun 12 14:09 /udev/tty0 -> vc/0
lrwxrwxrwx  1 root root     4 Jun 12 14:09 /udev/tty1 -> vc/1
lrwxrwxrwx  1 root root     4 Jun 12 14:09 /udev/tty2 -> vc/2
lrwxrwxrwx  1 root root     4 Jun 12 14:09 /udev/tty3 -> vc/3
lrwxrwxrwx  1 root root     4 Jun 12 14:09 /udev/tty4 -> vc/4
lrwxrwxrwx  1 root root     4 Jun 12 14:09 /udev/tty5 -> vc/5
lrwxrwxrwx  1 root root     4 Jun 12 14:09 /udev/tty6 -> vc/6
lrwxrwxrwx  1 root root     4 Jun 12 14:09 /udev/tty7 -> vc/7
lrwxrwxrwx  1 root root     4 Jun 12 14:09 /udev/tty8 -> vc/8
lrwxrwxrwx  1 root root     4 Jun 12 14:09 /udev/tty9 -> vc/9
crw-------  1 root root 4, 64 Jun 12 14:09 /udev/ttyS0
crw-------  1 root root 4, 65 Jun 12 14:09 /udev/ttyS1
crw-------  1 root root 4, 66 Jun 12 14:09 /udev/ttyS2
crw-------  1 root root 4, 67 Jun 12 14:09 /udev/ttyS3
crw-------  1 root root 4, 68 Jun 12 14:09 /udev/ttyS4
crw-------  1 root root 4, 69 Jun 12 14:09 /udev/ttyS5
crw-------  1 root root 4, 70 Jun 12 14:09 /udev/ttyS6
crw-------  1 root root 4, 71 Jun 12 14:09 /udev/ttyS7

Are you sure your rules file matches the configured one in udev.conf?
By default, udev reads all files in /etc/udev/rules.d/ ending with
"*.rules".

Please try udevtest:

[root@pim kay]# /usr/bin/udevtest /sys/class/tty/tty9
version 026
looking at '/class/tty/tty9'
configured rule in '/etc/udev/rules.d/10-local.rules' at line 1 applied, added symlink '%k'
configured rule in '/etc/udev/rules.d/10-local.rules' at line 1 applied, 'tty9' becomes 'vc/%n'
creating device node '/udev/vc/9', major = '4', minor = '9', mode = '020600', uid = '0', gid = '0'

[root@pim kay]# /usr/bin/udevtest /sys/class/tty/tty10
version 026
looking at '/class/tty/tty10'
configured rule in '/etc/udev/rules.d/10-local.rules' at line 2 applied, 'tty10' is ignored


If this doesn't help, please build udev with "make DEBUG=true" and look
at the syslog, how your rules are processed.

Good luck,
Kay



-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the
one installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  reply	other threads:[~2004-06-12 12:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-11 22:03 udev.rules behavior changed ? Mike Frysinger
2004-06-12 12:19 ` Kay Sievers [this message]
2004-06-13 17:11 ` Mike Frysinger

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=1087042764.2337.7.camel@pim \
    --to=kay.sievers@vrfy.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.