June 2010 - openSUSE Features - openSUSE Mailing Lists

[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 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 307359] Create openSUSE Specific Branding for WebYaST
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Andreas Jaeger (a_jaeger) Feature #307359, revision 1 Title: Create openSUSE Specific Branding for WebYaST openSUSE-11.2: Evaluation Priority Requester: Mandatory Requested by: Andreas Jaeger (a_jaeger) Description: Create an openSUSE specific branding for WebYaST. -- openSUSE Feature: https://features.opensuse.org/307359

1 5

[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 307116] support hauppauge wintv hvr h900
by fate_noreply＠suse.de 15 Nov '10

15 Nov '10

Feature added by: Josef Siegel (emmentaler) Feature #307116, revision 1 Title: support hauppauge wintv hvr h900 openSUSE-11.2: Unconfirmed Priority Requester: Desirable Requested by: Josef Siegel (emmentaler) Description: There are sources in the source tree which told me that there could be support for that USB device. But nobody seems to be responsible. Would be very nice, if someone could take the chance. -- openSUSE Feature: https://features.opensuse.org/307116

1 1