October 2016 - openSUSE Features - openSUSE Mailing Lists

[openFate 305582] Off-Line one click install (MSI for Linux)
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Duncan Mac-Vicar <dmacvicar(a)novell.com> Feature #305582, revision 1, last change by Title: Off-Line one click install (MSI for Linux) openSUSE-11.2: New Priority Requester: Important Requested by: Duncan Mac-Vicar <dmacvicar(a)novell.com> Partner organization: openSUSE.org Description: Idea from community member Raul Romero. Same concept as MSI packages for Windows but exploiting the One Click Install concept of openSUSE (and therefore inheriting the simplicity, code and security. Basically a compressed file which includes a repository inside, plus one click install information, and a script to trigger the oneclickinstall handler with the data as payload in the script. Therefore is a collection of rpms that can be installed detailed description is here http://en.opensuse.org/OSI There is already a prototype working. Example script: http://dl.getdropbox.com/u/363315/MozillaFirefox.osi This requires some extra features in one click install and other pieces * ability to force OneClick to add the repo (the one inside the compressed file) Additionally I see other features: * ability to suggest an update repo for the installed bundle * support from build service to generate bundles * easy way to generate them locally Out of scope but interesting: * Ablity to trigger a YaST workflow (its own control.xml?) Business case (Partner benefit): openSUSE.org: This solves the business case of distributing service packs, applications, codecs bundles by just downloading a big file, 100% offline, supporting dependencies and repo signatures. -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305582

1 40

[openFATE 306907] Add support for Ksplice
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Stephan Kleine (bitshuffler) Feature #306907, revision 1 Title: Add support for Ksplice openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Stephan Kleine (bitshuffler) Description: KSplice allows it currently to apply most but not all kernel updates without the need to reboot which is especially great for servers. It's backed by a newly founded corporation that continually tries to improve it so hopefully sometime in the future a reboot wont be necessary for any kernel update. Fedora as well as Ubuntu already support it so openSUSE shouldn't stay behind. URL: http://www.ksplice.com/ -- openSUSE Feature: https://features.opensuse.org/306907

1 18

[New: openFATE 310164] Choose Better Wallpapers for SUSE
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Andres Silva (anditosan) Feature #310164, revision 1 Title: Choose Better Wallpapers for SUSE openSUSE-11.4: Unconfirmed Priority Requester: Desirable Requested by: Andres Silva (anditosan) Description: I made a list of Wallpapers that could potentially be on the next version of KDE. http://anditosan.blogspot.com/2010/07/from-land-of-reptiles.html -- openSUSE Feature: https://features.opensuse.org/310164

1 4

[New: openFATE 310163] Remove Welcome Screen on OpenSUSE KDE
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Andres Silva (anditosan) Feature #310163, revision 1 Title: Remove Welcome Screen on OpenSUSE KDE openSUSE-11.4: Unconfirmed Priority Requester: Desirable Requested by: Andres Silva (anditosan) Description: Hey you all. I would first like to thank all of you who have visited this website and looked at the ideas I have posted. I am deeply honored that many of you too have considered these ideas worthwhile and would like to see them implemented. Well, here comes a good one I think. As I was talking to some people on the KDE IRC channel yesterday, there was a comment made about a possible way to orient new KDE users on how to use the desktop. However, I believe that users should be left clues to discover their desktop on their own. There should not be an intro popup or anything like that. Ponder about this for a moment. What can you say, for example, about paintings. Paintings are not "explained" to anyone. You look at it and you get it in your own particular way. That is enough for you and you know what it means. The clues left by the artist are clear enough to your mind that you find meaning in the painting. You intuitively "know" what the purpose of the painting is. Reflect for a moment on this Cezanne and know what it means... REMOVE KDE WELCOME POPUP SCREEN anditosan.blogspot.com -- openSUSE Feature: https://features.opensuse.org/310163

1 8

[New: openFATE 312876] Deny individual users' access to screen-saver settings
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: Per Jessen (pjessen) Feature #312876, revision 1 Title: Deny individual users' access to screen-saver settings openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Per Jessen (pjessen) Partner organization: openSUSE.org Description: This is an extension of feature#312871, but because it's a little more involved than changing a simple default, I thought it would be better to have a separate feature request. The screen-saver settings for time-out and "require password" are security settings that really should not be freely available to the individual user. I propose that we 1) set a reasonable default (60sec, 15sec, always require passwd) (see feature#312871) and 2) only let these settings be modified by someone with root-access. To a regular user, the timeout and "require password" settings should appear "greyed out", clearly indicating "not available". Use Case: Office user - the user is able to select a screen-saver, but the other settings cannot be accessed, accidentally or otherwise. The install or admin person need not change anything to get a sane security setup for the desktop. SOHO or home users - same as above, but the default screen-saver settings may be changed by switching to root access. Business case (Partner benefit): openSUSE.org: This is simply a reasonable security measure, fitting nicely into the overall security-conscious profile of openSUSE. Security measures (firewall, apparmor, encryption etc) are typically accessible only with root-access; it's only sensible that we apply this principle to the screen-saver settings too. -- openSUSE Feature: https://features.opensuse.org/312876

