directhex wrote:
> You're right - the combined minimum size of two of my defined partitions was smaller than the maximum capacity of the drive - which caused the installer to go with sda1=/,sda5=swap
>
> Is this the expected behaviour when a partman recipe can't be resolved on a given machine?
>
I thought that partman would die and go back to the install menu with an
error when it couldn't resolve the recipe. I have always had to grow at
least one partition to fill the drive to successfully get the recipe to
run on drives of differing sizes.
Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
directhex wrote:
> You're right - the combined minimum size of two of my defined partitions was smaller than the maximum capacity of the drive - which caused the installer to go with sda1=/,sda5=swap
>
> Is this the expected behaviour when a partman recipe can't be resolved on a given machine?
>
I thought that partman would die and go back to the install menu with an
error when it couldn't resolve the recipe. I have always had to grow at
least one partition to fill the drive to successfully get the recipe to
run on drives of differing sizes.
Tim enigmail. mozdev. org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iD8DBQFET54ugLV M9zV5AaMRAsXYAJ 4uwRPBJSSoEi/ 7RrxySs4iz77sLg CcD2C6 t7fkUVZU=
O6bPGs4yIfCXU9b
=8Gf7
-----END PGP SIGNATURE-----