I wanted to add my 2 cents, as I had similar proposal which in general
can reduce development costs for the YaST team. Obviously, that does
Our installer has very reach functionality, which is also available in
the installed system. So, removing some advanced UI functionality will
also affect decision on the modules.
From my experience, YaST doesn't handle hacking in console yet. E.g. if
I edit disks after the proposal, there will be many errors while trying
to remove non-existing partitions, etc. Therefore, providing extended
functionality from console, there will be extra efforts needed to handle
those changes at any stage of the installation.
On 1/27/21 4:50 PM, José Iván López González wrote:
On 12/3/20 3:44 PM, Steffen Winterfeldt wrote:
There are many ways to teak the installer and
people keep asking for
We are discussing use cases and ways to improve things on github:
If you have suggestions or more use cases or just want to stay in
touch, feel free to join the discussion.
YaST Development mailing list -- yast-devel(a)lists.opensuse.org
To unsubscribe, email yast-devel-leave(a)lists.opensuse.org
Regarding this topic, Ladislav did a great presentation today about
this POC . I have some doubts about this approach (having an
"installer console"), so I would like to open the discussion here:
* Having a console to do "whatever" could lead to tons of misuses (and
I believe that having console will actually reduce number of bugs, as it
will be easier to handle. But this solution will increase load on
support dept. unless good documentation is provided.
As an example, I can refer to arch linux installer, which is an extreme,
but we can have this solution.
* YaST users might be not that accustomed to run
"yast commads". After
all, current yast CLI is not that well shaped.
* Opening a console to configure the installer sounds a bit tricky.
Personally, I would prefer to have some dialog to configure the
installer. I see it more understandable and easier to use:
* Configuration options would be more discoverable.
* Options would be clearly limited to only what we offer in the config
* It would be less tricky on text mode.
One of the thing I would expect is to avoid to use many of the current
linuxrc parameters in order to affect YaST. I would like to open a
configuration dialog and tweak the installer directly there.
What do you think?
Rodion Iafarov <riafarov(a)suse.com>
Senior QA Engineer
Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/
SUSE Software Solutions Germany GmbH (HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer