July 2009 - openSUSE Features - openSUSE Mailing Lists

[openFATE 306895] Gnome-main-menu improvements
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Atri Bhattacharya (badshah400) Feature #306895, revision 1 Title: Gnome-main-menu improvements openSUSE-11.2: Unconfirmed Priority Requester: Mandatory Requested by: Atri Bhattacharya (badshah400) Description: For openSUSE 11.2, it would be very useful if gnome-main-menu could be improved feature-wise and also performance-wise. Several common features that need to be implemented are as follows: 1) Right click menu to clear recent documents, recent places, etc in the main-menu slab. Important for privacy purposes. 2) Relabelling of YAST to Administrator settings in the main menu slab. 3) Adding frequently used shortcuts to the gnome-control-centre slab. At the moment the commonly used tasks in the gnome-control-centre only has a shortcut to 'set preferred applications'. Other commonly used shortcuts like user-account prefs, etc might be very useful. Performance-wise the main-menu is a lot faster and responsive today than in 10.3, except during the first startup of the application-browser slab after a restart or log-in. This takes a few seconds, and this time taken increases with increasing number of applications (tested on 11.1). -- openSUSE Feature: https://features.opensuse.org/306895

1 6

[openFATE 306337] Partitioning with non-standard disk geometry
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Herbert Graeber (hgraeber) Feature #306337, revision 1, last change by Title: Partitioning with non-standard disk geometry openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Herbert Graeber (hgraeber) Description: For SSDs it is important to respect their erase block size (usually 128KB). So instead of using the standard sectors per track of 63 and 255 heads Theodore Ts'o suggests to use 56 and 224 instead to get a cylinder size which is a multiple of 128KB. Similar tricks may be neccessary to achive optimal cylinder sizes for devices which are used for raid partitions. It would be useful, to have the ability to specify the values for sector per track and heads in the expert before any partition is defined. For special cases, like SSDs it would nice, if proper values will be suggested. Theodore Ts'os Blog: Aligning filesystems to an SSD’s erase block size (http://thunk.org/tytso/blog/2009/02/20/aligning-filesystems-to-an-ssds-eras…) -- openSUSE Feature: https://features.opensuse.org/306337

1 12

[openFATE 306984] Create a Single way of Managing NIC Devices
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Scott Couston (zcnnnnzc) Feature #306984, revision 1 Title: Create a Single way of Managing NIC Devices openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Scott Couston (zcnnnnzc) Description: In Opensuse 11.1 the decision was made to remove Yast control of Network Manager. This created 2 semi-dependant ways of managing Network Interface Cards, that in retrospect offered poor or impossible singular control. This decision may have had technical merit however it created a huge deal of complication and bugs as a result. At this time KDE4 NM was not available and KDE3 NM was the only form of NM available to this version of openSuse. In the case where NM is selected over IFUP, other dependant Yast Applications offered no control over the NIC and IP itself. Take the small example of the Yast Firewall. If NM was selected over IFUP, the Yast Firewall offered NO control over the IP. If NM is selected over IFUP, the NIC(s) as a devices, offered no control as Yast defines all dependencies over NIC(s) as a device or multiple devices. If NM is selected over IFUP during Installation, there was no facility to input static IP's or effect any control over NM as Installation only offered the user to choose the alternate NM but not configure it. Poor or No testing of a PC that was on a LAN where NO DHCP Services were offered was obvious. Without DHCP Services, it was not possible to Install updates as IFUP could not provide nominated DNS Services. IFUP could only set a static IP, but failed to provide DNS Services despite being present in IFUP's configuration. NM also suffered at the fate of DHCP Services. Despite Static Services being present in NM, the presence of DHCP Services overruled static entries in NM as these were ignored. NM only provided static services so configured, when DHCP Services were Not present. The control over NIC cards became a total IF issue. Any variant from IFUP using DHCP Services and the LAN also providing them, meant we lost control over the NIC(s).* We need to decide IF we need to maintain both IFUP and NM for control over NIC(s) as of 11.1 we offer almost NO control over any variant so configured* The downline application to configure WIFI, VPN, IPV6 etc are all compromised. 2 totally different methods of applying downline services need provision for the rest of further developments. I do not think it is realistic for us to continue to maintain both IFUP and NM as the down line repercussions are so huge and without control over an IP and DNS we might as well stop development. It is not sufficient to depend on DHCP Services always being present as we then assume a condition that may not be set. This would be akin to stating in the"Installation Requirements" and adding a line stating that OpenSuse requires DHCP Services to be present for the software to "Install and Function Correctly" Either we dump NM or IFUP. Certainly unless Yast can control NM it must go OR if we want to take the other down-line services of VPN, WIFI, IPV6; IFUP must go. Request for Comment needs to start, both in the technical requirements of a singular control and the usability of same. The above statements are all supported by various bugs, mostly opened by the author. Any Commnts please? -- openSUSE Feature: https://features.opensuse.org/306984

