June 2013 - openSUSE Features - openSUSE Mailing Lists

[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

[New: openFATE 315081] Manual repository release option
by fate_noreply＠suse.de 08 Jul '13

08 Jul '13

Feature added by: Adrian Schröter (adrianSuSE) Feature #315081, revision 1 Title: Manual repository release option Buildservice: Evaluation by engineering manager Milestone: 2.5 Priority Requester: Important Projectmanager: Desirable Requested by: Adrian Schröter (adriansuse) Partner organization: openSUSE.org Description: OBS already supports to release binaries to another repository via releasetarget definition when using the OBS maintenance support. This feature is also useful outside of maintenance, when a staging repository should be created first and the result shall be released to another repository after testing. Therefore we want to extend current releasetarget definition by a trigger="manual" mode. In addition to that we need a command to execute the release process. For example -X POST /build/$PROJECT?cmd=release or for a specified repo only: -X POST /build/$PROJECT/$REPOSITORY?cmd=release the command will return with "invoked" state after successfully creating the event. -- openSUSE Feature: https://features.opensuse.org/315081

1 3

[New: openFATE 315061] improve YaST installer to allow patterns and packages from network
by fate_noreply＠suse.de 08 Jul '13

08 Jul '13

Feature added by: Tomas Cech (sleep_walker) Feature #315061, revision 1 Title: improve YaST installer to allow patterns and packages from network openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Tomas Cech (sleep_walker) Partner organization: openSUSE.org Description: As you probably already noticed, I'm fighting to get E17 as desktop choice in YaST2 installer. To get E17 choice in installer I need to have pattern and packages present on medium which is already more than full. I proposed replacing LXDE with E17, but there are still users who wants to keep it on medium and I agree, that this shouldn't be the way to fix it. Proper fix I believe is patch YaST2 installer to offer packages and pattern from default repository in http://download.opensuse.org/distribution/ if the network is up. Having checkbox 'Enable network repositories' during installation workflow would make this behavior optional and selected by default if the server is reachable. Business case (Partner benefit): openSUSE.org: I also received feedback from MATE maintainer, who would welcome such option as well and I believe there are others too. This is artificial limitation which should have been removed long time ago. -- openSUSE Feature: https://features.opensuse.org/315061

1 10

[openFATE 307765] Debuginfo file system
by fate_noreply＠suse.de 05 Jul '13

05 Jul '13

Feature added by: Ruchir Brahmbhatt (Ruchir) Feature #307765, revision 1 Title: Debuginfo file system openSUSE-11.3: Unconfirmed Priority Requester: Important Requested by: Ruchir Brahmbhatt (ruchir) Description: It would be nice to have internet mountable debuginfo file system just like fedora. This will allow users to get traces from gdb without installing lots of debuginfo packages. This way we can have access to all debuginfo packages without installing them. This will encourage more users to report bugs. Some users may not be willing to install additional debuginfo packages due to lack of enough disk space or willingness to report bugs. -- openSUSE Feature: https://features.opensuse.org/307765

1 2

[New: openFATE 311124] Consolidate faillog, pam_tally, pam_tally2, pam_faillock
by fate_noreply＠suse.de 27 Jun '13

27 Jun '13

Feature added by: Thorsten Kukuk (kukuk) Feature #311124, revision 1 Title: Consolidate faillog, pam_tally, pam_tally2, pam_faillock openSUSE Distribution: Unconfirmed Priority Requester: Important Requested by: Thorsten Kukuk (kukuk) Partner organization: openSUSE.org Description: There are four different ways to track the number of failed logins and react to this: faillog, pam_tally, pam_tally2, pam_faillock. They are all incompatible together and pretty hard next to impossible to configure. Goal: Write one new module "pam_faillog", which replaces all of them. Should be able to read all current databases, supports all features together but uses advanced PAM functionality to make configuration very easy. The module depends on correct behavior of calling application, which means we need some checks if application behaves correct and maybe fix them. -- openSUSE Feature: https://features.opensuse.org/311124

1 3