There's a request for the nvme-cli package to generate a unique name to use when connecting to NVMe-over-fabrics targets: https://bugzilla.redhat.com/show_bug.cgi?id=1633814 I'm wondering what the right approach is. For the various Atomic variants, ISTM it's not very nice for the package to generate files in /etc in a postinstall script. And it also seems like it might be surprising for a remove-and-reinstall of nvme-cli to generate a whole new NQN. Maybe /etc/machine-id could just be symlinked to /etc/nvme/hostnqn. Or maybe the user should be responsible for setting it up themselves. Or maybe installing nvme-cli could create an NQN but uninstalling could leave it there? Is there any guidance for how to handle this? Debian has "purge" for things like this, but I don't think Fedora has any equivalent. --Andy _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
