May 2013 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 314814] Upgrade jack
by fate_noreply＠suse.de 08 Aug '13

08 Aug '13

Feature added by: Steffen Klein (tithrion) Feature #314814, revision 1 Title: Upgrade jack openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Steffen Klein (tithrion) Partner organization: openSUSE.org Description: A new release of jack 1.9.9 is available since 2012-12-10. http://www.jackaudio.org/node/63 Oh, and please ensure it works with current libffado 2.1.0 aka firewire-support. (which the current releases in factory and multimedia:libs don't) Business case (Partner benefit): openSUSE.org: Support for new features and hardware. -- openSUSE Feature: https://features.opensuse.org/314814

1 2

[New: openFATE 314915] Default keyboard layout US English for dutch users (and others....?)
by fate_noreply＠suse.de 08 Aug '13

08 Aug '13

Feature added by: Gertjan Lettink (Knurpht) Feature #314915, revision 1 Title: Default keyboard layout US English for dutch users (and others....?) openSUSE Distribution: Unconfirmed Priority Requester: Mandatory Requested by: Gertjan Lettink (knurpht) Partner organization: openSUSE.org Description: On 12.3 the keyboard layout for the dutch language is US International instead of US English. Those who want windows behaviour can set US International on their desktop, for the system US International is unacceptable. F.e, working in the console is hardly doable. -- openSUSE Feature: https://features.opensuse.org/314915

1 2

[New: openFATE 314916] PHP 5.4
by fate_noreply＠suse.de 08 Aug '13

08 Aug '13

Feature added by: Jorge Hernandez (jurgen73) Feature #314916, revision 1 Title: PHP 5.4 openFATE: Unconfirmed Priority Requester: Important Requested by: Jorge Hernandez (jurgen73) Partner organization: openSUSE.org Description: Hey guys, Please don't let OpenSUSE fall behind, please release PHP 5.4 for OpenSUSE 12.3 and keep it up to date (5.5 is coming soon) Thanks much. -- openSUSE Feature: https://features.opensuse.org/314916

1 2

[New: openFATE 314986] Add razor-qt to openSUSE oss repo
by fate_noreply＠suse.de 08 Aug '13

08 Aug '13

Feature added by: Chris Gnineil (zerum) Feature #314986, revision 1 Title: Add razor-qt to openSUSE oss repo Package Wishlist: Unconfirmed Priority Requester: Mandatory Requested by: Chris Gnineil (zerum) Partner organization: openSUSE.org Description: It would be nice if razor-qt would be included in the standard oss repo. -- openSUSE Feature: https://features.opensuse.org/314986

1 2

[New: openFATE 314467] virtio-scsi backport the sles10
by fate_noreply＠suse.de 07 Aug '13

07 Aug '13

Feature added by: yi li (liyicybertan123) Feature #314467, revision 1 Title: virtio-scsi backport the sles10 openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: yi li (liyicybertan123) Partner organization: openSUSE.org Description: virtio-scsi driver backport the sles10 -- openSUSE Feature: https://features.opensuse.org/314467

1 4

[New: openFATE 313152] Distribution cleanup (smaller disk footprint)
by fate_noreply＠suse.de 07 Aug '13

07 Aug '13

Feature added by: Andreas Jaeger (a_jaeger) Feature #313152, revision 1 Title: Distribution cleanup (smaller disk footprint) openSUSE Distribution: New Priority Requester: Mandatory Requested by: Andreas Jaeger (a_jaeger) Partner organization: openSUSE.org Description: We want to have an as small as default base system (default text install) as possible. For this, I suggest to install a base system and investigate then what can be done to decrease the footprint. One idea is to check documentation (in /usr/share/doc/packages) and move them to doc or devel package (with the exception of license files). Also, we can check whether all dependencies (manual requires) are still correct - or in other words: Does every package that's there needs to be in the base install? Business case (Partner benefit): openSUSE.org: A small base system is important especially for appliances and virtual environments. -- openSUSE Feature: https://features.opensuse.org/313152

1 3

[New: openFATE 310310] Installer partition layout to allow "Whole Disk Usage"
by fate_noreply＠suse.de 07 Aug '13

07 Aug '13

