From: "H. Peter Anvin" <hpa@zytor.com> Date: Tue, 18 Sep 2007 11:41:34 -0700I appreciate the effort you put into klibc and the offer to make initrd's easier to build. But the point is that the initrd shouldn't be necessary in the first place. There becomes zero point in building these drivers statically into the kernel, which many of us do specifically to avoid module loading, initrds, and all that fuss. Because the driver is totally crippled even though it's been fully built into the main kernel image. I mean, it's so incredibly stupid and makes kernel development that much more difficult. Every new dependency, be it requiring initrd or something else, is one more barrier added to kernel development. I really pine for the days where everything was so simple, and initrd and modules were the odd ball cases, most developers built everything into their kernel image. -
| Ingo Molnar | Re: containers (was Re: -mm merge plans for 2.6.23) |
| Greg Kroah-Hartman | [PATCH 009/196] Chinese: add translation of sparse.txt |
| holzheu | Re: [RFC/PATCH] Documentation of kernel messages |
| Vladislav Bolkhovitin | Re: Integration of SCST in the mainstream Linux kernel |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | [GIT]: Networking |
| Antonio Almeida | HTB accuracy for high speed |
