From: Mike Frysinger <vapier@gentoo.org>
To: linux-hotplug@vger.kernel.org
Subject: possible to mask nodes from being created ?
Date: Thu, 19 Feb 2004 19:52:08 +0000 [thread overview]
Message-ID: <200402191452.14645.vapier@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
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 ;)
-mike
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]
next reply other threads:[~2004-02-19 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 19:52 Mike Frysinger [this message]
2004-02-21 0:35 ` possible to mask nodes from being created ? Greg KH
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=200402191452.14645.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).