before it was just that you had to be aware to redo it when something changed. (which for me usually means booting from external media, dd'ing the pbr file onto a usb stick, booting into windows, and copying it into the right place.
having to boot windows every time you upgrade is a pain. On Fri, Mar 7, 2014 at 9:49 AM, Bob Beck <[email protected]> wrote: > No, because moving it means that you have to manually redo it every > time you install a snap. which is really a pita. > > > On Fri, Mar 7, 2014 at 9:44 AM, Mark Kettenis <[email protected]> wrote: >>> From: Theo de Raadt <[email protected]> >>> Date: Fri, 07 Mar 2014 09:24:13 -0700 >>> >>> > Whereas new installboot tends to shift it around: >>> > >>> > # installboot -v sd1 2>&1 | grep shift >>> > fs block shift 2; part offset 64; inode block 56, offset 2344 >>> > # installboot -v sd1 2>&1 | grep shift >>> > fs block shift 2; part offset 64; inode block 48, offset 16168 >>> > # installboot -v sd1 2>&1 | grep shift >>> > fs block shift 2; part offset 64; inode block 56, offset 2472 >>> > >>> > Meaning that the pbr must be updated with the new location. >>> >>> It doesn't just "tend" to move around (ie. tend == "prone to move"). >>> It moves every time, since it is using mkstemp to create a new file. >> >> But isn't this a good thing? >> >> Now it moves around consistently, so people perhaps won't forget and >> be surprised when it moves eventually. They just need some retraining ;). >>
