On Wed, Apr 13, 2022 at 7:35 AM Frederic Crozat <FCrozat@suse.com> wrote:
Le mercredi 13 avril 2022 à 12:27 +0200, Carlos E. R. a écrit :
On 2022-04-13 12:19, Ancor Gonzalez Sosa wrote:
On 4/13/22 12:00, Carlos E. R. wrote:
On 2022-04-13 10:21, Stefan Behlert wrote:
(Sending to both openuse-project as well as opensuse-factory. Please keep discussions on the -project list to make life easier for all.)
...
Another important point is that we intend to split what was a more generic, everything is closely intertwined into two parts: One smaller hardware enabling piece, a kind of "host OS", and the and the layer providing and supporting applications, which will be container (and VM) based.
You mean that we users will have to run our openSUSE Linux in a virtualized machine, instead of our real hardware machine?
That's not at all what I understood from the paragraph you quoted.
To my eyes, it says the operating system will be separated into two parts:
1) a small core including only what is needed to interact with the hardware and to manage it, no matter whether that's real or virtual hardware (somehow similar to MicroOS[1]) 2) all the applications and user-space tools that will run as containers or virtual machines on top of that minimal core, way more isolated from each other and from the core compared to a current Leap in which all pieces are interconnected.
This is nuts.
Please explain.
Better now?
No, you are saying that in a year or two I will have to reinstall my desktop machine as small core system that runs a virtual machine inside having the all real things I use.
No, Ancor didn't write that either.
ALP concepts are indeed focused on Server Workloads (since this is what mostly interest SUSE as a company), where we will focus on containers and virtual machines.
For desktop like system, something similar to MicroOS Desktop / Silverblue is more aligned with the concepts around ALP.
And note, there is *no* technical reason we have to *require* that model for openSUSE ALP (in absence of a better name here...). We already have a layered repository model for Leap, that will probably continue and will allow us to do the traditional composition model that regular desktop Linux users generally prefer. That said, supporting a model that resists hysteresis (I refuse to call it immutable, because immutable it ain't) and makes it easier to do things like factory resets and such is very useful for offering the Linux desktop to a wider audience. -- 真実はいつも一つ！/ Always, there's only one truth!