On Fri, Oct 12, 2018 at 3:44 PM, Chris Murphy <li...@colorremedies.com> wrote: > On Fri, Oct 12, 2018 at 4:30 AM, Marek Marczykowski-Górecki > <marma...@invisiblethingslab.com> wrote: >> On Thu, Oct 11, 2018 at 09:24:08PM -0600, Chris Murphy wrote: > >>> I'm pretty sure the original reason was the default live install use >>> dd to block copy the root file system into the fedora-root LV, and >>> then resized the LV and ext4 file system. >> >> How is it done now? > > On Live media installs, anaconda does: > > rsync -pogAXtlHrDx --exclude /dev/ --exclude /proc/ --exclude /sys/ > --exclude /run/ --exclude /boot/*rescue* --exclude /etc/machine-id > /mnt/install/source/ /mnt/sysimage > > On DVD and netinstalls, I'm guessing based on packaging.log that it's > a dnf+rpm installation even though I never see a dnf or rpm process in > either top or ps. In any case, the rpm packages are directly on the > iso9660 file system, not baked into the
One other thing that really hogs system resources for some reason, is one of the loopback mount devices, I think loop1 which is root.img, hogs nearly 100% CPU for the duration of the installation for LiveOS media. I don't know why, but it might be worth benchmarking nbd based mounts for comparison. The installation turns my computers into hair dryers. The installation process bottleneck should be reading the compressed root image, not CPU. -- Chris Murphy _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
