| 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
| ||
|
Message-ID: <20310.57932.964124.347872@quad.stoffel.home> Date: Tue, 6 Mar 2012 23:21:32 -0500 From: "John Stoffel" <john@...ffel.org> To: linux-kernel@...r.kernel.org Subject: Why does NET_VENDOR_DEC default to y? I just tried building a 3.3-rc6 kernel, based on my 3.1.0-rc4 kernel config that I'm running. Sue me, I don't upgrade my home server quickly. Anyway, I was watching the 'make oldconfig' zoom by and I noticed that I was suddenly adding in DEC networking cards. Now I admit I loved the tulip cards from ages ago, but this is crazy. I haven't had a DEC card in my systems for years, and it's not like you find them in new systems. So I poked into drivers/net/ethernet/dec/Kconfig and the stupid thing is now setup so that NET_VENDOR_DEC defaults to Y. Wtf? Why do I suddenly have to build in these drivers now? Or even get asked about them by default now? Maybe I'm just being too testy... John -- 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/
Powered by blists - more mailing lists