On Fri, Mar 7, 2014 at 9:22 PM, Colin Walters <walters@xxxxxxxxxx> wrote: > On Fri, Mar 7, 2014 at 4:42 AM, Sandro red Mathys <red@xxxxxxxxxxxxxxxxx> > wrote: > > Sorry, missing something here. What would I need that code for? I was > actually thinking about writing something like: > > > Yep, that code is just the JS implementation of the shell script you posted. So, two questions: - How does one activate the deployed product if extlinux is the active bootloader? The website has only instructions for GRUB (bls_import, etc). - How does one get rid of the 'traditional Fedora' once the product is active? ...figure both won't be necessary anymore once we can use Anaconda to install a product directly, but in the meantime it would be helpful for some testing and more generally help my understanding. :) Thanks, Sandro > Hm, does Anaconda write the bootloader config before or after executing > %post scripts? Either the above could still work or not, I guess. > > > Now that I dove more into Anaconda code last night, there is an important > detail: we need to pass the kernel arguments like root= to OSTree. That's > the "--karg" option to "ostree admin deploy". > > (We could edit it after but that'd be ugly) > > > _______________________________________________ > cloud mailing list > cloud@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/cloud > Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct > _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
