Re: comments on the new custom partitioning UI

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

 



> The very first thing that surprised me was the top-down configuration of
> storage.  What I mean by this is that you specify a file system mount
> point, and size, without any mention of where it will live.  It actually
> took me several minutes of staring at the UI looking for what I was
> missing before I actually went ahead and created a file system.  After
> that, I found the obvious drop-downs for choosing whether the file
> system would be backed by a partition or a logical volume.

Yes, top-down is a pretty new scheme for storage configuration.  It's
going to take some getting used to.  We need to document this, and
dlehman also has an idea for the future about adding in some sort of
quick tutorial for the first time you go in there.

> On my system I have two identical disks, and I decided to create a
> volume group to host 2 logical volumes, 1 for /boot and one for swap.
> Then, I created a RAID1 volume to mirror the / partition.  This all
> worked fine, though I was a bit uneasy about not being able to inspect
> how the partitions were laid out before beginning the installation.

We've also kicked around the idea of having some dialog that shows
exactly what we are going to do, but there's been no definite talk on it
and no mockups.  So, it's not going to hapen for F18.  The unease kind
of stems from the top-down approach, I think.

> I did leave space on both disks.  Initially, I had hoped I would be able
> to create a single volume group that would be larger than I needed, and
> then just carve out the logical volumes I would use (and leave the rest
> of the volume group available for expansion).  However, due to the way
> the interface is laid out, there is no way to do this.
> 
> I can, of course, achieve the same thing after the system is installed
> by adding another partition to each of the disks, running pvcreate and
> vgextend.  However, I had hoped to set this up in the installer.

Hm, that is true.  I don't know that we specifically have any plans to
tackle this in the installer, though.  As a hack, you could create an LV
that consumes as much space as you want to reserve and then post-install
delete it.

- Chris

_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list


[Index of Archives]     [Kickstart]     [Fedora Users]     [Fedora Legacy List]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]
  Powered by Linux