Hi there!
Today, while I was working to fix an issue when executing "yast2
system_settings" without enough permissions[1][2], some questions arose
to my mind. Let me share them,
* If I run "/usr/sbin/yast2" it warns about the permissions and only
shows a few modules[3]. So,
* Can we manage [1] and [2] in a "centralized" way? I mean, do we have
a way to know in advance when the execution of a certain module will
require root permissions? If the answer is NO,
* Can we open a discussion/research/whatever to do something to this
regard? Do you think it worth it? Or do you already had such discussions
in the past? If so, what was the conclusion?
Apart from these questions, a little bit off-topic but also related to
the topic, I found weird that "yast2 storage" prompt a warning[4] saying
> The storage subsystem is locked by an unknown application.
> You must quit that application before you can continue.
>
> Would you like to abort or try again?
when it is executed as a normal user. Actually is a problem with
permissions, not an "unknown application locking the storage subsystem".
Waiting for your inputs, thanks in advance.
See you.
[1] https://github.com/yast/yast-tune/pull/40
[2] https://github.com/yast/yast-bootloader/pull/583
[3]
https://gist.github.com/dgdavid/323e5aa879490e24ea2d0d520550e1fe#gistcommen…
[4]
https://gist.github.com/dgdavid/323e5aa879490e24ea2d0d520550e1fe#gistcommen…
--
David Díaz González
YaST Team at SUSE Linux GmbH
* The System Role selection dialog got usability improvements
* and we added a CustomStatusItemSelector to the widget library in the process.
* Snapper gained machine-readable output
* Storage:
* remote encrypted devices are activated properly at boot time
* random and pervasive encryption also supported in AutoYaST
* improved support for AutoYaST Guided Partitioning
https://lizards.opensuse.org/2019/11/22/highlights-of-yast-development-spri…
--
Martin Vidner, YaST Team
http://en.opensuse.org/User:Mvidner
Hi,
there is a discussion about what is so special about YaST:
https://old.reddit.com/r/openSUSE/comments/dsni1k/what_is_so_special_about_…
ciao
Arvin
--
Arvin Schnell, <aschnell(a)suse.com>
Senior Software Engineer, Research & Development
SUSE Software Solutions Germany GmbH
Maxfeldstraße 5
90409 Nürnberg
Germany
(HRB 36809, AG Nürnberg)
Geschäftsführer: Felix Imendörffer
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Orphaned/unneeded and some other package classes were integrated in
Package Groups view (I understand as sort of "meta-groups"). In current
TW (I have now 20191112) there is no more Package Groups - no way to
display this information anywhere else.
Was it really intentional? This was useful functionality.
... there seems to be Repositories - @System - "Unmaintained Packages";
this list looks like what was called orphaned packages in the past. Is
it correct and it is where orphans are shown now?
Still am not sure whether there is something like "unneeded".
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
I wonder was it coordinated with YaST? The first fallout is YaST Users
and Security modules which now default to DES password encryption due to
missing /etc/login.defs.
I am not even sure what the right semantic should be, given that users
now can create multiple files each containing single parameter so
anything done via YaST is not guaranteed to actually have any effect.
https://bugzilla.opensuse.org/show_bug.cgi?id=1155735
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org