Messages in this thread | | | Date | Tue, 25 Feb 2003 13:35:33 +0000 | From | Russell King <> | Subject | Re: zImage now holds vmlinux, System.map and config in sections. (fwd) |
| |
On Tue, Feb 25, 2003 at 01:50:10PM +0100, Remco Post wrote: > Hmm, and how would you implement that on a system (ppc/prep) that could very > easily netboot a kernel... no /boot needed? I for one build kernels on one > box that is more or less production and netboot another just to see it fail > horribly... having all stuff in one file could help....
So you want to transfer the complete zImage, including the redundant configuration and system.map to the target over the network, only to have it thrown away?
Guess what? I netboot ARM boxes as well. I cope. It's easy. You change /boot/ to be $TARGET (eg, /var/boot/kernels/), which is where you put your netboot kernel image today.
If you have more than one kernel build, then put it in TARGET=/var/boot/kernels/<machine-name>/
Or, in the case of a NFS root setup, you place all the files in the boot directory of the NFS root image for the target system. This way, the target gets the correct System.map, again with no extra hastles.
I do all of the above (minus the .config.) It works. Nice. Simple. No hastle.
-- Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux http://www.arm.linux.org.uk/personal/aboutme.html
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |