Re: Understanding kexts in the early boot process
Re: Understanding kexts in the early boot process
- Subject: Re: Understanding kexts in the early boot process
- From: mm w <email@hidden>
- Date: Mon, 15 Jun 2009 11:03:18 -0700
open /usr/standalone/bootcaches.plist -> PostBootPaths
somehow, yes, a bootloader is not made check the integrity of a
system, bootloader steps: power on, list table, read
On Mon, Jun 15, 2009 at 10:55 AM, Thomas Tempelmann<email@hidden> wrote:
> Nik,
>
>> Again some confusion in terminology. The boot loader copies kexts into
>> memory that the kernel knows how to find, it does not load kexts (in the
>> sense of getting them actually running, as it does for the kernel). To "load
>> a kext" is a pretty involved process, which varies between early boot and
>> when kextd starts, of which linking is only a part.
>
> I meant "load" in its more raw sense, i.e. read from disk into memory.
>
> So, if I understand you right, the boot loader reads the kexts into
> memory and passes a pointer to them to the kernel. The kernel then
> iterates over the kexts, executing their code.
>
> I just try to understand when the files get read and when they get
> executed. If it is how I just suggested, then this means that the boot
> loader is the authority in selecting all the kexts for the kernel, and
> the kernel has no choice than to work with those - if they're not
> sufficient, the kernel may fail to boot because the kernel does _not_
> read essential kexts on its own. Correct?
>
> --
> Thomas Tempelmann, http://www.tempel.org/
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Darwin-kernel mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden