Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Udev generates too many tty dev nodes
Date: Thu, 17 Jan 2013 14:19:07 +0100	[thread overview]
Message-ID: <20130117141907.3d71a934@skate> (raw)
In-Reply-To: <CAKvQZ_085YC_LpJhD5Oxq6KOg9mnRY1O6KSRw75+++6+Fh_+SA@mail.gmail.com>

Dear Willy Lambert,

On Thu, 17 Jan 2013 14:05:46 +0100, Willy Lambert wrote:

> I do ^^. The bad argument is that I hate having mess on my device,
> especially when typing "ls /dev". The good one is that if something
> behave strangly I like to tackle the root cause. It's not an
> industrial projet, it's a personnal one on which I can take the time I
> want to look at everything I like :D. And in this case I do *not* have
> a need for 64 ttys and I did *not* (at least consciently) ask for
> having them. So somehting, somewhere is doing thing on my back, and I
> want to know what.
> 
> udev is supposed to show only what's available or in use. It's sure
> that some of those devices are not meeting this criterias.

Those devices *are* available. They have been registered by the kernel,
so they are available, and it makes perfect sense for udev to create
device files for them.

If you really don't want to see them in /dev, then create a udev rule
to not create those device files. See the answer at
http://unix.stackexchange.com/questions/25021/change-the-number-of-generated-dev-tty-devices
for a hint (not tested, not sure it is the correct way of writing the
udev rule, check udev's documentation).

At the kernel level, this number of tty is not configurable. It's
defined by MAX_NR_CONSOLES, and interestingly, this constant is part of
the kernel to userspace ABI, so I am not sure it is entirely safe to
change it to some other random value.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-01-17 13:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-17  0:48 [Buildroot] Udev generates too many tty dev nodes Willy Lambert
2013-01-17  9:57 ` Jérôme Pouiller
2013-01-17 13:10   ` Willy Lambert
2013-01-17 12:55 ` Thomas Petazzoni
2013-01-17 13:05   ` Willy Lambert
2013-01-17 13:19     ` Thomas Petazzoni [this message]
2013-01-17 13:43       ` Willy Lambert

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=20130117141907.3d71a934@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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