Hi John,
On 6/30/20 12:58 AM, John M. Harris Jr wrote:
On Monday, June 29, 2020 1:04:48 PM MST Ben Cotton wrote:
https://fedoraproject.org/wiki/Changes/RemoveDeviceMapperMultipathFromWorkst
ationLiveCD
== Summary ==
The Fedora workstation livecd is the default Fedora variant getfedora.org
advices people to download.
As such most Fedora workstation installs will be done from the livecd. This
means that any package which is part of the livecd will be part of the
default install for most users.
device-mapper-multipath is 1 of only 2 packages in the default install
which still Requires the long obsoleted systemd-udev-settle.service, which
waits for all device-detection to be done + some extra waiting just to be
sure. This significantly slows down booting on various systems.
Multipath support is only necessary for installations in data-centers or
other enterprise setups, as such having device-mapper-multipath on the
livecd is not really necessary. For installations which do actually need
this device-mapper-multipath the server installation iso can be used and
this is a better fit for such installations.
== Owner ==
* Name: [[User:jwrdegoede| Hans de Goede]]
* Email: hdegoede@xxxxxxxxxx
== Detailed Description ==
device-mapper-multipath is 1 of only 2 packages in the default install
which still Requires the long obsoleted systemd-udev-settle.service. The
other package is dmraid see [[Changes/DisableDmraidOnFirstRun|Disable
dmraid.service on first run]].
Multipath support is only necessary for installations in data-centers or
other enterprise setups, as such having device-mapper-multipath on the
livecd is not really necessary. For installations which do actually need
this device-mapper-multipath the server installation iso can be used and
this is a better fit for such installations.
Actually, multipath is used outside of datacenters and enterprise setups.
Can you give use-case scenarios where multipath would be used and the
workstation livecd would be the preferred installation media (prefered
over say the server netboot iso) ?
A better solution would be to use Anaconda to include it when configured, and
leave it out otherwise..
As mentioned in the Change page anaconda already keeps track of whether
it needs device-mapper-multipath and will bring it in when anaconda is
in control over which packages to install. But that only happens with
netboot installations.
With livecd installs the livecd rootfs simply gets rsync-ed over, so
anything which is in the livecd will also end up on the real system.
There is a post-install configuration phase, so I guess we could
disable things which are only brought in when necessary with netboot
installs in the livecd post-install configuration phase instead of
dropping them from the livecd.
That same solution would also work for dmraid, so that would be a more
generic solution in general and as such might be better. What do
others think?
Regards,
Hans
_______________________________________________
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