1 10

[New: openFATE 312337] clear /tmp-dir at bootup
by fate_noreply＠suse.de 25 May '17

25 May '17

Feature added by: M K (tux93) Feature #312337, revision 1 Title: clear /tmp-dir at bootup openSUSE Distribution: Unconfirmed Priority Requester: Neutral Requested by: M K (tux93) Partner organization: openSUSE.org Description: Please clear the /tmp-dir at boot-up per default. At the moment this has to be activated manually with every new installation, is there a reason for not doing this out of the box? -- openSUSE Feature: https://features.opensuse.org/312337

1 6

[New: openFATE 309487] Clean out X11 keyboard configuration in YaST
by fate_noreply＠suse.de 24 May '17

24 May '17

Feature added by: Jiří Suchomel (jsuchome) Feature #309487, revision 1 Title: Clean out X11 keyboard configuration in YaST Requested by: Jiří Suchomel (jsuchome) Developer: (Novell) Developer: (Novell) Description: Currently, 'yast2 keyboard' is using kind of strange way of determining which X11 keyboard layout to use. There's a map of internal YaST keyboard names, to which the list of kbd console maps is mapped (like, us.map.gz). Such console map is taken as a parameter for calling /usr/sbin/xkbctrl script, which returns the informations about corresponding X11 keyboard layout (usable for setxkbmap). One problem is that not for all languages, there's a sense to have console map, and because of this situation in YaST, we are using files like ar.map.gz, which are only links to us.map.gz. Other part is that the list of X11 keyboard layouts is part of sax2-tools package which we probably want to drop. New solution would mean that YaST has all the information currently provided by xkbctrl: either by building its own data structure (if there's no other application using it), or using a better way to get the data YaST needs to know. References: https://bugzilla.novell.com/show_bug.cgi?id=603950 https://bugzilla.novell.com/show_bug.cgi?id=601587 -- openSUSE Feature: https://features.opensuse.org/309487

1 16

[New: openFATE 320834] Create a /var/cache subvolume
by fate_noreply＠suse.de 17 May '17

17 May '17

Feature added by: Thorsten Kukuk (kukuk) Feature #320834, revision 1 Title: Create a /var/cache subvolume Requested by: Thorsten Kukuk (kukuk) Partner organization: openSUSE.org Description: On the openSUSE Factory list, somebody found a valid bug in our current setup for snapshots: /var/cache is part of the snapshot. This means: all RPMs used for an update are part of the snapshot and will be deleted only afterwards. This is a big problem if you regular update online, it will eat up your diskspace very fast. We need to add /var/cache to the list of directories, for which we create a subvolume with btrfs. And (that's why I created a FATE and no bug) we need to add something to the release notes, so that customers are aware of this and can create the subvolume at their own for existing installations. Business case (Partner benefit): openSUSE.org: Save disk space by excluding irrelvant/outdated cached data from snapshots. -- openSUSE Feature: https://features.opensuse.org/320834

1 28

[New: openFATE 320819] DHCPv6-PD - wicked
by fate_noreply＠suse.de 11 May '17

11 May '17

Feature added by: James Knott (james_knott) Feature #320819, revision 1 Title: DHCPv6-PD - wicked openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: James Knott (james_knott) Partner organization: openSUSE.org Description: With more & more ISPs providing IPv6 via DHCPv6, DHCPv6-PD support is essential. This is how a router determines the assigned prefix via DHCP. Later versions of dhcpc support DHCPv6-PD, but wicked apparently doesn't. https://tools.ietf.org/html/rfc3633 -- openSUSE Feature: https://features.opensuse.org/320819

1 3

[New: openFATE 319119] drop not functional yast2-ca-management
by fate_noreply＠suse.de 08 May '17

08 May '17

Feature added by: Michael Calmer (mcalmer) Feature #319119, revision 1 Title: drop not functional yast2-ca-management Requested by: Michael Calmer (mcalmer) Partner organization: openSUSE.org Description: yast2 ca-management cannot be maintained anymore. No resources. So let's drop it. -- openSUSE Feature: https://features.opensuse.org/319119

1 12