summaryrefslogtreecommitdiffstats
path: root/70-anaconda.rules
Commit message (Collapse)AuthorAgeFilesLines
* Remove rules handled by the device-mapper package's rules.David Lehman2010-02-121-16/+4
|
* Fix udev rule to test whether we're in anaconda.David Lehman2009-11-301-1/+1
| | | | The rules use shell glob syntax, not regular expressions.
* More udev fixups for device-mapper and cryptsetup temp devices. (#526699)David Lehman2009-10-221-2/+7
|
* Don't run 70-anaconda.rules on an installed system (#527781).Chris Lumens2009-10-131-0/+3
| | | | | | | | 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.
* Tell udev to ignore temporary cryptsetup devices. (#526699)David Lehman2009-10-061-0/+2
|
* Include hidden volumes and lv attributes in udev db.David Lehman2009-09-211-1/+1
| | | | | | | | Hidden volumes include mirror stripes/copies and log volumes, which we need to accurately account for vg space usage. The lv_attr field allows us to identify snapshot volumes, mirrored volumes, and components of mirrored volumes.
* Recognize mpath devices when we see them.Peter Jones2009-08-061-1/+1
| | | | | This identifies that a device is part of a multipath, and builds an mpath device for partitioning.
* 70-anaconda.rules: pass --ignorelockingfailure to lvm invocationHans de Goede2009-07-151-3/+3
| | | | | | | | | | | During testing I noticed that anaconda did not recognize pre-existing logical volumes and thus that I could not upgrade / rescue an existing default partitioning install. I tracked this down to the last lvm call in 70-anaconda.rules failing (udevadm test is your friend). Passing --ignorelockingfailure to lvm fixes this. For good measure this patch does this for all invocations in 70-anaconda.rules
* 70-anaconda.rules: always import blkid outputHans de Goede2009-07-091-2/+2
| | | | | | | We are currently not calling blkid when a block device is not an mdraid set or a device mapper device, resulting in us not identifying mdraid members as such. This probably worked when still using vol_id because some other rules file was doing an import vol_id before our rules.
* udev dropped vol_id (#506360)Jeremy Katz2009-06-261-2/+2
| | | | | | udev no longer ships a vol_id binary, so we have to use blkid instead. Require a new enough util-linux-ng that this does what we want
* New udev rule for using mdadm for isw_raid_memberJacek Danecki2009-06-221-0/+1
|
* Make paths somewhat flexible so we'll work in normal environments.David Lehman2009-03-131-6/+9
| | | | This is needed for live installs since they run on a normal system.
* Add udev rules for handling for mdraid arrays.David Lehman2009-03-121-2/+26
| | | | | This will enable us to detect filesystems or other formatting on md arrays.
* If a pv somehow does not contain a vg_name, do not try to get other vg infoHans de Goede2009-03-121-0/+1
| | | | | In the anacond udev rules do not execute the 2 import commands which depend up on the vg_name if we don't have a vg_name.
* Fix anaconda udev rules to not require pre-existing device nodesHans de Goede2009-03-111-2/+2
| | | | | | | The way the anaconda udev rules are currently written, they require the device nodes to already be present when they run. This is not always the case (as udev creates the nodes after running the rules). This patch fixes this, which fixes the recognition of lvm VG's and LV's on iscsi disks.
* Fix paths in udev rules so they work in the installer environment.David Lehman2009-02-261-5/+5
|
* Add udev rules until device-mapper starts using udev.David Lehman2009-02-231-0/+29
generated by cgit (git 2.34.1) at 2024-05-04 07:15:39 +0000