Testing:Features 11.1

From openSUSE

we will put the numbers of the features someone is already working on in the topic, so look there first
scan through the list below and pick one you want to do
announce the number in the irc channel, it will added to the topic
if you finished the test, say it on the channel. Number will be removed from topic again and added to the wiki.

To make it less complicated we should think about that only one person edits the wiki page.

openSUSE 11.1 Feature Test List

Here is the list of openSUSE 11.1 features. All of these features have to be tested if they are implemented and working as expected.

If you want to help testing, select the feature you want to test, edit this page and set it's "Testing Result" to "running" when starting the tests. After finishing the test, please edit the page again and set the result either to "passed" or to "failed".

If the test do not pass, please also create a bug report in Bugzilla (see Bug Reporting FAQ for details) including the "Feature No".

If you are unable to finish the test, please reset the "Testing Result" from "running" to "idle".

Thanks a lot for your support.

YaST DNS module should support creation of all RR types (Feature No: 206)

Category: YaST

Status: ready to test

Test Result: idle

Tester:

Description:

At present using YaST DNS module we can create records of only four RR types. It

should be extended to create all the BIND 9.x supported RR types

Make Fn-F7 work on laptops to switch the internal/external displays (Feature No: 4147)

Category: Mobility

Status: implementation

Test Result: idle

Tester:

Description:

Different laptops have different methods of reporting the Fn-F7 key ("switch the internal/external displays"). We have to make all laptops eventually produce the same X keysym, so that desktops can grab that key and process it. Once the key is pressed, the desktop should scan the available monitors/projectors and set up a reasonable configuration for them.

No root for adding a local printer (Feature No: 4162)

Category: Desktop, Usability

Status: implementation

Test Result: idle

Tester:

Description:

An administrator for a machine should be able to specify whether the user needs

the root password to add a printer.

Security Issues with Suspend and Resume (Feature No: 100243)

Category: Mobility

Status: ready to test

Test Result: idle

Tester:

Description:

Simple request:

For security reasons, the user should - perhaps optionally - get asked

for user password and also for passwords of crypto partitions when the

system wakes up from suspend.

But

Following a summary of a discussion between Vojtech Pavlik, Stefan Seyfried,

Stefan Behlert and Andreas Jaeger:

Best way would be to have an encrypted swap, because swap does

contain sensitive data (including possibly the crypto paritition

password).

Have an encrypted swap. All the time.

While suspending most pages are simply swapped out, and thus

also encrypted.

Then, the rest of memory and nonswappable memory are dumped

out. This would also need to be encrypted, and WILL contain the crypto

partition and cryptoswap passwords.

Initramfs can then ask for the _swap_ password, and initiate

resume with that.

The resume process will overwrite the in-RAM kernel with the

one that knows all the passwords.

We're running.

Encrypted swap.

Encrypted swsusp, passing password on

resume.

Vojtech still believes that it'd be very nice if we could pass in the

password through the bootloader, as the bootloader has a nice graphical

interface, and thus it looks much nicer than doing it in the init

scripts. Also the need to wait until the system asks would be gone.

This doesn't preclude doing resume from initramfs of course. Just moves

the data entry.

Theming by OEM (Feature No: 100246)

Category: OEM Preload

Status: ready to test

Test Result: idle

Tester:

Description:

An OEM might also want to add theming, e.g. icons, wallpaper, and

extra packages.

Easy Setup of Bluetooth Headsets (Feature No: 100301)

Category: Bluetooth, Configuration

Status: implementation

Test Result: idle

Tester:

Description:

Headsets that are connected to the computer using Bluetooth should be easily

configurable and usable for the normal user.

There's a project called 'bluetooth-alsa' that's working on that feature.

But that solution is not in a final state. Best solution would be to have an

ALSA-plugin which allows the connection to the Bluetooth-headset. Such a plugin

can only be created after the ALSA-SDK has been finished by tiwai@suse.de.

The current available solution with bluetooth-alsa requires a kernel-modul

named snd-bt-sco. This should not be part of the 'normal' kernel package but an

extra one. Additionally the programm btsco is currently needed.

It would be nice to have this in 9.3, but a first look at the modules was not

very convincing. We will wait until a sane ALSA-plugin exists before supporting

this.

Configuration using yast should only be considered after we have a final

solution.

Support a verbose logging mode in yast (Feature No: 100386)

Category: YaST

Status: ready to test

Test Result: idle

Tester:

Description:

Create a verbose logging mode in yast, where any action yast performs is logged. Any file yast touches should be logged (to /var/log/YaST2/y2log AND clean up the structure of that log file, to make it easier to read and interpret) and all changes on the systems configuration. The goal is to make it really transparent what yast does.

General Device Handling (Feature No: 110016)

Category: Base System, Hotplug, Storage and Partitioning

Status: ready to test

Test Result: idle

Tester:

Description:

It should be possible to configure any device except the root device (which is handled by initrd / initramfs) by hotplug processes. E.g. LVM or EVMS on devices configured by hotplug should be possible.

Hannes: The main problem is that udev for example has to learn to wait for multiple disks till LVM could be startet. Questionable for the SP1 timeframe

Package history (Feature No: 110205)

Category: Systems Management

Status: implementation

Test Result: failed

Tester: badshah

Description:

There should be a way to view the package origin and history.

Where does the package come from ?

Why was it installed ?

Part of product ? Part of patch ? Manually ?

Which were the previous versions ?

And possibly where did the previous version come from

...

Of course, this would also need a config file history. (A backup of changed

config files is already created during distribution upgrade.)

When is the history cleared ?

Probably at every distribution upgrade.

...

partially passed, does most of the things well. But when a software is manually 
installed by invoking zypper from command-line the history shows installation due 
to solver (empty column, instead of root@host). Yet when called from yast, it 
correctly registers history.)

bnc#442718

OCFS2 Posix compliance - aka: General Purpose OCFS2 (Feature No: 110294)

Category: DATA Center Features, Novell Open Enterprise Server

Status: ready to test

Test Result: idle

Tester:

Description:

Add support for posix ACLs, ext. ATTR, locking capabilities.

YaST Heartbeat Command line support (Feature No: 120045)

Category: Configuration, High Availability

Status: ready to test

Test Result: idle

Tester:

Description:

The YaST Heartbeat module should provide command line interface for easy configuration from shell.

LDAP Server managment API enhancements (Feature No: 120061)

Category: Configuration, LDAP Service

Status: ready to test

Test Result: idle

Tester:

Description:

The perl API of the ldap server component should be enhanced by

the following functions

* delete databases

* acl support (see above)

* ldbm backend support

Command line support for routing settings (Feature No: 120078)

Category: Configuration, Network, YaST

Status: ready to test

Test Result: passed

Tester: mlasars

Description:

The YaST routing module should provide a command line interface

for easy configuration from scripts.

Ability to Ignore Updates (Feature No: 120118)

Category: Desktop, YaST, ZENworks, zypp

Status: ready to test

Test Result: failed

Tester: cboltz

kupdateapplet does not offer an option to do this Bug #442388

Description:

There should be a way to tell the update applet to ignore an update and

not turn red for it. A user might not want to go through the hassle of

downloading a specific package and ignore it but wants to be informed

about further updates.

Use gettext for .desktop translations (Feature No: 300461)

Category: Internationalization (I18N / L10N)

Status: implementation

Test Result: idle

Tester:

Description:

Right now we use .desktop files for GNOME menu.

This should be either replaced or enhanced with a gettext lookup in

desktop_translations - so we can update translations easily.

See feature #110086.

Note that this not strictly a SP1 feature. But we don't need it earlier than

we have the first language update - which might sooner than SP1, but will

be later than GA.

In GNOME, translating .desktop files is not sufficient. There is a list of places, where GNOME carries translations in multi-lingual files: gdm configuration, gdm themes, soundlists, mime-info keys (obsolete), icon themes, emblem descriptions, mime descriptions (freedesktop standard), gconf schemas, gconf keys (autogenerated), dia sheets, gok stuff, background names, xkb maps, gedit tags, gnopernicus presentations, gweather locations, printer names, gnome-about info, bonobo servers

In Xorg: Keymap names

RPM_OPT_FLAGS everywhere (Feature No: 300498)

Category: Package building, Security

Status: ready to test

Test Result: idle

Tester:

Description:

We should make the use of RPM_OPT_FLAGS mandatory for all autobuild packages.

checks for this already exists, but only warn currently.

Integrate Support for openWSman (Feature No: 300594)

Category: CIM

Status: ready to test

Test Result: idle

Tester:

Description:

OpenWSMan is a project intended to provide an implementation of the Web Services Management specification.

WS-Management is the first specification in support of the DMTF initiative to expose CIM resources via a set of Web services protocols.

More information:

http://www.openwsman.org/ ,

http://www.dmtf.org//standards/wsman/ ,

http://intel.com/technology/manage/downloads/convergence.pdf

IPv6 transport for NFS (TI-RPC User-Space Library) (Feature No: 300607)

Category: not specified

Status: ready to test

Test Result: idle

Tester:

NFS over ipv6 was probably reverted after beta2, see Bug #431542 --cboltz

Description:

NFSv4 shall run natively over IPv6.

make "/" mountable ro (Feature No: 300617)

Category: not specified

Status: ready to test

Test Result: idle

Tester:

Description:

Especially in ThinClient-Environments it is desirable, to have only one root-fs for all systems; the same condition also applies for SAN-booting systems and clusters, where all systems should be able to boot off only one image.

This goal can be reached in two ways:

FHS, Chapter 2

Boot from the network

/ is read only and all variable content external to /

Mount Server Home Directory Automatically with Authentication (Feature No: 300967)

Category: Directory Services

Status: implementation

Test Result: idle

Tester:

Description:

When the user logs in, the network-mounted home directory should be mounted.

Printer browser (Feature No: 300969)

Category: Directory Services

Status: implementation

Test Result: idle

Tester:

Description:

Printer browser

Provide a way to easily find printers by searching for them instead of looking at workgroups/computers/shares to locate shares.

The interface will provide a way to search 'all' to create a browse interface similar to what is currently available.

Writer Fields in OpenOffice (Feature No: 300994)

Category: OpenOffice.org

Status: ready to test

Test Result: idle

Tester:

Description:

