June 2009 - openSUSE Features - openSUSE Mailing Lists

[openFate 305725] Use gettext for gconf schemas translations
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Vincent Untz (vuntz) Feature #305725, revision 1, last change by Title: Use gettext for gconf schemas translations openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Vincent Untz (vuntz) Partner organization: openSUSE.org Description: The translations of all the descriptions of gconf keys in schemas are already in the gettext files of the application. Removing them from the schemas would make the packages smaller and would possibly improve gconf performance in normal usage (ie, outside of gconf-editor, where the descriptions are used). Martin Pitt and I talked about this, and Martin has implemented it for Ubuntu: https://bugs.launchpad.net/bugs/123025 -- openSUSE Feature: https://features.opensuse.org/?rm=feature_show&id=305725

1 5

[openFATE 306310] Improve Section About Keyboard Configuration
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Karl Eichwalder (keichwa) Feature #306310, revision 1, last change by Title: Improve Section About Keyboard Configuration openSUSE-11.2: New Priority Requester: Desirable Requested by: Karl Eichwalder (keichwa) Description: What about explaining here how to add the Euro sign to e.g. the 5 key on the keyboard... And what to do with the 'Win/Start' key. Should it be Meta, Hyper, Super, etc? What is the difference? http://doccomments.provo.novell.com/admin/main?/admin/viewcomment/10258 References: http://doccomments.provo.novell.com/admin/main?/admin/viewcomment/10258 Comment: 8174 http://www.novell.com/documentation/opensuse110/opensuse110_startup/data/ch… Customer email: beheer at vahsen dot nl Customer name: Rob Vahsen -- openSUSE Feature: https://features.opensuse.org/306310

1 2

[openFATE 306508] external checksum for supplied files
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Marcus Meissner (msmeissn) Feature #306508, revision 1 Title: external checksum for supplied files openSUSE-11.2: New Priority Requester: Desirable Requested by: Marcus Meissner (msmeissn) Description: (on behalf of Elmar Stellnberger) I would appreciate the OpenSuse-project to keep sha-1s/md5sums of all valid files as other professional OS vendors do (Microsoft, Apple). I believe the effort to implement this would not be too high; the creation of an automatic cheksum list could be implemented in the build service (see also: https://bugzilla.novell.com/show_bug.cgi?id=491193). To me keeping such a list is the only way to verify that a system is clean because in my case attackers succeeded to alter the checksum table of the rpm database (rootkit was additionally not found by any antivirus sw i.e. clamav, norton, chkrootkit, etc.). Without such a checksum table I had to recreate a plain installation by hand (i.e. some self written script) by redownloading exactly the same realease and package versions from the same source as they had been drawn originally from in order to compare both roots: very cumbersome, laborious (about 2000 packages) and error prone; some packages from Packman differed although they were of same version, release and download URL; others were not available any more. I believe maintaining such a checksum table would be a true win for the Opensuse project in means of security and error reporting. Relations: - provide boot cd to md5sum core system files (novell/bugzilla/id: 491193) https://bugzilla.novell.com/show_bug.cgi?id=491193 -- openSUSE Feature: https://features.opensuse.org/306508

1 13

[openFATE 305946] NetworkManager - Autoselect correct peap version
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Helmut Schaa (hschaa) Feature #305946, revision 1, last change by Title: NetworkManager - Autoselect correct peap version openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Helmut Schaa (hschaa) Description: If no peap version is specified wpa_supplicant will already choose the right one. However, NetworkManager does not make use of that feature yet. It would be much easier for users to select peapversion "Auto" instead of having to know if the authentication server allows version 0 or 1. The peap version selection should still be possible as the user may restrict the connection to a specific peap version. Hence, I suggest a drop down combo with the items "Auto", "version 0" and "version 1". -- openSUSE Feature: https://features.opensuse.org/305946

1 4

[openFATE 306330] Creating .document files for PDF and HTML
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Karl Eichwalder (keichwa) Feature #306330, revision 1, last change by Title: Creating .document files for PDF and HTML openSUSE-11.2: New Priority Requester: Mandatory Requested by: Karl Eichwalder (keichwa) Description: To make PDFs visible in yelp, we need .document file; for more information, see fate#306322. The same is valid for HTML output. All I need is the title in the "Name" entry of a .document file. The rest I'll create at packaging time with my script. "make package" resp. make package-html resp. "make package-pdf" must create these files. As the file name I propose to use $(BOOK)_$(LL).document. -- openSUSE Feature: https://features.opensuse.org/306330

