[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: why doesn't /root/anaconda-ks.cfg contain partition info?

rpjday wrote:
#clearpart --linux
#part / --fstype ext3 --onpart hda1
#part /7.3 --fstype ext2 --noformat --onpart hda7
#part /home --fstype ext3 --noformat --onpart hda5
#part /usr --fstype ext3 --onpart hda6
#part /win --fstype vfat --noformat --onpart hda2
#part /var --fstype ext3 --size=512
#part swap --size=512
#part /preserve --fstype ext3 --noformat --onpart hda3

  so where's the partition size info?  i would have assumed that the
whole point of this generated file would be to support creating another
host practically identical to this one.  it's kind of tough to do that
when you have no partition size info stored in the file.

The lines in anaconda-ks.cfg mirror what you specify interactively. In this case you apparently recycled almost all your old partitions.

Note that --size and --onpart are mutually exclusive. It doesn't make sense to specify the size for an existing partition.

Also keep in mind the reason these lines are always commented. These partition lines may need to be modified before they will work on another machine. Even on the same machine, the you can have problems. Consider something like.

clearpart --all --linux
part / --fstype ext3 --size 2048 --grow
part /win --fstype vfat --size 1024
part swap --size 512

Every successive install on the same machine will create a new vfat partition, but the old one will stick around. Eventually an install will fail because of lack of space.

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]