On Tue, Aug 8, 2017 at 2:04 AM, Vladimir 'phcoder' Serbinenko
wrote:
> Did you mount /proc ? What is the contents of /proc/self/mountinfo ?
/proc is mounted. The way these ostree environments get assembled is
super messy, and I can't be sure I'm truly assembling it exactly as
the OS installer doe
Did you mount /proc ? What is the contents of /proc/self/mountinfo ?
On Tue, Aug 8, 2017, 06:35 Chris Murphy wrote:
> On Mon, Aug 7, 2017 at 9:09 AM, Vladimir 'phcoder' Serbinenko
> wrote:
> > Upstream doesn't use grub2 prefix. Please try with latest upstream and
> make
> > sure it's compiled w
On Mon, Aug 7, 2017 at 9:09 AM, Vladimir 'phcoder' Serbinenko
wrote:
> Upstream doesn't use grub2 prefix. Please try with latest upstream and make
> sure it's compiled with libdevmapper
Same result with current git as of today.
[chris@f26wnuc grub]$ ./configure --build=x86_64 --host=x86_64
--wi
Upstream doesn't use grub2 prefix. Please try with latest upstream and make
sure it's compiled with libdevmapper
On Mon, Aug 7, 2017, 08:57 Chris Murphy wrote:
> It's not the double bind mount. I've removed it by eliminating the -o
> subvol option and adjusted paths accordingly during assembly.
Chris Murphy schreef op 07-08-2017 8:56:
The non-working case looks like it starts failing after line 213,
openat /proc/self/mountinfo as if whatever it finds there is not at
all helpful.
The only similar thing I ever experienced is when my system inside a
chroot actually had a line filtering
It's not the double bind mount. I've removed it by eliminating the -o
subvol option and adjusted paths accordingly during assembly. But
grub2-probe still fails inside the chroot, even though it works on the
path I'm chrooting.
mount assembly
https://pastebin.com/LMSPeeiP
strace grub2-probe inside
