From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] Udev generates too many tty dev nodes
Date: Thu, 17 Jan 2013 10:57:17 +0100 [thread overview]
Message-ID: <3906424.A8B2AW86f2@sagittae> (raw)
In-Reply-To: <CAKvQZ_2FEFO7BNqkzXTCeH5+scxg6ZhuW+Ruy99Q8xxivjhx_w@mail.gmail.com>
On Thursday 17 January 2013 01:48:41 Willy Lambert wrote:
> Hi all,
Hi,
> I'm trying to put my /dev folder into order, and I recently switched
> from static config to udev. All device are correctly set up exept tty*
> that are umerously present (something like 64 nodes).
>
> _ Does anyone know if it is normal that so many files are generated ?
> (or said differently should I wonder about my buildroot outputs)
> _ Is there any mean to change that ?
> _ Is this only and udev problem or is it linked to buildroot integration ?
Udev only create devices declared by kernel. So this setting is somewhere in
kernel configuration.
> I think it's a quite "common problem" but googling it didn't helped :(
> The better answer was that :
> http://unix.stackexchange.com/questions/25021/change-the-number-of-generated
> -dev-tty-devices but it's a bit hackish... I generate a rootfs from scratch
> so I want to manage everything that's happening inside, so in this case I
> want to tell it how many device it may/should create.
It looks, there is no configuration entry to change this setting.
Nevertheless, you can try to change MAX_NR_CONSOLES from linux/vt.h.
BR,
--
J?r?me Pouiller
next prev parent reply other threads:[~2013-01-17 9:57 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 [this message]
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
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=3906424.A8B2AW86f2@sagittae \
--to=jezz@sysmic.org \
--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