* H. Peter Anvin <[EMAIL PROTECTED]> wrote:
> Ingo Molnar wrote:
>> * H. Peter Anvin <[EMAIL PROTECTED]> wrote:
>>
>>>>> Nope. It runs inside an initramfs, of course; that initramfs is linked
>>>>> into the kernel binary.
>>>> would be nice to have a single-image variant for all of this. having the
>>>> separate initrd was always trouble - and it's pointless as well. (we
>>>> rarely update the initrd without updating the vmlinuz as well)
>>> We do. Am I missing something?
>>
>> do we have a single-image way of getting both the kernel image and the
>> initram set up at once? What i know of is a two-image approach: vmlinuz
>> and initrd.
>>
>
> Yes, we do. The initramfs can be linked into the kernel image. The
> unified klibc build tree does that by default.
argh. Guess i misread your answer:
>>>>>> nor do i - i was under the impression that klibc was able to work
>>>>>> out of a bzImage too? Am i wrong?
>>>>> Nope. It runs inside an initramfs, of course; that initramfs is linked
>>>>> into the kernel binary.
i took that "Nope" as referring to my impression - but you in fact meant
that i am not wrong? :-) So nothing to see here. single-bzImage initrd
was and is possible, so we could in fact move chunks of system-related
userland (such as irqbalanced) into the kernel proper?
Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
