| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
* autopart.py (autoCreatePartitionRequests): Fix for autopart with
not lvm (msw@rpath.com)
2005-08-15 Chris Lumens <clumens@redhat.com>
* anaconda.spec: Bump version.
|
|
|
|
|
| |
LVM grow debugging code. Perhaps this could be worked in as another
command line arg in the future? No, that seems like a bad idea.
|
|
|
|
|
| |
* autopart.py (doAutoPartition): Fix from lxo for
clearpart --none (#162445)
|
|
|
|
| |
selected to put partitions on.
|
|
|
|
|
|
|
| |
* autopart.py (partlist.getFreeSpace): Fix problem Chris and Paul
saw on Friday where manual partition growing would stop at the
size of the partition. When imposing a max size based on the free
sectors available, it should remember how big the part originally was.
|
| |
|
|
|
|
|
|
|
|
| |
* fsset.py (HfsPlusFileSystem.__init__): Add hfs+ support.
* autopart.py (growParts): Don't try to grow a partition beyond
the size of the largest free space. Fixes pathological problem
hit when installing a dual boot with MacOS X.
|
| |
|
|
|
|
| |
/etc/fstab (#97560).
|
| |
|
|
|
|
| |
clamp each LV's max size, initial size, and growth amounts to pesize
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
<instance> info.
log how much free space we're starting with.
don't clamp an lv's total size, instead clamp pv's sizes appropriately
* lvm.py: remove and recreate all PVs when we do a vgremove, so they
don't lose 1 PE each time due to an lvm2 bug.
log what lvm commands are being run, since that doesn't go into lvmout.
log total vs actual in getVGFreeSpace
* partRequests.py: get rid of getPVSize, that way can't work (oopsie).
remove bogus check in getActualSize.
clamp totalspace for preexisting PVs.
clamp each PV's size and trim 1 PE off when computing total space.
don't clamp the LV's overall size.
* iw/lvm_dialog_gui.py: clamp each PV and trim 1 PE when computing
availSpaceMB.
Ow. My head hurts. But autopartition actually works, and even shows the
same numbers as the editor afterwards.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
group defined (Potential fix for #144280, #145145).
|
|
|
|
| |
partition. (Potential fix for #101432).
|
|
|
|
|
|
| |
* autopart.py (setPreexistParts): Fix handling of existing
partitions on drives which don't have a partition table we
understand (#131333)
|
| |
|
|
|
|
|
|
|
|
|
| |
* autopart.py (getAutopartitionBoot): Use
iutil.hasiSeriesNativeStorage instead of iutil.hasIbmSis()
* partitions.py (Partitions.sanityCheckAllRequests): Likewise.
* iutil.py (hasiSeriesNativeStorage): Rename from hasIbmSis(),
check for ipr as well as ibmsis.
|
|
|
|
|
|
|
|
| |
* autopart.py (doAutoPartition): Don't hard code VG name for
auto-partitioned volume groups as VolGroup00 (#134263)
* partRequests.py (VolumeGroupRequestSpec.__init__): Add autoname
hack for autopart + lvm.
|
|
|
|
|
| |
* autopart.py (doAutoPartition): Be more certain we have
one of "our" LVM partitions (#135440)
|
|
|
|
|
| |
* autopart.py (doAutoPartition): Fix LVM traceback if going back
from not enough space (#131325)
|
|
|
|
| |
patch from stuart hayes AT dell (#130885)
|
| |
|
| |
|
|
|
|
|
|
|
| |
* Create /boot partition (or appropriate for the arch)
* For each drive being used in auto-partitioning, create a PV
* Use these pvs in a vg
* Create auto-partition requests as logical volumes in the vg
|
| |
|
| |
|
|
|
|
|
|
| |
# we want to clear the part if:
# 4) the ptable doesn't support numeric ids, but it appears to be
# a RAID or LVM device (#107319)
|
|
|
|
| |
for "modern" hardware. (#122535)
|
|
|
|
|
|
|
|
|
| |
* firewall update
* iSeries PReP size
* ppc mediacheck
* tzdata stuff
* cmdline mode
* pkg defaults screen
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
summary of looking through the diff is
* clean up warnings, we build with -Wall -Werror here too
* product.img stuff
* max logical partitions enforcement
* 1 TB max fs size
* ethtool stuff
* autopart in kickstart
* driver disk fixes
* RHEL upgrade stuff
* network driver disks
* variant pkgorder/tree splitting
|
|
|
|
|
|
|
|
| |
* ppc boot constraints
* md5 endianness
* don't prompt to save tracebacks to a floppy without a floppy
* autopart for kickstart
* network configuration in the loader if vnc/display case
|
|
|
|
| |
and cleanups in here too
|
|
|
|
|
|
|
|
| |
after-taroon-merge
this one adds s390 fixes, basic i/p series platform support, support for
multiple kernels and one second stage, cmdline kickstart mode (nice for s390),
some warning cleanups.
|
| |
|
| |
|
|
|
|
|
| |
will be tagged after-taroon-merge after. taroon at this point is tagged
taroon-merge-point for where to base merges from in the future
|
| |
|
| |
|
| |
|
|
|
|
| |
preexisting stuff
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the partition strings in error cases to avoid breaking string freeze
(should be fixed post gingin)
Adds the following:
raid / --device md0 --useexisting
Use existing raid device md0, don't format it
raid /home --device md0 --noformat
Use existing raid device, but format it
volgroup myvg --noformat
volgroup myvg --useexisting
Use existing volume group. Doesn't run vgcreate
logvol /foo --vgname=myvg --name=root --noformat
Reuse existing logical volume myvg/root and don't format
logvol / --vgname=myvg --name=root --useexisting
Reuse existing logical volume myvg/root and format it
clearpart --none
For completeness sake (and because I tried to use it :-)
These aren't really supported but are there so that people can play
with them and hopefully find the bugs before taroon :)
Also has the side effect of probably fixing the occasional traceback
mikem sees with lvm that I haven't reproduced (but got something similar to
while testing this stuff)
|