I don't have any problem with switching to XFS or getting rid of the /home split. The former should be pretty invisible to users, and split home is more of a trap for users than a help. But switching to leaving most of the disk unpartitioned seems wrong. With the move to overlay2 for Docker storage, everything you want to do with disk space is inside / - the OS image, your overlay RPMs, your docker storage, your home directory. Yes, early adopters of the Atomic Workstation can deal, but long term, we don't want Atomic Workstation to be for the adventurous - we want it to just work. Yes, it's easier to grow partitions then shrink them, but I don't think that can excuse leaving users out of the box with a less-than-useful partitioning setup. Owen ----- Original Message ----- > The actual PR is posted in: https://pagure.io/pungi-fedora/pull-request/257 > > This is only for: https://fedoraproject.org/wiki/Changes/WorkstationOstree > > The primary reason to do this is that the blivet defaults break with ostree, > since `/home` needs to be `/var/home` with ostree. > https://bugzilla.redhat.com/show_bug.cgi?id=1382873 > > But bigger picture than that, having a split `/home` makes less sense using > rpm-ostree, because the primary original rationale for introducing that split > was to make upgrades easier by reinstalling but preserving `/home`. With > rpm-ostree upgrades should be much more reliable and easier. > > We also to use XFS (as opposed to the blivet ext4 default) for the same > reason as Atomic/Server - > it works better with overlay2 because it avoids inode limits. > > And not using all of the disk makes it easier to do more advanced > partitioning *post* installation. For example, in the past I've used dm-crypt > for the OS and `/home`, but not for `/srv` where I put non-private data like > my > git repositories. (Although I recently switched back to dm-crypt for > everything > for simplicity). > > Another good example of this is that `container-storage-setup` supports > allocating a separate LV for `/var/lib/docker`, so container storage is > isolated > from the host. > > Anaconda is making it easier to do arbitrary partitioning in the installer > via > blivet-gui, but I think doing it post-install is more flexible. One can > use scripts as well (e.g. Ansible). > > The flip side of course is that users are going to wonder why they only have > `14G` of space...we should likely teach the installer to have a simple "use > all > of my disk" button, and also have one post-install (something like Nautilus > launching `Disks` with awareness of LVM)? > > Signed-off-by: Colin Walters <walters@xxxxxxxxxx> > --- > fedora.conf | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/fedora.conf b/fedora.conf > index a7d403b..edc3586 100644 > --- a/fedora.conf > +++ b/fedora.conf > @@ -812,7 +812,7 @@ ostree_installer = [ > "x86_64": { > "repo": "Everything", > "release": None, > - "installpkgs": ["fedora-productimg-workstation"], > + "installpkgs": ["fedora-productimg-atomic"], > "rootfs_size": "8", > "add_template": > ["workstation-ostree-installer/lorax-configure-repo.tmpl", > "workstation-ostree-installer/lorax-embed-repo.tmpl"], > -- > 2.9.4 > _______________________________________________ > desktop mailing list -- desktop@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to desktop-leave@xxxxxxxxxxxxxxxxxxxxxxx > _______________________________________________ desktop mailing list -- desktop@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to desktop-leave@xxxxxxxxxxxxxxxxxxxxxxx
