On Sat, Jul 11, 2009 at 07:32:36PM +0100, Colin Watson wrote: > On Sat, Jul 11, 2009 at 06:20:13PM +0200, Michal Suchanek wrote: > > The other problem is that scripts like os-prober that use linux > > filesystem code for probing filesystems destroy your data. > > > > Linux cannot mount journalled filesystems readonly. It always modifies > > them. The extent of the modifications and the impact may vary > > depending on the state of the filesystem (clean/mounted) and the way > > you are going to use it in the future (resume the system/fresh boot) > > but until Linux people implement readonly filesystem support any Linux > > based os-probers cannot be recommended. > > I'm pretty sure this is fixable with blockdev --setro. The main reason > we haven't got round to doing this in os-prober yet is that we need to > get round to adding blockdev to busybox (which is important for > os-prober's original purpose, the Debian installer).
Does D-I use os-prober for anything other than GRUB ? With grub-pc, it doesn't need to invoke os-prober directly, installing it to the target system would be enough. -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all." _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
