I asked this on the test list, but it's more appropriate here.
What are the expected partitioning states for F18? Including Apple hardware, I'm imagining roughly seven possible states (MBR vs GPT, btrfs vs LVM), none of which are what Alpha TC3 produces. What I get is no LVM usage, an extended partition just for /home, and ext4. Is this transitional behavior?
Chris Murphy
On08/18/2012 08:28 AM, Chris Murphy wrote:
I asked this on the test list, but it's more appropriate here.
What are the expected partitioning states for F18? Including Apple hardware, I'm imagining roughly seven possible states (MBR vs GPT, btrfs vs LVM), none of which are what Alpha TC3 produces. What I get is no LVM usage, an extended partition just for /home, and ext4. Is this transitional behavior?
The current default in the gui is to not use LVM, and to default to ext4. btrfs is not yet ready to be the default, and LVM is too complex of a setup for a large portion of our users.
The default autopartitioning scheme can include a broken out /home/ directory if there is sufficient disk space available, and a broken out /boot and swap.
It would be a good idea to review the autopart expectations in the QA tests and update them for code reality.
On Aug 18, 2012, at 1:42 PM, Jesse Keating wrote:
On08/18/2012 08:28 AM, Chris Murphy wrote:
I asked this on the test list, but it's more appropriate here.
What are the expected partitioning states for F18? Including Apple hardware, I'm imagining roughly seven possible states (MBR vs GPT, btrfs vs LVM), none of which are what Alpha TC3 produces. What I get is no LVM usage, an extended partition just for /home, and ext4. Is this transitional behavior?
The current default in the gui is to not use LVM, and to default to ext4. btrfs is not yet ready to be the default, and LVM is too complex of a setup for a large portion of our users.
OK so for F18, it's changing from using LVM for autopartitioning, to not using it?
Chris Murphy
On 08/20/2012 11:45 AM, Jesse Keating wrote:
On 08/18/2012 02:12 PM, Chris Murphy wrote:
OK so for F18, it's changing from using LVM for autopartitioning, to not using it?
That is correct, for now.
Hi, does "for now" mean that eventually F18 anaconda will provide the same level of support for VGs and LVs as F17, et al?
TIA
On Mon, 2012-08-20 at 12:36 -0400, Clyde E. Kunkel wrote:
On 08/20/2012 11:45 AM, Jesse Keating wrote:
On 08/18/2012 02:12 PM, Chris Murphy wrote:
OK so for F18, it's changing from using LVM for autopartitioning, to not using it?
That is correct, for now.
Hi, does "for now" mean that eventually F18 anaconda will provide the same level of support for VGs and LVs as F17, et al?
The "for now" is only talking about using lvm by default for automatic partitioning.
As for support for lvm in general, you will be able to use preexisting VGs and LVs. How you go about specifying that your existing LVs get used as the new system's mounts will be different, but it will be possible to use new or existing lvm, btrfs, and md.
David
On 08/20/2012 09:36 AM, Clyde E. Kunkel wrote:
On 08/20/2012 11:45 AM, Jesse Keating wrote:
On 08/18/2012 02:12 PM, Chris Murphy wrote:
OK so for F18, it's changing from using LVM for autopartitioning, to not using it?
That is correct, for now.
Hi, does "for now" mean that eventually F18 anaconda will provide the same level of support for VGs and LVs as F17, et al?
TIA
What it means is that the decision to not use LVM by default for auto partitioning may be reverted, nothing is completely set in stone at this point.
On 08/18/2012 07:42 PM, Jesse Keating wrote:
The current default in the gui is to not use LVM, and to default to ext4. btrfs is not yet ready to be the default, and LVM is too complex of a setup for a large portion of our users.
The default autopartitioning scheme can include a broken out /home/ directory if there is sufficient disk space available, and a broken out /boot and swap.
It would be a good idea to review the autopart expectations in the QA tests and update them for code reality.
Does this mean we can ( finally ) disable lvm and related services by default and default to initramfs less boot thus decreasing users boot time and improving their out of the box experience?
JBG
anaconda-devel@lists.stg.fedoraproject.org