Hi Jonathan!
On 2/13/24 16:47, Jonathan Lebon wrote:
Ok, I thought there are Fedora Linux, Fedora Silverblue and Fedora CoreOS (maybe others :) ). Thanks!Has it got fixed during the time? Or is there a new technology which would do the trick for Silverblue and Fedora Linux alike?Just a note: I would say "for Silverblue and traditional systems alike" instead. Silverblue is part of Fedora Linux. :)
The common way to make "image-mode friendly" system state changes is to e.g. use a systemd service
Do you have an example of such systemd service? I could see that a shell script can be started by systemd unit to do the migration, but that would have to be run in %post scriptlet again AFAIK - unless you would require machine restart (and the service is run during reboot) or manual service start...
tmpfiles.d won't work for me, I have to make changes in /usr/bin
:( - looks like it designed for temp/volatile files.
:)or a tmpfiles.d dropin or to bake the migration into the application itself (all these would of course work across OSTree and non-OSTree based variants). Specifically for alternatives, see also https://github.com/fedora-sysv/chkconfig/issues/9 which calls for changing how it's implemented to be more compatible with image-based updates. Specifically for your issue though, it's not clear to me how much it's worth supporting this. Do they also have a way to prevent `sudo vi` from e.g. creating/modifying a systemd unit that can run arbitrary code?
Thank you in advance!Hope that helps! -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
-- Zdenek Dohnal Senior Software Engineer Red Hat, BRQ-TPBC
-- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
