* Ben Hutchings <ben@decadent.org.uk> [Tue Aug 24, 2010 at 03:09:06PM +0100]: > On Tue, 2010-08-24 at 14:54 +0100, Colin Watson wrote: > > Consider building a filesystem image inside a chroot which one is about > > to build into a live filesystem image with mksquashfs or something. In > > the event that it contains flash-kernel, then the flash-kernel hook > > (once such a thing exists; in the meantime, the hardcoded flash-kernel > > code in run_bootloader) will write to the host system's flash memory. > > (Take another similar example if you disagree with the precise details > > of this one; LILO may well have similar properties.) > If the live filesystem image includes a boot loader package with a > kernel or initramfs hook, you're already running the risk of breaking > the user's machine by installing a boot loader they never wanted. > Protecting the build machine only hides the problem. So what's the proper way to disable the kernel or initramfs hook in your opinion? I explore the same problem Colin is talking about and deploying kernel and bootloader packages is something people building live systems have to deal with, so I'm interested in getting this situation fixed as well. regards, -mika-
Attachment:
signature.asc
Description: Digital signature