Re: change boot-file doesn't work
Re: change boot-file doesn't work
- Subject: Re: change boot-file doesn't work
- From: Jim Magee <email@hidden>
- Date: Sun, 14 Nov 2004 15:53:19 -0500
On Nov 14, 2004, at 9:54 AM, Gong Michael wrote:
I successfully built the latest kernel, xnu-517.9.4.
Before actually using it , I need to test whether it
works or not.
From some previous threads, I learn that I can change
boot-file variable to boot the Mac with my built
kernel, but it seems not works.
Here is what I did:
sudo cp <path_to_my_built_kernel>/mach_kernel
/mach_kernel.gcc
sudo nvram boot-device
boot-device hd:,\\:tbxi
sudo nvram boot-file='hd:, mach_kernel.gcc'
sudo reboot
There are typically a LOT of extensions to process during boot. Each
one has to be relocated against the current kernel and their dependent
extensions. That can take quite a bit of time - and yet the result
rarely changes. So, the kernel booting mechanism keeps a few caches
around:
/System/Library/Extensions.mkext
/System/Library/Extensions.kextcache
/System/Library/Caches/com.apple.kernelcaches/*
If you just replace the kernel (through a boot-arg assignment) BootX
can sometimes pick up the wrong Extension.kextcache file and have a
failed boot. Therefore, you should remove all these files booting an
alternate kernel. Alternatively, you can just "touch
/System/Library/Extensions," but you have to make sure your date is
correct, etc.... I find it easier just to remove the cache files.
--Jim
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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