On Mon, Jan 13, 2014 at 05:08:49PM +0400, Andrey Borzenkov wrote: > On Mon, Jan 13, 2014 at 1:12 PM, Michael Chang <mch...@suse.com> wrote: > > > > OK. To be more verbose, the question of mine is that I'm uncertain if > > we don't explicitly install to a partition using blocklists, the > > /fs/core.img would still automatically get blocklists of itself > > updated on it's own diskboot.S header or stay with default? > > > > On i386-pc you boot core.img by using "multiboot". It bypasses > blocklists completely so it is irrelevant. On EFI you get standard EFI > binary that you can "chainload".
Now I understand it, thanks for the explaination. Regards, Michael > > >>>> > >>>> BTW 30_os-prober will happily fetch boot entries from every existing > >>>> snapshot, presenting them all with identical names and "merging" all > >>>> boot entries from all snapshots because it generates the same menu id > >>>> (it includes only fs UUID, but no subvolume information). > >>> > >>> Are you suggesting to use os-prober, instead sourced by master config > >>> directly for inclusion of boot entries of snapshots ? Or I've > >>> misinterpreted it? > >>> > >> > >> Oh, sorry for confusion. I simply meant that current 30_os-prober is > >> buggy and needs fixing. I think I have an idea how. > > > > You meant fixing 30_os-prober or getting btrfs snapshot booting to > > work ? > > I mean fixing 30_os-prober > > _______________________________________________ > Grub-devel mailing list > Grub-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/grub-devel _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
