From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: possible to mask nodes from being created ?
Date: Sat, 21 Feb 2004 00:35:26 +0000 [thread overview]
Message-ID: <20040221003526.GC18146@kroah.com> (raw)
In-Reply-To: <200402191452.14645.vapier@gentoo.org>
On Thu, Feb 19, 2004 at 02:52:08PM -0500, Mike Frysinger wrote:
> i looked through the files in /etc/udev/ but wasnt able to figure out a way to
> keep udev from creating nodes i'll never use ...
>
> for example, /dev/vc/ is populated with 64 nodes for the console and /dev/rd/
> is populated with 16 nodes for ramdisks ... personally i know i'm never going
> to use 64 nodes for my console nor am i going to use 16 nodes for
> ramdisks ...
>
> is there anyway for me to say 'only create tty[0-5]' or 'only create
> ram[0-3]' ? note that even throwing them in subdirs and just not creating a
> symlink isnt good enough in my book ;)
Yes there is. Just make a rule that matches the devices that you do not
want to have created and do not specify a NAME field (or give it a empty
string.) Something like:
KERNEL="tty[6-9]", NAME=""
or just
KERNEL="tty[6-9]"
Hope this helps.
greg k-h
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id\x1356&alloc_id438&op=click
_______________________________________________
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 prev parent reply other threads:[~2004-02-21 0:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 19:52 possible to mask nodes from being created ? Mike Frysinger
2004-02-21 0:35 ` Greg KH [this message]
2004-02-21 0:53 ` Jon Smirl
2004-02-21 3:23 ` 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=20040221003526.GC18146@kroah.com \
--to=greg@kroah.com \
--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.