January 2013 - openSUSE Features - openSUSE Mailing Lists

[openFATE 306469] "Publish Current State" Button
by fate_noreply＠suse.de 08 Aug '13

08 Aug '13

Feature added by: Stephan Binner (Beineri) Feature #306469, revision 1, last change by Title: "Publish Current State" Button Buildservice: Unconfirmed Priority Requester: Important Requested by: Stephan Binner (beineri) Description: Building packages can take quite some time (and publishing too). While upgrading a whole chain of interdepending packages some can fail to build and leave the repository in an inconsistent and non-installable state => not good to leave the repository in "Publish" state (over night/week-end). Switching from "Not Publish" to "Publish" state AFAIK doesn't trigger immediate publishing but only when some package build finished. It would be very nice to have a "Publish Current State" button which allows one to publish the current package state without having to manually switch publishing state, triggering a fake/unnecessary package rebuild and having to wait/remember to switch back to "Not Publish" state in time. -- openSUSE Feature: https://features.opensuse.org/306469

1 1

[openFATE 305874] Enable peer to peer downloading of patches/software
by fate_noreply＠suse.de 08 Aug '13

08 Aug '13

Feature added by: Johan Kotze (gogga) Feature #305874, revision 1, last change by Title: Enable peer to peer downloading of patches/software Buildservice: Unconfirmed Priority Requester: Important openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Johan Kotze (gogga) Description: It would be great if we could somehow include a peer to peer functionality for the download of patches/packages. This would greatly reduce the number of mirrors required and would increase the performance for many users in countries with limited international bandwidt. I was thinking that we host a torrent tracker on opensuse.org and build a torrent client into zypper/libzypp and allow the user to allocate a portion of disk space for downloaded packages. Most modern systems have ample disk space and should be able to spare around 4GB for downloaded packages. This is also in line with the spirit of community where we help each other out. If it works well, it could also be used to distribute patched internally inside an organization when they deploy SLE. -- openSUSE Feature: https://features.opensuse.org/305874

1 6

[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

[New: openFATE 311085] Enhance Monitoring Software
by fate_noreply＠suse.de 10 Jul '13

10 Jul '13

Feature added by: Lars Vogdt (lrupp) Feature #311085, revision 1 Title: Enhance Monitoring Software Hackweek VI: Unconfirmed Priority Requester: Important Requested by: Lars Vogdt (lrupp) Partner organization: openSUSE.org Description: With the new Nagios forks (icinga, shinken, ...) at the door and the additional tools around them, I think it's time for testing and packaging this stuff to be able to run the best monitoring solution on our own Products without any trouble. So evaluating the current Nagios package and also the forks would be the starting point - the next steps should be to create packages for our distribution and maybe also special documentation, if needed. -- openSUSE Feature: https://features.opensuse.org/311085

1 1

[New: openFATE 308824] Drop appending 127.0.0.2 line to /etc/hosts (incl. related configuration options)
by fate_noreply＠suse.de 09 Jul '13

09 Jul '13

Feature added by: Katarina Machalkova (kmachalkova) Feature #308824, revision 1 Title: Drop appending 127.0.0.2 line to /etc/hosts (incl. related configuration options) openSUSE-11.3: New Priority Requester: Important Requested by: Katarina Machalkova (kmachalkova) Description: For years, SUSE-based products have been appending '127.0.0.2 host.domain host' to /etc/hosts as a convenience for applications which want to resolve the hostname and which thus become irresponsive without active network [1] Localhost IP associated with FQDN however causes various network services (samba, SLP, LDAP, ntp, ... ) to behave oddly [2]. An option in product-wide control files has been introduced so as not to append 127.0.0.2 on server-oriented products (SLES) - FaTE#303875, while keeping user the possibility to override the default in GUI and AutoYaST profile. Nevertheless, even reasonably set default doesn't prevent misconfigurations and user complaints [3] The suggestion is therefore to drop 127.0.0.2 modification of /etc/hosts altogether and drop GUI/control options associated with configuration thereof. These include: * GUI option in YaST installer * XML profile elements in AutoYaST * Variable in product-wide control file (control.xml) * Possibly also sysconfig variable Appending 127.0.0.2 line has always been sort of workaround for flawed (mostly) desktop applications and DNS servers, so rather than providing workaround with plethora of side effects, it'd more reasonable to have affected apps fixed. Bugs have been filed against some of them and fixed already. References: [1] Apps become slow when offline bugs https://bugzilla.novell.com/show_bug.cgi?id=304632 https://bugzilla.novell.com/show_bug.cgi?id=383336 [2] Network services going insane with localhost IP associated with FQDN https://bugzilla.novell.com/show_bug.cgi?id=207392 https://bugzilla.novell.com/show_bug.cgi?id=355608 https://bugzilla.novell.com/show_bug.cgi?id=570108 [3] Even reasonably set default doesn't help https://bugzilla.novell.com/show_bug.cgi?id=510228 -- openSUSE Feature: https://features.opensuse.org/308824

1 21