Joshua Kinard <ku...@gentoo.org> writes: > Put simply, the kernel's single purpose, as nothing more than a > hyper-complex while loop, is to get the hardware up into a usable state and > then hand off to userland, then sit and service userland's needs as called > upon. The kernel should have all of the subsystems loaded into it necessary > to accomplish this task. The fact that the userland, in the current > ill-conceived case, cannot get itself up and running simply because /usr is > on a yet-to-be-mounted partition is not a concern of the kernel's. Thus, > the loading of an initramfs into the kernel to solve this issue is, in > principle, a violation (and a Cthulhu-awful hack). > > Maybe I'm just a old codger who refuses to accept change. I'm fine with > that description. I like things to remain somewhat simple, and my view of > Linux, both kernel and userland, over the last few years is one of growing > dismay due to the constant introduction of subsystem layer atop subsystem > layer for very little gain. How much longer until we need a kernel to boot > the kernel to mount the userland that mounts the userland (yo dawg)?
This a very well put argument that I find enjoyable reading. Thank you Joshua. Yours, Benda
