From: Bodo Eggert <7eggert@gmx.de>
To: David Miller <davem@davemloft.net>
Cc: 7eggert@gmx.de, viro@ZenIV.linux.org.uk, jengelh@computergmbh.de,
devzero@web.de, linux-kernel@vger.kernel.org, bunk@kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] Force UNIX domain sockets to be built in
Date: Tue, 1 Jan 2008 05:48:06 +0100 (CET) [thread overview]
Message-ID: <alpine.LSU.0.999.0801010459500.12978@be1.lrz> (raw)
In-Reply-To: <20071231.194843.136619677.davem@davemloft.net>
On Mon, 31 Dec 2007, David Miller wrote:
> From: Bodo Eggert <7eggert@gmx.de>
> > The big question is: Is there any non-embedded system where you have
> > to aim for a small kernel image?
>
> One some platforms, due to bootloader restrictions or whatever,
> there are hard limits on how large the main kernel image can be.
>
> On sparc64 for example the limit is around 6.5MB
That would be about the size of a complete rescue system. I don't think we
need to worry about unix sockets there, do we?
> But this "big question" isn't the important issue, in fact it's
> tangental and has no bearing on the final decision we make
> here.
>
> Rather, choice is, and taking choice away is bad. I may have a reason
> to make AF_UNIX modular, I might not, but either way taking that
> option away from me is not the right thing to do.
_You_'ll still have the option, because you have selected EMBEDDED=y
(otherwise, you'd miss all other valuable options to cripple your kernel),
while the folks that just care for a working systems will have what they'd
select anyway without being bothered with useless questions.
--
Top 100 things you don't want the sysadmin to say:
5. Just add yourself to the password file and make a directory...
next prev parent reply other threads:[~2008-01-01 4:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-31 12:09 Bodo Eggert
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 [this message]
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.0801010459500.12978@be1.lrz \
--to=7eggert@gmx.de \
--cc=bunk@kernel.org \
--cc=davem@davemloft.net \
--cc=devzero@web.de \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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®