April 2009 - openSUSE Features - openSUSE Mailing Lists

[openFATE 305313] creating nonexistent directories with Autoyast
by fate_noreply＠suse.de 16 Apr '09

16 Apr '09

Feature changed by: Thorsten Kukuk (kukuk) Feature #305313, revision 8 Title: creating nonexistent directories with Autoyast openSUSE-11.2: Evaluation Priority Requester: Important + Projectmanager: Important Requested by: Uwe Gansert (ug) Description: from bug #429491 It should be possible to create directories just like files with its permissions and ownership. Today it is impossible (using just "files") to put for example /root/.ssh/authorized_keys. To anticipate possible comments, the "file_script" is not IMHO the right way to deal with the problem since it is invoked after writing the file to a filesystem. Yet it may be considered a workaround as of today. Discussion: #1: Federico Lucifredi (flucifredi) (2009-01-23 14:19:55) up for Engineering's comment. Is workaround adequate ? -- openSUSE Feature: https://features.opensuse.org/305313

1 0

[openFATE 306326] mount encrypted /home before user config
by fate_noreply＠suse.de 16 Apr '09

16 Apr '09

Feature changed by: Michael Löffler (michl19) Feature #306326, revision 3 Title: mount encrypted /home before user config - openSUSE-11.2: New + openSUSE-11.2: Evaluation Priority Requester: Important Requested by: Stefan Behlert (sbehlert) Description: Taken from bugzilla, requested by development. When installing with an encrypted /home partition I am informed during user creation that the /home partition is not mounted (see screenshot in bugzilla). What is missing here is the possibility to enter the password for the partition, mount the partiton and continue with the user configuration. Relations: - mount encrypted /home before user config (novell/bugzilla/id: 456004) https://bugzilla.novell.com/show_bug.cgi?id=456004 -- openSUSE Feature: https://features.opensuse.org/306326

1 0

[openFATE 305561] Install Debuginfo Package by build-id
by fate_noreply＠suse.de 16 Apr '09

16 Apr '09

Feature changed by: Stephan Kulow (coolo) Feature #305561, revision 9 Title: Install Debuginfo Package by build-id - openSUSE-11.2: Candidate + openSUSE-11.2: Done Priority Requester: Mandatory Projectmanager: Important Requested by: Jan Blunck (janblunck) Developer: Jan Blunck (jblunck) Description: Since SLE11 we embed build-ids into all binaries. This build-id can be used to match the corresponding debuginfo to a binary file, a running process or a core file. To make it easy for user to install the correct debuginfo, he should be able to run the following command to get the correct debuginfo package installed: zypper install debuginfo-build-id- eb49eeaf82eff32cfbf44d94f9aa8e3cdcf0e461 Discussion: #1: Stephan Kulow (coolo) (2009-02-17 11:17:46) Not sure why agruen is set as engmgr, this is simply some rpm hackery. Put a debuginfo.prov script in place, that checks the file list given and give it all /usr/lib/debug/.build-id files. And it will transform /usr/lib/debug/.build- id/00/d9cff1044033b4781ab47388b422b07cb72708.debug into debuginfo (d9cff1044033b4781ab47388b422b07cb72708). After that you can use zypper install -C "debuginfo (d9cff1044033b4781ab47388b422b07cb72708)" and you get kdepim4-debuginfo installed (11.1-x86_64 example). This is an effort of half an hour without testing. #2: Andreas Gruenbacher (agruen) (2009-02-17 16:15:18) (reply to #1) This should work, and the debug info repository metadata should still remain reasonably small. + #3: Stephan Kulow (coolo) (2009-04-16 10:43:47) + the debuginfo meta data for 11.2 and sle11 contain the build ids. + Zypper support is not implemented, but I don't think it's needed as it + requires a 10 line shell script wrapper that can live very well in + ptools -- openSUSE Feature: https://features.opensuse.org/305561

1 0

[openFATE 306356] Icons in YaST: Use /usr/share/icons/hicolor/ as a fallback
by fate_noreply＠suse.de 16 Apr '09

16 Apr '09

Feature changed by: Michael Löffler (michl19) Feature #306356, revision 3 Title: Icons in YaST: Use /usr/share/icons/hicolor/ as a fallback openSUSE-11.2: Evaluation Priority Requester: Important Requested by: Lukas Ocilka (locilka) + Partner organization: openSUSE.org Description: YaST icons are expected to be in /usr/share/YaST2/theme/current/icons/ directory but the list of icons is fixed because the current is a symlink to the currently installed and selected theme-directory which is different for openSUSE or SLES. If another (e.g., 3rd party) YaST module wants to add its own icon, it has to put it into the current directory which will change when using another YaST theme. The proposal is simple: If an icon is not found in the current theme, try to use /usr/share/icons/hicolor/ as a fallback. Business case (Partner benefit): - 3rd party add-ons with YaST modules, Our own add-ons with YaST modules - (SMT, OES)... + openSUSE.org: 3rd party add-ons with YaST modules, Our own add-ons with + YaST modules (SMT, OES)... -- openSUSE Feature: https://features.opensuse.org/306356

1 0

[openFATE 305317] Default to hidden bootloader menu
by fate_noreply＠suse.de 16 Apr '09

16 Apr '09

