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

[Davis Roman <davis roman84 gmail com>]

I had checked out my ostree repository into a directory on my host directory however I probably should have shown what it looks like on my target instead:

root@target:/boot# tree

.

|-- loader -> loader.0

|-- loader.0

|   |-- entries

|   |   |-- ostree-poky-0.conf

|   |   `-- ostree-poky-1.conf

|   `-- uEnv.txt

`-- ostree

    `-- poky-0f4de6813eb21e874a48b6a880e77c325b7f269a74b7a195045c8031234e6a08

        |-- boot.itb

        |-- loader -> boot/loader.0

        |-- loader.0

        `-- loader.1

7 directories, 5 files

root@target:/boot# 

On Tue, Jan 30, 2018 at 10:05 AM, Davis Roman <davis roman84 gmail com> wrote:

Hello,

We've ported ostree to run on our embedded device and I'm trying to make sure that the /ostree/boot directory jives with how the documentation states it should be laid out.

On our target, there doesn't appear to be anything in the 'loader.0' and 'loader.1' directories ( despite the documentation stating that there should be files in these folders), instead the boot.itb file simply resides in /boot

( FYI, we've enabled u-boot fit and so the kernel, devicetree and initrd are contained in the boot.itb blob)

Does anyone see any issue with this file structure? Just wanted to make sure there's nothing wrong in our implementation.

root@XPS-15-9560:~/ostree-test/target-generic-ota/boot# tree

.

├── boot.itb-330fec4aae217fd2d588307bac836388fd7d3f68cf522cef114592bef81315aa

├── loader -> boot/loader.0

├── loader.0

└── loader.1

2 directories, 2 files

root@XPS-15-9560:~/ostree-test/target-generic-ota/boot#

Thank you,

Davis