Okay, thank you for your look into this.
I assumed that it is 'just' due to the implementation that was chosen.
But I think it's not intuitive,
and renders the usage of the device list to not always usable - for cases the
sequence is relevant.
There is fortunately a workaround, that is to (be on the safe side and to)
enable the devices one-by-one, each with it's own chzdev call.
That's okay if just a few devices need to be enabled,
but if the amount grows, it becomes more annoying (and will take longer).
Thanks for considering this as potential future enhancement.
I'll update the status of this LP bug to "Opinion" and the importance to
"Wishlist" for now,
and will add an entry to the Ubuntu on s390x FAQs (and might need to add a
'Notice' to the Ubuntu Server docs ...)
** Changed in: ubuntu-z-systems
Status: In Progress => Opinion
** Changed in: ubuntu-z-systems
Importance: High => Wishlist
** Changed in: s390-tools (Ubuntu)
Status: Confirmed => Opinion
** Changed in: s390-tools (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: ubuntu-z-systems
Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2097613
Title:
(auto-)Install issue with 25.04 on s390x using DASD disks
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/2097613/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
