From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: tty devices
Date: Wed, 21 Jan 2004 23:47:28 +0000 [thread overview]
Message-ID: <20040121234728.GB1958@kroah.com> (raw)
In-Reply-To: <20040117195133.90850.qmail@web14901.mail.yahoo.com>
On Wed, Jan 21, 2004 at 07:23:46PM +0200, Bob Barry wrote:
> On Sat, 17 Jan 2004 11:51, Jon Smirl wrote:
> > Why do I have 60 tty devices under udev; is this controllable?
> > What would I use the 60 tty devices for?
>
> I asked the same thing of Martin Schlemmer (the gentoo udev packager) :
>
> >> I have several times pruned the tty's to tty0-tty6 and restarted. I have verified that
> >> dev-state/devices.bz2 contains only tty0-tty6, but hotplug/udev always re-creates
> >> tty's through tty63. Is that good or correct? Is it configurable?
>
> He replied:
>
> > That is what is supported by the kernel, so is created. You could
> > change the tty stuff in /etc/udev/udev.rules to rather call a script,
> > and only handle what you want ...
>
> Like Jon, I feel it's contrary to udev's charter. Is it really right?
"udev's charter"? Huh?
The kernel is creating all of those tty devices. It is exporting that
information to userspace. If udev it told to, it will create all of
those device nodes. If you write a rule to ignore them, udev will
ignore them.
What's the problem here?
And are you _sure_ you don't need those nodes? Some programs expect to
see them (screen, expect, etc.)
thanks,
greg k-h
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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-01-21 23:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 19:51 tty devices Jon Smirl
2004-01-19 18:47 ` Greg KH
2004-01-21 17:23 ` Bob Barry
2004-01-21 23:47 ` Greg KH [this message]
2004-01-22 0:05 ` Jon Smirl
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=20040121234728.GB1958@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 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).