summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* Log system messages to /tmp/syslog instead of /tmp/messages.log.Chris Lumens2010-01-281-1/+1
| | | | | This is what the rest of anaconda expects and what we've been telling people to attach for years.
* Make sure we always check /lib64 and /lib in find_library (#555669).David Cantrell2010-01-271-3/+3
| | | | | LD_LIBRARY_PATH ended up being /tmp/updates on my test system, so make sure we always check the default library paths in find_library().
* Make sure we get required nss-softokn libs in the images.David Cantrell2010-01-272-3/+13
| | | | Check /lib and /usr/lib for these files.
* Add 5 second ping delay for gateway and dns test on s390x (#536815).David Cantrell2010-01-271-3/+3
|
* Update =~ regexps in linuxrc.s390 for bash-4.1 (#558537).David Cantrell2010-01-271-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | GNU bash 4.1 changes the behavior of the =~ operator in the [[ command. From the bash FAQ: E14) Why does quoting the pattern argument to the regular expression matching conditional operator (=~) cause regexp matching to stop working? In versions of bash prior to bash-3.2, the effect of quoting the regular expression argument to the [[ command's =~ operator was not specified. The practical effect was that double-quoting the pattern argument required backslashes to quote special pattern characters, which interfered with the backslash processing performed by double-quoted word expansion and was inconsistent with how the == shell pattern matching operator treated quoted characters. In bash-3.2, the shell was changed to internally quote characters in single- and double-quoted string arguments to the =~ operator, which suppresses the special meaning of the characters special to regular expression processing (`.', `[', `\', `(', `), `*', `+', `?', `{', `|', `^', and `$') and forces them to be matched literally. This is consistent with how the `==' pattern matching operator treats quoted portions of its pattern argument. Since the treatment of quoted string arguments was changed, several issues have arisen, chief among them the problem of white space in pattern arguments and the differing treatment of quoted strings between bash-3.1 and bash-3.2. Both problems may be solved by using a shell variable to hold the pattern. Since word splitting is not performed when expanding shell variables in all operands of the [[ command, this allows users to quote patterns as they wish when assigning the variable, then expand the values to a single string that may contain whitespace. The first problem may be solved by using backslashes or any other quoting mechanism to escape the white space in the patterns. Bash-4.0 introduces the concept of a `compatibility level', controlled by several options to the `shopt' builtin. If the `compat31' option is enabled, bash reverts to the bash-3.1 behavior with respect to quoting the rhs of the =~ operator.
* Sending translation for Spanishelsupergomez2010-01-271-580/+595
|
* Sending translation for Punjabijassy2010-01-271-242/+274
|
* Add strace to the stage2 image and initrd.Chris Lumens2010-01-262-1/+3
|
* Sending translation for Hebrewelad2010-01-261-1648/+1868
|
* multipath gives us CCISS devices names with ! in them, but we expect /.Chris Lumens2010-01-251-1/+1
|
* Fix visibility counting on filter notebook pages.Chris Lumens2010-01-251-1/+10
| | | | | | | | 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.
* Fix thinko in displaying the first filter notebook page that disks.Peter Jones2010-01-251-0/+1
| | | | Previous version had a missing break. Put the break in.
* DMRaidArrayDevice don't pass major/minor to DMDevice.__init__ (#558440)Hans de Goede2010-01-251-4/+2
| | | | | | | | The changes for the filtering UI and the whole disk formatting seem to have broken dmraid BIOS RAID support, the first traceback I hit while testing is due to DMRaidArrayDevice.__init__ now calling DMDevice.__init__ (was DiskDevice.__init__), and DMDevice.__init__ does not accept major and minor arguments.
* Filter UI: don't show cciss controllers without setsHans de Goede2010-01-251-0/+4
|
* Filter UI: give BIOS RAID sets a usable model string and display thatHans de Goede2010-01-251-2/+3
| | | | | | 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.
* Make MDRaidArray description the same as DMRaidArrayHans de Goede2010-01-251-3/+3
|
* Add DMRaidArrayDevice description and model properties (#558440)Hans de Goede2010-01-251-0/+8
|
* DMRaidArrayDevices exist when created (#558440)Hans de Goede2010-01-251-1/+1
| | | | | | DMRaidArrayDevice, used to inherit from DiskDevice, whose exists init argument has a default of True. Now that it inherits from DMDevice instead we must explicitly set exists to True when calling DMDevice.__init__ .
* Clarify syslinux menu text (#557774)Hans de Goede2010-01-252-2/+2
|
* Use description property for MDRaidArrayDevice modelHans de Goede2010-01-251-1/+1
| | | | | | The description property properly differentiaties between regular mdraid and biosraid sets, using this for model makes for a more informational display in cleardisks_gui.
* MDRaidArrayDevice: Get rid of the ugly self.devices[0].type checkingHans de Goede2010-01-251-13/+11
| | | | | | | | Now that we have a separate type for MD BIOS RAID arrays, there is no need to do: self.devices[0].type == "mdcontainer" To check for there, replace all these with the much nicer: self.type == "mdbiosraidarray"
* Make storage.unusedMDFoo also check mdcontainer membersHans de Goede2010-01-251-3/+10
| | | | This becomes important when mixing regular and bios raid mdraid arrays.
* Remove MDRaidArrayDevice biosraid propertyHans de Goede2010-01-252-8/+1
| | | | | Now that MD BIOS RAID arrays have their own type, there is no longer a need for the biosraid property.
* Give MD BIOS RAID arrays there own typeHans de Goede2010-01-252-1/+2
| | | | | | | | | | | Before the whole disk formatting changes MD BIOS RAID arrays used to have their own type of "partitionable mdarray". And we check for the normal "mdarray" type in various places (mostly to do with mdraid /boot handling where I'm seeing a traceback qtm), and when the type matches mdarray the code assumes a regular mdarray. So this code restores MD BIOS RAID arrays having their own type, so as to not trigger all these checks meant for regular mdraid arrays.
* Check for devices with no media present in filter_gui.py (#558177)Hans de Goede2010-01-251-2/+13
| | | | | This stops us from backtracing on for example usb cardreaders without a card in them.
* multipath requires libaio.soPeter Jones2010-01-251-1/+2
| | | | Add libaio to PACKAGES and KEEPFILE so that it's in install.img
* init, fixes a bug in getSyslog() causing a SEGVAles Kozumplik2010-01-251-1/+1
| | | | The error could be triggered, e.g. by appending 'stage2=hd:label="fedora"' to the boot line.
* Sending translation for Punjabijassy2010-01-251-1284/+1646
|
* Sending translation for Albanianbesnik2010-01-241-1642/+1887
|
* Sending translation for Italiantombo2010-01-231-1403/+1404
|
* New version.Chris Lumens2010-01-222-1/+54
|
* Only /boot needs to be on one of the bootFSTypes. (#557718)David Lehman2010-01-221-1/+3
|
* nss files moved around again, NM needs more (#557702)David Cantrell2010-01-222-1/+3
| | | | | We need libsoftokn3.so and libnssdbm3.so now for NetworkManager, both are in the nss-softokn package.
* Fix broken log message.Peter Jones2010-01-221-1/+2
| | | | | Format strings need to match the things being formatted, as Hans correctly pointed out.
* MDRaidMember.__str__ add biosraid attribute to the returned stringHans de Goede2010-01-221-1/+2
|
* Remove setting of _isDisk and _partitionable from iscsi and fcoe disk codeHans de Goede2010-01-221-4/+0
| | | | | | They already enherit the correct values from DiskDevice, and setting them explictly is inconsisten with ZFCPDevice and DASDDevice which do not do this.
* Add isDisk property to MDRaidArrayDeviceHans de Goede2010-01-221-0/+5
| | | | And make it return True for BIOS RAID sets (but not for containers).
* Make isDisk a propertyHans de Goede2010-01-221-6/+10
| | | | | Some MDRaidDevices are disks (BIOS RAID) others are not, so make it a property so that MDRaidDevice can override it.
* Remove DMRaidDevice.mediaPresent methodHans de Goede2010-01-221-5/+0
| | | | It is the same as the one we inherit from StorageDevice
* Honor clearPartDisks when clearing whole disk formatting formatted disksHans de Goede2010-01-221-0/+4
|
* Fixup MDRaidArrayDevice.biosraidHans de Goede2010-01-221-4/+6
| | | | | | | | | | | | 1) Containers don't have formats, so this checks always fails, making mdraid BIOS RAID sets not show up in storage.partitioned. 2) MDRaidArrayDevice.biosraid is used to not show biosraid related mdraid sets as editable raid sets in the partition UI, so we should return true for containers too, as we don't want to show those there either 3) Containers however are not partitionable, so we cannot use the biosraid property in the partitionable property.
* Update exclusiveDisks when handling mdraid BIOSRAID in isIgnoredHans de Goede2010-01-221-2/+3
| | | | | | When checking for mdraid BIOSRAID sets in isIgnored and finding one, update the exclusiveDisks entry, so that the correct name is present for other usage of exclusiveDisks (such as in cleardisks_gui.py).
* MDRaidDevice does not have serial, vendor or bus argumentsHans de Goede2010-01-221-4/+6
|
* Don't traceback on devices without a serialHans de Goede2010-01-221-1/+1
|
* Make addUdevPartitionDevice add lvm filters for ignored partitionsHans de Goede2010-01-221-0/+6
| | | | | | When we ignore a partition because its disk cannot be found, or des not have a disklabel format, or is not partitionable, we should lvm to ignore the partition too.
* Remove BIOSRAID see if ignored again code from addUdevPartitionDeviceHans de Goede2010-01-221-8/+0
| | | | | | | Since addUdevPartitionDevice now checks that the disk the partition lives on has a disklabel format (which the member disks do not have), there is no reason to call isIgnored again, esp as isIgnored no longer does any partition -> disk checking.
* Remove special partition handling from isIgnoredHans de Goede2010-01-221-16/+0
| | | | | Remove special partition handling from isIgnored, addUdevPartitionDevice does all the necessary checking itself now a days.
* Fix MDRaidArrayDevice mediaPresent to not depend on paritioned stateHans de Goede2010-01-221-8/+8
| | | | | | | Wether or not a RaidSet is partitioned, should not matter for its mediaPresent handling. What sort of RaidSet it is matters. This patch fixes us trying to do format handling on a Raid Container, which ends badly.
* Special handling for mdraid BIOS RAID sets in exclusive disksHans de Goede2010-01-221-0/+16
| | | | | | | | | Special handling for mdraid external metadata sets (mdraid BIOSRAID): 1) The containers are intermediate devices which will never be in exclusiveDisks 2) Sets get added to exclusive disks with their dmraid set name by the filter ui. Note that making the ui use md names instead is not possible as the md names are simpy md# and we cannot predict the #
* 2 small mdraid related storage/udev.py changesHans de Goede2010-01-221-1/+4
| | | | | 1) Make it safe to call udev_device_get_md_level on none md devices 2) Add udev_device_get_md_name() function
generated by cgit (git 2.34.1) at 2025-09-04 19:14:28 +0000