<div dir="ltr">nevermind, I somehow missed the part where you were trying to say you wanted to do this *without* having a separate gadget snap :)</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 6, 2015 at 12:56 PM, Paul Larson <span dir="ltr"><<a href="mailto:paul.larson@canonical.com" target="_blank">paul.larson@canonical.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Couldn't we just put it in uEnv.txt and have uboot read it from there like we do with uenvcmd and bootpart?</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 6, 2015 at 10:56 AM, Oliver Grawert <span dir="ltr"><<a href="mailto:ogra@ubuntu.com" target="_blank">ogra@ubuntu.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">hi,<br>
<br>
we are currently facing a problem of having hardcoded console= options<br>
on the kernel commandline ...<br>
<br>
(grub images currently default to: "console=ttyS0 console=tty0" (the<br>
first option applies to kernel while the second sets the output console<br>
for userspace) while u-boot images default to whatever serial console<br>
device an embedded board uses)<br>
<br>
to change your console= option you theoretically would have to build<br>
your own gadget snap just for that one option modified ...<br>
... or we would have one gadget snap per possible option in the store so<br>
the user can pick the "amd64-serial-console.snap" for his serial snappy<br>
project ... this would indeed make us end up with tons of identical<br>
snaps that only have a single option changed ...<br>
<br>
i would like us to find a way how we can set the console option<br>
dynamically at image creation time for this case ...<br>
technically grub based images do not need a console= option set by<br>
default (they will resort to tty0 which is fine for VM as well as for<br>
real hardware) but you might want to use some x86 based embedded board<br>
that only offers serial ports for debugging or logging in ... u-boot<br>
images should default to whatever the HW requires. but while i do not<br>
expect us to use a beaglebone for any graphical images (since it is<br>
simply not designed for this), i expect that RPi2 users will likely want<br>
to be able to use graphical consoles (and a boot splash etc) in case<br>
they run some desktop or some media playback tool on their snappy<br>
install.<br>
<br>
while we technically could use "snappy config" to adjust this, this is<br>
practically only possible after you booted ... so you would have to boot<br>
blind to an invisible console to change the default setting ...<br>
<br>
the only sane option i see is to add some option to ubuntu-device-flash<br>
so this value can be modified at image creation time before the first<br>
boot ... but this seems to be unwanted either (u-d-f already has a<br>
plethora of options and slowly gets crowded with them)<br>
<br>
since i don't see an easy path out of this dilemma, i was wondering if<br>
anyone else has any good idea what we can do here ...<br>
<br>
ciao<br>
oli<br>
<span><font color="#888888"><br>
<br>
<br>
--<br>
snappy-devel mailing list<br>
<a href="mailto:snappy-devel@lists.ubuntu.com" target="_blank">snappy-devel@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/snappy-devel" rel="noreferrer" target="_blank">https://lists.ubuntu.com/mailman/listinfo/snappy-devel</a><br>
</font></span></blockquote></div><br></div>
</div></div></blockquote></div><br></div>