No once care about this for more than 2 years, I'm hereby closing this issue.

So we're carrying this issue for more than a year. Any opinions what to do about
this one?

* Christian Hofstaedtler wrote in grml's BTS on 20101214 / 08:26:

> Doesn't this break persistence for _all_ existing USB sticks handed
> out at various conferences?

I'd say so, yes. That's why I'd prefer to not include the feature in
grml-live but instead give the user a choice using grml2usb.

regards,
-mika-

Doesn't this break persistence for _all_ existing USB sticks handed
out at various conferences?

%flavour? On the other hand it may break existing installations as another directory is used and can not easily disabled completly.


My change for grml2usb would just be to add persistent-subtext per default to the bootoptions and provide a feature to remove it.

Ulrich



"Michael Prokop" <bts@bts.grml.org> schrieb:

>
>Michael Prokop <mika@grml.org> added the comment:
>
>* Ulrich Dangel wrote in grml's BTS on 20101214 / 02:15:
>
>> Hm, just implemented it in grmlu2b but why not add it to the the
>isolinux/grub 
>> template in grml-live? Then we don't have to change any code at all.
>
>What values should persistent-subtext=... receive?
>Is there a consistent way without introducing too much headache?
>
>regards,
>-mika-
>
>_____________________________________
>GRML issue tracker <bts@bts.grml.org>
><http://bts.grml.org/grml/issue910>
>_____________________________________

* Ulrich Dangel wrote in grml's BTS on 20101214 / 02:15:

> Hm, just implemented it in grmlu2b but why not add it to the the isolinux/grub 
> template in grml-live? Then we don't have to change any code at all.

What values should persistent-subtext=... receive?
Is there a consistent way without introducing too much headache?

regards,
-mika-

Hm, just implemented it in grmlu2b but why not add it to the the isolinux/grub 
template in grml-live? Then we don't have to change any code at all.

Some way of automatically doing the right thing could be nice, yes.
A hypothetical --no-shared-persistence flag could enable
persistent-subtext + set it to the flavour name...

This coul be already done manually...if really wanted/needed we can add it per default with sane defaults (like flavourname)



"Michael Prokop" <bts@bts.grml.org> schrieb:

>
>Michael Prokop <mika@grml.org> added the comment:
>
>Uli + Christian: do think it makes sense to implement support for
>persistent-
>subtext=... in grml2usb? (This bootoption allows assignment of
>different 
>persistency partitions for different live systems, it's also available
>within 
>live-boot.)
>
>----------
>nosy: +ch, mru
>status: unread -> needs-progress
>
>_____________________________________
>GRML issue tracker <bts@bts.grml.org>
><http://bts.grml.org/grml/issue910>
>_____________________________________

Uli + Christian: do think it makes sense to implement support for persistent-
subtext=... in grml2usb? (This bootoption allows assignment of different 
persistency partitions for different live systems, it's also available within 
live-boot.)

The persistent-subtext=... bootoption supported by live-initramfs provides 
assignment of different persistency partitions for different live systems, 
which would be nice to have for 32bit vs. 64bit, full vs. medium vs. small, 
different versions of it, etc. - see http://bugs.debian.org/cgi-bin/
bugreport.cgi?bug=536728

We should discuss whether automatically setting persistent-subtext=... would be 
an option for grml2usb. Definitely needs further discussion, just submitting it 
as bugreport so we don't forget it.