Feature added by: Darryl Miles (dlmiles) Feature #310310, revision 1 Title: Installer partition layout to allow "Whole Disk Usage" openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Darryl Miles (dlmiles) Description: Currently the installer doesn't provide any option for Whole Disk Usage for a single purpose (such as rootfs or swap or /home etc...). Whole disk usage means there is no partition table and that file-system or swap is formatted directly. This has use-cases for virtulization where it is easier for the hypervisor to provision two block devices to the guest, one for rootfs and one for swap. These may come from LVM, SAN, etc... it is easier to manage because resizing either is a straight forward event due to the single purpose of each block device. One possible option to shoe-horn it into the UI would be under the Expert.../Advanced... buttons when either a partition or a disk device is selected. More ideas suggested in the bugzilla link further down this comment. Other possible considerations go with the bootloader options for installing GRUB. It would need to be adjusted to disallow/auto-disable MBR when no partition table is present. But the option still remains to install in the rootfs. Also submitted as ENH in Buzilla please read => https://bugzilla.novell.com/show_bug.cgi?id=628056 "installer doesn't support whole-disk usage", since this contain other comments not found here. -- openSUSE Feature: https://features.opensuse.org/310310

1 6

[New: openFATE 310103] wireless bridge configuration support in sysconfig
by fate_noreply＠suse.de 06 Aug '13

06 Aug '13

Feature added by: Marius Tomaschewski (mtomaschewski) Feature #310103, revision 1 Title: wireless bridge configuration support in sysconfig openSUSE-11.4: New Priority Requester: Important Requested by: Casual J. Programmer (casualprogrammer) Developer: (Novell) Developer: (Novell) Description: Wireless interfaces currently can not be bridged. In Windows XP it is quite easy to create and operate a bridge, saving one to setup and maintain all sorts of route information. It would make sense to support the bridged configuration in sysconfig when hostap implements 802.11c. Relations: - network bridge fails to integrate wlan (ipw3945) with WPA (novell/bugzilla/id: 541817) https://bugzilla.novell.com/show_bug.cgi?id=541817 - Bridge FAQ: I still don't understand!! (url: http://www.linuxfoundation.org/collaborate/workgroups/networking/bridge#I_s…) - Bridge FAQ: It doesn't work with my Wireless card! (url: http://www.linuxfoundation.org/collaborate/workgroups/networking/bridge#It_…) -- openSUSE Feature: https://features.opensuse.org/310103

1 3

[New: openFATE 310491] Add dracut to openSUSE
by fate_noreply＠suse.de 01 Aug '13

01 Aug '13

Feature added by: Luis Medinas (lmedinas) Feature #310491, revision 1 Title: Add dracut to openSUSE openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Luis Medinas (lmedinas) Description: Dracut is suppose to be a replacement for the old initrd tools like mkinitrd. >From the project description, dracut is an initramfs infrastructure. Unlike previous initramfs systems, Dracut aims to have as little as possible hard-coded into the initramfs. It contains specific configuration files for init drivers and includes plymouth support. Dracut advantage seems to be a modern replacement to generate initrd and it's suppose to be easy to use/manage. -- openSUSE Feature: https://features.opensuse.org/310491

1 24

[New: openFATE 309148] boot-process: starting network / dbus with ldap authentification
by fate_noreply＠suse.de 30 Jul '13

30 Jul '13

Feature added by: Alexander Fleischer (afleischer) Feature #309148, revision 1 Title: boot-process: starting network / dbus with ldap authentification openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Alexander Fleischer (afleischer) Description: I asked to file this bug report as feature request: https://bugzilla.novell.com/show_bug.cgi?id=569953 (https://bugzilla.novell.com/show_bug.cgi?id=569953) After configuring LDAP authentification via yast the system needs about 20 minutes to start the dbus-daemon on boot. I got a lot of ldap messages in /var/log/messages like these: Jan 12 12:01:44 w2 dbus-daemon: nss_ldap: failed to bind to LDAP server ldaps://10.0.0.10: Can't contact LDAP server Jan 12 12:01:44 w2 dbus-daemon: nss_ldap: reconnecting to LDAP server (sleeping 8 seconds)... Of course, because network is started after dbus, dbus can't connect to the ldap server, and waits several times until the timeout is reached. Network has dbus as "required-start", so i can't change the startup order and add $network to required-start in the dbus script. My temporary solution is to replace the /etc/nsswitch.conf file with a one without ldap access in /etc/init.d/boot.local and restoring the original one after the network is up. But this is not a clean solution, maybe an extra startup script can solve the problem. -- openSUSE Feature: https://features.opensuse.org/309148

1 2