| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The initial loop through udev's block device list is mostly to
identify and assemble mpaths. Already-active mpaths in that list
cause problems because of the special way mpaths are handled. However,
mpath member devices are never device-mapper devices so we can safely
skip over them in this mpath-specific loop.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This accompanies a kickstart option to autopart, type:
autopart --type=lvm|btrfs|plain
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Adds support for scanning existing btrfs, including subvolumes.
Also adds an optional arg to getDeviceByPath to accommodate the fact
that btrfs volumes don't have a separate device node to represent the
top-level volume.
btrfs format.uuid is the member device's UUID (ID_FS_UUID_SUB),
while format.volUUID (ID_FS_UUID) is the top-level volume's UUID.
This prevents some further madness in which multiple devices would
have the same UUID.
|
| | |
| | |
| | |
| | | |
This will probably break the md dialogs and possibly others.
|
| | | |
|
| | |
| | |
| | |
| | | |
Things that should be on lvm should not necessarily be on btrfs.
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
This reverts commit 899c15ff69c97e96f2598cac3dea5d7f7f15c874.
|
| | |
| | |
| | |
| | |
| | | |
Their use is very limited, so just define them in the modules that
use them primarily.
|
| | | |
|
| | |
| | |
| | |
| | | |
Resolves: rhbz#671230
|
| | |
| | |
| | |
| | |
| | |
| | | |
mdadm --examine doesn't output metadata version for 0.90 superblocks
to preserve backwards compatibility so if no metadata version is
indicated we must assume 0.90.
|
| | |
| | |
| | |
| | |
| | | |
fix whitespace etc. to match usual coding style, and send output to
/dev/tty5 (as is our tradition)
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Here is a proposed patch that updates a PowerPC's BIOS to boot from the
newly installed hard disk rather than back to the installer.
The BIOS maintains a list of bootable targets which can be queried with
the nvram utility. This list can be modified so that the installation
harddrive will show up first. This code will read the list, figure out
what drive contains the PReP partition, prepends that drive to the list,
and then updates BIOS.
For example the list could be the DVD, hard drive, and ethernet.
[anaconda root@(none) /]# nvram --print-config=boot-device
/vdevice/v-scsi@30000005/disk@8100000000000000
/vdevice/v-scsi@30000002/disk@8100000000000000
/vdevice/l-lan@30000003:speed=auto,duplex=auto,000.000.000.000,[etc.]
After running this function, the list will be as follows:
[anaconda root@(none) /]# nvram --print-config=boot-device
/vdevice/v-scsi@30000002/disk@8100000000000000
/vdevice/v-scsi@30000005/disk@8100000000000000
/vdevice/l-lan@30000003:speed=auto,duplex=auto,000.000.000.000,[etc.]
|
| | |
| | |
| | |
| | | |
Report whether the failure was due to cpio, unpack or script error.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Instead of falling into an infinite loop like cmdline raise an error
with a useful description of the problem. Select it with -S or --script
This removes the infinite loops from cmdline mode, allowing it to
be subclassed for use with either cmdline or script mode.
|
| | |
| | |
| | |
| | | |
task. (#643786)
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
yum doesn't close its fd's when finished so disable it
to prevent it from holding the mountpoint open. Anaconda adds its
own log handler so no logs are lost by doing this.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This will fail if /var is on a separate partition, since we do not have
the logic to mount additional partitions at this point. Instead, just
run a chrooted /bin/arch which should always succeed.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
We removed the max size for the partition and/or format but didn't
limit the size of new ones we create.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Changes, eg: (hd0,2) to (hd0,gpt2) or (hd0,msdos2), depending on
hd0's disklabel type.
Related: rhbz#748121
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This way, it looks highlighted when you come back to the hub just like if
it was selected with the keyboard, and keyboard navigation will start on
the spoke that was just visited.
|
|/ /
| |
| |
| | |
I knew I'd forgotten something when I did this for MountpointSelectors.
|