Comments on: Highlights of YaST Development Sprint 83 https://lizards.opensuse.org/2019/08/30/yast-sprint-83/ Blogs and Ramblings of the openSUSE Members Fri, 06 Mar 2020 17:50:09 +0000 hourly 1 https://wordpress.org/?v=4.7.5 By: Yast Team https://lizards.opensuse.org/2019/08/30/yast-sprint-83/#comment-17092 Mon, 16 Sep 2019 13:23:06 +0000 http://lizards.opensuse.org/?p=14003#comment-17092 Just to clarify, the latest changes about the proposal and using multiple values will only affect SUSE Manager, the SUSE’s purpose-specific distribution to manage software-defined infrastructures.

For openSUSE everything will keep working as expected, using only one disk by default and with the already known Guided Setup (for the time being, at least).

]]> By: Tony Su https://lizards.opensuse.org/2019/08/30/yast-sprint-83/#comment-17037 Tue, 03 Sep 2019 03:18:18 +0000 http://lizards.opensuse.org/?p=14003#comment-17037 Some very interesting changes.
I’ll be looking forward to seeing how those change in the disk layouts are implemented, it sounds like there will be at least two base proposals (multi-disk preferred over single disk) which could be helpful if BTRFS volumes continue to be recommended everywhere. Am hoping though that they’can be customized which is how the current “Guided setup” works… ie you should be able to choose the base layout pattern to start and then modify as desired.

Even so, there are so many reasons one can pick and choose or ignore for deploying separate volumes (or partitioning) I wonder if it’s really possible to make a suggestion that won’t often be heavily modified.

And then, I’m thinking about the Snapper consequences… including and excluding directories and volumes because of why those volumes are created in the first place…

It all becomes so complex.
The current openSUSE single disk layout proposal vastly simplifies how each application is installed and the location of application data.

But still looking forward to what is being proposed…

]]>