From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: linux-kernel@vger.kernel.org
Subject: seems to be impossible to disable CONFIG_SERIAL [2.6.7]
Date: Fri, 10 Sep 2004 12:08:19 +0100 [thread overview]
Message-ID: <20040910110819.GE14060@lkcl.net> (raw)
hi,
has anyone noticed that it's impossible (without hacking) to remove
CONFIG_SERIAL?
remove the entries or set all SERIAL config entries to "n"...
hit make...
CONFIG_SERIAL_8250 gets set to "m", CONFIG_SERIAL gets set to "y"!
seeerrrriiialllll muuuusssstttt dieeeeeee kill kill kill.
actually there is a serious reason: udev at the moment is
taking up a significant amount of startup time (with selinux
enhancements) due to the number of entries to create in /dev.
if the dbus stuff was enabled as well it would be _even longer_.
there are 64 ttys created
there are 64 serial devices created.
only three of these are actually used on my computer - well two at most:
tty0 and tty7.
why in hell's name would i want 128 unnecessary devices created?
i feel a kernel parameter coming on...
l.
--
--
Truth, honesty and respect are rare commodities that all spring from
the same well: Love. If you love yourself and everyone and everything
around you, funnily and coincidentally enough, life gets a lot better.
--
<a href="http://lkcl.net"> lkcl.net </a> <br />
<a href="mailto:lkcl@lkcl.net"> lkcl@lkcl.net </a> <br />
next reply other threads:[~2004-09-10 10:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 11:08 Luke Kenneth Casson Leighton [this message]
2004-09-10 11:09 ` seems to be impossible to disable CONFIG_SERIAL [2.6.7] Russell King
2004-09-10 12:20 ` Luke Kenneth Casson Leighton
2004-09-10 12:35 ` Russell King
2004-09-10 12:59 ` Roman Zippel
2004-09-10 14:00 ` Alan Cox
2004-09-10 13:07 ` Luke Kenneth Casson Leighton
2004-09-10 18:12 ` Bill Davidsen
2004-09-10 20:55 ` Kyle Moffett
2004-09-15 14:56 ` Bill Davidsen
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=20040910110819.GE14060@lkcl.net \
--to=lkcl@lkcl.net \
--cc=linux-kernel@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