In fact the OS is just a minimal rescue OS. On a second partition we run our main OS, which is ‘properly’ installed. So, I’m afraid using a ‘proper’ file system wouldn’t fit our use case. We run the rescue OS as RAMdisk to be able to self-update it without having to worry about modifying a mounted file system.
Norman Mit freundlichen Grüßen / Best regards Norman Stetter SW ENWICKLUNG EMBEDDED SYSTEMS Garz & Fricke GmbH 21079 Hamburg Direct: +49 40 791899 - 477 Fax: +49 40 791899 - 39 norman.stet...@garz-fricke.com www.garz-fricke.com<http://www.garz-fricke.com/> WE MAKE IT YOURS! [cid:image001.jpg@01D51228.BD16AF70] Sitz der Gesellschaft: D-21079 Hamburg Registergericht: Amtsgericht Hamburg, HRB 60514 Geschäftsführer: Matthias Fricke, Manfred Garz, Marc-Michael Braun Von: Burton, Ross [mailto:ross.bur...@intel.com] Gesendet: Friday, May 24, 2019 11:45 AM An: Norman Stetter <norman.stet...@garz-fricke.com> Cc: yocto@yoctoproject.org Betreff: Re: [yocto] Building single package as image, respecting dependencies On Fri, 24 May 2019 at 07:30, Norman Stetter <norman.stet...@garz-fricke.com<mailto:norman.stet...@garz-fricke.com>> wrote: For the OS image I use cpio.gz as file system. It gets booted as a RAMdisk. Sorry, forgot to mention that. Would you consider switching to a proper filesystem? The peril of using a cpio.gz is that every file you add slows the boot down: using a proper filesystem solves this. Ross
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
