From: Mike Frysinger <vapier@gentoo.org>
To: linux-hotplug@vger.kernel.org
Subject: udev.rules behavior changed ?
Date: Fri, 11 Jun 2004 22:03:10 +0000 [thread overview]
Message-ID: <200406111803.10401.vapier@gentoo.org> (raw)
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
-------------------------------------------------------
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
next reply other threads:[~2004-06-11 22:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 22:03 Mike Frysinger [this message]
2004-06-12 12:19 ` udev.rules behavior changed ? Kay Sievers
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=200406111803.10401.vapier@gentoo.org \
--to=vapier@gentoo.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 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).