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

["Wise, Philip" <philip wise here com>]

Here is our libostree + Yocto integration:

 

https://github.com/advancedtelematic/meta-updater

 

And some getting started docs:

 

https://docs.atsgarage.com/quickstarts/raspberry-pi.html

 

Best Regards

 

Phil

 

From: ostree-list <ostree-list-bounces gnome org> on behalf of Gatis Paeglis <Gatis Paeglis qt io>
Date: Tuesday, 30. January 2018 at 22:48
To: Colin Walters <walters verbum org>, "ostree-list gnome org" <ostree-list gnome org>
Subject: Re: trying to understand how the /boot/loader symlink is supposed to work.

 

> Maybe for the people who are making libostree-based OSes - if you have
publicly available systems, post here so we can gather a list?  That way
we can all use each other more easily as references.

 

Here is one reference system, ostree + yocto-based linux images:

 

Doc: http://doc-snapshots.qt.io/qtota/index.html

Source code: https://github.com/qt/qtotaupdate

 

---

From: ostree-list <ostree-list-bounces gnome org> on behalf of Colin Walters <walters verbum org>
Sent: Tuesday, January 30, 2018 8:41:07 PM
To: ostree-list gnome org
Subject: Re: trying to understand how the /boot/loader symlink is supposed to work.

 

On Tue, Jan 30, 2018, at 10:05 AM, Davis Roman 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.

I am not sure if there is actually a public (freely available) "reference OS"
using libostree + uboot.  For Fedora Atomic on aarch64 I think we're doing u-boot -> grub2,
but I haven't tried it myself yet.

Maybe for the people who are making libostree-based OSes - if you have
publicly available systems, post here so we can gather a list?  That way
we can all use each other more easily as references.

> 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)

libostree is currently unaware of this.  We just merged devicetree support:
https://github.com/ostreedev/ostree/pull/1411

I think .itb support would need to touch all of those code paths.  Mind
filing an issue?  Do you have the ability+time to implement it?  If not,
is it viable to drop down to split kernel/initramfs/dt?

_______________________________________________
ostree-list mailing list
ostree-list gnome org
https://mail.gnome.org/mailman/listinfo/ostree-list

 

 

ATS Advanced Telematic Systems was acquired by HERE Technologies.

 

 

Philip Wise

Senior Software Engineer Lead

M: +49 302 00073525

 

HERE Technologies

Kantstraße 162, 10623 Berlin

52° 30' 18" N 13° 19' 56" E

 

               

 

HERE Deutschland GmbH, Place of Business: Invalidenstraße 116, 10115 Berlin, Germany – Commercial Register: Amtsgericht Charlottenburg, HRB 106443B - USt-IdNr.: DE 812 845 193 - Managing Directors: Michael Bültmann, Robertus A.J. Houben