* Andrew Lutomirski: > 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 How many bits can the NQN have? Is it long enough that random generation of IDs is feasible? > 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. You could have a separate nvme-filesystem package which generates and owns the file (via %ghost). Thanks, Florian _______________________________________________ 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
