On Fri, 2018-10-12 at 15:53 -0700, Adam Williamson wrote:
On Fri, 2018-10-12 at 15:44 -0600, Chris Murphy wrote:
> On Fri, Oct 12, 2018 at 4:30 AM, Marek Marczykowski-Górecki
> <marmarek(a)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
anaconda uses dnf's python interface, it does not *run* 'dnf'.
Yep, but the DNF Python code still actually runs in a Python subprocess.
This is needed as aparently something during the package installation transaction
- most likely RPM - does a chroot. If the DNF code did run directly in Anaconda process,
Anaconda would get chrooted as well and BAD THINGS (TM) would happen.
Bad things ranging from missing icons to GTK crashing due to files is uses suddenly
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines