summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* BR system-config-keyboardDavid Cantrell2009-10-131-1/+3
| | | | Required for getlangnames.py
* New version.David Cantrell2009-10-133-90/+103
|
* Remove extra echo in 'make rpmlog'.David Cantrell2009-10-131-1/+0
|
* Do not traceback if network device doesn't have HwAddress property (#506013).Radek Vykydal2009-10-131-2/+7
|
* Fix liveinst to (1) not unmount /dev/pts, (2) unmount in order (509632).Chris Lumens2009-10-131-1/+6
|
* Do not read DASD data from /tmp/install.cfg in booty (#526354).David Cantrell2009-10-131-2/+0
| | | | The DASD kernel parameters will be coming from DASDDevice objects.
* Merge branch 'master' of ssh://git.fedoraproject.org/git/anacondaBill Nottingham2009-10-1310-15/+40
|\
| * Support upgrading when the language isn't in lang-table (#528317).Chris Lumens2009-10-1310-15/+40
| |
* | Fix task selection when tasks contain the same group. (#528193)Bill Nottingham2009-10-131-9/+6
|/ | | | | | If we just iterate over the task list selecting and deselecting groups, then we'll deselect groups we want if a later task also contains those groups. So deselect all unchecked tasks, then select all checked tasks.
* Update drivelist with bootloader --driveorder ks option instead of replacing ↵Radek Vykydal2009-10-131-1/+1
| | | | | | | it (#506073). Just update the order of drives instead of using only drives entered in --driveorder option.
* Use ID_SERIAL to write multipath.conf, but ID_SERIAL_SHORT for UI.Peter Jones2009-10-131-2/+3
| | | | | multipath and multipathd expect the leading "3" in wwids, but that's bad in the user interface. So use one for one and the other for the other.
* Don't run 70-anaconda.rules on an installed system (#527781).Chris Lumens2009-10-133-0/+7
| | | | | | | | The livecd includes anaconda, for obvious reasons. However this means that 70-anaconda.rules will be installed on the finished system and running our rules has some unusual side effects. While we slowly push our udev rules changes into upstream packages, this should make them a no-op on the installed system.
* Handle Installation Repo (base repo) as any other in repo edit UI.Radek Vykydal2009-10-132-53/+32
| | | | | | | | | | With present UI, edit repos, not base repos (methodstr). Works with assumption that base repo (repo/method) url points to a single repo, which is true for Fedora (as opposed to RHEL5 where we various repos in directories). dgregor told me that the target for RHEL6 is to have just one repo and handle product differentiation by comps. If we had to work with multirepo base urls, the UI for repo editing would need to be redesigned and rewritten because now we are mixing base urls with repo urls there.
* Fix methodstr editing dialog.Radek Vykydal2009-10-133-5/+10
| | | | We need to pass dummy repo object. Also pass methodstr as argument.
* Store methodstr url of repo (#502208, #526022).Radek Vykydal2009-10-132-11/+33
| | | | | We need it for repo editing or correction of repo= arguments in UI, especially in case of nfs: or cdrom: which can't be stored in AnacondaYum.baseurl,
* Show user of which repository he edits the url (methodstr editing).Radek Vykydal2009-10-131-2/+1
| | | | | I'd set insensitive also the other elements instead of hiding them which makes the dialog desert. The dialog probably needs some more polishing.
* Don't traceback with malformed repo= nfs: parameter.Radek Vykydal2009-10-131-4/+7
|
* New version.David Cantrell2009-10-123-73/+82
|
* Missing volume_key shouldn't break LUKS support completely. (#526899)David Lehman2009-10-121-1/+7
| | | | | | Live images don't contain volume_key, which makes sense since key escrow is kickstart-only functionality. At any rate, failure to import volume_key should only break key escrow.
* Write multipathd.conf in anaconda so that dracut can find it.Peter Jones2009-10-123-0/+70
| | | | | | This writes a multipathd.conf that whitelists the devices we're using in our multipath devices. It's a fairly basic configuration, and it doesn't handle ALUA yet.
* We moved from dialog to newt.. (#528497)Martin Sivak2009-10-121-1/+1
|
* Fix a segfault when stage2= boot parameter and kickstart url method is used ↵Radek Vykydal2009-10-121-3/+2
| | | | | | (#524417). Concerns cases when stage2= can't be parsed as http or ftp url.
* Sending translation for Spanishfgonz2009-10-111-1795/+2553
|
* Fix parsing of optional portnr in iscsi target IP (#525118)Hans de Goede2009-10-102-4/+18
| | | | | | | | | | 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.
* Sending translation for Russiansergeyr2009-10-101-895/+1123
|
* New version.David Cantrell2009-10-093-168/+188
|
* Reset PartitionDevice attributes after failed edit. (#498026)David Lehman2009-10-091-0/+11
| | | | | | If we are editing, not creating, we overwite several attributes instead of creating a new device/action pair. Since these changes have no corresponding action they need to be reversed manually.
* Add MultipathDevice.getDMNode(), because .updateSysfsPath() needs it.Peter Jones2009-10-091-0/+8
| | | | This should have been part of the previous commit but wasn't.
* Add MultipathDevice.updateSysfsPath()Peter Jones2009-10-091-0/+13
| | | | | MultipathDevice needs its own .updateSysfsPath(), because self.name is "mpath0" but the sysfs directory is /sys/class/block/dm-0 .
* Run implantisomd5 on boot.iso on x86. (bz#526902)Peter Jones2009-10-091-0/+1
| | | | | We're doing this on other architectures but not here, and we prompt to run mediacheck on the disc, so we ought to be checksumming it.
* Consider encryption when checking for duplicate mountpoint. (#526697)David Lehman2009-10-093-3/+12
|
* Fix grub stage1 installation for /boot on md raid1.Radek Vykydal2009-10-092-31/+94
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a patch to fix installation of grub in case we have md raid 1 /boot device. I posted similar patch some time ago, Hans reviewed it, but it didn't gather much attention so I was afraid to push it - it changes behavior. Now I decided to do things a bit differently. Also, some weeks ago Hans has pushed a patch fixing bootloader target selection for mdraid (commit 45a7048e5f56316e052e4699b5ec70aa291ddd5e) upon which my patch is standing. So here I come again (sorry for repeating myself). We offer installation into mbr or boot partition (/dev/mdX) in UI. In F11 and RHEL5 if md boot partition was on /dev/sda1 and /dev/sdb1, in case of "mbr" we installed grub twice into mbr of /dev/sda, and in case of "partition" into mbr of /dev/sda and /dev/sdb. Member drive removal in the second case didn't work I think (no boot). Hans's patch changed the behavior (it was expected) - we are really installing bootloader into boot device if /dev/mdX is selected, and if mbr is selected, we are installing twice into mbr of selected drive as before. My patch wants to make it behave "the right" way, that is - install where you were asked to, and be able to boot when one member disk is removed (see bug https://bugzilla.redhat.com/show_bug.cgi?id=213578), so: A) In case of installing into boot partition: install it there in a way that the boot works if one member is removed. B) In case of installing into mbr: iff the disk contains member of boot md array, install also into mbrs of other members. If one member is removed, be able to boot - this is fixed by the patch. Note: I'd like to fix upgrade of grub part too, especially when now the behavior has changed wrt what we write out in grub.conf and /etc/sysconfig/grub. Also UI can writing for mbr could say that we'd install into mbr of other member disks too (if it is the case) If you want details, below are some cases that illustrate the change (also the code may be hard to follow for given case, I can post a test script using which you can get resulting grub input for given case) 1) sda, sdb, install to mbr, /boot is sdb1 works both with and without the patch, the same grub commands are run 2) sda, sdb, sdc, install to mbr of sda, /boot is mdarray of sdb3 and sdc3 without the patch: - boots with both disks, doesn't if any is removed - log: Running... ['/sbin/grub-install', '--just-copy'] Running... ['/sbin/grub', '--batch', '--no-floppy', '--device-map=/boot/grub/device.map'] GNU GRUB version 0.97 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename.] grub> root (hd0,2) Filesystem type is ext2fs, partition type 0xfd grub> install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0) /grub/stage2 p (hd0,2)/grub/grub.conf grub> Running... ['/sbin/grub-install', '--just-copy'] Running... ['/sbin/grub', '--batch', '--no-floppy', '--device-map=/boot/grub/device.map'] GNU GRUB version 0.97 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename.] grub> root (hd1,2) Filesystem type is ext2fs, partition type 0xfd grub> install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0) /grub/stage2 p (hd1,2)/grub/grub.conf grub> both disks - OK 2nd disk removed - OK 1st disk removed - OK with the patch: - boots even when any of member disks is removed - log: Running... ['/sbin/grub-install', '--just-copy'] Running... ['/sbin/grub', '--batch', '--no-floppy', '--device-map=/boot/grub/device.map'] GNU GRUB version 0.97 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename.] grub> root (hd1,2) Filesystem type is ext2fs, partition type 0xfd grub> install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0) /grub/stage2 p (hd1,2)/grub/grub.conf grub> 3) sda, sdb, install to mbr of sda, /boot is mdarray of sda3 and sdb3 without patch: - it boots with both disks, doesn't find stage1 (_ on screen) if any of them is removed - log: Running... ['/sbin/grub-install', '--just-copy'] Running... ['/sbin/grub', '--batch', '--no-floppy', '--device-map=/boot/grub/device.map'] GNU GRUB version 0.97 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename.] grub> root (hd1,1) Filesystem type is ext2fs, partition type 0xfd grub> install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0) /grub/stage2 p (hd1,1)/grub/grub.conf grub> Running... ['/sbin/grub-install', '--just-copy'] Running... ['/sbin/grub', '--batch', '--no-floppy', '--device-map=/boot/grub/device.map'] GNU GRUB version 0.97 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename.] grub> root (hd2,1) Filesystem type is ext2fs, partition type 0xfd grub> install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0) /grub/stage2 p (hd2,1)/grub/grub.conf grub> with the patch: - boots even when one of member disks is removed - log: Running... ['/sbin/grub-install', '--just-copy'] Running... ['/sbin/grub', '--batch', '--no-floppy', '--device-map=/boot/grub/device.map'] GNU GRUB version 0.97 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename.] grub> device (hd0) /dev/sdb grub> root (hd0,2) Filesystem type is ext2fs, partition type 0xfd grub> install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0) /grub/stage2 p (hd0,2)/grub/grub.conf grub> Running... ['/sbin/grub', '--batch', '--no-floppy', '--device-map=/boot/grub/device.map'] GNU GRUB version 0.97 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename.] grub> root (hd0,2) Filesystem type is ext2fs, partition type 0xfd grub> install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0) /grub/stage2 p (hd0,2)/grub/grub.conf grub> 4) like 3), but /boot is mdarray of sda3 and sdb2 - notice different partition numbers - removing a specific one of member disks can't work as location of grub.conf file stored in first block of stage2 is shared and so contains only the last grub-installed value. without the patch: - doesn't boot with both disks, doesn't boot with any single disk - log: Running... ['/sbin/grub-install', '--just-copy'] Running... ['/sbin/grub', '--batch', '--no-floppy', '--device-map=/boot/grub/device.map'] GNU GRUB version 0.97 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename.] grub> root (hd0,2) Filesystem type is ext2fs, partition type 0xfd grub> install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0) /grub/stage2 p (hd0,2)/grub/grub.conf grub> Running... ['/sbin/grub-install', '--just-copy'] Running... ['/sbin/grub', '--batch', '--no-floppy', '--device-map=/boot/grub/device.map'] GNU GRUB version 0.97 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename.] grub> root (hd1,1) Filesystem type is ext2fs, partition type 0xfd grub> install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0) /grub/stage2 p (hd1,1)/grub/grub.conf grub> with the patch: - boots when one second disk is removed, not when the first one is removed (in the sense of boot order) - log: Running... ['/sbin/grub-install', '--just-copy'] Running... ['/sbin/grub', '--batch', '--no-floppy', '--device-map=/boot/grub/device.map'] GNU GRUB version 0.97 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename.] grub> device (hd0) /dev/sdb grub> root (hd0,1) Filesystem type is ext2fs, partition type 0xfd grub> install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0) /grub/stage2 p (hd0,1)/grub/grub.conf grub> Running... ['/sbin/grub', '--batch', '--no-floppy', '--device-map=/boot/grub/device.map'] GNU GRUB version 0.97 (640K lower / 3072K upper memory) [ Minimal BASH-like line editing is supported. For the first word, TAB lists possible command completions. Anywhere else TAB lists the possible completions of a device/filename.] grub> root (hd0,2) Filesystem type is ext2fs, partition type 0xfd grub> install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0) /grub/stage2 p (hd0,2)/grub/grub.conf grub>
* Do not show the VNC-over-text question, when there is not enough memory for ↵Martin Sivak2009-10-091-0/+5
| | | | GUI (#527979)
* Fix filtering out of 'Sending translation for' log messages in bumpver.Radek Vykydal2009-10-091-1/+1
| | | | | I hit it in the last build that I've done where the filtering was introduced (and I have to add that I also acked the original patch).
* Use addUdevPartitionDevice() for adding dmraid / multipath partitions (#527785)Hans de Goede2009-10-081-16/+7
| | | | | | | | | | With a kickstart install, with "clearpart --label", we will end up scanning pre-existing partitions after clearing the label. This leads to the backtrace as seen in #527785 and #526517. addUdevPartitionDevice() has special handling for this case, instead of copy and pasting this, this patch modifies addUdevPartitionDevice() so that it can be used for dmraid and multipath partitions too.
* Set partedPartition system to the correct FS when creating an FSHans de Goede2009-10-083-0/+22
| | | | | | | | | | | | | | The playing around with partedPartition flags only allows us to determine the partition table entry for certain usuages which are deemed special by parted. For normal FS usuage, parted will default to the type for the FS it has detected (for pre-existing partitions) or to Linux (83) for new partitions. This means that for example reformatting a vfat partition as ext3, or a new partition as vfat will lead to incorrect partition type entries in the partition table. This patch fixes this. This patch is intended for both master and F-12.
* Reset parted flags in createFormat not destroyFormatHans de Goede2009-10-081-8/+10
| | | | | | | | | | | | | | | | We were resetting the parted flags for re-use of existing partitions in destroyFormat, but this assumes that the existing partition actually has a type in the partition table matching its current formatting, this has 2 problems: 1: If the partition has a type which needs to have flags reset to become the correct type for the new format (for example swap -> ext2), but it is not formatted, the flags wont get reset 2: If the partition has a type which does not match the formatting (for example type linux raid, formatting ext2), the flags won't get reset This patch moves the resetting of the flags to the creation of the new format, and resets all flags except for the one for the to be created format (and boot and lba which are special).
* Default to mbr bootloader target for mdraid 1 boot device too (#526822).Radek Vykydal2009-10-081-2/+1
| | | | | | | It used to be so, because for boot device target (/dev/mdX) we installed into MBRs anyway. With Hans's patch 45a7048e5f56316e052e4699b5ec70aa291ddd5e we do what we promise (install to boot device) in this case, but it is a change and it doesn't seem to be expected as default by users.
* Clear out state before calling XkbGetState.Chris Lumens2009-10-081-0/+1
|
* New version.Radek Vykydal2009-10-083-126/+148
|
* Override fstabSpec in PartitionDevice for by-path DASD (#526364).David Cantrell2009-10-071-0/+9
| | | | | If the partition is on a DASD disk, write out the /dev/disk/by-path/... value to the /etc/fstab file rather than a UUID= line.
* Create DASDDevice objects for DASD devices when building devicetree.David Cantrell2009-10-071-0/+3
| | | | | When building the device tree, if the block device is a DASD, create a DASDDevice object rather than a DiskDevice object.
* Add udev_device_is_dasd() to detect DASD devices.David Cantrell2009-10-071-0/+8
| | | | | | The only thing I can tell is available for us from the udev db is to see if the DEVNAME starts with 'dasd'. We'll need this for the dracut changes for DASD later.
* Change existing call to deviceNameToDiskByPath().David Cantrell2009-10-071-1/+1
| | | | | | The only existing use of deviceNameToDiskByPath() expected the basename returned. Since the function returns the full /dev/disk/by-path/... path, take the basename of the returned value.
* Make storage.devices.deviceNameToDiskByPath() more robust.David Cantrell2009-10-071-2/+10
| | | | | | | | | Have deviceNameToDiskByPath() return the full device path rather than just the basename path. Have it check to see if the entry in /dev/disk/by-path is actually a symlink, then readlink that. Otherwise just take the basename of the entry. Also fix a problem where passing it a full device path would not match (e.g., '/dev/dasdb1'). Take the basename of deviceName and match that against the readlink() value.
* Do not copy over 70-persistent.rules if instPath is '' (#527707)David Cantrell2009-10-071-1/+1
|
* Filter out 'Sending translation for' log messages in bumpver.David Cantrell2009-10-071-1/+4
| | | | We don't want these messages in the RPM changelog entries.
* Don't copy _raidSet, but merely pass around a referenceHans de Goede2009-10-081-2/+5
| | | | | | | | block.dmraid.RaidSet keeps track of the state of the devicemaps and will try to add / remove maps when activating / deactivating the set depending on its internal state, shallow copying it copies this state, creating 2 copies of it, which can result in trying to bring the set up or down twice, which causes a backtrace.
* Action...Format setup device before modifying the partition tableHans de Goede2009-10-081-2/+4
|
* map() -> filter() in storage.writeEscrowPackets()David Cantrell2009-10-071-2/+3
| | | | | map() gives us a list of bool objects, filter() gives us the actual device objects we are expecting.
generated by cgit (git 2.34.1) at 2025-10-03 08:41:35 +0000