Feature changed by: Stephan Kulow (coolo) Feature #305317, revision 7 Title: Default to hidden bootloader menu openSUSE-11.2: Evaluation Priority Requester: Desirable Requested by: Jiri Srain (jsrain) Description: As long as there is no other operating system present (SUSE is the only system), it makes sense to default to hidden bootloader menu (and booting directly). References: http://www.gnu.org/software/grub/manual/grub.html#Hidden-menu-interface https://bugzilla.novell.com/show_bug.cgi?id=425717 + Discussion: + #1: Stephan Kulow (coolo) (2009-04-16 10:34:48) + I like that idea. I guess it's a tiny change for bootloader, but has + possibly some docu impact. -- openSUSE Feature: https://features.opensuse.org/305317

1 0

[openFATE 305641] Bring Puppet to fully supportable status
by fate_noreply＠suse.de 15 Apr '09

15 Apr '09

Feature changed by: Duncan Mac-Vicar (dmacvicar) Feature #305641, revision 17 Title: Bring Puppet to fully supportable status openSUSE-11.2: Evaluation Priority Requester: Mandatory Projectmanager: Mandatory Requested by: Federico Lucifredi (flucifredi) Partner organization: openSUSE.org Description: Dedicate a developer for the duration of the 11.2 cycle to shaking out Puppet on openSUSE, contribute patches upstream correcting integration with our base system, and analyzing what future integration areas (particularly with YaST, but not limited) appear promising. The objective is to walk through the Puppet documentation (http://reductivelabs.com/trac/puppet/wiki/DocumentationStart) Turnbull's book (ISBN 159059978), and test out that things work as they should, patching and sending upstream when they do not. Finally, contribute a small "Puppet on SUSE" document to the community detailing any platform- specific factors (you will see there are a number for other distors already). Additional notes: The plan is to _INSTALL_ the Puppet infrastructure by default. No default-running is planned - I thought it was important to clarify this. Addtionally, Facter needs to be packaged and supportable alongside Puppet. Cft should be packaged, but not default installed, and not the target of this focused infrastructure work in this cycle (i.e. Best effort). Relations: - Feature for 11 GA tech Preview (feature/id: 303687) Business case (Partner benefit): openSUSE.org: The ultimate intent is to integrate a policy management framework into the platform and have it available as default infrastructure. This has a number of consequencies: for one, the ability of third parties, both internal and external, to leverage the policy language for platform management. Secondly, I want to support the Puppet objective of being a pervasive policy language for *NIX, which may or may not be achievable. This combines with the set of enabling management technologies we want to have on the platform as blocks to build on: integrated libraries (libzypp, libstorage, ..), management instrumentation (SFCB, management profiles exposing the libraries wherever possible), Stateless YaST interface (to enable access to configuration facilities), and support instrumentation (the Novell Support Link, formerly known as Aurora and Onstar). Discussion: #1: Federico Lucifredi (flucifredi) (2009-01-08 16:25:48) . #2: Federico Lucifredi (flucifredi) (2009-01-26 18:49:40) As per for phone conversation, this requirement is not only about technology ("Policy framework"), but also about the political decision of what solution to adopt - in which context the technology is not an Engineering decision, but a Business one. I am chosing Puppet on the theory that we will do our bit to help the rise of a cross-*NIX management tool by making it available and supported. If the interest in Puppet contines at this pace, and other things go the right way, we will consider further investment. For now, we just make Puppet (and Facter with it) L3 supported. If the market keeps moving in this direction, then good, we will integrate beyond the "managing by configuration file" scheme, and look at what YaST integration we can do. If it does not, we just keep the L3 package and move3 on. Think of it as Perl - it is on Every *NIX, and if you use it is good if not, it does not hurt. #3: Pavol Rusnak (prusnak) (2009-02-10 15:45:06) I think anicka did some experiments with puppet. + #4: Duncan Mac-Vicar (dmacvicar) (2009-04-15 09:35:35) + Progress note: integration of the community authored zypper plugin for + puppet is integrated (and working) and will be submitted to stable. -- openSUSE Feature: https://features.opensuse.org/305641

1 0

[openFATE 306361] iFolder Trash Can Support
by fate_noreply＠suse.de 15 Apr '09

15 Apr '09

Feature added by: Biswajeet Mahapatra (mbiswajeet) Feature #306361, revision 1, last change by Title: iFolder Trash Can Support Requested by: Biswajeet Mahapatra (mbiswajeet) Description: Trash Can Support for iFolder -- openSUSE Feature: https://features.opensuse.org/306361

1 0

[openFATE 306360] iFolder WebDav Support
by fate_noreply＠suse.de 15 Apr '09

15 Apr '09

Feature added by: Biswajeet Mahapatra (mbiswajeet) Feature #306360, revision 1, last change by Title: iFolder WebDav Support Requested by: Biswajeet Mahapatra (mbiswajeet) Description: Support WebDav in iFolder -- openSUSE Feature: https://features.opensuse.org/306360

1 0

[openFATE 306359] iFolder Mapped Drive Support
by fate_noreply＠suse.de 15 Apr '09

15 Apr '09

Feature added by: Biswajeet Mahapatra (mbiswajeet) Feature #306359, revision 1, last change by Title: iFolder Mapped Drive Support Requested by: Biswajeet Mahapatra (mbiswajeet) Description: Support Mapped Drive -- openSUSE Feature: https://features.opensuse.org/306359

1 0

[openFATE 306358] File Access Layer
by fate_noreply＠suse.de 15 Apr '09

15 Apr '09

Feature added by: Biswajeet Mahapatra (mbiswajeet) Feature #306358, revision 1, last change by Title: File Access Layer Requested by: Biswajeet Mahapatra (mbiswajeet) Description: Users should be able to transparently access files in any file system irrespective of the protocol -- openSUSE Feature: https://features.opensuse.org/306358

1 0