We need to interoperate with read-only word documents containing special fields (that writer currently doesn't support) that allow you to tab through a word document, entering data [ as if in a simple web form ], and then print / file the document.

Evolution SOAP performance (Feature No: 301016)

Category: Evolution

Status: ready to test

Test Result: idle

Tester:

Description:

Performance and other IMAP/SOAP protocol usage issues

IMAP protocol usage fixes - DESIRABLE

http://bugzilla.gnome.org/show_bug.cgi?id=206061 has complete information. The issue lies in the amount of internet-bandwidth that is being consumed by the IMAP provider in Evolution.

GW Protocol usage issues: - MANDATORY

Performance issues - Mailer (MANDATORY)

Incremental Message-Loading

Instead of waiting for all the messages to be loaded. Load messages as they arrive. (50 at a time)

Memory Usage

For GW read-cursor ALL and IMAP refresh_info a lot of memory is used. Typically O(n) amount of memory is used where n is the number of mails. This has to be reduced to a constant value, say, K.

No interface available to get the list of items deleted after a given timestamp

No interface available to get the count of items in a container - mails in a folder

Use getItems instead of getItem to reduce the number of round-trips to the server - thereby reduces the time to fetch-mails. However, this might lead to memory build-up, which should be considered.

Improved performance in main menu, app browser and control center (Feature No: 301038)

Category: Aesthetics, Applications, Desktop

Status: ready to test

Test Result: passed

Tester: badshah

Description:

Improved performance in main menu, app browser and control center

performance of main-menu and application-browser have improved since 11.0 improved, could do with    
speeding up the very first time application-browser is started after reboot though.

Accessible Yast (Feature No: 301084)

Category: Accessibility, Systems Management, YaST

Status: ready to test

Test Result: idle

Tester:

Description:

Leverage Yast-gtk to provides the ability to make the system configuration accessible.

Configure firewall to accept bcast replies (Feature No: 301134)

Category: Configuration, Security, YaST

Status: implementation

Test Result: idle

Tester:

Description:

Currently firewall cannot be configured to accept replies for the hosts broadcasts. It brings several limitations:

- network cannot be scanned via the SLP protocol

- Samba network browsing does not work

Switching firewall off is no way even in trusted networks, due to mobility of some hosts, which may bring malware to the network.

The best solution would be to add support for accepting bcast replies to iptables. YaST can do some hack solution for its purposes (scanning network via SLP).

There is some discussion in bzilla about this topic.

the DASD section in an autoyast profile can't be changed via pre-script (Feature No: 301193)

Category: AutoYaST, Storage and Partitioning

Status: ready to test

Test Result: idle

Tester:

Description:

it would be nice if one could change the DASD section for s390 in the autoyast profile via pre-script

There is no openSUSE for system z - this will be tested by mmichna on SLES11

CJK: Chinese measurements (Feature No: 301291)

Category: OpenOffice.org

Status: ready to test

Test Result: idle

Tester:

Description:

We should layout pages based on char/line measurements not absolute cm, for familiarity.

Modify the paragraph dialogs and rulers to match.

Run online update during autoinstallation (Feature No: 301298)

Category: Systems Management

Status: ready to test

Test Result: idle

Tester:

Description:

Currently it there is no direct way to run online update (non-interactively) during autoinstallation. Adding the call of inst_you.ycp to yast2-online-update should be easy, but the challanging part is to solve restarting of YaST during autoinstallation.

During standard installation, online-update might require reboot (after the installation of kernel update) or restart of YaST (after updating YaST packages) - in both cases the installation succesfully continues: after the reboot it goes to next installation step, after YaST restart it runs the online-update step again (because there might be some patches left).

Heartbeat: Leverage openAIS infrastructure (Feature No: 301322)

Category: High Availability

Status: ready to test

Test Result: idle

Tester:

Description:

openAIS is a standards-based and "widely" adopted messaging infrastructure, providing virtual synchrony and other features. This should replace the legacy messaging service in Heartbeat 2.x. The intent is to make the cluster stack more reliable, easier to maintain by leveraging a standard library, and easier to integrate with other software also using openAIS (like some Device Mapper storage targets and other cluster-aware applications).

While the messaging layer switch should be straightforward, openAIS does not provide quorum, nor "ping" members. Switching messaging layers also has upgrade implications and certainly requires extensive QA.

Detect available Kerberos and LDAP Servers during Installation (Feature No: 301340)

Category: Initial Configuration (2nd Phase of Installation), Installation, User Authentication

Status: ready to test

Test Result: idle

Tester:

Description:

During installation, while setting up user authentication, YaST should try to detect if there are an LDAP and/or Kerberos Servers available in the Network and offer the user to configure those Servers as the authentication source of the system.

The detection of LDAP and Kerberos Servers e.g. is possible by looking up DNS SRV records. Addtionally SLP could be utilized as well (e.g. if DNS didn't reveal anything).

It also seems possible to detect what type of directory is used (OpenLDAP, eDir, Active Directory) by quering the root-DSE and start the corresponding configuration workflow (e.g. samba-client if the detected directory is AD) based on that detection.

Branding: provide the ability to modify the default screensaver (Feature No: 301475)

Category: OEM Preload

Status: ready to test

Test Result: idle

Tester:

Description:

Our distribution(s) should provide a way to modify the default screensaver to reflect corporate branding or OEM partnership.

sysconfig should try using BIOS-provided ethernet device names if available (ETH-device reordering switched off by default - kernel/boot option) (Feature No: 301528)

Category: not specified

Status: ready to test

Test Result: idle

Tester:

Description:

From Matt Domsch:

Dell PowerEdge 1950, 1955, 2900, and 2950 servers, with 2.6 kernels, enumerate

their onboard ethernet NICs "backwards" from what the BIOS presents. (i.e.

BIOS names devices NIC1 and NIC2; the kernel names those devices eth1 and eth0,

reverse of expectations). This is primarily due to way the motherboards are

physically routed, where in a depth-first search of the PCI tree, NIC2 is found

first, then NIC1; whereas in a breadth-first search of the PCI tree, NIC1 would

be found first. We also have reports of some HP and Sun systems behaving

similarly. This has been discussed on the linux-pci mailing list, where I

proposed a kernel patch to address this, which caused additional problems for

people with other systems.

SLES10 sysconfig has a nice method in udev + rename_netiface where it assigns

persistent names to devices after being discovered for the first time. I want

to hook into that initial discovery, and run an external program to query the

hardware for what names it would recommend for the network devices, and then

use those names. If the 30-net-persistent_names.rules file exists, that gets

used, otherwise it falls into this new path.

I'll have legal approval to release this external program, bios_dev_name, under

the GNU GPL v2 shortly, but wanted to start the conversation here. I'll upload

a patch to the /etc/sysconfig/network/config that adds a BIOS_DEV_NAME_POLICY

option where the user can specify one of several naming policies, and the patch

to /lib/udev/rename_netiface which calls bios_dev_name.

Branding: provide the ability to modify the YaST theme (Feature No: 301794)

Category: OEM Preload

Status: ready to test

Test Result: idle

Tester:

Description:

Our distribution(s) should provide a way to modify the YaST theme to reflect corporate branding or OEM partnership.

Drop support for C/H/S BIOS disk access (Feature No: 301805)

Category: not specified

Status: ready to test

Test Result: idle

Tester:

Description:

This affects the bootloader only.

Yast2-bootloader and perl-Bootloader should always use force-lba when writing grub configs. The generic MBR code should also drop C/H/S support in favour of being able to boot from logical partitions.

very old BIOSes (pre-Pentium?) without LBA support will not be able to boot this installation

broken BIOSes still in existence which support LBA but do not report it will be able to boot

we do not have to deal with C/H/S geometry mismatches of partitions or bootblocks anymore, this is no longer a problem

the space currently used in the MBR for this legacy support can be utilized for more useful things like booting from logical partitions

Support all EFI platforms - was: Grub2 support for EFI BIOS (Feature No: 301882)

Category: Base System, Booting

Status: ready to test

Test Result: idle

Tester:

Description:

Intel is pushing EFI instead of traditional BIOS systems for x86 (specifically for x86-64). Apple's new xServer line (and Intel based laptops/desktops) are *only* EFI based, and recently some opportunities to run SLES on Apple Intel based hardware have surfaced. Apparently Grub2 has had a great deal of work recently to support booting EFI. eLilo also has had some work to support this. Apple is willing to supply hardware to SUSE Labs to help with this effort.

ext4 Support in Basesystem (technology preview). No YaST- or Installer-Integration (Feature No: 301897)

Category: Filesystems, Installation

Status: ready to test

Test Result: idle

Tester:

Description:

The base system should support ext4. This means especially support in e2fsprogs. I'm not sure if other tools need support as well.

Whole software management stack should warn about oudated update repo (Feature No: 301904)

Category: Package and patch repositories, Product and Registration Handling, Update, YaST, zypp

Status: ready to test

Test Result: idle

Tester:

Description:

The whole package management stack (command line tools, notification applets, GUI package manager) should warn if no update source at all is configured or an update source does not get updated anymore (see [1], [2] for real life trouble).

Public directory support for encrypted home directories (Feature No: 301923)

Category: not specified

Status: ready to test

Test Result: failed

Tester: jeffery/cboltz

Description:

There are many directories such as ~/.vacation, ~/.procmail, ~/.forward, ~/public_html and especially ~/.ssh that are not able to be accessed when the user's home directory is encrypted as per fate #253 and the user is not logged in. We should have a solution that allows these directories to be made accessible when the user is not logged in.

<jeffery> notlocalhorst, 301923 works as expected. I created new user with encrypted home. 
Logged in as that user and created index file in public_html and then logged out. Installed 
apache2 and then logged in as another user and tested http://localhost/~encrypteduser/ to server 
that index.html page

<cboltz> After some more discussions/testing with original tester <jeffery>, we have come to the conclusion this feature is "broken by design"[tm] https://bugzilla.novell.com/show_bug.cgi?id=442524

Make Suggested, Recommended and Required Packages Visible (Feature No: 301930)

Category: Pattern Deployment, Systems Management, YaST

Status: ready to test

Test Result: failed

Tester: badshah

Description:

Currently the pattern dialog only shows a list of all packages but it does not show which ones are suggested/recommended or required. I would like to see the packages in e.g. different colours or a different font to visualize which are which.

Show list of applications using device when its busy and can't be unmounted (Feature No: 301934)

Category: Desktop

Status: implementation

Test Result: failed

Tester: zonker

Description:

Show list of applications using device when its busy and can't be unmounted. Currently you receive a generic "Busy" error message with no clues as to what to do to solve the problem.

dolphin just shows device busy, doesn't tell me which apps / files are in use

Firstboot Editor (Feature No: 301946)

Category: OEM Preload, YaST

Status: ready to test

Test Result: idle

Tester:

Description:

To improve configurability of YaST-firstboot, a module in YaST to edit all its options would be nice

YaST-firstboot is is an important feature for systembuilders, who deliver systems that require final configuration steps at the customer.

The module should also be able to integrate with an autoYaST profile (ie. autoYaST does the steps to enable firstboot automatically after the installation procedure)

Role based YaST (Feature No: 301960)

Category: YaST

Status: ready to test

Test Result: idle

Tester:

Description:

Currently YaST always asks for root password every time any operation is requested. This is annoying mainly in the consumer and desktop area. Also granting root rights to every user who wants to manage only a small part is a security hole.

The goal of this feature is to allow users without a root password to perform certain management tasks on the system. Still we need to maintain an acceptable degree of security on the system.

Some use cases are:

See also FATE #302522: PackageKit, and FATE #304493: PolicyKit Master feature

One user might have different rights in terms of management tasks

Users can be in groups where one group shares a set of management rights

Users rights must be granted by root or an other entitled user with granting rights

Users and Groups must be manageable in YaST

Correct device mapping in case windows is installed on the second HD (Feature No: 301994)

Category: Booting

Status: ready to test

Test Result: idle

Tester:

Description:

If windows is installed on a second harddisk, and linux on the first disk, the device mapping needs to be changed by grub to make windows think it's on the first disk.

We've got quite some bugs about this, meanwhile

This needs to be detected and reflected by a menu.lst entry like this:

###Don't change this comment - YaST2 identifier: Original name: windows###

Category: not specified

Status: implementation

Test Result: idle

Tester:

Description:

IN SLES 9, we had CKRM, which is not present in SLE10. We need a replacement,

because the functionality is still requested by our customers. (And is present in Solaris.)

Control Groups allow similar functionality in recent 2.6 kernels, we must make them

useful in SLE11, possibly extending them to cover most of CKRM / Solaris Zones functionality.

zypper - rug command parity (Feature No: 302148)

Category: YaST, zypp

Status: ready to test

Test Result: idle

Tester:

Description:

Zypper as replacement for rug needs to be fully compatible on the command line level to rug.

Only exceptions to this parity are commands which can only be used in ZENworks environments.

The need for this feature derives from the fact we want our customers be able to still use their scripts they might have developed on rug technology with Code 10 deployments.

Please remark that mainly the user/role based functionalities are not available right now and need coverage the latest for SLE11 timeframe. Deliverable of this feature is also a clear documentatory statement on which of the rug commands are available or no longer available with zypper.

Please also refer to feature #301960

See comparison tools at: http://w3.suse.de/~emap/comparison-cli-software-management.odt

KDE 4.1 Integration into openSUSE 11.1 (Feature No: 302155)

Category: Desktop, Installation, Package and patch repositories

Status: implementation

Test Result: passed

Tester: badsha

Description:

KDE 4 should be ready for openSUSE 11.1.

- decide which KDE 3.x parts to keep

- docu needs to be informed about the plan

- translation as good as it gets

- for Beta1 we decide which KDE4 Apps make it into 11.1

- we'll have a mix in icons as KDE4 comes with a new icon set (oxygen)

KDE 4 integration is going good, apart from a few bugs reported at bugzilla, so i guess this is passed

Make zypper support wildcards or regular expressions (Feature No: 302193)

Category: zypp

Status: ready to test

Test Result: passed

Tester: Dave Plater

Description:

It's pretty handy to be able to i.e. do:

zypper install 'beryl*'

...to install all the beryl* packages, or, say:

zypper install 'kde*Messenger'

I notice that this will be an issue if zypper is meant to handle local/HTTP/FTP

RPMs, so perhaps the wildcards can only be activated when you use quotes, as

above. I believe APT/Smart handle it this way, too.

Make it possible to use variables in repository urls. (Feature No: 302196)

Category: Systems Management, YaST, zypp

Status: ready to test

Test Result: failed

Tester: Dave Plater

Description:

Most repository's URLs consist of the SuSE version, for example

http://download.opensuse.org/distribution/10.2/repo/oss/

Lots of users add third party repositories and thus may like it to replace 10.2

with a variable which always changes to the installed SuSE version, for example

$SUSEVERSION gives back 10.2. After upgrades to new SuSE versions, the user

would not have to readd and / or change his third party repositories.

A URL would then look like

http://download.opensuse.org/distribution/$SUSEVERSION/repo/oss/

Use and choose persistent device names for disk devices (as opposed to partition devices) (Feature No: 302219)

Category: Booting, Device Handling, Storage and Partitioning, YaST

Status: ready to test

Test Result: idle

Tester:

Description:

/dev/disk/by-id/scsi-SATA_SAMSUNG_SP1614CS01XJ20Y233091-part1 -> /dev/sda1

/dev/disk/by-id/scsi-SATA_SAMSUNG_SP1614CS01XJ20Y233091 -> /dev/sda

yast2-bootloader uses disk devices in several places, most importantly in the mapping between BIOS devices and Linux devices ("device.map") and as the specification of the MBR as the target device for stage1 for some bootloaders (lilo). A mapping to a selected persistent device name is needed here.

Because yast2-storage already handles the mapping of partition device names, and yast2-bootloader uses this information then, it seems most logical from a user perspective to be able to select persistent device names for disk device names with yast2-storage as well.

improve wireless kernel driver power savings (Feature No: 302345)

Category: NetworkManager, Power Management

Status: ready to test

Test Result: idle

Tester:

Description:

Wireless driver should set the device into a powersavings mode while not used.

The old request about unloading drivers is deprecated:

The wireless card (ipw2200) consumes about 1W of power in my notebook, even if I "Disable Wireless" in NetworkManager.

Unloading the kernel module manually, and later loading it manually works like a charm (at least with the ipw2200 driver and saves power.

Do not stop some init scripts during shutdown (Feature No: 302375)

Category: Desktop

Status: ready to test

Test Result: idle

Tester:

Description:

As discussed during the dist meeting 2007-06-21, it would be good if we had a way to disable most init scripts from being stopped during shutdown.

I guess insserv and startpart need to be modified for that.

Collecting hardware information (Feature No: 302445)

Category: Product and Registration Handling, Systems Management

Status: implementation

Test Result: passed

Tester: badshah

Description:

Gathering information about the system hardware is a long standing request in order to better plan and decide on requirements.

SMOLT project

request participation

----

This feature request the inclusion of the smolt package into the distribution

UI to schedule wakeups (Feature No: 302448)

Category: Desktop, Power Management

Status: implementation

Test Result: idle

Tester:

Description:

UI to easily set and manage scheduled wakeups of the system:

e.g. user can trigger "suspend-to-disk until ..." -> shows up dialog

to enter one-time or repeating wakeup triggers.

This is request by EnergyStar specification.

Make thermal management more robust and architecture independent (Feature No: 302452)

Category: Linux Kernel

Status: implementation

Test Result: idle

Tester:

Description:

Evaluate possiblities to make current ACPI thermal management more robust and architecture independent.

Robustness:

Currently thermal (fan, thermal, power resources) management can easily get confused if e.g. the BIOS decides to switch state behind the back of the kernel (which could happen after a suspend, or if BIOS decides to switch e.g. fan states).

ThinkPad-laptop module already has a watchdog, checking fan activity.

Evaluate possiblities and check whether it makes sense to implement a system wide, maybe even architecture indepent thermal watchdog. Maybe there are already approaches in the hwmon layer. Henrique Holschuh already posted some ideas here: http://marc.info/?l=linux-acpi&m=117821469108441&w=2

Interoperability - Architecture independence

Evaluate how general ACPI functionality (in this case thermal specific) could be made available for all architectures. I am thinking about using and/or extending hwmon/sensors interfaces and let ACPI kernel layer make use of it. Also the passive cooling mechanism (reduce CPU frequency on a thermal limit) will also get interesting for other archtitecures (maybe there already exist arch dependent implementations for ARM or other archs?).

Package management must adapt to (repo/system) changes (Feature No: 302453)

Category: Product and Registration Handling, Systems Management, YaST, zypp

Status: ready to test

Test Result: idle

Tester:

Description:

Fate #301224 and #301225 already cover the "what to do if hardware changes" case.

However, package management need support for a more generic use case - changes in repositories or the system

A just-added repository provides drivers for already installed hardware.

A just-added repository provides additional support for a requested language.

A system was installed from CD - omitting recommended (optional) packages. Such package should be added once a repo providing them is available.

useful

Update of the ISC dhcp packages (server, client, relay) (Feature No: 302480)

Category: DHCP Service

Status: ready to test

Test Result: idle

Tester:

Description:

- A significantly enhanced Failover protocol implementation, which:

: - Implements MAC Address Affinity to reduce the frequency of : clients being assigned new IP addresses; : - Supports the assignment of failover-protected addresses to : legacy BOOTP clients; : - Implements a dynamic lease reservation system that provides : improved accounting of the use of fixed address assignments, : by allocating fixed addresses out of the pool of dynamic : leases; and : - Further improves tools and reduces operator oversight : necessary for maintaining a functioning system. : - Support for DHCP Leasequery, and the VIVCO/VIVSO options, which : makes easy and comfortable integration with DOCSIS devices and : the environment in which they are used. : - Management of class and subclass statements via OMAPI. : - Several server configuration options related to dynamic DNS : behavior : - Other new configuration functions, including "execute()", : which runs a shell command from within a dhcpd or dhclient : configuration file

Our dhcp package includes a dhcp-3.0.2-extended_option_environment.patch (dhcdbd support),

adding a "-x" option to the dhclient, that conflicts with a new "-x" option in dhcp-3.1.x version.

Possible solution would be to use "-X" for extended_option_environment and adopt the patch,

because of changes in the internal implementation of the option hashes. Further, it may also

require adoption of the NetworkManager code.

Another patches from our dhcp package can be adopted without problems (done).

sync GPT and MBR on MacBook (mactel) (Feature No: 302485)

Category: Booting, YaST

Status: ready to test

Test Result: failed

Tester: Camm

Description:

on multiboot setups on MacBooks and other mactel machines, using a combination of GPT and MBR is pretty common (and necessary if you either want to use grub or are also using Windows)

for installation on these machines we need to offer a way to sync the GPT to the MBR whenever a change to the GPT is made.

There exists a patch for parted to do just this (see bugzilla#220839) and also the sources of refit (refit.sourceforge.net, tool gptsync).

TESTERS EXPERIENCE: ended up corrupting both MBR partions on testers Macbook Pro (penryn). Difference between GPT and MBR was one cylinder difference between MBR partitions and marked space on GPT. rEFIt gptsync brings error after install of Error: Analysis inconclusive will not touch this disk.

Handling of licenses and confirmations in ZYPP (Feature No: 302516)

Category: Systems Management, zypp

Status: ready to test

Test Result: idle

Tester:

Description:

Current handling of licenses and confirmations could be improved. (We use for maintenance update patches "licences" tag due to its better semantic.)

If you decline a license(confirmation), patch update is set to taboo. But if another patch triggers packages from patch with declined confirmation by dependency solving these packages are selected. This is a logicial behaviour per se, but it does not really match the uses cases.

This feature is triggered by bug #223667:

(initially reported in bug 222829, comment #24)

I run YaST2 online_update to install the kernel test updates.

I clicked "Ãœbernehmen" (continue/apply) to install the updates. Then I

answered the dialog reminding me of a reboot after the kernel update with

"Abbrechen" (cancel).

After this, kernel-default was dropped in as auto-dependency

I clicked "Abbrechen" and now see the following:

- the _patch_ "Test kernel update" is taboo

- the patches "perl-Bootloader" and "kernel module packages" are selected for

installation

- the perl-bootloader package was marked for update ("Aktualisieren")

(so far, everything is ok. Now to the big problem...)

- some kmp packages (those I have installed) were marked for update

- the kernel-default _package_ was marked for update - but I had explicitely

rejected it and the _patch_ is marked as taboo.

Expected result:

- kernel-default should not be marked for update

- the kmp packages should also not be updated because they depend on the kernel

update

I'm just syncing the y2logs and a solver testcase to www.cboltz.de/tmp/

(filename y2logs-tabookernel-222829.tar.bz2, too large for bugzilla)

Sidenotes:

- I'm going to update to RC1, so if you want me to test something, you have to

be fast ;-)

- workaround: set the kmp patch to taboo also

- maybe the solution is to make the kmp patch depend on the kernel patch

We need a relationship between a license/confirmation text an various resolvables to avoid agreeing multitimes to same license in one run.

It needs to be clear to which resolvables a license is related.

If license is declined, all related resolvables needs to be set to taboo.

It might be usefull to have a attribute to a license/confirmation if it needs to be displayed during installation, update (via patch) or both.

Create yast2-power-management-Module for server (Feature No: 302521)

Category: Power Management, Systems Management, YaST

Status: ready to test

Test Result: idle

Tester:

Description:

The YaST interface for Powermanagement (and other features) must not be dropped. Please consider, that servers not usually have a GUI, so that configuration via YaST is essential.

As GREEN-IT is one of the major components for Code 11, we have to take care, that we enforce our capabilities in that area, not drop.

Use PackageKit for Updater Applets (Feature No: 302522)

Category: Package management, Systems Management

Status: ready to test

Test Result: passed

Tester: badshaj

Description:

PackageKit

role based software management

Role Based YaST

Testing 302522: partially passed, difficulties with packagekit in kde-update-applet, 
will file bugs tonight. No problems with gnome-update-applet yet.
done with factory updated packagekit (version 0.3.9), and not the bet4 live-cd one (version 0.3.7).

Certificate store for key management (Feature No: 302530)

Category: Applications, Desktop, Evolution, Firefox, NetworkManager, Security

Status: implementation

Test Result: idle

Tester:

Description:

Customers are complaining that our desktop applications are putting their security certificates at risk. By requiring the use of certificate keys in file form is exposing them in a way they many deem unacceptable. We have received the urgent request on several occasions over the past months to provide a real 'desktop' certificate management solution for SLE.

Many have expressed the strong need to use non-exportable private keys certificates on SLE which is not possible today. This alone should be a reason enough to introduce certificate store use on SLE.

Applications that have been identified as certificate consumers that would need to be integrated:

Will create separate fate entries for each application integration.

"Appropriate key management has been a key issue for many of our potential customers. The fact that we require them to store certificates in plain files on our file systems is killing them. That for Wireless security, file system encryption, Email signing, VPN login or others. Getting a solid key management solution across all open source projects that compose SLE seems long overdue to me (VPN client, NetworkManager, Evolution, OpenOffice.org, Firefox, ...)" -- Guy Lunardi

-

"Indeed, I've been urging that our desktop security efforts focus on strong key management for about a year and a half. It would be nice if we could kick-start this with efforts to bring our Linux desktops up to par with Windows on key management for encrypted storage." -- Crispin Cowan

- NetworkManager (wireless network certificates)

: - NetworkManager (wired network certificates) : - NetworkManager (VPN certificates) : - Evolution (content signing) : - Firefox : - OpenOffice.org (content signing)

Add DMRAID support to SLES Installer (Feature No: 302565)

Category: not specified

Status: ready to test

Test Result: idle

Tester:

Description:

Add DMRAID support to SLES installer. The SuSE autoyast installer needs to

see and install SLES to SW RAID volumes, using DMRAID.

Provide more settings in YaST LDAP Browser. (Feature No: 302858)

Category: Systems Management, YaST

Status: ready to test

Test Result: idle

Tester:

Description:

YaST LDAP Browser could offer at least a checkbox for using crypted connection. The point is that the module can be used to browse different LDAP server than the one configured by LDAP client and the TLS settings might be different.

TabletPC: allow user to config tablet for TabletPCs while install (Feature No: 302888)

Category: Initial Configuration (2nd Phase of Installation), Installation, YaST

Status: ready to test

Test Result: idle

Tester:

Description:

Currently the user can only configure the graphic card while installation (2nd phase of install). For users of TabletPCs it would be usefull to be able to configure also the Tablet of a machine at this point (instead of finish the install, login as root, start sax2, configure tablet, logout and maybe reboot X/system).

It's easy to detect if a machine is a TabletPC via HAL: system.formfactor.subtype='tabletpc' on /org/freedesktop/Hal/devices/computer

In this case simply add something like for graphic cards. Currently it's maybe not needed to select a config by default. Let the user select the correct one from the Tablet section of SaX2

MHTML: open mhtml archives from local store (Feature No: 302911)

Category: Applications, Desktop, Firefox

Status: implementation

Test Result: idle

Tester:

Description:

Our Firefox MHTML implementation shall be able to open MHTML content hosted on a local drive.

This could prove very useful for debugging purposes for mockingbirg in particular.

Improved argument handling for zypper (Feature No: 302919)

Category: CIM, Systems Management

Status: ready to test

Test Result: passed

Tester: badshah

Description:

Please improve argument handling on the zypper command line.

zypper install foo

foo

--name

--capability

-

be generous in what you

accept, and strict in what you send

zypper in foo-1.2-3

zypper in foo-1.2

zypper in foo

zypper in foo = 1.2-3

-

zypper in opensuse:foo

-

To be discussed on opensuse-softwaremgmt and cross-checked with other tools like smart and yum.

use the raw meta-data cache to save downloads (Feature No: 302924)

Category: Systems Management, zypp

Status: ready to test

Test Result: idle

Tester:

Description:

At least for http, zypp shouldn't download a file which already is (unchanged) in its meta-data cache again. This will most probably need to make the media back-end aware of the raw cache. Also, this feature can be implemented keeping the rpm file caching in mind (FATE #302159).

Synchronize X11 keyboard setting with console (Feature No: 302925)

Category: YaST

Status: ready to test

Test Result: idle

Tester:

Description:

"Yast2 keyboard" launches the sax2 module which changes only Xorg config.

either the user should be informed with a popup to run also "yast keyboard" to

change the keyboard setting for text mode,

or it should be handled internaly in sax2 : f.ex. a checkbox "adapt keyboard

for textmode"

Installation In An IPv6 Environment (Feature No: 302926)

Category: Booting, Installation

Status: ready to test

Test Result: idle

Tester:

Description:

Currently, the InstSys does not set up IPV6 networking, so IPv6-only resources cannot be accessed during the first phase of the installation.

load the ipv6 module, and

when in an IPv6 environment, use DHCPv6 to figure out which DNS servers to use.

Support for --nodoc option in ZYpp commit as a policy (Feature No: 302952)

Category: Package and patch repositories, Systems Management, zypp

Status: ready to test

Test Result: passed

Tester: dl9pf

Description:

Usecase:

a made a great effort to put a minimal x11 system on a quite old machine with

enough ram but just 2GB of storage. getting a bigger disk is not an option. it

runs with a CF card in an environment that kills harddisk. I ended up with just

70MB of free space or so. eventually I decided to delete

/usr/share/doc/packages/* as its contents are useless to me, its just docs and

in my case about 150MB large.

Problem:

When updating, rpm is not able to unpack the files in the doc directories because they don't exists.

Thin clients and virtualization will lead to stripped down images and we can see the usecase above to appear.

The 'commit' part of the software management should support some policy flags,

one of them being '--nodocs'

Medialess update (Feature No: 302956)

Category: YaST

Status: implementation

Test Result: idle

Tester:

Description:

As discussed in Prague, I'd like to see a serious evaluation of a medialess update.

What I'd like to see is a binary to download (in doubt from media) in the installed system. That one would gather information about the system and the wanted update, writes basically an autoyast profile, adopts the system as needed and kexecs into the new kernel to update the system without further user interaction.

It's very unclear to me what problems arise from doing it this way, so I don't suggest doing it at any prize.

Combined "where am I" page (Feature No: 302957)

Category: Installation, YaST

Status: ready to test

Test Result: idle

Tester:

Description:

Our (openSUSE) statistics show that most of our users are not native english speakers. So I'm blindly assuming they do not have a english keyboard either and do not live in an english speaking timezone.

So I want the first page to be not just the language in a blue box, but to have _one_ installation page with language, timezone and keyboard selection.

These selections should depend on each other, so depending on where I click first the others change.

To have a good looking addon, I picture the timezone selection as picture and not as fullscreen list boxes.

YaST2 Storage Library to support a process lock so it can't be used by two processes at the same time. (Feature No: 302971)

Category: Storage and Partitioning, Systems Management, YaST

Status: ready to test

Test Result: idle

Tester:

Description:

Assuming that the storage library currently used underneath of YaST in future might/will be used by YaST and CIM and ... this library has to be prepared to either refuse or properly handle different concurrent requests from different ressources at a given time.

Define Smart Card support (Feature No: 302981)

Category: Security, YaST

Status: ready to test

Test Result: idle

Tester:

Description:

There is lot of Smart Card devices (readers, cards) and a lot of possible applications (signing, online signing on web, GPG, secure login, secure remote login, secure VPN, banking, credit card processing, eID card acceptance, entry systems, PKI).

Each of them have specific requirements and may require work on setup and testing. Not all features are implemented in Linux (for example credit card processing is possible only with readers of Security Class 3, but most of those readers have no Linux support).

Many of Smart Card applications may be important in the enterprise.

We need to define Smart Card support matrix: Which devices are supported in SLE and which smart card enabled applications are working and tested on Server and/or Desktop.

It means providing of information, which card rearers are tested and working and which potential limitations these readers have (e. g. pinpad is supported, display is supported, EMV terminal mode is supported,...).

The same is valid for cards: Each card OS and model has to be tested with each particular application or interface and we have to provide information, which use cases are supported for each card model. Hopefully card interface are well standardized (only one interface for chip cards in two variants exists for contact chip cards, situation is becoming clean in contactless cards as well) and card matrix could be well independent on reader matrix.

Note: To provide official support for some use cases, QA probably should have special test sets (e. g. for testing eID cards we need a testsuite including testing eID card and ID verification access to government database).

Smart Cards in OpenSUSE

Category: Debugging, Linux Kernel

Status: ready to test

Test Result: idle

Tester:

Description:

This is an addition to fate #301538.

Kdump should always be run from the initrd. The current method of mounting the root filesystem and calling the dump scripts from it should be removed. Mount the root filesystem of a crashed system means that eventually the filesystem needs to be repaired while running the crash kernel.

Therefore all the scripts and tools necessary to support the following dump methods must be available in the initrd that is used by the crash kernel:

- Network Dump: send the dump across the network via different methods (NFS, ssh, ftp, iSCSI, ATAoE)

- Disk Dump: save the dump to a plain block device somewhere on the system

- Filesystem Dump (not recommended): save the dump to a file in a filesystem

Finally, while the size of the initrd is growing, the prereserved memory for the crash kernel can hopefully be shrinked.

VFS hooks for per-filesystem permission model (Feature No: 303048)

Category: Filesystems, Linux Kernel

Status: ready to test

Test Result: idle

Tester:

Description:

Right now, the vfs uses the permission() inode operation for asking

filesystems whether certain operations like creating or deleting a file are

allowed before the file is actually created or deleted. It asks in terms of

combinations of the read, write, and execute permissions relying on the

semantics those have in POSIX.

IN order to allow specific filesystems to implement other permission

models such as NFSv4 ACLs for improved interoperability, we need additional

vfs hooks that the vfs will use if defined by the filesystems, which will

enable filesystems to control when file creates and deletes are allowed.

yast2-ldap-server: Support for /etc/sysconfig/openldap settings (Feature No: 303058)

Category: LDAP Service

Status: ready to test

Test Result: idle

Tester:

Description:

YaST2 ldapserver should be able to change the /etc/sysconfig/openldap settings. E.g. offer to enable OPENLDAP_START_LDAPS when the user configures SSL Certificates (Bugs #336199 and #338952 requested this).

LDAP Server TLS Setting (Feature No: 303165)

Category: LDAP Service

Status: ready to test

Test Result: idle

Tester:

Description:

If setting up an LDAP server TLS settings shall be created if the default server certificat exists.

AutoYaST support for Kdump (Feature No: 303263)

Category: AutoYaST, Debugging, Linux Kernel, YaST

Status: ready to test

Test Result: idle

Tester:

Description:

It should be possible to set up kdump during the installation with AutoYaST. I.e. the same information that is entered interactively in the Kdump module for YaST should be configured in the XML profile.

Especially it's necessary to add the correct crashkernel parameter in the bootloader configuration and to install the right packages.

Include a friendly graphical user interface for Subversion (Feature No: 303292)

Category: Desktop, Usability

Status: ready to test

Test Result: idle

Tester:

Description:

Several requests have been made to include a graphical user interface for Subversion.

As part of a customer/developer focused SLE11, we should identify and introduce a good solution for Subversion access.

This is related to bug b.n.c. 198498

VMware open source tools (Feature No: 303293)

Category: Virtualization

Status: ready to test

Test Result: idle

Tester:

Description:

Request to include VMware's (open source) open-vm-tools.

VMware will provide:

code under an open source license (preffered: "GPLv2 or v3", license should not say: "GPLv2 or later")

SRPM packaged in openSUSE buildservice (as test for internal autobuild). We need an internal maintainer anyways, but this will make it more easy.

beta-testing for SLE 10 SPx

L3 support for SLE 10 and SLE 11 lifetime

Avoid Duplication of YaST NFS client and Expert Partitioner (Feature No: 303326)

Category: NFS Service, Storage and Partitioning, YaST

Status: ready to test

Test Result: idle

Tester:

Description:

Remove YaST2 NFS client module completely and merge its functionality with expert partitioner

Make YaST2 NFS client module a specific view for partitioner

Bootloader configuration should allow persistent/default kernel parameters (Feature No: 303348)

Category: CIM, YaST

Status: ready to test

Test Result: idle

Tester:

Description:

It is typical to share many kernel options (such as vga mode) between different

kernels. Not an expert on grub, but it seems that it doesn't have such a

feature. Debian has chosen to fit various options into comments of menu.lst. A

sample:

## ## Start Default Options ##

## default kernel options

## default kernel options for automagic boot options

## If you want special options for specific kernels use kopt_x_y_z

## where x.y.z is kernel version. Minor versions can be omitted.

## e.g. kopt=root=/dev/hda1 ro

## kopt_2_6_8=root=/dev/hdc1 ro

## kopt_2_6_8_2_686=root=/dev/hdc2 ro

# kopt=noapic acpi=off root=/dev/mapper/bork-newroot ro

## default grub root device

## e.g. groot=(hd0,0)

# groot=(hd0,0)

## should update-grub create alternative automagic boot options

## e.g. alternative=true

## alternative=false

# alternative=true

For example, my motherboard has a problem which wouldn't let it boot without

the noapic option. The extra options make the kernel upgrade safe.

Better Beagle Acceptance (Feature No: 303367)

Category: Searching

Status: ready to test

Test Result: idle

Tester:

Description:

There have been several discussions on the public openSUSE mailing lists, e.g. http://lists.opensuse.org/opensuse-factory/2008-01/msg00157.html where people complain about resource usage or garbage from beagle.

I suggest that we analyze the current situation and check where are real problems and consider solutions. One option would be to make it easier for users to not enable beagle on their systems.

Note: The feature request is about getting a better acceptance by our users of our indexing technology - and therefore let's figure out what are the problems they are hitting in real life.

PCIE ASPM support (Feature No: 303373)

Category: Linux Kernel

Status: ready to test

Test Result: idle

Tester:

Description:

PCI Express ASPM defines a protocol for PCI Express components in the D0

state to reduce Link power by placing their Links into a low power state

and instructing the other end of the Link to do likewise.

Our client who ship a huge mount of SLED need to do the battery saving. So they would like to have this function in our kernel by default.

Network setup tools (Feature No: 303386)

Category: Network, NetworkManager

Status: ready to test

Test Result: idle

Tester:

Description:

This is a "meta feature" - that requests to define the requirements for setting up and maintaining network connections on a server running a CODE11 product.

Today we have a set of traditional bash-scripts and we have NetworkManager to deal with network settings. The scripts will need to undergo a basic rework in order to ensure future maintainability and to cover new functionality together with virtualized systems and more complex setups (VPNS) etc.

Please comment.

arptables support (Feature No: 303394)

Category: Security

Status: ready to test

Test Result: idle

Tester:

Description:

The kernel supports ARP firewalling (firewalling based on ARP addresses

and mangling of ARP addresses) for hosts and bridges since quite some time.

But we don't have a package for the arptables package to configure it

on the command line. ARP firewalling would be a nice feature for SLES11.

I actually think we used to have one in 10.1 (http://www.novell.com/products/linuxpackages/suselinux/arptables.html)

but 10.3 has it dropped.

http://ebtables.sourceforge.net/

testcases and test setups for perl-Bootloader (Feature No: 303444)

Category: Booting, TPM/TCG, YaST

Status: ready to test

Test Result: idle

Tester:

Description:

The perl-Bootloader code to update various boot configurations during update of a kernel RPM has made us trouble for 3 products (SUSE Linux 10.1, 10.2 and 10.3) now.

I learned that there are no regression tests and no automated testsuite.

To avoid a fourth product release with again updates breaking bootloader configurations, a testsuite and testsetups are Ship Stoppers.

Button order, positioning, labeling in YaST (Feature No: 303446)

Category: YaST

Status: ready to test

Test Result: idle

Tester:

Description:

The button order, positioning and labeling in YaST is a long and sad story.

Currently some of the modules are only using two buttons in their overviews but the majority uses three buttons in their overviews.

To clean up the design of our modules and to take away confusion from the user I suggest to use two buttons for overview and edit dialogs: OK and Cancel.

The only case where we need three buttons are complex workflows like wizards when the user adds something.

This is the only case where we need three buttons: Back, Next, Cancel.

As labeling I suggest to use "Cancel" and "OK" because they are commonly used, especially in desktop environment.

The button order should be consistent with the desktop.

That means: KDE button order (OK/Cancel, Back/Next/Cancel) for KDE desktop and GNOME button order (Cancel/OK, Cancel/Back/Next) for GNOME desktop.

Other desktops like ncurses should use either KDE or GNOME.

As the modules run in a framework called wizard.ycp we wouldn't even need to touch every module but just modify the framework.

Please take a look at some mock ups (with dummy content) at:

http://en.opensuse.org/Image:Yast_navigation.png

http://en.opensuse.org/Image:Yast_navigation1.png

Simplifiying Software Management (Feature No: 303458)

Category: Package management, Systems Management, YaST

Status: ready to test

Test Result: idle

Tester:

Description:

Actually this is a leftover from last year's discussion about software management :-)

Online Update

Software Management

Add-On Product

Automatic Online Update

Community Repositories (not in SLES)

Installation into Directory

Media Check

Online Update Configuration

Patch CD Update

Software Repositories

unclear wording and meaning (What'S the difference between online update, automatic online update and online update configuration?)

inefficient working as 10 modules need to be processed by the users mind

unclear workflows (e.g. selected community repositories appear in software repositories)

Merging "Add-On Product" and "Community Repository" module into "Software Repositories" module to have one module for "Add Software Sources". If a user wants to add a new repository this could look like this:

What is different about "Add-On-Product"? From the first look it seems to me that is contains exactly the same steps and UI as add software repository

Why are we using "Software Repositories" in openSUSE and "Installation Sources" in SLES? There should be a unification.

What about Merging "Patch-CD" into "Software Management" module?

What about merging Online Update and Automatic Online Update?

How to deal with the NCC-registration module? Currently it is called "Online Update Configuration" in openSUSE and "Novell Customer Center Configuration" in SLES. I guess the term "Online Update Configuration" was chosen to avoid the term "registration" but it is highly confusing in combination with the two other online update modules.

One possibility would be to merge the registration module into either "Online Update" module or "Software Management" module.

As the new YaST control center doesn't contain a "Miscellaneous" category what about moving "Autoinstallation" and "Installation Server" into the "Software" category?

What about "Vendor Driver CD"? Can this be included into software repositories?

Redesign of Local Security Module (Feature No: 303472)

Category: YaST

Status: ready to test

Test Result: passed

Tester: cboltz

Slightly different to the screenshot below (list on the left instead of tabs), but looks good :-)

Description:

Currently the settings of each profile are scattered into 5 different screens. This means that the user has no idea how many pages are before him and where he can look for special settings.

So I suggest to use tabs to display these settings to him.

This could look like:

http://en.opensuse.org/Image:Redesign_local_security.png

<jeffery> I have a related bug to this security module: https://bugzilla.novell.com/show_bug.cgi?id=442552

System to be more robust and reliable in DHCP controlled environments (like Hotels, Airports, ...) wired and wireless (Feature No: 303474)

Category: DHCP Service, Network

Status: ready to test

Test Result: idle

Tester:

Description:

It is a common experience of people like Roger Levy, Gerald Pfeifer, Scott Bahling and MgE that SLE* and openSUSE are sometimes "unreliable" in DHCP controlled environments. "unreliable" here means that Windows works perfectly while SLE* or openSUSE simply do not find stuff like Gateway, DNS-Servers or the like. This applies for wired and wireless environments.

Gerald has some logfiles.

MgE has the "impression" that this usually happens if the router is not configured perfectly and information like Gateway or DNS-Servers are not transmitted to the client. In this case (proposal!) our system should assume, that DHCP-Server=DNS-Server=Default-Gateway.

Drop evolution-specific NTLM patch in OpenLDAP libraries (Feature No: 303480)

Category: Evolution, LDAP Service

Status: implementation

Test Result: idle

Tester:

Description:

A few years ago (NLD9 timeframe) a patch was added to our OpenLDAP library packages, that adds hooks to allow Evolution to authenticate to the LDAP interface of Exchange. This patch is of no use to any other application as it adds no real functionality, just hooks. The authentication mechanism itself is implemented completely inside Evolution. The patch was only accepted under the condition that it is tried to cooperate with the OpenLDAP upstream to integrate the patch (or some similar functionality), this has never happened.

Work with upstream to integrate the current patch. The chances to get the patch in its current for accepted seem quite low,

as it is to specific to Evolution. A more generic approach has to be found

discussion

mentioned

Current Exchange/Active Directory has support of various other standards based authentication mechanisms that are supported through the stock OpenLDAP libaries or cyrus-sasl (e.g. GSSAPI, DIGEST-MD5). Evolution could be enhanced to support those.

Go back to Evolution's old approach and ship Evolution with it's own private build of a patch OpenLDAP librariy

Acoustic signal for bootloader when booting from installation medium (Feature No: 303481)

Category: Booting, Installation

Status: ready to test

Test Result: passed

Tester: niim

Description:

SLED and openSUSE are partially usable for visually impared users. And Marco is

working on more improvements.

But one major problem for people who cannot see the screen is the start of the

installation. They cannot deal with grub, because there is no braille support

at this time.

Therefore we need an acoustic signal when grub menu appears on the screen.

The rest of the installation can then be done via braille device.

Would be nice if we can get optional beep when grub menu appears also at normal

bootings.

DumbTab widget for NCurses (Feature No: 303491)

Category: Storage and Partitioning, YaST

Status: ready to test

Test Result: idle

Tester:

Description:

The ncurses version of YaST does not have a proper Tab-widget or a similar widget. Qt and Gtk version have it.

New YaST widget: table with multi-select functionality (Feature No: 303492)

Category: Storage and Partitioning, YaST

Status: tested

Test Result: passed

Tester: Jan-Simon

Description:

Currently in a table only one item can be selected. A widget should be introduced into YaST where from a table arbitraty rows can be selected.

The solution could be a Table widget with multiple selections or a MultiSelectionBox widget with columns. We want this

to look nice.

Build libreiserfs into parted (Feature No: 303510)

Category: Filesystems

Status: ready to test

Test Result: idle

Tester:

Description:

Parted does not presently support ReiserFS without being rebuilt with libreiserfs. Until recently, reiserfs was the default filesystem choice for SLE. On both running systems as well as on the rescue CD, parted does not include support for reiser. Can we add this, please?

Move parts of installation to separate image (Feature No: 303513)

Category: Installation

Status: ready to test

Test Result: idle

Tester:

Description:

Currently we have modular inst-sys used for localizations (FATE #302955). We could make the base installation system even smaller by moving some other parts to separate images (mostly servers) and load them on the fly. This would make the default installation system smaller and this installable on machines with less RAM (and faster on another ones).

Xvnc server (loaded in case USEVNC/VNC=1)

SSHD server (loaded in case USESSH/SSH=1)

Qt (if TEXTMODE=1)

...

/lbin/load_extension qt

Provide some predefined CUPS policies (Feature No: 303515)

Category: Printing

Status: ready to test

Test Result: idle

Tester:

Description:

Currently we provide only the "default" policy in /etc/cups/cupsd.conf.

I suggest to provide some more predefined policies.

For example one totally secure "paranoid" policy

and one more open "relaxed" policy

and one totally open "allowanything" policy.

The reason behind is that with predefined policies

it would be possible to offer the admin clear and simple choices

in printer setup tools which level of security versus ease of use he likes.

Furthermore we would know what exactly which policy allows so that for example

the GUI of a printer setup tool could adapt depending on which policy

is actualy used by the cupsd and/or which operation policy is actually

set for each print queue. If an unknown (i.e. selfmade) policy is used,

the GUI could show an info message and fall back to whatever

seems to be reasonable in this case.

Finally it might be possible to get rid of evil hacks

like in the Novell iPrint Client "sl" (security low) package

which silently replaces the default settings in cupsd.conf

with insecure settings via RPM postinstall script.

For background information about CUPS policies see

http://www.cups.org/documentation.php/policies.html

Default NTP Setup (Feature No: 303520)

Category: Installation, Systems Management

Status: ready to test

Test Result: failed

Tester: Lorenzo Paulatto (paulatz)

Description:

A Yast pane should prompt for NTP set up, which should be configured by default, but of course can also be disabled there.

Reason of failure:

If the network is active, but the NTP protocol is blocked by a firewall then the installation (at least from live CD) will hang forever (or for a very long time). The only possible solution to install the system has been to unplug the network cable - which caused the network to not be configured automatically during installation.

A reasonable timeout should be waited, after that yast2 should proceed without NTP.

Resolve dependencies after ignoring package download failure (Feature No: 303527)

Category: Systems Management, zypp

Status: ready to test

Test Result: idle

Tester:

Description:

YaST and Zypper should run the solver before resuming installation if download of a package fails and the user chooses to ignore that package. Currently YaST continues withough solving which makes the ignore button useful only if the user knows how the missing package will affect the system.

Include Empathy (Feature No: 303528)

Category: Desktop

Status: ready to test

Test Result: idle

Tester:

Description:

Adding Empathy to openSUSE 11 when installing GNOME.

Empathy is a Telepathy based IM program for GNOME.

http://live.gnome.org/Empathy

It is currently packaged in the telepathy project in OBS, along with its dependencies.

delta.rpm support when installing from rp-md and susetags (Feature No: 303531)

Category: zypp

Status: ready to test

Test Result: idle

Tester:

Description:

For allowing updating changing repositories, like openSUSE Factory, we would like to have the possibility to support delta.rpms directly in libzypp. So upgrading a package would download only the delta.

We need to define and to support how delta.rpms get added to the repository meta data for rp-md and susetags.

The new solv format shall support it as well.

Compress cracklib password database (Feature No: 303536)

Category: Security

Status: ready to test

Test Result: failed

Tester: cboltz

/usr/share/cracklib contains about 10 MB
cracklib changelog says compression was disabled again:
* Mo Sep 01 2008 mc@suse.de
- do not zip the dict by default. A check takes too long.
  The support for zip'ed dicts is still available

Description:

The cracklib password database is 10MB uncompressed and 400KB compressed. We need to store it compressed for small images.

Avant Window Navigator (Feature No: 303541)

Category: 3D Accelerated Desktop, Desktop

Status: implementation

Test Result: idle

Tester:

Description:

Avant Window Navigator (Awn) is a dock-like bar which sits at the bottom of the screen. It has support for launchers, task lists, and third party applets.

http://wiki.awn-project.org/ or

http://launchpad.net/awn

YaST LDAP Server module should offer to start CA-Management to create a Server Certificate (Feature No: 303546)

Category: Directory Services, LDAP Service, YaST

Status: ready to test

Test Result: idle

Tester:

Description:

Currently the LDAP Server Module only offers to import an existing certificate. We should consider to let the user start the CA-Module in order to directly create a new certificate.

Grub: limit device.map to devices detected by BIOS Int 13 (Feature No: 303548)

Category: Booting

Status: ready to test

Test Result: idle

Tester:

Description:

Grub is only able to handle a device map with <= 8 devices, thus we need to limit the No. of devices, as in case of multipath or other external storage, the number can be much higher, and Grub will fail then.

So we have to limit the device.map to disks with BIOS int 13 Ids.

Redesign of Autoyast Module (Feature No: 303552)

Category: AutoYaST, YaST

Status: ready to test

Test Result: idle

Tester:

Description:

Navigation within the autoyast module is currently extremly confusing.

A suggestion for redesign can be found at: http://en.opensuse.org/Image:Redesign_autoyast.png

using the categories from YaST Control center instead of a tree on the left side

using the layout of the installation proposal to display current settings and change them. Instead of "Expert" tab a tab called "Source" is used, which allows the user to edit settings directly. this way the "view" in the tool bar becomes redundant.

"General Options" consists of two tabs: "General Options" and "Reporting and Logging"

"Customize" consists of two tabs: "Complete Configuration Files" and "Custom Scripts"

Documents tab on "slab" does not display network docs (Feature No: 303566)

Category: not specified

Status: implementation

Test Result: idle

Tester:

Description:

Beta Customer: Jason Womack

SR#: 10377977057

On the GNOME main menu "slab" select "Documents". Recent documents will show up if they are stored on a local drive but those that exist on a network share will not show up.

Conventional wisdom is to have users store data on a network, the value of the Documents cache on the Main Slab is minimized by limiting it to displaying only local documents.

Provide overview of installed add-on products (Feature No: 303588)

Category: Installation, Systems Management, YaST

Status: ready to test

Test Result: idle

Tester:

Description:

During the first stage of the installation, there is an overview table (with

add/delete buttons) displayed for Addon products.

However, after the installation is complete, an overview of add-on products

using the 'Add-on Product' wizard is not present.

LVM proposal needs to leave remaining free Volume Group space for OES installs (Feature No: 303594)

Category: Novell Open Enterprise Server, YaST

Status: ready to test

Test Result: idle

Tester:

Description:

This feature is created to ensure that the LVM install proposal is implemented in a way that allows for additional LVM Volume Groups to be installed on a single disk. The LVM "system" Volume Group should not consume the entire disk.

The proposed solution is to define a max-size for the "system"-Volume Group.

yast2-ldap: use original LDAP object names (Feature No: 303596)

Category: YaST

Status: ready to test

Test Result: idle

Tester:

Description:

YaST LDAP modules lowercase the names of all LDAP objects they create and show. This is inconvenient for people used to the correct naming. YaST should use the correct name schema.

Consider to switch from nss_ldap to nss-ldapd (Feature No: 303597)

Category: Directory Services, LDAP Service, User Authentication

Status: ready to test

Test Result: idle

Tester:

Description:

nss_ldap has some design limitations that already hit us pretty regulary. E.g. by it's nature it is loaded into every process that calls functions of the NSS interface. This leads to the problem that a single client machine can have dozens of open LDAP connections, pushing the server to its limits. Additionally it causes problems with conflicting libraries e.g. Firefox comes with it own LDAP library which clashes with some symbols in the system's libldap, OpenOffice comes with an own version of libdb and VMware console ships with its own libssl causing similar issues.

nss-ldapd is a reimplementation based on nss_ldap but split in to a daemon and a very small nss-module. The daemon contains all the library dependencies and does all the LDAP communications, this will limitl the number of open connections per client (ideally to a single connection) and help us to get rid of the library conflicts. Addtionally this should improve performance a bit because we get rid of a lot of bind request an costly SSL handshakes

An additional advantage of nss-ldapd is that we can be configured to securly authenticate via SASL/GSSAPI (Kerberos). nss_ldap can be configured for SASL/GSSAPI as well, but not in a secure way (every user need rw access to the credential cache).

Before doing such a switch nss-ldapd needs of course to be very well evaluated an audited.

'Security health status' YaST Module ('Bastille' like functionality) (Feature No: 303598)

Category: High Availability, Usability, YaST

Status: ready to test

Test Result: passed

Tester: zonker

Description:

Our SLES customers think that they need 'Bastille' to improve security of SLES.

After a detailed look at this in the OBS (see references) I am confident that our security infrastructure is (nearly) good enough; just don't run 'Bastille', as it will screw up the whole system.

To remedy this awareness problem, we need a YaST module extending/ consolidating the various Security settings and showing a "security health status" - like 'Bastille' does - or better:-)

Services / Modules

File Permissions

Login Settings

Boot Settings

Password Settings

Firewall

... ??? ...

Non-interactive mode for AutoYaST (Feature No: 303601)

Category: AutoYaST

Status: ready to test

Test Result: idle

Tester:

Description:

Currently, the automated installation using AutoYaST stops on any single problem, asking for manual intervention. We would like to have an option to change this behaviour when needed. The errors would be just logged, and the installation would continue, unless the errors are absolutely fatal.

Background: we (QA) are maintaining a large pool of test systems, and we need to reinstall them frequently (with each Beta release). Fully automatic installations with no user interventions are preffered.

We would even like to do automated reinstalls as a part of a larger test batch. Any dialog asking for manual intervention would stop the batch.

a particular package does not exist in the repositories anymore

cannot properly setup sound/graphics etc.

It could be also helpful, when AutoYaST could be set up to use default values, where those from the XML couldn't be used.

Support for pygrub in Xen (Feature No: 303603)

Category: Virtualization, Xen Virtual Machine Monitor

Status: ready to test

Test Result for RC1: passed

Tester: dbaxps

Description:

Leverage the community development and testing resources that surround pygrub.

Allow SLES to properly boot paravirtualized guests from other distrubutions (e.g. RHEL).

Allow other distributions to host SLES as a paravirtualized guest on their platform (see bug #372715).

libStorage: LVM Requirements for SMI-S providers (Feature No: 303613)

Category: Altix specific features, Novell Open Enterprise Server, YaST

Status: ready to test

Test Result: idle

Tester:

Description:

Libstorage should provide following interfaces:

1) Renaming a LVM VG (LVM container): VG renaming capability is given by LVM command line

utilities vgrename and lvrename respectively. libstorage can provide a

wrapper API for the same.

2) Renaming LVM LV (LVM regions): LV renaming capability is given by LVM command line utilities vgrename and lvrename respectively. libstorage can provide a wrapper API for the same.

3) Getting MD RAID state, whether its active or degraded: The requirement is to have a libstorage API for probing the state of MD RAID. This interface can

Category: Security

Status: ready to test

Test Result: idle

Tester:

Description:

Umbrella-Request: Details to be defined. AppArmor to remain default. SELinux not shipped in products by default.

Enablement means:

Enablement does not mean:

Build the kernel to support SELinux

Apply all patches to all "common" userland packages

ship necessary libraries (libsepol, libsemanage, ...) in codebase

run QA with SELinux disabled

ship SELinux specific software packages (e.g. checkpolicy, policycoreutils, selinux-doc)

ship a policy

run QA with SELinux enabled

Make SELinux or AppArmor bootable alternatively - was: Make SELinux- and AppArmor-module loadable alternatively (Feature No: 303663)

Category: Security

Status: implementation

Category: Systems Management, zypp

Status: implementation

Test Result: idle

Tester:

Description:

Provide a switch in Zypper "--report-licensing" to dump the EULA and Licenses of installed packages.

Software that was installed outside of our update stack's control (make-install driven tarball) is, of course, excluded.

This is relevant to our appliance plans.

[CODE11-GM] Mascot for YaST (Feature No: 303708)

Category: YaST

Status: implementation

Test Result: idle

Tester:

Description:

Every successfull product has it's own logo and mascot. We should create and market one for YaST as well, display it prominently on all YaST project pages and also in YaST, e.g. in any About screens or as easter egg.

Full suspend/resume support for HP workstations (Feature No: 303714)

Category: Power Management, Suspend

Status: ready to test

Test Result: idle

Tester:

Description:

Currently, sleep and hibernate functions do not work correctly on our workstations with SLED 10 SP1. As interest in green Linux grows, this functionality will become increasingly important.

Add "command not found" handling to the shell (Feature No: 303730)

Category: Systems Management

Status: ready to test

Test Result: passed

Tester: badshah

Description:

Ubuntu has a very friendly message when one types the name of an executable coming from a package not installed:

"the program fulano can be found in the following packages:

* foo

* bar

* baz

try: apt-get install <package>"

now that we will have the pool channels online, we can leverage them, and make things friendlier for entry-level users.

wsman compliance testing (Feature No: 303732)

Category: CIM, Systems Management

Status: ready to test

Test Result: idle

Tester:

Description:

Microsoft is developing a new wsman compliance tool (currently named or code-named "pivot").

Compliance testing via this tool for any wsman component in the platform is mandatory.

Violations should be considered bugs. Violations which are due to faulty tool, cosmic rays, or dubious standard interpretations on MS's part, should be brought to the PM for exception (and reporting to MS).

Yast Progress dialogs must not steal focus (Feature No: 303771)

Category: Systems Management, YaST

Status: ready to test

Test Result: idle

Tester:

Description:

YaST progress dialogs must _not_ cause focus stealing.

Category: X.org

Status: ready to test

Test Result: idle

Tester:

Description:

Provide a fool-proof video fallback when X is not configure correctly.

Enable redetection of hardware at customer first boot (Feature No: 303939)

Category: OEM Preload

Status: ready to test

Test Result: idle

Tester:

Description:

When using autoyast to deploy SLED across systems with differing graphics adapters, we need the system to automatically (re)detect and configure graphics at customer first boot.

Add more break-points for custom scripts in AutoYaST (Feature No: 303942)

Category: AutoYaST, OEM Preload, Systems Management

Status: ready to test

Test Result: idle

Tester:

Description:

Currently there are 4 break points defined in the autoyast.xml file where custom scripts can be run. It would be helpful to have more of these. For example, it would be good to have one that occurs AFTER reboot so that we could modify the xorg.conf file or enable Desktop Effects.

Shirley Peak Wireless driver and uCode (Feature No: 303996)

Category: not specified

Status: ready to test

Test Result: idle

Tester:

Description:

Shirley Peak is the next generation wireless hardware after Kedron (4965).

It's included in Montevina platform.

Please include Shirley Peak wireless driver (iwlwifi) and uCode to support

the device.

mac80211 stack for Shirley Peak Wireless driver (Feature No: 303997)

Category: not specified

Status: implementation

Test Result: idle

Tester:

Description:

Shirley Peak Wireless driver requires mac80211 stack in kernel to function.

Novell should include the mac80211 stack that is verified to work with Shirley

Peak driver.

BuildID support (Feature No: 304088)

Category: Debugging, Toolchain

Status: ready to test

Test Result: idle

Tester:

Description:

Make core dumps self-identifying enough to find the exact correct versions of all relevant binaries and debuginfo.

Compressed debuginfo sections (Feature No: 304092)

Category: Debugging, Toolchain

Status: implementation

Test Result: idle

Tester:

Description:

Symbol tables and the debuginfo sections necessary for debugging take up a huge amount of space in the installed debuginfo package. The symbol table consists of strings which compress very well.

Incremental debuginfo (Feature No: 304096)

Category: Debugging, Toolchain

Status: implementation

Test Result: idle

Tester:

Description:

When a new version of a package is build the debuginfo package is updated. All new introduced or changed types are appended to the already existing debuginfo. Since the old types are still available the updated debuginfo works for the old packages as well as for the new package.

Solaris is already using a similar thing in the Compressed Text Format (CTF, sometimes also refered to as Compact C Type Format). Although this should in theory work well for type information and symbol tables, the complex part of this feature is how to handle call frame information etc.

Generic crash reporting infrastructure (Feature No: 304162)

Category: Base System, Debugging

Status: ready to test

Test Result: idle

Tester:

Description:

uses core_pattern proc filesystem interface

uses packagekit to download and install debuginfo packages

doesn't have tons of dependencies (optimally a stand-alone app)

SLES-PRIORITY: integrate with the YaST support module and the "Onstar" functionality

integrate into both KDE and Gnome existing infrastructure (Dr. Konqi and bug-buddy)

integrate into Firefox (Google breakpad)

integrate into OpenOffice

integrate into YouNameIt and its successor

Use more recent Xorg bits (Feature No: 304211)

Category: not specified

Status: ready to test

Test Result: idle

Tester:

Description:

Intel graphics driver needs to work with Xorg server to have full-featured

functionality. SLE11 should pull a more current Xorg release at August to

ensure the necessary components for Intel graphics driver are ready.

iAMT 5.x support - drivers (Feature No: 304212)

Category: not specified

Status: implementation

Test Result: idle

Tester:

Description:

iAMT 5.x support need the MEI drivers to beincluded.

Enable CONFIG_PNP by default on x86_64 kernel (Feature No: 304236)

Category: not specified

Status: implementation

Test Result: idle

Tester:

Description:

"Plug and Play" support is necessary for TPM and AMT 5.x support. Current

SLE10 kernel for x86_64 leave CONFIG_PNP off by default, and blocks TPM and AMT

5.x supports.

In SLE11, please ensure the CONFIG_PNP is enabled.

Please see Bug #388202 for details.

Make Xgl work properly with nvidia cards (Feature No: 304290)

Category: 3D Accelerated Desktop, NVIDIA driver updates

Status: ready to test

Test Result: idle

Tester:

Description:

Xgl currently does not properly detect newer nvidia cards and claims they are not supported. Also, even for older nvidia cards, if a user has the nvidia accelerated driver installed, Xgl does not seem to recognize that nor the fact that 3D is indeed enabled. As a result, the user has to resort to workarounds to enable Xgl on these cards.

Shanghai CPU support (Feature No: 304317)

Category: not specified

Status: ready to test

Test Result: idle

Tester:

Description:

Shanghai is the successor to Barcelona processors and should be functionally compatible with the

current Barcelona support

Category: not specified

Status: ready to test

Test Result: idle

Tester:

Description:

Novell had requested Kerberos support be added to the kernel CIFS client for better enterprise (including Active Directory) Interoperability. The Kernel support is in mainline and is expected to be included in the periodic cifs backport. The optional Kerberos support requires a new helper module which will be located in the Samba source in the same directory with the existing mount.cifs mount helper which you include. This is a reminder to package the new cifs kerberos helper for SLES11 in order to get the Kerberos support for cifs network mount which you had previously requested.

IPv6 Secure Neighbor Discovery (SEND) (Feature No: 304365)

Category: Linux Kernel, Network, Security

Status: implementation

Test Result: idle

Tester:

Description:

Support the following RFCs to support IPv6 Secure Neighbor Discovery(SEND)

SEND is applicable in environments where physical security on the link is not assured (such as over wireless) and attacks on Neighbor Discovery Protocol are a concern.

RFC 3971: Secure Neigbor Discovery

RFC 3972: Cryptographically Generated Addresses.

Disabling (or handling) screensaver during installation (Feature No: 304395)

Category: Installation, Systems Management, Update, YaST

Category: Virtualization, Xen Virtual Machine Monitor

Status: implementation

Test Result: idle

Tester:

Description:

While the installed base of SLES 10 Xen is still small, we need to have a well-defined, perfectly working and fully supported way of moving Xen guests from a SLES 10 hypervisor to a SLES 11 hypervisor. This should not need extra tools/licenses, e.g. for PlateSpin V2V.

live

Kernel ABI Stability (Feature No: 304458)

Category: Linux Kernel

Status: implementation

Test Result: idle

Tester:

Description:

Symbols that the kernel exports for the use by modules automatically are assigned a so-called modversion, which is a checksum computed from all the data types that the symbol uses (recursively).

This recursive checksum computation (done by genksyms) takes all data types into account which are known at the point where the symbol is exported (EXPORT_SYMBOL). The computation does not enforce complete type information. When more type information becomes available (for example, due to an additional #include), the checksum will change.

We should look into how the checkum computation can be changed so that the resulting checksums become more stable.

Let libzypp handle special cases (when removing software) (Feature No: 304459)

Category: Systems Management, zypp

Status: ready to test

Test Result: idle

Tester:

Description:

Recently I wanted to upgrade some package which dragged some dependency that wanted to remove glibc. After waved zypper to proceed, the system finally ended up without any glibc installed (which means unusable). Frankly, I overlooked that glibc was going to be removed because there were so many changes printed.

libzypp, zypper, package managers, kernel, glibc, rpm...

break

system consistency

In packagers, a popup with different background color and in zypper different text-color should be used to emphasize what is going to happen. Moreover, zypper should print that right above the lines that ask whether to proceed.

One-click install: administrator-disable (Feature No: 304484)

Category: Systems Management, YaST

Status: ready to test

Test Result: idle

Tester:

Description:

It should be possible for an administrator to easily disable one-click install at his discretion.

This feature, combined with PoliciKit support for non-root installs, provides the full security spectrum from standard (root required) to lax (user-install enabled) with the ability to fine-tune availability of the one-click install independently of the above. independently

SMT support for code 11 products (Feature No: 304486)

Category: Systems Management

Status: ready to test

Test Result: idle

Tester:

Description:

SMT "1.0" should be updated to adequately support code 11 products.

This is on the assumption that concurrent release of SMT-11 will be a difficulty on staffing grounds.

Release of SMT-11 within 3 weeks of SLE 11 GA would of course also meet this requirement.

x86info packaging, integration (Feature No: 304487)

Category: Systems Management, YaST

Status: ready to test

Test Result: idle

Tester:

Description:

Package x86info for SLE and leverage its library form in hwinfo.

Update of base product to trigger update of addon where available (and removal otherwise) (Feature No: 304488)

Category: Systems Management, YaST, zypp

Status: implementation

Test Result: idle

Tester:

Description:

Support of add-on products needs to include a clean way for the update of the base product to (a) remove the add-on or (b) trigger the update of the add-on.

(b)'s triggering of the best option for workflow-based add-ons (oes) needs engineering analysis, while it is fairly straightforward for simpler add-ons (SDK).

PolicyKit Integration (Feature No: 304493)

Category: Systems Management

Status: ready to test

Test Result: idle

Tester:

Description:

Integrate PolicyKit into the base system.

Direct uses are in 302477 (YaST module to configure), 302522 (PackageKit, which leverages PolicyKit), 301960 (Role-based Yast).

Category: Systems Management

Status: ready to test

Test Result: idle

Tester:

Description:

Consider this an "informational" feature.

The business priorities in the update/migration sector are as follows based on what we understand of the market currently:

(1) Stability, reliability.

Hands down, enterprise and community users want the update and migration process to be reliable as the most important factor.

Stability refers to the Updater, Reliability refers to the migration/update paths.

(2) Minimize downtime.

This is very important from an enterprise perspective. The least number of reboots, the smallest time a system has to be out of operation, the greatest business availability. This trumps installation speed in paractice in business environments, as speed is a cost in admin time, downtime is a cost in "all users of the service"-time.

(3) Installation speed.

This is paramount community-wise, where there are "acceptable" options such as Yum, and excellent ones such as Apt, and it reflects on the business side in terms of Administrator annoyance and cost in terms of admin-hours.

soon, the following will be as important:

(4) dist-upgrade.

With Ubuntu's success, more and more users are becoming accustomed to full-version migration with the ease offered by Debian/Ubuntu. We need to work on this front as it will take a long time to get this right (it is not only about technology, it is about packages as well), and it will become more and more important.

(5) featurefulness

Of course, some people will consider "feature X, Y, or Z" critical. But it is important to understand the above priorities beat any other feature in market relevance.

Of course, PM passes the market priorities down to engineering in what we flag as more or less important, but I wanted to have this information explicitly in the PRD as it gives direction to all our efforts in the area

Find corresponding source package (Feature No: 304515)

Category: Systems Management

Status: ready to test

Test Result: idle

Tester:

Description:

The update stack should have the ability to find the corresponding source package automatically, given either a binary package or a reference to an installed one.

The rationale for this is in the Applicance applications.

technically, %{COOKIE} needs to be the same in binary and source rpm, and %{SOURCEPKGID} should match the SigMD5 of the source. The automatic match-up should be possible to available repos providing source RPMs.

Note that this is a build-time (for images) or a source certification/auditing (for particularly precise F/OSS consumers) process, being fast for this one is not that important. Being able to do it automatically is.

There is a component of this which is about the packages themselves being formed to do this (i.e. getting the _actual_ source package used for the build).

Liberation Fonts (Feature No: 304544)

Category: Desktop, OpenOffice.org

Status: ready to test

Test Result: idle

Tester:

Description:

Red Hat released the Liberation font

family. We should add to OpenOffice mapping for these. Any

document using the MS font, where said

font is not installed, would have them remapped to the Liberation

fonts that would be installed.

We should do this for openSUSE where there are no Agfa fonts.

Monitor to see if coverage gets more complete as an Agfa

replacement.

Enable desktop effects by default (Feature No: 304756)

Category: 3D Accelerated Desktop, Desktop, Look & Feel

Status: ready to test

Test Result: idle

Tester:

Description:

With compiz introduced for a while now, we should be able to detect

and profile hardware in a way that machines capable of running our

desktop effects should have them enabled by default. Competitive

distributions are doing this today (Ubuntu 8.04).

KMP Interdependencies: support them or fail (Feature No: 304864)

Category: Linux Kernel

Status: implementation

Test Result: idle

Tester:

Description:

Currently, by compiling the same interdependent kernel modules twice, and packaging some of them in one KMP, and others in another KMP, it is possible to end up with interdependent KMPs. (Point in case: OFED, Bugzilla 395577.)

These packages can even be installed, but module reuse for compatible kernels does not work.

We need to decide whether to implement support for KMP interdependencies, or to fail the build of such KMPs.

Enhance YaST Modules to cooperate better handling the product licenses (Feature No: 304865)

Category: EULA / Package Licenses, Installation, YaST

Status: ready to test

Test Result: idle

Tester:

Description:

Currently, there is a code that copies wrong product license (changed in bnc #396976) to some directory on the just installed system (yast2-installation) and firstboot by default searches for a different file in a different directory. License is then displayed by ProductLicense module (yast2-packager) that ignores some settings defined by yast2-installation. It actually somehow works with user-defined licenses and directory but never with the default values.

/etc/sysconfig/firstboot

/license.tar.gz

/etc/YaST/license/

/etc/sysconfig/firstboot

/etc/YaST/license/

Document the defined behavior (or as a first step)

Clean up the YaST code (currently very confusing)

Evaluate kbd-1.14 (Feature No: 304869)

Category: Base System

Status: ready to test

Test Result: idle

Tester:

Description:

We have kbd version 1.12 in our products. Upstream was dead for a long time. We have accumulated a list of patches, and a number of open defects filed against kbd.

A new upstream is active with 1.14 - where a range of our patches already went in, and presumably also some defects got addressed.

I suggest to evaluate and upgrade.

I will not maintain kbd-1.14 or later.

OO.o Batch Command Line Document Conversion (Feature No: 304874)

Category: Desktop, OpenOffice.org

Status: ready to test

Test Result: idle

Tester:

Description:

Utilize the headless operation capabilities of OpenOffice to provide a command line script that allows two documents to be converted.

Provide conflict with other providers of resolvable (Feature No: 304881)

Category: Systems Management, zypp

Status: ready to test

Test Result: idle

Tester:

Description:

As file conflicts of branding packages are invisible for zypp, we need a feature, which will make one branding package conflicting with all other branding package providing the same file. List of potentially conflicting packages is not known in time of writing of the spec file.

Solution proposed by mls:

Up to 11.0 betas, Conflicts: foo / Provides: foo was just working in desired way, but this behavior was changes, as it is not bug-compatible with rpm.

Provides: foo

: Conflicts: otherproviders(foo)

needs_relogin/needs_reboot as a generic flag (Feature No: 304889)

Category: Systems Management, YaST, zypp

Status: ready to test

Test Result: idle

Tester:

Description:

There are situations, where relogin or reboot are needed to activate update:

Now this situation is not done in a consistent way (silently ignoring problem, note in help, abuse of License entry, pop-up...).

Providing a common way for setting these flags (via package provides, YaST calls, sysconfig comments) (and maybe comment what will happen ignoring it) would help in user experience (user is notified about need of relogin/reboot in a consistent way and only once) and administration (automatic relogin or reboot during maintenance window).

package updates

proxy settings

Provide tabs shortcuts in YaST Qt UI (Feature No: 304890)

Category: Systems Management, YaST

Status: ready to test

Test Result: idle

Tester:

Description:

Tabs, unlike most (if not all) other widgets are not accessible via shortcuts. From user's point of view, they are just a widget like any other and there is no obvious reason for this functionality missing.

ncurses UI is fine, because it uses PushButtons instead, which can have shortcuts associated. However I don't know how this changes after implementation of feature 303491.

I think it would really enhance the usability of YaST dialogs.

NetworkManager: umtsmon capabilities (Feature No: 304897)

Category: Mobility, NetworkManager

Status: implementation

Test Result: idle

Tester:

Description:

As we progress towards more use of GPRS, EDGE, WCDMA, UMTS, HSDPA cards (and built-in) by our customers, we need to integrate the umtsmon capabilities in NetworkManager.

- Enable the device by providing PIN and PUK

- Change PIN and PUK

- Provide details from sim and modem card

- Display signal strength and operator available or in use

- Roaming outside of home country

perl-Bootloader should not require perl-gettext (Feature No: 304898)

Category: Base System

Status: ready to test

Test Result: idle

Tester:

Description:

perl-Bootloader currently requires perl-gettext. For creating minimal distribution images, like SLE JeOS ore openSUSE LimeJeOS, this is drawback, since perl-gettext requires perl.

The goal should be to only have perl-base in the minimal images, and still be able to use perl-Bootloader -- even without the features that require perl-gettext.

zypper features required for registration (Feature No: 304915)

Category: Product and Registration Handling, Systems Management, zypp

Status: ready to test

Test Result: idle

Tester:

Description:

Due to the fakt that SLE11 will not have rug/zmd, zypper needs to take over all

features which are required to do a successful registration.

This is a (hopefully) complete list of the features which suse_register

requires from zypper for SLE11. I expect, that some of them are already

implemented and available.

!!! Attention: All the features below _MUST_ be executable if another

instance of libzypp is running. !!!

(E.g. during online SP update libzypp is installing patches. Inside of

such a patch suse_register is called (via <script>) to register

the new products and re-configure the repositories.)

All output is required in a format which can be parsed by suse_register

and do not change too often.

The following features may not be required. It depends on the discussion

currently happens.

command which return all patterns which are satisfied(installed)

command which return all products which are satisfied(installed)

There should be a function in libzypp which should return the

correct value for this.

(NU service will be implemented in libzypp)

list services (show service type rpmmd/NU)

list catalogs (dependency to the service required)

"list" must show name, url, alias, etc.

(Special requirement:

suse_register must be able to define a name for this service.

This name must be unique for the libzypp repositories.

This name must be displayed in the "list" commands.)

support enable/disable/refresh/refresh setting of a service

(no acception key question)

It should download the repoindex file and do all required

modifications on the catalogs but do not refresh the catalogs.

(No metadata download of the catalogs and

no acception key question is important here)

For rpmmd type this is the same as for the service,

for NU type this is different.

Attention: You cannot delete a NU catalog. Delete a NU service, delete

delete all catalogs.

command for creating deviceid and secret file

If yes, it may makes sense to have have zypper support

for viewing and changing these options. See also "rug get"/"rug set"

Provide the "option" driver supporting the latest hardware (Feature No: 304916)

Category: Desktop, Hardware and Drivers, Linux Kernel, Miscellaneous Drivers, Mobility, Network, Network Drivers, NetworkManager, OEM Preload, Plug and Play external devices

Status: ready to test

Test Result: idle

Tester:

Description:

Always support the newest revision of the option driver (or, if not possible, have the latest hardware support backported, so that new hardware will work).

Additionally we need to make sure, that HAL's fdi files contain the new devices, so that NetworkManager can work on them.

If that is not enough, NetworkManager support needs to be backported, too.

Provide the "nozomi" driver supporting the latest hardware (Feature No: 304917)

Category: Desktop, Hardware and Drivers, Linux Kernel, Miscellaneous Drivers, Mobility, Network, Network Drivers, NetworkManager, OEM Preload, Plug and Play external devices

Status: ready to test

Test Result: idle

Tester:

Description:

Always support the newest revision of the nozomi driver (or, if not possible, have the latest hardware support backported, so that new hardware will work).

Additionally we need to make sure, that HAL's fdi files contain the new devices, so that NetworkManager can work on them.

If that is not enough, NetworkManager support needs to be backported, too.

Provide the "hso" driver supporting the latest hardware (Feature No: 304918)

Category: Desktop, Hardware and Drivers, Linux Kernel, Miscellaneous Drivers, Mobility, Network, Network Drivers, NetworkManager, OEM Preload, Plug and Play external devices

Status: ready to test

Test Result: idle

Tester:

Description:

Always support the newest revision of the hso driver (or, if not possible, have the latest hardware support backported, so that new hardware will work).

Additionally we need to make sure, that HAL's fdi files contain the new devices, so that NetworkManager can work on them.

If that is not enough, NetworkManager support needs to be backported, too.

Provide the "sierra" driver supporting the latest hardware (Feature No: 304919)

Category: Desktop, Hardware and Drivers, Linux Kernel, Miscellaneous Drivers, Mobility, Network, Network Drivers, NetworkManager, OEM Preload, Plug and Play external devices

Status: ready to test

Test Result: idle

Tester:

Description:

Always support the newest revision of the option driver (or, if not possible, have the latest hardware support backported, so that new hardware will work).

Additionally we need to make sure, that HAL's fdi files contain the new devices, so that NetworkManager can work on them.

If that is not enough, NetworkManager support needs to be backported, too.

Provide the "airprime" driver supporting the latest hardware (Feature No: 304920)

Category: Desktop, Hardware and Drivers, Linux Kernel, Miscellaneous Drivers, Mobility, Network, Network Drivers, NetworkManager, OEM Preload, Plug and Play external devices

Status: ready to test

Test Result: idle

Tester:

Description:

Always support the newest revision of the airprime driver (or, if not possible, have the latest hardware support backported, so that new hardware will work).

Additionally we need to make sure, that HAL's fdi files contain the new devices, so that NetworkManager can work on them.

If that is not enough, NetworkManager support needs to be backported, too.

Pulse-audio awareness in YaST sound card module (Feature No: 304936)

Category: Desktop, Hardware and Drivers, Mobility, Usability, YaST

Status: ready to test

Test Result: idle

Tester:

Description:

Related fate request: 303460 redesign of sound card module

With the general direction of our desktop environments to leverage Pulse-audio, it seems necessary for YaST to be very aware of it.

Devices abstraction

Volume Control

Network transparency

Software mixing of multiple audio streams

Receiving WMI Event and notify (Feature No: 304941)

Category: Desktop, Hardware and Drivers, Mobility, Usability

Status: ready to test

Test Result: idle

Tester:

Description:

Windows Management Instrumentation (WMI) contains an event infrastructure that produces notifications about changes in WMI data and services.

Our power management requirements need to be notified of WMI events.

Faster booting: samba-winbindd-patch (Feature No: 304965)

Category: Booting, OEM Preload

Status: ready to test

Test Result: idle

Tester:

Description:

diff -urN /etc/sysconfig-vanilla/network/scripts/samba-winbindd /etc/sysconfig/network/scripts/samba-winbindd

: --- /etc/sysconfig-vanilla/network/scripts/samba-winbindd 2008-06-04 13:42:22.000000000 +0200 : +++ /etc/sysconfig/network/scripts/samba-winbindd 2008-06-04 13:42:54.000000000 +0200 : @@ -28,6 +28,12 @@ : configname="$1" : shift : interface="$1" : + : +if [ $interface = "lo" ] : +then : + exit 0 : +fi : + : shift : # And shift away the '-o'. : shift

Faster booting: Sabayon patch (Feature No: 304966)

Category: Booting, OEM Preload

Status: ready to test

Test Result: idle

Tester:

Description:

if [ -f /etc/opt/gnome/desktop-profiles/users.xml ]; then

: if [ "x$DISABLE_SABAYON_XINITRC" = "x" ] ; then : if [ -x /opt/gnome/sbin/sabayon-apply ] ; then : /opt/gnome/sbin/sabayon-apply : fi : fi : fi

Faster booting: dhcpcd-hook-samba-patch (Feature No: 304967)

Category: Booting, OEM Preload

Status: ready to test

Test Result: idle

Tester:

Description:

diff -urN /etc/sysconfig-vanilla/network/scripts/dhcpcd-hook-samba /etc/sysconfig/network/scripts/dhcpcd-hook-samba

Support IOMMU for AMD CPUs in Xen. At least there should be a technology preview version in the product

AMD: Support for 'Puma' mobile platform (Feature No: 305001)

Category: not specified

Status: implementation

Test Result: idle

Tester:

Description:

With SLES10 we already covered the Griffin processor support #302868 and the SB600 southbridge support. Make sure with tests on at least one shipping example of the platform that everything works as expected.

Expect not much to be done. But it should be tested properly and be ready for advertising/marketing.

Bookmark for Documentation Web Site in Browser (Feature No: 305003)

Category: Desktop, Documentation, Usability

Status: ready to test

Test Result: failed

Tester: zonker

Description:

On a freshly installed product, the "SUSE Linux" or "SUSE" bookmark folder in the GNOME and KDE browsers includes bookmarks to some key Web sites like www.novell.com/linux, www.novell.com/coolsolutions, www.novell.com/support, www.opensuse.org, etc.

Why not also include a bookmark to the documentation Web site there by default for easy access to the online manuals available for the products?

Wouldn't cost much effort and would help to make the documentation more "visible" (number and scope of manuals, available also in languages other than English. etc.).

Joint proposal by PMM and PM:

As these pages should stay relativly constant, a more detailed structureing should take place on subsequent referenced pages.

http://www.novell.com/documentation/ for SLE (enterprise related products) and

http://www.opensuse.org/documentation/ for openSUSE.org, respectively

no bookmarks at all in konqueror kde4

Enable SMTPS in postfix ootb (Feature No: 305005)

Category: Network

Status: ready to test

Test Result: idle

Tester:

Description:

IANA has omitted the port 465/tcp to smtps assignment in its latest /etc/services file (part of openSUSE since 11.0). This causes SMTPS setups to fail.

If postfix used the port explicitly on smpts connetions rather than "smtps", everything should work again, at least for postfix based setups.

Drop lilo from supported boot scenarios (Feature No: 305006)

Category: Booting

Status: ready to test

Test Result: idle

Tester:

Description:

Drop lilo from supported boot scenarios

lilo is now deprecated since ages, lilo package has no L3 support. Lilo configuration is in no good state. In order to consolidate the boot loader environment, we should drop lilo support completely

Nevertheless this has to be documented properly and a clear and smooth migration path has to be given and implemented

Drop EVMS from supported boot scenarios (Feature No: 305007)

Category: Booting

Status: ready to test

Test Result: idle

Tester:

Description:

Drop EVMS from supported boot scenarios as a consequence of general EVMS drop

Nevertheless this has to be documented properly and a clear and smooth migration path has to be given and implemented. Special tests needed for OES customers.

[Tech Preview] Software Management CIM Profile (Feature No: 305012)

Category: Systems Management

Status: ready to test

Test Result: idle

Tester:

Description:

As part of the OpenPegasus/CIM strategy defined at the Systems Management Summit, Software Management is one of 4 profiles prioritized for delivery in SLE 11 GA.

Include 'rsyslog' package as alternative (with L3 support). (Feature No: 305014)

Category: Base System

Status: ready to test

Test Result: idle

Tester:

Description:

Looking at http://www.rsyslog.com/doc-rsyslog_ng_comparison.html it seems(claim!) that (regarding features and license) rsyslog is the more promising long-term strategy than other syslog-implementations. we need that specifically with respect to "compliance".

configure the files to copy from a previous installation (Feature No: 305019)

Category: AutoYaST

Status: ready to test

Test Result: idle

Tester:

Description:

from a customer:

In newer SUSE releases (at least in 10.3 and 11.0) I found that autoyast saves

the ssh-keys from a previous installation of the same system. This is done

in /usr/share/Yast2/clients/inst_pre_install.ycp. Unfortunately, the list of

files in that script is fixed. I would like to add some files to it, for

instance /etc/krb5.keytab, but without hacking around in the yast script.

Would it be possible to make the list of files to be saved from a previous

installation to be configurable in the XML profile? That would be a very

handy feature for us to have.

Note from me:

maybe that should be configureable via control.xml file anyway + an API to get/set those values via autoyast.

suse_register support for CODE11 (Feature No: 305047)

Category: Product and Registration Handling

Status: implementation

Test Result: idle

Tester:

Description:

We need suse_register to support CODE11 handling of products and libzypp version delivered as a part of this codebase

XEN: Support Xen Version 3.3 (Feature No: 305054)

Category: Virtualization, Xen Virtual Machine Monitor

Status: ready to test

Test Result: idle

Tester:

Description:

Xen version 3.3 will be the hypervisor and tool set for upcoming Suse operating systems.

openSUSE Testfeature (Feature No: 305081)

Category: not specified

Status: ready to test

Test Result: running

Tester: BartOtten

Description:

Feel free to play around with this feature.

better handling of unsupported modules in module-init-tools (Feature No: 305100)

Category: Base System

Status: ready to test

Test Result: idle

Tester:

Description:

Make the handling of unsupported modules in m-i-t more user friendly, as discussed with Andreas privately:

provide an explicit option "allow_unsupported_modules" in /etc/modprobe.d/unsupported-modules to enable/disable unsupported modules

don't implement it using the blacklist keyword, which only applies to aliases

command-line option --allow-unsupported-modules to override the setting in modprobe.conf

Support new product definition in Add-On and Product creators (Feature No: 305172)

Category: Installation, YaST

Status: implementation

Test Result: idle

Tester:

Description:

Add-on and Porduct creators need to be adapted to create proper product definition on its media.

[CODE11-RC] EULA translations (Feature No: 305248)

Category: EULA / Package Licenses

Status: implementation

Test Result: idle

Tester:

Description:

Localized products must present the EULA in the language of the localized product. Multi-lingual products must present the EULA in all the languages of the product. English products for sale internationally should present the EULA in at least

SLES11: English, German, French, Dutch, Spanish, Portugese, Czech and Polish.

SLED11: English, German, French, Dutch, Spanish, Portugese, Czech and Polish.

openSUSE11.1: English, German, French, Dutch, Spanish, Portugese, Czech and Polish.

Remove agfa-fonts from openSUSE 11.1 (Feature No: 305249)

Category: OpenOffice.org

Status: ready to test

Test Result: idle

Tester:

Description:

As Liberation fonts looking really good meanwhile I propose to replace the proprietary agfa-fonts with the open source fonts for openSUSE 11.1 and future versions.

Desktop icons settable by the sysadmin (Feature No: 305252)

Category: Administration, Configuration, Desktop, Desktop lockdown, Systems Management, ZENworks

Status: implementation

Test Result: idle

Tester:

Description:

Sysadmins need to be able to define desktop icons to be displayed in user's accounts. Examples: link to corporate web page, links for in-house applications.

There is some intiial work for this, out of the 2007 Summer of Code: http://live.gnome.org/SummerOfCode2007/Reports/Sayamindu

Testing:Features 11.1

From openSUSE

Contents

Feature test plan

openSUSE 11.1 Feature Test List

YaST DNS module should support creation of all RR types (Feature No: 206)

Make Fn-F7 work on laptops to switch the internal/external displays (Feature No: 4147)

No root for adding a local printer (Feature No: 4162)

Security Issues with Suspend and Resume (Feature No: 100243)

Theming by OEM (Feature No: 100246)

Easy Setup of Bluetooth Headsets (Feature No: 100301)

Support a verbose logging mode in yast (Feature No: 100386)

General Device Handling (Feature No: 110016)

Package history (Feature No: 110205)

OCFS2 Posix compliance - aka: General Purpose OCFS2 (Feature No: 110294)

YaST Heartbeat Command line support (Feature No: 120045)

LDAP Server managment API enhancements (Feature No: 120061)

Command line support for routing settings (Feature No: 120078)

Ability to Ignore Updates (Feature No: 120118)

Use gettext for .desktop translations (Feature No: 300461)

RPM_OPT_FLAGS everywhere (Feature No: 300498)

Integrate Support for openWSman (Feature No: 300594)

IPv6 transport for NFS (TI-RPC User-Space Library) (Feature No: 300607)

make "/" mountable ro (Feature No: 300617)

Mount Server Home Directory Automatically with Authentication (Feature No: 300967)

Printer browser (Feature No: 300969)

Writer Fields in OpenOffice (Feature No: 300994)

Evolution SOAP performance (Feature No: 301016)

Improved performance in main menu, app browser and control center (Feature No: 301038)

Accessible Yast (Feature No: 301084)

Configure firewall to accept bcast replies (Feature No: 301134)

the DASD section in an autoyast profile can't be changed via pre-script (Feature No: 301193)

CJK: Chinese measurements (Feature No: 301291)

Run online update during autoinstallation (Feature No: 301298)

Heartbeat: Leverage openAIS infrastructure (Feature No: 301322)

Detect available Kerberos and LDAP Servers during Installation (Feature No: 301340)

Branding: provide the ability to modify the default screensaver (Feature No: 301475)

sysconfig should try using BIOS-provided ethernet device names if available (ETH-device reordering switched off by default - kernel/boot option) (Feature No: 301528)

Branding: provide the ability to modify the YaST theme (Feature No: 301794)

Drop support for C/H/S BIOS disk access (Feature No: 301805)

Support all EFI platforms - was: Grub2 support for EFI BIOS (Feature No: 301882)

ext4 Support in Basesystem (technology preview). No YaST- or Installer-Integration (Feature No: 301897)

Whole software management stack should warn about oudated update repo (Feature No: 301904)

Public directory support for encrypted home directories (Feature No: 301923)

Make Suggested, Recommended and Required Packages Visible (Feature No: 301930)

Show list of applications using device when its busy and can't be unmounted (Feature No: 301934)

Firstboot Editor (Feature No: 301946)

Role based YaST (Feature No: 301960)

Correct device mapping in case windows is installed on the second HD (Feature No: 301994)

Support update of add-on products properly (Feature No: 301997)

Allow Package to be installed in several versions (Feature No: 302050)

YaST disk management UI facelift (Feature No: 302054)

Control Groups - enablement in SLE11 (Feature No: 302085)

zypper - rug command parity (Feature No: 302148)

KDE 4.1 Integration into openSUSE 11.1 (Feature No: 302155)

Make zypper support wildcards or regular expressions (Feature No: 302193)

Make it possible to use variables in repository urls. (Feature No: 302196)

Use and choose persistent device names for disk devices (as opposed to partition devices) (Feature No: 302219)

improve wireless kernel driver power savings (Feature No: 302345)

Do not stop some init scripts during shutdown (Feature No: 302375)

Collecting hardware information (Feature No: 302445)

UI to schedule wakeups (Feature No: 302448)

Make thermal management more robust and architecture independent (Feature No: 302452)

Package management must adapt to (repo/system) changes (Feature No: 302453)

Update of the ISC dhcp packages (server, client, relay) (Feature No: 302480)

sync GPT and MBR on MacBook (mactel) (Feature No: 302485)

Handling of licenses and confirmations in ZYPP (Feature No: 302516)

Create yast2-power-management-Module for server (Feature No: 302521)

Use PackageKit for Updater Applets (Feature No: 302522)

Certificate store for key management (Feature No: 302530)

Add DMRAID support to SLES Installer (Feature No: 302565)

Provide more settings in YaST LDAP Browser. (Feature No: 302858)

TabletPC: allow user to config tablet for TabletPCs while install (Feature No: 302888)

MHTML: open mhtml archives from local store (Feature No: 302911)

Improved argument handling for zypper (Feature No: 302919)

use the raw meta-data cache to save downloads (Feature No: 302924)

Synchronize X11 keyboard setting with console (Feature No: 302925)

Installation In An IPv6 Environment (Feature No: 302926)

Support for --nodoc option in ZYpp commit as a policy (Feature No: 302952)

Medialess update (Feature No: 302956)