1 4

[openFATE 305851] Include kiwi-ltsp in Factory
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Stephan Kulow (coolo) Feature #305851, revision 1, last change by Title: Include kiwi-ltsp in Factory openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Jigish Gohil (cyberorg) Description: I've been maintaining KIWI-LTSP: LTSP5 implementation on openSUSE using KIWI in server:ltsp Build Service repository, now it is at the stable and production ready state. This is request to include the packages(not all of them) in openSUSE Factory, and possibly 11.3 later. Relations: - Include kiwi-ltsp in Factory (novell/bugzilla/id: 474360) https://bugzilla.novell.com/show_bug.cgi?id=474360 Discussion: #1: Jigish Gohil (cyberorg) (2009-02-10 08:42:08) Should this have gone on https://features.opensuse.org/ ? #2: andrea florio (anubisg1) (2009-02-10 09:16:58) +1 for me... kiwi-ltsp is great and works fine! #3: Shrenik Bhura (sbhura) (2009-02-11 05:20:31) The inclusion will largely serve as an impetus for further development of this great project. With increased exposure, the motivation to deliver a quality project shall also increase. #4: Ken Yap (ken_yap) (2009-02-11 06:31:44) Yes, please include it in OpenSUSE, it will make OpenSUSE more attractive to people who want to build thin client clusters. #5: Stephan Kulow (coolo) (2009-02-11 06:53:23) why not Factory:Contrib? And I agree with #1 Having it in Factory means currently that someone from novell needs to review them and that's why we created contrib where everyone capable can maintain packages that go with a specific openSUSE release. And for having it on the DVD it's a bit too special use case, so it would be online repo only anyway. #6: Jigish Gohil (cyberorg) (2009-02-11 07:00:00) Not on the DVD, but Factory and OSS online repo. Instead of Contrib isn't current location - server:ltsp more appropriate? Idea is to include it officially in the distribution. I am sure we can make a same kind of arrangement we have in place for compiz to maintain this as well. -- openSUSE Feature: https://features.opensuse.org/305851

1 8

[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 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 306321] disk id change in fstab
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Jean-Daniel Dodin (jdd_sysop) Feature #306321, revision 1, last change by Title: disk id change in fstab openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Jean-Daniel Dodin (jdd_sysop) Description: "That basic request is that one or more simple tools be provided to allow a fstab to be automatically converted from /dev/sdaX nomenclature to one of the preferred methods." In other words, its now necessary to use YaST partitionner to change the fstab entry from /dev/sdx to the veeeeeeeeery long disk identification. This is very scary and is now nearly mandatory for updates. So it would be important to have some utility to make only this change in fstab and no other. If possible add the choice to use and set on the fly disk ID. -- openSUSE Feature: https://features.opensuse.org/306321

1 8

[openFATE 306291] ADD ability to launch YaST modules via SystemSettings
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Stephan Kulow (coolo) Feature #306291, revision 1, last change by Title: ADD ability to launch YaST modules via SystemSettings openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Paul Lubetsky (vegeek) Description: It would be better and simplier for novice to have only one configuration panel in the system, both for KDE and general System Administration via YaST. Similiar work was done for gnome: now opensuse has an integrated all-in-one control panel there. I propose to add an Administration tab in systemsettings, which would provide launchers for YaST`s system administration tools. Reproducible: Always Steps to Reproduce: Simply open menu: you`ll find there two different launchers for YaST and SystemSettings. Actual Results: Now SystemSettings and YaST aren`t integrated. Expected Results: User want to do some system administration tasks, he/she opens SystemSettings and opens required configuration tool. Something similiar was in SuSE 10.0 with KDE3.4. Relations: - ADD ability to launch YaST modules via SystemSettings (novell/bugzilla/id: 487611) https://bugzilla.novell.com/show_bug.cgi?id=487611 -- openSUSE Feature: https://features.opensuse.org/306291

1 7