I know this isn't the place for this, but since I can't get my e-mail addresses
in order, can anyone help me with a small problem?
I am trying to boot my F20 security essentials, however due to the antiquated
Unetbootin I am using, I can only get my flash drive working with versions F19
and below. It keeps kicking me back to dracut, after which I go to bash and
kernel thrash for a while.
Any idea when the folks at Windows will catch up with us? Anyone have a
link to the F19 security essentials? My cyber security is important to me.
Please advise,
-Matt
in order, can anyone help me with a small problem?
I am trying to boot my F20 security essentials, however due to the antiquated
Unetbootin I am using, I can only get my flash drive working with versions F19
and below. It keeps kicking me back to dracut, after which I go to bash and
kernel thrash for a while.
Any idea when the folks at Windows will catch up with us? Anyone have a
link to the F19 security essentials? My cyber security is important to me.
Please advise,
-Matt
------
Powered by:
![Knoppix logo]()
Powered by:
On Sunday, March 9, 2014 1:00 AM, "Sandro "red" Mathys" <red@xxxxxxxxxxxxxxxxx> wrote:
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
> 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
_______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
