| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
This is required so the source layout and package layout have a similar enough
structure to make our test setup work. Without this move, you can't run
"make check" or checkbot without getting error messages about no such module
pyanaconda.booty.
|
| |
|
|
| |
It really is just another pyanaconda subpackage.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Note this patch is also intended for rhel6-branch, where it fixes #531722.
I'll amend the commit mesg for rhel6-branch after cherry picking to
show the right bz nr.
|
| | |
|
| |
|
|
|
|
|
| |
...well, it can mostly be removed. The s390 and x86 classes still do some
complicated things that end up with a justConfig test, so it has to stay
in those files. However, their write() methods no longer need to accept
that parameter.
|
| |
|
|
|
|
|
| |
This is yet another way of running anaconda that gets extremely limited use,
no testing, and no consideration during development to making sure it still
works. Again, we need to stop pretending and get rid of modes that we don't
support.
|
| |
|
|
|
|
|
|
|
| |
If the bootLoaderInfo is old-style class, setting of its property drivelist
doesn't work, instead the property is overwritten with attribute and therefore
for example any following calls of updateDriveList have no effect.
AFAIK it doesn't cause problems anywhere at the moment, but I think it should
be fixed it in master.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add the following methods and properties to class Storage which map
through to FSSet methods, modify existing calls to use the method on
class Storage:
turnOnSwap()
mountFilesystems()
umountFilesystems()
parseFSTab()
mkDevRoot()
createSwapFile()
fsFreeSpace()
mtab
mountpoints
migratableDevices
rootDevice
Callers no longer need to pass the Anaconda object to the FSSet methods
directly. The method on Storage takes care of that.
The mtab() method on FSSet is exposed as a property on Storage. The
same is true for fsFreeSpace().
|
| |
|
|
|
|
|
|
| |
dracut using kernel come with a prebuild initrd-generic-<version> instead
of initrd-<version>, so if we fail to find /boot/initrd-<version>.img, check
for /boot/initrd-generic-<version>.img instead. I've done things this way
so that if we ever need to generate system specific (so non generic) initrd's
for some reason the code will stay working.
|
| |
|
|
|
|
|
|
|
| |
Currently we are passing storage and network to booty's __init__, for
writing the necessary kernel cmdline parameters for dracut for international
consoles / keyboards booty will also need access to keyboard and language,
instead of passing these all in seperately just pass InstalltData to booty's
__init__. This is a preparation patch for writing out the dracut kernel
cmdline commands for i18n support.
|
| |
|
|
|
|
|
|
|
| |
Add a dracutSetupString method to network.py, this can be used to
ask the Network class to get a dracut setup string to setup the interface
needed for a connection to a certain host.
This patch also adds code to booty to use this to get kernel cmdline dracut
setup commands for any NIC's needed to connect to devices needed for /
|
| |
|
|
|
| |
Switch to using iutil.isFoo() methods rather than checking the
value of rhpl.getArch()
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
iutil uses subprocess.Popen and passes in the argv as a list, which causes
Popen to use the first entry of the list as the executable, and the rest of
the entires as arguments to that executable. This is different from how
rhpl did things in which the first argument of the arglist had to be the
executable itself.
Also iutil expects argv to be a real list not a tuple.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
booty was using its own code to find out wether to pass in
UUID=.... or /dev/.... as root= option, leading to inconsistencies
between fstab (/dev/mapper/Volgroup-lv_root) and grub.conf (UUID=...)
Harmless, but confusing. This patch fixes this by removing the no longer
needed getRootDevName method from booty and instead using device.fstabSpec
|
| |
|
|
|
|
| |
Booty was expecting the xxxxxxx part of /dev/xxxxxx paths instead of
new storage device names, this patch fixes this, making booty work on
dmraid with the new storage code.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Also, this gets rid of the goofy self.noKernelsWarn method which doesn't
serve any useful purpose now that booty's part of anaconda.
|
| | |
|
| |
|
|
|
|
| |
We could pass storage around to all the various functions that will need it,
but that's a big mess. It's far easier to just set this when we create the
bootloaderInfo class and never worry about it again.
|
| | |
|
| | |
|
| |
|
