October 2010 - openSUSE Features - openSUSE Mailing Lists

[New: openFATE 310673] enable showopts before root= on menu.lst default kernel line via perl-bootloader
by fate_noreply＠suse.de 06 Oct '10

06 Oct '10

Feature added by: Felix Miata (mrmazda) Feature #310673, revision 1 Title: enable showopts before root= on menu.lst default kernel line via perl-bootloader openSUSE-11.4: Unconfirmed Priority Requester: Desirable Requested by: Felix Miata (mrmazda) Description: https://bugzilla.novell.com/show_bug.cgi?id=620434#c19</p> <p> In Factory, sometimes root= doesn't work and some experimenting is necessary to get a boot and find out why. e.g. for a long while, root=LABEL= syntax was not working, and still might not be in certain cases. Also, modern root=/dev/disk* syntax makes most kernel lines are longer than the text editor screen is wide (wrapping makes more confusion), which means also /dev/disk entries are too long for human brains to remember for manual typing. And, sometimes troubleshooting requires /dev/sdX# syntax. When dropping back to text mode to edit cmdline and mistake is made, grub doesn't recover nicely, and reboot to restart Grub is often required to retry. So, showopts before root= in gfxmenu would be a nice facility provided via /etc/sysconfig/bootloader and perl-bootloader instead of having to manually change it after each kernel update.</p> <p> inputting on in this typing box is a nightmare. There's no auto-wrap, so everything just keeps moving right until a hard return is input. If this looks insanely formatted, that is why. -- openSUSE Feature: https://features.opensuse.org/310673

1 0

[New: openFATE 309067] Stabelize group handling
by fate_noreply＠suse.de 02 Oct '10

02 Oct '10

Feature added by: Adrian Schröter (adrianSuSE) Feature #309067, revision 1 Title: Stabelize group handling Buildservice: Candidate Priority Requester: Mandatory Projectmanager: Important Requested by: Adrian Schröter (adriansuse) Description: The user management allow also to use groups for permission settings. However, the current implementation is not yet finished. This feature is about to complete it and to allow group permission handling for * attribute settings * request and review handling -- openSUSE Feature: https://features.opensuse.org/309067

1 2

[openFATE 306616] test feature
by fate_noreply＠suse.de 02 Oct '10

02 Oct '10

Feature added by: Michael Löffler (michl_test) Feature #306616, revision 1 Title: test feature openSUSE-11.2: Unconfirmed Priority Requester: Important Requested by: Michael Löffler (michl_test) Description: test feature -- openSUSE Feature: https://features.opensuse.org/306616

1 2

[openFATE 305877] Popularity contest
by fate_noreply＠suse.de 01 Oct '10

01 Oct '10

Feature changed by: 6tr6tr 6tr6tr (6tr6tr) Feature #305877, revision 33 Title: Popularity contest Hackweek V: Unconfirmed Priority Requester: Important openSUSE-11.2: Rejected by Stephan Kulow (coolo) reject date: 2009-09-07 13:57:05 reject reason: No update, too late for 11.2 - and for the future I would rather see it integrated into smolt Priority Requester: Important Projectmanager: Desirable openSUSE-11.3: Unconfirmed Priority Requester: Desirable openSUSE-11.4: Unconfirmed Priority Requester: Important Requested by: Vladimir Nadvornik (nadvornik) Developer: (Novell) Description: We need a feedback about packages that are preferred by users and actively used. Debian already has a tool named Popularity contest (popcon) * reusing popcon will give us results that are directly comparable with Debian and Ubuntu * packagers team can take care of the package * we need a configuration dialog in YaST that is visible enough * we need a server infrastructure on opensuse.org. (There are certain privacy issues, see Debian FAQ for details) References: http://en.opensuse.org/BrainStorming_Prague#We_don.27t_know_which_packages_… http://popcon.debian.org/FAQ http://popcon.debian.org/ http://popcon.ubuntu.com/ Discussion: #1: Michal Vyskocil (mvyskocil) (2009-02-20 12:56:06) The pupularity-contest executable is a simple Perl script, which should be ported to rpm (replacing of dpkg calls by appropiate rpm alternative should be enough). #2: Pavol Rusnak (prusnak) (2009-03-11 15:53:13) (reply to #1) Replacing of dpkg calls with rpm is a no-go, because of the transactions in RPM. I started to work on a rewrite, will post results soon ... #3: Marek Stopka (m4r3k) (2009-03-13 09:28:08) (reply to #2) And here is a result... :-) http://stick.gk2.sk/blog/2009/03/popcorn-popularity-contest-for-rpm/ #4: Jay Mistry (zmdmw52) (2009-03-15 15:36:25) The software equivalent of Smolts Hardware profiler. Results can be uploaded to a dedicated website (such as is for Smolts- http://www.smolts.org/) so that users can see the relative weight/popularity of various commonly-used applications. #7: Carlos Gonçalves (cgoncalves) (2009-07-25 19:03:58) (reply to #4) There is a GSOC project (http://socghop.appspot.com/student_project/show/google/gsoc2009/gentoo/t124…) which is addressing this (Smolt) feature to Gentoo, though the author has been coding this aswell to Debian-based distros and more recently considering RPM distros too. I've been working with him on the client integration since I'm its author, and from my side all I can say is that Smolt sooner or later will be addressing this feature, too, but won't be ready in time for openSUSE 11.2 since feature/version freeze is next week (July 31). #5: T. J. Brumfield (enderandrew) (2009-06-13 21:16:54) During install, there can be a simple checkbox such as "Share hardware/software details with openSUSE servers for profiling." #6: Stephan Kulow (coolo) (2009-06-24 11:29:15) first we need the package in and someone to maintain the server or contact debian if they host other distros too. + #9: 6tr6tr 6tr6tr (6tr6tr) (2010-10-01 20:16:28) + I would actually prefer that things not just have one ranking but: + + 1. Trustworthiness + 2. Privacy + 3. Reliability/Uptime/Speed + 4. Popularity + + I think those are all important and very different requirements. -- openSUSE Feature: https://features.opensuse.org/305877

1 0

[New: openFATE 310659] specify whether bootloader is to be master bootloader for whole system
by fate_noreply＠suse.de 01 Oct '10

01 Oct '10

Feature added by: Felix Miata (mrmazda) Feature #310659, revision 1 Title: specify whether bootloader is to be master bootloader for whole system openSUSE-11.4: Unconfirmed Priority Requester: Desirable Requested by: Felix Miata (mrmazda) Description: Most of my systems are multiboot. As a consequence, some bootloader has already been installed. I should be able to specify that the new openSUSE bootloader being installed will only be used for the new openSUSE system and not any of those previously installed. This would keep the new openSUSE bootloader's menu much simpler, and prevent the need for the installer to hunt for stanzas to add to menu.lst, as well as saving me the often considerable time required to manually remove those unwanted stanzas. Furthermore, I would have NOT be preselected in any case that the new / or /boot is not on the first BIOS disk, and when the new / or /boot is a logical partition. -- openSUSE Feature: https://features.opensuse.org/310659

1 0

[New: openFATE 310657] New user registration improvments.
by fate_noreply＠suse.de 01 Oct '10

01 Oct '10

Feature added by: Adrian Schröter (adrianSuSE) Feature #310657, revision 1 Title: New user registration improvments. Buildservice: Done Priority Requester: Important Requested by: Adrian Schröter (adriansuse) Description: webui shall offer to use the existing api user registration call. admins shall also be able to limit user registration to * deny in general * allow, but require admin approval. -- openSUSE Feature: https://features.opensuse.org/310657

1 0