From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bodo Eggert <7eggert@gmx.de> Subject: Re: [PATCH] Force UNIX domain sockets to be built in Date: Mon, 31 Dec 2007 14:26:42 +0100 (CET) Message-ID: References: <20071231122419.GA13803@does.not.exist> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=us-ascii Cc: Bodo Eggert <7eggert@gmx.de>, Jan Engelhardt , devzero@web.de, linux-kernel@vger.kernel.org, netdev@vger.kernel.org To: Adrian Bunk Return-path: Received: from moutng.kundenserver.de ([212.227.126.186]:55151 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751739AbXLaN1G (ORCPT ); Mon, 31 Dec 2007 08:27:06 -0500 In-Reply-To: <20071231122419.GA13803@does.not.exist> Sender: netdev-owner@vger.kernel.org List-ID: On Mon, 31 Dec 2007, Adrian Bunk wrote: > On Mon, Dec 31, 2007 at 01:09:43PM +0100, Bodo Eggert wrote: > > 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. > >... > > Is this just a purely theoretical thought or is this a reasonable use > case people actually use in practice? For now, it's a theoretical thought, but having an embedded device, I can see the reason for $EVERYTHING=m there. > After all, changing it to a bool will allow us to make the kernel image > for nearly everyone smaller by a few hundred bytes... I can't see why optionally building it as a module would force us to make the kernel bigger. It may be a little more ugly to support =m, but thats it, isn't it? -- Logic: The art of being wrong with confidence...