From: Bodo Eggert <7eggert@gmx.de>
To: Jan Engelhardt <jengelh@computergmbh.de>,
devzero@web.de, linux-kernel@vger.kernel.org,
Adrian Bunk <bunk@kernel.org>,
netdev@vger.kernel.org
Subject: [PATCH] Force UNIX domain sockets to be built in
Date: Mon, 31 Dec 2007 13:09:43 +0100 (CET) [thread overview]
Message-ID: <alpine.LSU.0.999.0712311300020.3686@be1.lrz> (raw)
As suggested by Adrian Bunk, UNIX domain sockets should always be built in
on normal systems. This is especially true since udev needs these sockets
and fails to run if UNIX=m.
Signed-Off-By: Bodo Eggert <7eggert@gmx.de>
---
Last minute change: I decided against making it a bool because embedded
folks might depend on a small kernel image. Edited in the patch below.
diff -X dontdiff -pruN linux-2.6.23.base/net/unix/Kconfig linux-2.6.23.socket-y/net/unix/Kconfig
--- linux-2.6.23.base/net/unix/Kconfig 2006-11-29 22:57:37.000000000 +0100
+++ linux-2.6.23.socket-y/net/unix/Kconfig 2007-12-31 12:57:44.000000000 +0100
@@ -3,7 +3,8 @@
#
config UNIX
- tristate "Unix domain sockets"
+ tristate "Unix domain sockets" if EMBEDDED
+ default y
---help---
If you say Y here, you will include support for Unix domain sockets;
sockets are the standard Unix mechanism for establishing and
--
A. Top posters
Q. What's the most annoying thing on Usenet?
next reply other threads:[~2007-12-31 12:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-31 12:09 Bodo Eggert [this message]
2007-12-31 12:20 ` David Miller
2007-12-31 14:03 ` Bodo Eggert
2007-12-31 19:38 ` Al Viro
2008-01-01 3:45 ` Bodo Eggert
2008-01-01 3:48 ` David Miller
2008-01-01 4:48 ` Bodo Eggert
2008-01-01 5:01 ` Theodore Tso
2008-01-02 10:25 ` Herbert Xu
2008-01-02 12:26 ` Bodo Eggert
2007-12-31 12:24 ` Adrian Bunk
2007-12-31 13:26 ` Bodo Eggert
2007-12-31 14:42 ` Adrian Bunk
2007-12-31 15:19 ` Bodo Eggert
2007-12-31 15:34 ` Jan Engelhardt
2007-12-31 17:43 ` Patrick Mau
2007-12-31 22:20 ` Jan Engelhardt
2007-12-31 17:51 ` Adrian Bunk
2007-12-31 18:05 ` Adrian Bunk
2007-12-31 15:55 ` Torsten Kaiser
2007-12-31 15:59 ` Michael Buesch
2007-12-31 16:01 ` Alan Cox
2007-12-31 16:17 ` Torsten Kaiser
2007-12-31 16:38 ` Alan Cox
2007-12-31 17:18 ` Michael Buesch
2007-12-31 18:37 ` Torsten Kaiser
2007-12-31 19:05 ` Michael Buesch
2007-12-31 16:11 ` Torsten Kaiser
2007-12-31 13:23 devzero
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=alpine.LSU.0.999.0712311300020.3686@be1.lrz \
--to=7eggert@gmx.de \
--cc=bunk@kernel.org \
--cc=devzero@web.de \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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
all inboxes | Powered by JetHome®