Hi,
please add the new YaST package yast2-usbauth from
https://github.com/kochstefan/yast-usbauth or
https://build.opensuse.org/package/show/home:kochstefan/yast2-usbauth to
openSUSE Tumbleweed.
This work was initially created for SUSE in 2015. Part of it was the USB
interface authorization for the Linux kernel. It's contained in Linux
since kernel version 4.4. The packages libusbauth-configparser, usbauth
and usbauth-notifier are already part of openSUSE Tumbleweed.
packages from the usbauth development:
- libusbauth-configparser is a library that is used to parse the usbauth
config file.
- usbauth is a firewall against BadUSB attacks. It allows/denies USB
interfaces using a config file. The needed USB interface authorization
is part of Linux 4.4 and newer.
- usbauth-notifier is a graphical notifier for user interaction to allow
or deny USB devices.
- yast2-usbauth: is a YaST module to edit the usbauth configuration file
Thank you.
Best regards
Stefan Koch
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi,
In 15.1 we wanted to switch to using NetworkManager by default for all
desktop installations, replacing the not so obvious magic that only uses
NetworkManager when installing on a Laptop. Only the Server and
Transactional Server installations should keep wicked.
Furthermore, since SLE uses roles for such things, Richard
volunteered to rework Leap's control.xml using roles in Leap too.
The hope was to get rid of the desktop_roles code too.
So far so good:
https://openqa.opensuse.org/tests/759914#step/system_role/1
However, now we lost the ability to install with online repos
enabled. In 15.0 there was a button for that in the desktop selection:
https://openqa.opensuse.org/tests/678918#step/installer_desktopselection/1
In SLE that is covered when registering. There's a popup that asks
whether to enable online repos:
https://openqa.suse.de/tests/2084621#step/scc_registration/6
Since Leap doesn't use registration that popup doesn't exist there.
So now I wonder what alternatives we have. I'd rather like to avoid
introducing this ugly screen again:
https://openqa.opensuse.org/tests/302627#step/installation_mode/1
So any ideas how to get the feature back?
Would it be possible to add the "Configure Online Repositories"
button on the role selection dialog?
Or maybe have the popup of SLE when the system can reach
download.o.o, just without prior registration?
What's easier code wise?
cu
Ludwig
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.com/
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard,
Graham Norton, HRB 21284 (AG Nürnberg)
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi Ken (and yast-devel audience in general).
We already implemented a first prototype of the new partitioner UI which
makes RAIDs partitionable by adapting dynamically the set of buttons at
the bottom of the table (to reflect only actions that apply to the
selected row).
But there are still too many buttons to fit nicely in 80x24. So we
prepared the following gist with (animated) images explaining the
current problems and some possible solutions. We need advise to move
forward.
https://gist.github.com/ancorgs/bf81a230e2a4634df7a05b90a1241116#file-parti…
Cheers.
--
Ancor González Sosa
YaST Team at SUSE Linux GmbH
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Time and time again, NVidia gfx and Optimus users are unable to install without
appending nomodeset to the installer's cmdline.
cf. https://bugzilla.opensuse.org/show_bug.cgi?id=822769 resolved feature
No mention is made in that bug if a feature request was ever filed. The bug
request was to make appending nomodeset easier for users.
This trouble with installation is routinely followed by a new support request,
to resolve problems either with low resolution video modes, or black screens, or
both. e.g.
https://forums.opensuse.org/showthread.php/533157-How-change-screen-resolut…
More often than not, resolving this failure means the helpers must explain that
nomodeset needs to be removed from Grub configuration, and how to go about it,
which means temporarily at the Grub screen, and ultimately via /etc/default/grub
and grub2-mkconfig.
IMO it would be much a better user and support experience, and ultimately better
for openSUSE's reputation, that when the Yast installer finds nomodeset has been
used to install that it *not* be preserved in /etc/default/grub.
Agree? If yes, file this request where, B.O.O., or F.O.O?
If not agree, why not?
OT but related: is anything being done or planned to make it less likely that
nomodeset is necessary for a successful installation for Optimus and NVidia users?
--
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
On 9/24/18 6:37 PM, Rodion Iafarov wrote:
> 1) Will YCP be dropped in foreseeable future, if yes what shall be used
> instead? yaml+ruby?
I might add that this is also about the low-level YCP container classes such
as YCPValue, YCPList, YCPMap, YCPString etc. - and, most importantly, YCPTerm
which is what the UI interpreter uses heavily. It doesn't really use any
"real" YCP stuff, but it revolves around those YCPValue-related container
classes.
Should we decide to drop that completely, we will have to come up with an
alternative which in all likelyhood will work in a very similar way; the UI
interpreter needs some container classes for transporting the UI terms from
the application layer (no matter if it's YCP, Ruby, Perl or Python) to the UI
C++ classes.
The alternative would be to rewrite all UI-related application code
completely, using "new" for new objects and passing their parent as a parameter.
With the amount of UI terms we have all over the YaST code I don't think this
is realistic for the forseeable future. We'd break 99.9% of all YaST code.
Having said that, I don't believe those YCPValue-related classes will go away
in the forseeable future.
The macro player which basically uses YCP "eval" to execute a chunk of code
for each macro segment is another matter. We'll have to think about that.
(I had talked with Rodion about most of this; this is just a recap for those
who were not part of that discussion.)
Kind regards
--
Stefan Hundhammer <shundhammer(a)suse.de>
YaST Developer
SUSE Linux GmbH
GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
On Mon, 2018-09-24 at 15:51 +0200, Ludwig Nussel wrote:
> So any ideas how to get the feature back?
> Would it be possible to add the "Configure Online Repositories"
> button on the role selection dialog?
>
> Or maybe have the popup of SLE when the system can reach
> download.o.o, just without prior registration?
>
> What's easier code wise?
And just to clarify, when Ludwig says 'what's easier code wise', I
think he explicitly means from a narrow "YaST codebase" perspective
If what you propose to solve this problem requires any skelcd-
changes, I volunteer to do all of them, no matter if its a lot,
because I made this mess to start with ;)
ie. This isn't all on you lot, but we do need your help to figure out
the best solution to this sticky problem.
Thanks in advance for your insights & suggestions,
Rich
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org