After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 722845 - Handle interacting with current distribution syslinux/extlinux configuration
Handle interacting with current distribution syslinux/extlinux configuration
Status: RESOLVED WONTFIX
Product: ostree
Classification: Infrastructure
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: OSTree maintainer(s)
OSTree maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-01-23 16:51 UTC by Colin Walters
Modified: 2018-08-17 18:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Colin Walters 2014-01-23 16:51:46 UTC 
OSTree demands basically that /boot/loader be a swapped symbolic link to /boot/loader.[0,1].  It should work well enough for programs (e.g. distribution kernel packages %post) to write files into /boot/loader/ without being aware that it's a symlink.

But the question is - should OSTree, when first used, force it to become swapped?  It feels slightly dangerous to me, but maybe it's not.

This also interacts badly with bootloaders that don't implement BLS (like syslinux), so OSTree writes out the legacy config file for them.

Should we attempt to migrate even these?  I'm leaning a bit towards no.
Comment 1 André Klapper 2018-08-17 18:59:48 UTC 
OSTree has moved to Github a while ago.
Furthermore, GNOME Bugzilla will be shut down and replaced by gitlab.gnome.org.

If the problem reported in this Bugzilla ticket is still valid, please report it to https://github.com/ostreedev/ostree/issues instead. Thank you!

Closing this report as WONTFIX as part of Bugzilla Housekeeping.