| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Since all notebook pages share the same store, a device being visible on one
page means it'll be counted as being visible on all pages. That means
flipping to the correct initial page doesn't work. Instead, we need to count
using the visible methods on callback objects to only count the devices that
are members of each page as visible.
|
|
|
|
| |
Previous version had a missing break. Put the break in.
|
| |
|
|
|
|
|
|
| |
This makes the way they are displayed in the filter UI and in
cleardisks_gui.py consistent, and this makes us not show dmraid device
node names for sets which we will later activate with mdraid.
|
|
|
|
|
| |
Now that MD BIOS RAID arrays have their own type, there is no longer a
need for the biosraid property.
|
|
|
|
|
| |
This stops us from backtracing on for example usb cardreaders without
a card in them.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
If we've got an mpath device in FilterWindow, it should be added to the
selection, not the constituent devices for each path.
|
|
|
|
|
| |
Add udev_device_get_multipath_name() to find the name of a consituent's
device, and also reorganize a little. Also use this in FilterWindow()
|
|
|
|
|
| |
StorageDevice and all its heirs have device.model so it can be
subclassed; use it.
|
|
|
|
|
|
| |
We used to be always showing page 0, but it's possible there are no basic
devices in the system. The result is you staring at a blank page. Instead,
we should show whichever page has something on it to see.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I've been running pylint on a subset of anaconda:
booty storage iw/*.py platform.py
And it has found various errors this commit fixes:
- Restore line accidently dropped from iscsi.py
- execWithPulseProgress should propagate the return value of
execWithCallback
- storage.formats.fs:535 (FS.doCheck): self.intf should be just intf
- storage.formats.fs: add missing "import sys" (for sys.exit)
- advanced_config.py add missing import for NetworkConfigurator
- lvm_dialog_gui.py: VolumeGroupEditor.editLogicalVolume dev was renamed to d
- partition_gui.py: remove an unneeded semicolon
- partition_gui.py: PartitionWindow.createCB rc should be dialog_rc
- storage.FSSet.write: put docstring in the proper place
- platform.Sparc.minimumSector: sectors should be sector
|
| |
|
| |
|
|
|
|
|
| |
If ignoredisk --disks= was given, of course there's not going to be anything
in exclusiveDisks. So don't rely solely on that.
|
|
|
|
|
|
|
|
|
|
| |
This fixes a couple problems:
(1) If you go past the filter UI and then come back, your original selections
will now be preserved.
(2) If you do an interactive kickstart install with the ignoredisk command,
those selections will also be preserved.
|
|
|
|
|
|
|
| |
The only other place where exclusiveDisks are set is in ks and
in this case filter UI is skipped so it seems we can just assign
value to exclusiveDisks instead of extending it (which causes
the problem when going back to filtering UI).
|
|
|
|
| |
_genStore expects disk objects, not disk names.
|
|
|
|
|
| |
Corrects translation between device name and device path. Changes rendering
style of toggle button in list from check to radio (which is how it behaves).
|
|
|
|
|
| |
Seeing a count of more devices than you can find in the UI is confusing, so
only include them in the count if we're doing the advanced UI.
|
| |
|
|
|
|
|
|
|
| |
Having it be private was based upon the old assumption that you couldn't add
devices during installation. Of course, that's incorrect for things like
iSCSI and FCOE. So now that we need to update the size label when the
Add Advanced button is clicked, it needs to be renamed.
|
|
|
|
|
| |
Since the basic screen doesn't even have tabs to display the kinds of devices
that can be added with this button, it doesn't make any sense to show it.
|
|
|
|
|
|
| |
First, a gtk.ComboBoxEntry doesn't have a get_text() method. It has a
child that has a get_text() method. Second, filter-as-you-type works more
like you would expect if the filters use "contains" instead of "is".
|
|
|
|
|
|
| |
Most Fedora users don't need to see the advanced filtering UI with all its
multipath tabs and advanced storage buttons and search interfaces. So,
provide an introductory screen that allows skipping all that stuff.
|
|
|
|
|
|
| |
This UI is the screen that allows the user to select which devices will be
wiped during installation and which should just be mounted. It also allows
selecting which device the bootloader should be installed to.
|
|
|
|
|
|
|
|
|
| |
This brings back the old behavior of having a dialog that can prompt for
unusual storage devices that require manual intervention, like FCOE and iSCSI.
After the dialog is run, we have to put and new devices into the UI. However,
udev isn't going to provide just a list of newly appeared devices so we have to
maintain a list of what was around previously, and compare the current device
list to that. This promises to be slow but there's not a better option.
|
|
|
|
|
|
|
|
|
|
| |
This UI allows the user to select which devices they would like to include
in the rest of the installation process, sorted out by their types. All
devices not checked will never again be referenced by anaconda, though we
may see their udev information in the logs from time to time. This UI
supports two different ways of looking at things: the simple UI for
regular Fedora users with basic devices, and the complex UI with many tabs
and filtering options.
|
|
|
|
|
| |
Add some text at the top, rework the rest of the text to be more descriptive,
and bold/italicize other text to make it stand out more.
|
|
|
|
|
|
|
| |
This revised screen is part of the simple flow for the new storage
filtering UI. It only offers you to pick the kind of install you want
to do, check to review, and check to encrypt. Everything else will go
on another screen later.
|
| |
|
| |
|
|
|
|
| |
We don't want to show biosraid, multipath, &c disks in the GUI.
|
|
|
|
|
|
|
|
| |
When using the entire disk, whole-disk formats are replaced with a
new disklabel. When replacing existing linux installations, linux-
native whole-disk formats are replaced with a new disklabel. Disks
containing whole-disk formatting are not offered as bootloader
installation targets.
|
|
|
|
| |
Whole-disk formats are recognized but cannot be edited in any way.
|
|
|
|
|
|
| |
This is optional. To enable it, add a boolean column as the last column
of the TreeStore you pass in and specify 'sensitivity=True' when
instantiating WideCheckBox or CheckBox.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
In stage 2, the nfs options given in repo= boot parameter were malparsed, in UI
they were ignored.
Note that now the options can get to stage 2 only via method=/repo= boot
parameter. Ks nfs option --opts works only when its url specifies stage2 (i.e.
ends with images/install.img). In cases when method (--repo parameter for
anaconda python script) is inferred from stage2, nfs options of stage2
"nfs:..." url aren't passed to stage 2.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This makes sure the keyboard both defaults to the right setting and is
correctly set in /etc/sysconfig/keyboard post-install.
|
| |
|
|
|
|
|
| |
Also change the no initator set error dialog title from "Error with data"
to just "Error" to be consistent with the other error dialog titles.
|
|
|
|
|
|
|
|
|
| |
Make MDRaidArrayDevice.__init__ raise a value exception when creating
a new (so non existing) raid set and there are not enough members for
the requested raid level.
And catch this value exception in the GUI raid dialog and kickstart raid
commands.
|