1 2

[openFATE 306910] Add the possibility to enable Roaming Home Directories in the YaST Samba Client
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Andreas Schneider (gladiac) Feature #306910, revision 1 Title: Add the possibility to enable Roaming Home Directories in the YaST Samba Client openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Andreas Schneider (gladiac) Description: There should be the possibility to enable Roaming Home Directories with pam_csync in the YaST2 Samba Client module. pam-config has support to setup pam_csync. The YaST module has to change the config file (ini) from pam_csync and run pam-config. Test Case: Login to your Active Directory account. Check if the configuration files have been synchronized to the ADS. Use Case: Roaming Home Directories is the missing piece of the SUSE Active Directory Integration. This feature was planned already for SLE10 and should be possible in one of the next SUSE products. -- openSUSE Feature: https://features.opensuse.org/306910

1 2

[openFATE 306992] Zypper dup needs a --lock-vendor <vendor> switch
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Dave Plater (plater) Feature #306992, revision 1 Title: Zypper dup needs a --lock-vendor <vendor> switch openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Dave Plater (plater) Description: When using zypper dup it is very difficult and sometimes impossible to prevent certain packages from changing vendor. I propose a switch which will prevent certain vendors from being changed. Packman for instance has kaffeine and cairo. You have packman kaffeine installed and you wish to stay with the packman version but you wish cairo to stay opensuse. You can either give packman repo a higher priority in which case your cairo will change vendor or you can give opensuse repo a higher priority in which case your kaffeine will change vendor. Performing a "zypper dup --lock-vendor packman" will enable you to have a higher priority opensuse but still keep your packman packages and update with newer packman packages. -- openSUSE Feature: https://features.opensuse.org/306992

1 6

[openFATE 306994] Create a strong DE-neutral system/profiles
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: dmitry serpokryl (dmitry_serpokryl) Feature #306994, revision 1 Title: Create a strong DE-neutral system/profiles openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: dmitry serpokryl (dmitry_serpokryl) Description: it's just a response to the (http://lizards.opensuse.org/2009/07/31/openfate-feature-306967-kde-default) yet another proposed feature which i hope never will be accepted as a default. my response is in the 3-rd comment. suppose that the creation of a more flexible and DE-neutral system/settings/presets could benefit to all SLE/SUSE Users. examples: * pure GTK Desktop * pure Qt Desktop (why not?) * no Mono preset (we can easily use Tracker instead of Beagle and at least gNote/others to wipe out the Tomboy+Company) * no Java preset (mostly targeted to the OOo replacement option by Gnumeric+AbiWord) * Wicd instead of NM * more attention to the low-level core components like kernel, drivers, basic libs and so on. -- openSUSE Feature: https://features.opensuse.org/306994

1 2

