| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
a real Python package.
Also updates the build and autotools stuff to work with the new structure
|
| |
|
|
|
|
| |
originally removed in 2008 by 7ad65d9e30fd21d8c0356dc998ea97c579a73d53.
|
|
|
|
|
|
|
| |
Now when we set NM_CONTROLLED parameter more carefully before
writing a device, this parameter introduced by patch 898a891c
is no longer needed. OTOH it doesn't break anything and may
become handy in the future.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Key patch of series. enableNetwork method is the root of all other
changes in the patchset. The method is used both for network enabling
in stage 2 triggered by need of network (repos, network storage, etc..)
and [Configure Network] button
What we select in stage 2 network UI is:
- device to be activated (only in case of network enabling), this is
controlled by ONBOOT ifcfg setting, note that devices actually
activated depend on editing in nm-c-e
- devices to be controlled by NM (and thus visible in nm-c-e),
this is set by NM_CONTROLLED ifcfg setting
A dialog for that is part of the patch, it needs some polishing.
bringUp method had to be split into write and waitForConnection
because in case of just config, without actually activating any
device in nm-c-e, we don't want to wait for activation.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove reading of some keys from NM via dbus, count on ifcfg
file contents (written by stage 1, ks, or nm-c-e). This should
also ensure support for ipv6 in stage2 using nm-c-e.
Remove available() method - it is useless - HWADDR is read from ifcfg
file, description is set in constructor, and Network class will be
kept up-to-date (e.g. after configuring with nm-c-e) by explicit
call to added update() method.
readIfcfgContets became useless, we can use (now ifcfg-backed)
NetworkDevices' method loadIfcfgFile instead.
Hunk starting with if len(available_devices) > 0: is a noop,
probably some leftover - removing.
|
|
|
|
|
|
|
|
|
| |
it has been virtually nonexistent for three years, see
9e1a444c46abcfc29c2e44ffd102fcc1eda6289e,
2d90bc12dcc682a7f0ff68e599cbb81a34a0b4a3 and
076c853f50c10203b45a552735f692b13a191bcb.
I found out about this when auditing the rawhide logs today.
|
|
|
|
|
|
| |
Text mode doesn't have the UI to create a new bootloader config, and we just
write the default in installation mode. Therefore we shouldn't allow it on
upgrades either.
|
|
|
|
|
| |
We want to have a sane default for the UTC checkbox so we need to
fixup hasWindows() rather then removing it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As pylint rightfully points out the hasWindows function from bootloader.py
is broken, it tries to access bootloaderInfo.dosFilesystems, but
bootloaderInfo refers to the bootloaderInfo class, not the module.
This does not cause any tracebacks because it tries to access
bootloaderInfo.dosFilesystems while iterating over bootloader.images, and
bootloader.images has not been set up at this time (so its an empty dict).
Thus hasWindows() will always return false, as there is no way to
determine hasWindows at this point during the installation (we have not yet
paritioned, so any exsting windows partitions may end up being removed),
this patches fixes things by simply removing the hasWindows function and
fixing up any callers of it.
|
| |
|
|
|
|
|
|
|
|
| |
So that the user gets a wait dialog and thus gets feedback that the
add iSCSI drive dialog he entered information into actually is doing
something.
Related: rhbz#571808
|
|
|
|
|
|
|
|
|
| |
The reason behind this is to make these functions available for using
them in rescue mode too.
Note to reviewers, the code of addDriveDialog() and friends has not
changed a single letter it was only moved to the new textw/add_drive_text.py
file (and some boilerplate was added on the top to make it into a new class).
|
|
|
|
|
|
| |
This is a preparation patch for seperating addDriveDialog() and its
helper functions out of partition_text.py, so that it can be used for
rescue mode too.
|
|
|
|
| |
You know, like anaconda's any other python module.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This patch also moves rootPassword into Users where it belongs and auth
into Security where it belongs.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This also removes the hack where upgrade can be True, False, or None in order
to test whether we've seen the upgrade screen or not. Instead, it introduces
a global value hack. I consider this the slightly cleaner approach.
|
| |
|
|
|
|
|
|
| |
anaconda.ksdata is only non-None if there's a kickstart file, just like
anaconda.isKickstart would be. Therefore, we don't need two variables
to test for the same condition.
|
|
|
|
|
| |
iutil.execWithRedirect() stopped doing anything with searchPath in 2006
when clumens committed d0dec24. Remove these silly vestigal bits.
|
|
|
|
|
|
|
|
|
|
|
| |
- Remove unnecessary semi colons in various places
- textw/upgrade_text.py: add a few missing imports
- Fix various missplaced doc strings
- Fix several double imports
- Fix AnacondaKSScript.run: Module 'os' has no 'exists' member
- users.py: Remove double definition of Users.setRootPassword
- yuminstall.py: correct typo reop -> repo
- yuminstall.py: _run: anaconda -> self.anaconda
|
|
|
|
|
| |
This will be handy for the filtering interface that does not at all exist
in text mode.
|
|
|
|
| |
Whole-disk formats are recognized but cannot be edited in any way.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This patch fixes 2 issues with the parsing of the optional portnr in
iscsi target IP's:
1) We don't want to include the : in the portno, so port = target[idx:]
should be port = target[idx+1:]
2) An IPV6 IP always includes the : character, so specifying the port
was mandatory with IPV6, this patch looks for "]:" inside the
string to determine if a port is present for IPV6 strings.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a cleanup for the po files. xgettext displays the following
messages for some Python files:
warning: 'msgid' format string with unnamed arguments cannot be properly localized:
The translator cannot reorder the arguments.
Please consider using a format string with named arguments,
and a mapping instead of a tuple for the arguments.
This patch modifies the reported format strings to use named parameters
per the warning message. We were already using these style format
strings in users.py and possibly other files. Basically when there is
more than one parameter in the format string, we should use a hash table
with named parameters.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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().
|
|
|
|
|
|
|
|
|
| |
There's now just two important settings in the Language module: instLang,
which is the language used while anaconda is running; and systemLang, which
is the language the installed system itself will use. These two can be
different mainly due to anaconda's text mode interface. The rest of anaconda
should only set and get these two. All the other support functions still
exist for grabbing timezone, font, etc.
|
|
|
|
|
|
|
|
|
|
| |
(#507084).
The value of NM_CONTROLLED has to change from no to yes to trigger device
activation by updating of ifcfg file, so we need to update just the files of
devices selected by user (instead of all devices). Otherwise, selection of
another device after previously failed selection doesn't work.
Also make writing out of ONBOOT in text mode consistent with gui.
|
| |
|
|
|
|
|
|
|
| |
I came accross this by the way when working on something different. It adds
what was done with commit 2e8dfb72c0c296f24f99512e8fb00c377417a60a (#504216)
for GUI to text ui. Althoug BZ suggests that it was already present in text ui,
looking into code doesn't (I have no rawhide image to test if it is actually true).
|
|
|
|
|
| |
We have lots of strings that we display to users which are unclear or
contain poor usage and grammar. That's bad.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch adds support for using FCoE during the installation. This patch
merely lays the initial ground work, there is more work todo:
- The system will not boot without manual help after the install, as
dracut / mkinitrd do not support FCoE yet
- If FCoE is not used for / but for example for /srv, then information
about the nic used for FCoE needs to be written in a to be defined
config file in the system, and rc.sysinit needs to be thought to read
this file and bring up FCoE SAN's / Fabrics not used for /
- kickstart support for FCoE still needs to be done
|
|
|
|
|
| |
When manually adding an iscsi disk it will not show up in the where to
install the bootloader dropdown, this patch fixes this.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(#503310) (#503681)
Default clearPartType to None so that all devices are discovered during storage
initialization step, and UI parttype can be set to its default "Replace existing
linux system". Also set clearPartType appropriately when going back from partition dialog
so that all devices are discovered during storage reset.
There is one case that can't be resolved this way: clearpart --all or --linux
is set in ks and "Create custom layout" is selected in parttype UI step. Because of ks
setting, storage initialization doesn't discover devices (RAID, LVM) on
partitions that are to be cleared and therefore they are not present in custom
partition dialog. This can be workarounded by going back and than again to
custom partitioning dialog. I think we should grey-out type of partitioning
combo set to value from ks clearpart command.
|
| |
|