Re: trying to understand how the /boot/loader symlink is supposed to work.

[Dan Nicholson <nicholson endlessm com>]

On Tue, Jan 30, 2018 at 3:30 PM, Davis Roman <davis roman84 gmail com> wrote:
> Hi Dan,
>
> Thank you for replying. You response was helpful.
>
> Out of curiosity, what is in your loader.0 and loader.1 folders?
>
> Mine are currently empty which is what I'm currently trying to verify if
> this is normal or not.

Here's what /boot looks like on one of our ARM images:

/mnt/boot/
├── loader -> loader.1
├── loader.1
│   ├── entries
│   │   └── ostree-eos-0.conf
│   └── uEnv.txt
├── ostree
│   └── eos-95d3993aecf69103b801e1f3c344fedcaac46fbc00e6839d6bae2b414099d277
│       ├── initramfs-3.10-trunk-meson8b
│       └── vmlinuz-3.10-trunk-meson8b
└── uEnv.txt -> loader/uEnv.txt

The uEnv.txt file looks like this:

kernel_image=/ostree/eos-95d3993aecf69103b801e1f3c344fedcaac46fbc00e6839d6bae2b414099d277/vmlinuz-3.10-trunk-meson8b
ramdisk_image=/ostree/eos-95d3993aecf69103b801e1f3c344fedcaac46fbc00e6839d6bae2b414099d277/initramfs-3.10-trunk-meson8b
bootargs=rw splash plymouth.ignore-serial-consoles quiet loglevel=2
ostree=/ostree/boot.1/eos/95d3993aecf69103b801e1f3c344fedcaac46fbc00e6839d6bae2b414099d277/0

Whereas the BLS entries file looks like this:

initrd 
/ostree/eos-95d3993aecf69103b801e1f3c344fedcaac46fbc00e6839d6bae2b414099d277/initramfs-3.10-trunk-meson8b
options rw splash plymouth.ignore-serial-consoles quiet loglevel=2
ostree=/ostree/boot.1/eos/95d3993aecf69103b801e1f3c344fedcaac46fbc00e6839d6bae2b414099d277/0
title Endless 3.3.10 (ostree:0)
linux /ostree/eos-95d3993aecf69103b801e1f3c344fedcaac46fbc00e6839d6bae2b414099d277/vmlinuz-3.10-trunk-meson8b
version 1

I'd try to do the uEnv.txt prep like I pointed out. When I read the
code, it does look like it bails out early if it doesn't find
loader/uEnv.txt, so I suspect that you're not getting the rest of the
boot configuration after that error.