[openFATE 306373] revival of openCA
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Stephan Kulow (coolo) Feature #306373, revision 1, last change by Title: revival of openCA openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Hans Witvliet (digi_hans) Description: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.3) Gecko/20060425 SUSE/1.5.0.3-7 Firefox/1.5.0.3 Any chance of reviving OpenCA? In the security manuals, chapter x509, it says that the yast-module for maintaing certificates is nice for small set-up's, but not intented for large roll-outs. OpenCA seems to be right for that job, with (poosible) seperate CA, RA, OSCP, support for smartcards and LDAP, mysql. If i'm not mistaken, Adrian maintained some time ago an old version of OpenCA for openSuSE_10.3. Hence my question: is it possible to re-create it for the 1.0.2 (ten-ten) version of openCA, preferably for openSUSE_11.1 and SLES-11 ? It seems that current verion of OpenCA does build on older versions of openSUSE, but fails to compile on 11.1. (not yet tried on sles11, but expect same results) Relations: - revival of openCA (novell/bugzilla/id: 491024) https://bugzilla.novell.com/show_bug.cgi?id=491024 Discussion: #1: Stephan Kulow (coolo) (2009-04-08 09:11:05) if you can't even get it to compile, it doesn't seem to be that well maintained. So I would think it's not good to rely on security of it. #2: Hans Witvliet (digi_hans) (2009-04-08 16:19:04) To put in perspective... I couldn't complete a compile of the latest version on 11.1. openca offers binaries for fedora, centos, ubuntu and open slowaris. I just tried it on 32/64-bit versions of 11.1, I can try it aagain on older versions. Allthough i just upgraded our whole environment, using our install server with xen farm wouldn't take too long. At work i've got a tough job keeping all the noses point to one direction. But it would be hard to defend sticking with open/sles with considerable effort if it compiles flawless (I kow: seeing is believing..) with others. It seems that OpenCA is the only opensource product in this class, comparing with CASA, yaST, tinyCA, pyCA that are only intended for small scale deployment. And for this particular assigment was specifically asked to evaluate OpenCA, regardless of the environment it runs in, though my first choice would be a sles11-cluster and secondly an open-11.1 cluster. #3: Stephan Kulow (coolo) (2009-04-08 23:58:21) you have two options: a) the openSUSE way: you're free to maintain it in openSUSE:Factory:Contrib (see en.opensuse.org/Contrib) b) the SLES way: you convince your presales contact person that there is no way around The "file an enhancement bug against openSUSE to get a SLES feature" does not work. #4: Hans Witvliet (digi_hans) (2009-04-09 15:22:41) Sorry, if i gave you the wrong impression. imho, openca looks great (from the docu and the live-version) It used to be included 10.0 - 10.3 with the distro itself, and later on it became also available on the OBS (Adrian). I presume that if you got someone who has spent some time before on it, it would be the first one to humbly ask to have a look again, instead of re-inventing the wheel. Personnaly, i work on the R&D department, only doing prototypes and prove-of-concepts and i am happy using openSuSE. Our production department however is using the official SLES-9 and now SLES-10 version. a) So if there is a version on the OBS for open_11.1 i would be happy. b) If it could be incorporated in the list of packages for SLE it would make you happy (sales) c) If the OBS could hold versions for 11.1 and SLE, you would be happier, (sales but no additional packages to officially maintain) Final word about the code: Yes, it is _old_ code, but the only thing that comes close with regards with its features, is the code that comes from AOL: http://www.redhat.com/certificate_system/ And i'm neither eager to switch to rh/fc/ct, nor to suggest a re-write of the 10MB from openCA. Hence my req to revive it on the OBS, anyone would benefit. Or do you have plans to "adopt" the above mentioned GPL-ed java code ;=) -- openSUSE Feature: https://features.opensuse.org/306373

1 3

[openFATE 306779] a better support for Wlan driver
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Claus Rebler (Zunami) Feature #306779, revision 1 Title: a better support for Wlan driver openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Claus Rebler (zunami) Description: i have always a problem to install wlan drivers on opensuse i hab 1 acer laptop 1 hp laptop 1 asus latop and always the sam problem. the system have not the divers. i must after the system installation (opensuse 11.1) over again to install the driver. and then i must hope to find my network (next problem). when i install kubuntu i have no this problem. please make a easy or better wlan support. and after the installtion the system must be run -- openSUSE Feature: https://features.opensuse.org/306779

1 2

[openFATE 306949] Clearing Documents List from GNOME Slab Menu
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Eric Yeoh (yeoheric) Feature #306949, revision 1 Title: Clearing Documents List from GNOME Slab Menu openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Eric Yeoh (yeoheric) Description: There is no feature in openSUSE or SLED 11 to clear recently used documents under the GNOME desktop using the Slab Menu. This presents a possible privacy issue. If there is a way to clear via context-menu will be great. -- openSUSE Feature: https://features.opensuse.org/306949

1 1

[openFATE 306953] yast-GRUB: graphic
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: manuel m (manuel_songokuh) Feature #306953, revision 1 Title: yast-GRUB: graphic openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: manuel m (manuel_songokuh) Description: hello.. i want new grub from yast! i want not change grub from yast but new graphic and little change..i will send you my pictures..but my languange is italian ok? this picture is default of grub from yast opensuse 11.1 64bit (view-source://http//digilander.libero.it/jaoken2/grub-installazione.png) http://digilander.libero.it/jaoken2/grub-installazione.png (view-source://http//digilander.libero.it/jaoken2/grub-installazione.png) this is my idea for new graphic: http://digilander.libero.it/jaoken2/grub-presentaz.png (view-source://http//digilander.libero.it/jaoken2/grub-presentaz.png) this reason..it's for not-espert or neo-user, for not panic during install grub.. now i do an example picture for step-step: http://digilander.libero.it/jaoken2/1-step.png http://digilander.libero.it/jaoken2/2-step.png http://digilander.libero.it/jaoken2/3-step.png http://digilander.libero.it/jaoken2/4-step.png http://digilander.libero.it/jaoken2/5-step.png what do you think about pictures? -- openSUSE Feature: https://features.opensuse.org/306953

1 6