Re: logging mount assembly and bootloader install, chroot missing?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, 2017-09-09 at 18:36 -0700, Adam Williamson wrote:
> On Tue, 2017-08-08 at 12:22 -0600, Chris Murphy wrote:
> > The program.log shows mount commands for assembly, followed by
> > installation itself copying files to a path prefix /mnt/sysimage,
> > and
> > then bootloader setup. Isn't there a chroot happening before the
> > bootloader setup? It's not in the log so I'm having some difficulty
> > exactly replicating an installation environment while
> > troubleshooting
> > this bug:
> > 
> > So the questions are:
> > Is there a chroot?
> > Is there a way to discover the command being used?
> > And if there is a chroot, is there a way to log this command in the
> > future?
> > 
> > 
> > https://bugzilla.redhat.com/show_bug.cgi?id=1289752
> 
> Use the source, Luke:
> 
> https://github.com/rhinstaller/anaconda/blob/master/pyanaconda/bootlo
> ader.py
> 
> and then search for 'root='. You'll find that most of the bootloader
> installation-related commands run via iutil.execWithRedirect, with
> root
> set to iutil.getSysroot() . Of course, you can look in iutil.py to
> see
> what these do. If you *do* look there, you'll see that indeed the
> relevant functions don't *currently* log the root argument. I think a
> PR to add this wouldn't be unreasonable.

I like this idea so I've created PR for that:
https://github.com/rhinstaller/anaconda/pull/1191

Jirka

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list



[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux