linux-kernel - Re: [PATCH] CONFIG_NET=n - lots of link time errors

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0707221206280.15705@fbirervta.pbzchgretzou.qr>
Date:	Sun, 22 Jul 2007 12:10:38 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	David Miller <davem@...emloft.net>
cc:	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org
Subject: Re: [PATCH] CONFIG_NET=n - lots of link time errors


On Jul 21 2007 19:12, David Miller wrote:
>> Enabling drivers from "Devices > Networking" (in menuconfig), for 
>> example SLIP and/or PLIP, throws link time errors when CONFIG_NET itself 
>> is =n. Have CONFIG_NETDEVICES depend on CONFIG_NET.
>> 
>> Signed-off-by: Jan Engelhardt <jengelh@....de>
>
>This is the second time I've seen this change in the past few
>days, and people seem to hit it quite readily with randconfig.
>
>It seems reasonable and I'll apply it, thanks Jan.

While randconfig is nice and good, this error actually came by manually
tuning the .config for a specific goal (namely: make a small kernel for an
ancient i386 without modifying any code). Turning off CONFIG_NET
was then just an idea away, because I knew that TCP was quite big.


	Jan
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/