| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
|
|
|
|
| |
This will be handy for the filtering interface that does not at all exist
in text mode.
|
|
|
|
|
| |
Now you've got lots of room for lots of kernels and lots of gigantic initrds
and probably a couple install.imgs too.
|
|
|
|
|
| |
-Improve iscsi error logging
-Use udev_settle from udev.py instead of calling udevadm ourselves
|
|
|
|
|
|
|
|
|
|
| |
While doing some tests with iscsi and kickstart I noticed that currently
drives discovered through ibft (iscsi), edd (fcoe), or configured in the
rclinux script (zfcp), can not be used in kickstart's clearpart or
ignoredrive commands. This patches fixes this.
Note that the 3 added startup calls are complete no-ops on systems without
ibft / edd-fcoe info / pre configured zfcp.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) centralize the setting of the timeout parameter inside the
udev_settle function. I do realize that the time needed for
initially scanning all disks is much larger, then the time for
scanning a single new partition when we are creating partitions.
But since this is a timeout, and udevadm settle will exit as soon
as the scanning is done, I see no reason not to have a single place
to configure the timeout assuming the worst case scenario (the initial
disk scan). This way we won't have these magic values sprinkled all
over the code.
2) Given that in the past we've had bugs filed
about anaconda taking many minutes to scan hardware on big iron machine
and that our initial udev settle call will scan all disks, I think
that udevadm's default timeout of 1 minutes is too low, so this patch
sets the timeout to 5 minutes.
|
| |
|
| |
|
|
|
|
|
|
| |
This only existed so we could put cleanup code around the whole loop to pop
a window, but that's probably the least clear way we could ever do such a
thing. Just be more explicit now.
|
|
|
|
|
|
| |
Added some more debugging information which was helpful during
reIPL problem determination. Also, some of the messages did not
keep up with previous code changes...
|
|
|
|
|
|
|
|
|
|
|
| |
In F11 and F12 the command line option to enable btrfs during the installer was
"icantbelieveitsnotbtr". Unfortunately I can't spell believe the first time
every time, and btrfs has come quite a ways since F11 and is stable enough to
start being tested on a larger scale. So change the command line option to
"btrfs" in keeping with tradition and to make it a bit simpler for those who
want to take it for a test spin in F13. Thanks,
Signed-off-by: Josef Bacik <josef@redhat.com>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Be default mount makes tmpfs mounts 1/2 RAM size, on 256MB machines, where
part of the RAM is taken up by a shared framebuffer, this results in a
/tmp which is to small to hold install.img, resulting in install failure
when trying to do for example a network installation.
This patch fixes this by specifying a size for /tmp, it uses 250MB which
should be plenty for now and the forseeable future.
|
|
|
|
|
|
|
| |
...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.
|
| |
|
|
|
|
|
| |
All previous comments about test mode being untested apply to loader, but
doubly so.
|
| |
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
This mode is decaying as anaconda moves forward with things like udev, dbus
etc. No one is really working on making sure they continue to work. Let's
stop pretending and also get rid of some additional complicated ways to
run anaconda.
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
We used to accept only "nfs://". First, it was inconsistent with cmdline repo=
ks= stage2= options and it confused people. Second, when we offered editing of
url with invalid "nfs:" prefix in UI, there was nothing to correct in UI, just
clicking OK lead to success.
|
| |
|
|
|
|
|
|
|
|
|
| |
The cause of traceback is that repo._baseurlSetup changes repo.baseurl
attribute (removes all invalid urls from the list) so we have to keep
invalid urls in anacondaBaseURLs to be able to edit it eventually.
_baseurlSetup is called from whiteout plugin for all repos (by repo.retreiveMD)
after setup of first repo
|
|
|
|
|
|
|
|
|
|
| |
If the file is already linked with the source the raised inspection kills
anaconda. This happens in some unclear livecd situations but in general nothing
prevents the user or any software he runs on the livecd from arranging this
manually.
Tested when the file doesn't exist beforehand (the common scenario) and when the
file links to its later origin already (the bug scenario).
|
|
|
|
|
|
|
| |
'tmp/storage.log' file. (a part of #524980)
Previously, the method call was logged into 'tmp/anaconda.log' which made the
file harder to do anything useful with.
|
|
|
|
|
| |
This is to make the anaconda.log have consistent entries from loader and from
stage 2.
|
|
|
|
|
|
|
| |
The entry format and date format is standardized: do not show date but always
show miliseconds.
Includes a cleanup in the storage/storage_log.py code to use AnacondaLog.
|