Testing:Features 11.0

From openSUSE

Contents

openSUSE 11.0 Feature Test List

Here is a list of openSUSE 11.0 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.

Perl Bindings Encapsulation (Feature No: 412)

Category: YaST
Status: done
Test Result: idle

Description:
The Perl bindings so far are able to crash whole YaST
process if the embedded Perl interpreter encounters
for example a semantic problem in the interpreted
Perl code.
One possibility is to encapsulate the execution
in artifical "eval".


Translation Builtin (Feature No: 2826)

Category: Bluetooth, YaST
Status: done
Test Result: idle

Description:
A builtin for translation to custom language and using custom .mo-file is needed by
powermanagement module and bootloader.


Easy-to-use time/date applet needed (Feature No: 4134)

Category: Desktop
Status: done
Test Result: idle

Description:
Problem:
Solution:


Plug and play PDA and Cellphone (Feature No: 5533)

Category: Desktop, Mobile Device Synchronization, Mobility, Plug and Play external devices, Usability
Status: implementation
Test Result: failed

(plugging in Palm Centro via USB, switching it on and pressing the hot sync button all do not cause any reaction of the system)

Description:
When a PDA/Cellphone is connected to the system the PDA/Cellphone should be autoconfigure, and the user should be asked
if they want that PDA/Cellphone to be synchronized to the desktop. User should not need to change rights on /dev/ttyXX or
/dev/USBX or similar manually or ad users manually to special groups like video, dialup, uucp... All those things makes it
impossible to connect and synchronise Palms to PCs in Linux.

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

Category: DATA Center Features, Novell Open Enterprise Server
Status: implementation
Test Result: idle

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


YaST Heartbeat Command line support (Feature No: 120045)

Category: Configuration, High Availability
Status: done
Test Result: idle

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


CUPS server config (Feature No: 120080)

Category: Configuration, Printing
Status: done
Test Result: idle

Description:
https://bugzilla.novell.com/show_bug.cgi?id=suse40037
https://bugzilla.novell.com/show_bug.cgi?id=suse40713
https://bugzilla.novell.com/show_bug.cgi?id=suse34654
https://bugzilla.novell.com/show_bug.cgi?id=suse28435
https://bugzilla.novell.com/show_bug.cgi?id=suse40713


Flush all spooled, but unprinted jobs at start of daemon (Feature No: 120081)

Category: Configuration, Printing
Status: implementation
Test Result: failed
There is no such option in /etc/sysconfig :-( Bug #394354
--Christian Boltz 11:33, 25 May 2008 (UTC)

Description:
Enabling/Disabling to flush all spooled, but unprinted jobs at start
of daemon. This should be controlled via variable FLUSH_JOBS_ON_START of type
"yesno" in /etc/sysconfig/cups.
The reason for the customer selection is this:
on a print server the customer usualy doesnt want to lose any printjob
after a server boot. But a home user (or secretary) thinks switching
on/off the computer/printer solves a wrong print job.

Avoid the Automated Setup For "Non-Recommended" Printers (Feature No: 120083)

Category: Configuration, Printing
Status: done
Test Result: idle

Description:
What do you think about to avoid the automated setup for
"non-recommended" printers?
There are printers (in particular from Canon or Lexmark) where
the "recommended" PPD file may not work at all or doesn't work well.
There are printers for which none of the available PPDs is really good.
Such printers are "non-recommended".
Nevertheless one PPD is always "recommended".
In such cases I would like to have no automated setup and force
the user to select a PPD.


Switching LPD Protocol Support (Feature No: 120086)

Category: Configuration, Printing
Status: done
Test Result: idle

Description:
jsmeix: A button "enable lpd protocol" somewhere in CUPS configuration.
For backward compatibility reasons.
jsrain: switching LPD protocol support for CUPS On/Off
Should it be a button or a checkbox ?


Squid server configuration (Feature No: 120097)

Category: Configuration
Status: done
Test Result: idle

Description:
Squid is a proxy server for WWW/FTP. It is quite common
to install it on an internal network to save bandwidth.
The YaST module could configure the service status,
access control, cache parameters, filtering and blocking requested URLs etc.


Ignore Updates (Feature No: 120118)

Category: Desktop, ZENworks, zypp
Status: implementation
Test Result: idle

Description:
There should be a way to tell SuSEwatcher/zen-updater 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.
https://bugzilla.novell.com/show_bug.cgi?id=suse49201
since susewatcher does only call yast to determine avaliable updates, this
needs to be configured/configurable in yast
For SLE, the functionality has to be implemented in zen-updater and/or rug


Randomize Application and Library Adresses (Feature No: 120276)

Category: Security
Status: done
Test Result: idle

Description:
Some OS'es like OpenBSD and Redhat randomize memory locations of shared
libraries and the application binary in order to thwart certain
classes of security exploits (known as "jump-into-libc").
Also the current mainline kernel now supports stack address randomization.
Redhats execshield patch however randomizes more, but is not yet integrated.
  • mmap area, brk area and stack randomization support in the kernel.
    Redhat is trying to merge this from their exec shield support.
    We might also be able to extract things from grsecurity.
  • Bugfixes for the apps that break after above changes.


    Handle multiple CD/DVD drives (Feature No: 120298)

    Category: Media handling, Media Management, YaST
    Status: done
    Test Result: idle

    Description:
    If multiple CD/DVD drives are available, a single eject button is unable to eject the right drive.
    Instead, the eject button should be an eject combo box, offering every CD/DVD drive (maybe including 'all').
    See Bug 45946

    Split liby2util to avoid unnecessary yast2-core dependencies (Feature No: 120312)

    Category: Refactoring, YaST
    Status: done
    Test Result: idle

    Description:
    liby2util links with a lot of libraries just to provide
    transport mechanism for YaST2 package manager.
    Those are not necessary for yast2-core, but yast2-core
    must link against liby2util.
    Idea is to split liby2util to multiple parts to avoid
    unnecesary library linking in yast2-core binaries.


    Make handling of installation sources easier (Feature No: 120332)

    Category: Installation sources, Package and patch sources, Product and Registration Handling, YaST
    Status: done
    Test Result: idle

    Description:
    Bug 40447


    Respect taboo settings (Feature No: 120352)

    Category: YaST, zypp
    Status: implementation
    Test Result: passed

    Description:
    Bug 43461
    https://bugzilla.novell.com/show_bug.cgi?id=suse28461
    These bug numbers are not accessible to Joe Public!

    Provide different YaST module skeletons (Feature No: 120355)

    Category: YaST
    Status: done
    Test Result: idle

    Description:
    yast2-devtools allows one to easy create a new YaST module
    using create-new-package tool. However, we provide
    only a small set of skeletons: one for SCR agent, one for
    a hardware YaST module and one for new translation language.
    If YaST should be used by ISVs, we have to make skeletons
    more developer-friendly. It means to define a list of
    provided skeletons, their purpose and maybe a new way
    for generating YaST modules. The we can document how
    to use create-new-package for a YaST development
    quickstart.


    Package keywords filter (Feature No: 120368)

    Category: Package management, YaST
    Status: implementation
    Test Result: idle

    Description:
    Package keywords filter (one more filter view)
    Select packages via one or more categories like "KDE", "mail client", "license
    GPL" etc.; show all packages where either all or any keywords match. Keywords
    are present in PDB for quite some time yet. They need to be exported to the
    packages file, and the package manager backend needs calls to retrieve a list
    of all available keywords from all packages and a call to retrieve keywords
    belonging to each specific package.
    Nobody else has anything similar - we could set standards here.
    Probably post-9.2 due to limited development ressources in Y2 team.


    Unified Button Labels (Feature No: 120373)

    Category: Usability, YaST
    Status: done
    Test Result: idle

    Description:
    Unify button labels
    YaST currently uses several different button labels
    for basically the same action, i.e. 'Ok', 'Accept',
    and 'Finish'.
    Decision: Only a single label per action should be used. Labels should be generally "OK" and "Cancel" for standard modules
    and "Back", "Next", "Cancel" and "Finish" for wizards.


    Make better use of the window space in the proposal screens (Feature No: 120376)

    Category: Usability, YaST
    Status: done
    Test Result: idle

    Description:
    Make better use of the window space in the proposal screens
    The current proposal (rich-text) window too tall requiring the
    user to scroll. It also suffers from information overload because
    it tries to present everything at once.
    Think about
    - align headlines and data horizontally
    - reduce information, structure information differently
    - implement a 'folding' view where users can open/close
    the detailed information (tree style)


    VLAN creation at install time (Feature No: 142127)

    Category: Configuration, Initial Configuration (2nd Phase of Installation), Installation, Network, YaST
    Status: done
    Test Result: idle

    Description:
    We need the possibility to support VLAN creation on all available NICs including the VLAN id configuration of virtual NICs during the initial install and of course have it persist across reboots.


    choose bigsmp on i386 (Feature No: 159006)

    Category: Security
    Status: done
    Test Result: idle

    Description:
    bigsmp is currently the only
    kernel supporting the NX flag natively.
    SLES10 should choose this kernel as soon as PAE is available and not just for SMP system with more then 4GB.
    This might incur a small performance penalty, but the improved security possible should be worth it.


    Support for Suspend on Docking Station - Resume elsewhere (Feature No: 300334)

    Category: Linux Kernel, Power Management
    Status: done
    Test Result: idle

    Description:
    Customer is using IBM Thinkpads (T42p and T43p and T41p)
    The issue was reported in Bug# 96958, while docked a PS/2 mouse was used, the Laptop was suspended and then resumed elsewhere and the Touchpad was unresponsive.
    It was said that there's no support for "Changing the Hardware while suspended" (see also Bug# 99707).
    This should be made possible for SLES10 though.
    (If there's any hardware specifications besides the PS/2 mouse/Touchpad you need to know about, let me know)


    RPM_OPT_FLAGS everywhere (Feature No: 300498)

    Category: Package building, Security
    Status: implementation
    Test Result: idle

    Description:
    We should make the use of RPM_OPT_FLAGS mandatory for all autobuild packages.
    checks for this already exists, but only warn currently.


    Support UMTS cards (Feature No: 300518)

    Category: Configuration, Desktop, Hardware and Drivers, Linux Kernel, Mobility, Network Drivers
    Status: done
    Test Result: idle

    Description:
    More and more UMTS network cards are available. Additionally there are now
    notebooks sold with these cards built-in. Therefore it is neccessary to
  • find out what drivers are needed
  • verify if the drivers are in the kernel, help where this is not the case
  • update all configuration tools (hwinfo, yast, udev-rules) to support the hardware

  • Implement PIE support in the kernel (Feature No: 300592)

    Category: Linux Kernel, Security
    Status: done
    Test Result: idle

    Description:
    While PIE (Position Independend Executable) support is now in the compiler and some userland binaries,
    it is lacking from the kernel.
    The kernel still loads PIE binaries at a fixed address.
    This needs a kernel patch to fs/binfmt_elf.c.
    Two ways to do it:
    If (2) is chosen, the heap needs to be moved somewhere else, and could also be randomized now.
    (Remember: UNIX heap traditionally follows right after the executable in the address space.)
    This is not so easy. Redhat does a hack for this on i386, but I am not sure how often this works well.
    This will likely require a kernel hacker for 1 - 2 weeks.
    We can easily test the PIE apps we have currently, it won't affect other apps.
  • Randomize at start place.
  • Unclear how much randomness this allows.
  • Move binary to the already randomized shared libaries.
  • Red Hat is doing this in execshield already,
    but mostly to be able to do Soft-NX (%CS selector covering
    only parts of the address space).


    Integrate Support for openWSman (Feature No: 300594)

    Category: CIM
    Status: done
    Test Result: idle

    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: implementation
    Test Result: idle

    Description:
    NFSv4 shall run natively over IPv6.


    Create the infrastructure needed for using FUSE (Feature No: 300612)

    Category: not specified
    Status: done
    Test Result: idle

    Description:
    There are quite a few scenarios for using FUSE (filesystem in userspace) on SLED, e.g.:
    The deliverable is to make sure that all the typical scenarios for using FUSE share a common framework and work doesn't have to be duplicated. This includes:
  • user-specific, user-configurable, permanent SMB/CIFS mounts
  • userland encrypted folders (as opposed to encrypted partitions that only root can set up)
  • access to protocols like WebDAV or FTP from all applications that make use of filesystems
  • making sure that the FUSE kernel module is loaded if it is needed by a userland filesystem
  • desktop-agnostic solutions for managing FUSE filesystems (e.g. from context menus in the file browsers)

  • Interface Names Support in YaST Networking Modules (Feature No: 300636)

    Category: YaST
    Status: done
    Test Result: passed

    Description:
    YaST should be able to manage interface names using UI.

    Compressing YaST Logs on Fly (Feature No: 300637)

    Category: YaST
    Status: done
    Test Result: idle

    Description:
    The y2logs in /var/log/YaST2 can be very large (20-30MB), but they compress
    very well. As I saw they are periodically rotated. It would be nice if the
    older logs would be compressed with bzip2 (or even with gzip), jut like it is
    done with every other log file in /var/log. Hard disk space might be cheap,
    but not so cheap to simply throw away 70 MB.

    "Beta popup" during adding an external Repo (Feature No: 300640)

    Category: Installation sources, Package and patch sources, Product and Registration Handling
    Status: done
    Test Result: idle

    Description:
    As the buildservice is up and running now and we try to get more and more external people involved to produce their own repos with their own packages - we need an end-user friendly feature to point out that these installation repos are not supported by SUSE/Novell.
    So my proposal is to add a popup during adding an installation source (like the one we have already for importing gpg-keys) which points out the support status of a repo.
    For the buildservice-repos we can and should always add a "README.Beta" plain text file like we have for our Beta-CDs. But perhaps a partner wants to create an external installation source and also wants to support and maintain these packages. This partner should become a change to place a (text-)file in his repository containing licence and/or support information (like time periods, email- and web-addresses, ...). YaST should come up with the information in this file during the "add installation" source and keep the information available for later usage.
  • The first goal should be to add "README.Beta" files for every repo in the buildservice.so every user can read this information during browsing the repos. YaST should show the content of this files in a popup window during adding these repos to the installation source. So every user is informed about the support and maintainance status of the buildservice repos.
  • Later on we need a decission for filenames (or similar) which contain additional information about support and maintainance for a repo. The "product.xml" file could contain such information - but YaST should also show possible licence information for a repo.
  • first show only a popup if a special file ("README.Beta") is available
  • later: show a popup if NO special file ("product.xml" or "README.support") is present

  • Make dependency solver behaviour configurable (Feature No: 300707)

    Category: not specified
    Status: done
    Test Result: idle

    Description:
    The current dependency solver is based on libredcarpet, the client side of ZENworks Linux Management (ZLM).
    Its primary task is a fully automated package dependency resolution based on fixed rules. This either succeeds or fails. There is no user interaction in between.
    The current behaviour, although correct for a ZLM environment, is different from what YaST offered in the past.
    The solver behaviour should be configurable and support callbacks for user interaction.
    For example:
    - Choose one of many alternatives.
    - Choose 'best' package.
    - Choose 'best' repository.
    Additionally, different semantics when doing a bare-metal install compared to and add-on install are needed.
    Bug 191983


    Install diskless client (NFS-root) (Feature No: 300779)

    Category: YaST
    Status: done
    Test Result: idle

    Description:
    Starting point:
    Requested functionality:
    Actually you cannot do this, while you cannot define the above partition
    layout in the current version of YaST.
    First evaluation (from comment #19 in BZ #67320):
    Basically, we need to do the following to get "diskless client with root
    on NFS" to work:
    AFAICS this bug is requesting support for the client side of this
    feature.
    AFAICS what we need is this:
  • having a (huge) NFS root server already running SLES 9, and
  • configured to serve as DHCP, BOOTP and NFS server (using archtecture X
    e.g. "i386").
  • diskless
  • diskless
    not
    any
  • Inserts SLES 9 CD into CD-ROM on NFS boot client.
  • Boots NFS boot client from SLES 9 CD-ROM.
  • Entering YaST.
  • Wants to setup the partitions using NFS mount points on the NFS
    root server:
    NFSroot:/nfs/clients/10.10.3.50/root /
    NFSroot:/nfs/clients/10.10.3.50/usr /usr
    NFSroot:/nfs/clients/10.10.3.50/opt /opt
  • Run installation to install the NFS boot client with SLES 9.
  • booting a kernel via network needs to be configured on client and
  • server
  • NFS mounts need to be configured on client and server
  • both need to be available when the client is rebooted and probably
  • also during installation
  • yast2-storage is handling the disk configuration of the target
  • system, so it should handle or at least know about NFS-mounted target
    disks
  • we need some way to enter yast2-nfs-client during installation to set
  • up NFS-mounts (and probably make some proposal there)
  • NEW subfeature: maybe yast2-nfs-client can also look at autoyast/NIS mountpoints
  • we need some way to configure the client firmware to boot from the
  • network


    install the security updates for own packages (Feature No: 300899)

    Category: Security, Update, YaST, zypp
    Status: done
    Test Result: idle

    Description:
    (after a long thread on security-team/maint-coord)
    With multiple repositories in place it is difficult to make sure that a security update is installed
    for a package of us.
    For instance, a security update might just pull in a package from a 3rd party repository
    which satisfies the requires, but does not fix the actual problem.
    Prominent example:
    suseRegister in the libzypp mega update will be replaced by "kick-suseRegister" package from
    packman, if the packman repository is added, since it fulfills the requires.
    We should have a method of making sure that security update are installed.
    Idea: Attach "distribution" flag (by signature somehow?) to every package and only allow patch driven updates with packages of
    the same distribution/key.


    GCC: enable switch to control warnings for comparison of different enum types (Feature No: 300955)

    Category: Toolchain
    Status: implementation
    Test Result: idle

    Description:
    In GCC (C++) 4.1.x, the call to function build_new_op in gcc/cp/call.c emits a warning for the comparison of different enum types. This warning cannot be controlled in any way,
    This may render -Werror useless depending on the source code.
    We request to have a control option/flag for the mentioned warnings.


    Firewall support for SMB browsing (Feature No: 300970)

    Category: Directory Services
    Status: done
    Test Result: idle

    Description:
    Firewall support for SMB browsing


    VBA Shape (Feature No: 300983)

    Category: OpenOffice.org
    Status: done
    Test Result: idle

    Description:
    Shape support is the cornerstone of chart manipulation. In the same way that 'Range' is the basis of huge chunks of the Spreadsheet object model, Shape is that of charting.
    In order to support VBA chart manipulation interoperability, we need to implement chunks of the Shape object.


    Accelerate ConfigMgr (Feature No: 300988)

    Category: OpenOffice.org
    Status: done
    Test Result: idle

    Description:
    Currently, the biggest single slowness on OO.o startup (after linking) is configmgr. We need to do some hard-core profiling, find what is wrong, and improve on it. One idea is to provide a 'get-entire-tree' API, others are to reduce duplicated string wastage & comparison perhaps by better use of the schema data.


    Writer Fields in OpenOffice (Feature No: 300994)

    Category: OpenOffice.org
    Status: done
    Test Result: idle

    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.


    Remove intrusive error dialogs in Evolution (Feature No: 301008)

    Category: Evolution
    Status: done
    Test Result: idle

    Description:
    This involves providing a framework to capture errors from non-interactive operations, such as, automatically checking for messages every x secs/mins and display them in a non-intrusive way - a small "!" icon on the right-hand-side bottom of the status bar, that pops up the error message upon activation.
    User benefits: No more annoying error dialogs.


    Show more results in Beagle when we can (Feature No: 301071)

    Category: Searching
    Status: implementation
    Test Result: idle

    Description:
    Show more results when we can


    Port YaST Qt Interface to Qt4 (Feature No: 301119)

    Category: not specified
    Status: done
    Test Result: passed

    Description:
    The current YaST Qt interface uses Qt3. With advent of Qt4, a lot of new features has been done, e.g. improved memory footprint and performance, accessibility features built-in etc.

    autoyast signature check configureable for each add-on (Feature No: 301192)

    Category: AutoYaST
    Status: done
    Test Result: idle

    Description:
    it would be nice to be able to configure the signature checks in autoyast for each single add-on individually.


    Open CD tray when a new CD is requested (packagemanager) (Feature No: 301228)

    Category: not specified
    Status: done
    Test Result: idle

    Description:
    This was a request that originates at opensuse-factory mailing-list:
  • Opens up the CD tray during the package installation when new/another CD is requested
  • Do a system beep in this case
  • Open the CD tray on new media request
    Do not ask this question again
    eject /dev/hdc
    System beep was requested as UI::SystemBeep() function or something similar.


    Allow user to pick a mirror for updates (Feature No: 301267)

    Category: Product and Registration Handling, YaST
    Status: done
    Test Result: idle

    Description:
    For openSUSE distribution, we maintain a list of mirrors for update installation sources.
    YaST should provide a way to let users to pick the mirror they prefer, but we should provide a reasonable default at
    registration of the system. This should be an advanced option.
    The feature is a simple alternative for full feature #300625.


    GL slideshow animations (Feature No: 301276)

    Category: OpenOffice.org
    Status: done
    Test Result: idle

    Description:
    It would be very little work to add Xgl-like animations to the OO.o slideshow, and give a lot of whizzy / demo bang for the buck. We should investigate doing this for SP1.


    CJK: fixed defaults (Feature No: 301290)

    Category: OpenOffice.org
    Status: done
    Test Result: idle

    Description:
    a load of defaults need changing in CJK locales, fonts, font sizes, default styles, tab positions etc.


    CJK: Chinese measurements (Feature No: 301291)

    Category: OpenOffice.org
    Status: implementation
    Test Result: idle

    Description:
    We should layout pages based on char/line measurements not absolute cm, for familiarity.
    Modify the paragraph dialogs and rulers to match.


    Windows Domain Membership Yast module should include a field to specify the OU for the machine account (Feature No: 301320)

    Category: Directory Services, Pilot Issues, YaST
    Status: done
    Test Result: idle

    Description:
    The Windows Domain Membership Yast module should include a field to specify the OU
    for the machine account. I have spoken with both Skip and Nicolas about
    this and they agree.
    Customers are using custom solutions
    to join an AD domain because they need to specify the OU in which the
    machine account is created.


    Heartbeat: Leverage openAIS infrastructure (Feature No: 301322)

    Category: High Availability
    Status: implementation
    Test Result: idle

    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.


    Add support for suspend/resume in CCID driver (Feature No: 301343)

    Category: Smartcard Support
    Status: implementation
    Test Result: idle

    Description:
    from http://pcsclite.alioth.debian.org/ccid.html
    We should add support for managing suspend/resume


    Better Update of Translations (Feature No: 301344)

    Category: not specified
    Status: done
    Test Result: idle

    Description:
    With CODE 10 we face the challenge of translations that are too late for Goldmaster. With openSUSE 10.2 we have the additional challenge of languages for the upstream packages (not for our only packages), only available after the betas.
    Gary suggested: We really need to look at getting a tool in place like Ubuntu's Rosetta so we can take translations from the openSUSE community in the short term instead of re-directing upstream.


    Display Switching - Santa Rosa (Feature No: 301418)

    Category: X.org
    Status: implementation
    Test Result: idle

    Description:
    Support for display switching in Linux that can detect and activate displays not present at boot time (attached to dock, or plugged into mobile system after boot).
    In Intel graphics driver currently built with driver process.


    Enable Evolution's IMAP/POP with Kerberos 4 (Feature No: 301476)

    Category: not specified
    Status: implementation
    Test Result: idle

    Description:
    Evolution should be able to support Kerberos authentication (specifically Kerberos v4) for IMAP/POP connections.


    Add FreeNX remote display technology (Feature No: 301526)

    Category: Applications
    Status: done
    Test Result: idle

    Description:
    Please add FreeNX software packages, the Free Software (GPL) Implementation of the NX Server. Ideally, please add a YaST module for configuration as well. NX is an exciting new technology for remote display. It provides near local speed application responsiveness over high latency, low bandwidth links. The core libraries for NX are provided by NoMachine under the GPL. FreeNX is a GPL implementation of the NX Server.


    Show bitrate in KNetworkmanager Applet (Feature No: 301667)

    Category: not specified
    Status: implementation
    Test Result: idle

    Description:
    This is a split off of feature 300495. That feature was for Netapplet, but we have KNetworkmanager as frontend, too, and shoud add the functionality there, too:
    This is a request from one of the Desktop Beta sites.
    When connected to a wireless network, the tray icon shows signal strength, but not the bitrate. It would be nice if this could be exposed in some way though Network Manager


    Learn yast2-repair handle encrypted partitions (Feature No: 301729)

    Category: YaST
    Status: done
    Test Result: idle

    Description:
    During repair, YaST is not able to detect which partitions are encrypted and use them properly.
    As /etc/cryptotab and /etc/fstab cannot be accessed, possible choice is to ask user which partitions are encrypted and for their passwords, or clearly state that the repair module doesn't support encrypted partitions


    Run Pkg callbacks in full screen window (Feature No: 301731)

    Category: Installation, Usability, YaST, zypp
    Status: done
    Test Result: passed

    Description:
    Currently the package manager callbacks are run in popups, which are appearing/disappearing. Display the status in the main window instead.
    The request is about popups when initializing a source.

    Pattern description should be shown in detailed view (Feature No: 301786)

    Category: zypp
    Status: implementation
    Test Result: idle

    Description:
    suse-beta AT cboltz DOT de writes
    The installation has a nice screen were you can select which patterns to
    install. This included descriptions of the selected pattern.
    And it has a "detail" view (the packagemanager in pattern mode) that shows you
    what packages a pattern contains.
    Unfortunately, the detail view does not show the pattern description anywhere.
    Please add display it somewhere - the "Online Update" view of the package
    manager might give you some inspiration.

    Consistent language labels in YaST (Feature No: 301789)

    Category: not specified
    Status: done
    Test Result: idle

    Description:
    In YaST, the selection of languages offers a list with all supported langauges. There is a rule that every language starts with a capital letter. This is in conflict with some of those languages, which require lower case.
    See bug 220228 for the discussion. We must decide if we should follow current rule or change it only at some places and for which languages should we change it.


    One Mini-ISO to rule them all (for INTERNAL use - testing) (Feature No: 301806)

    Category: Installation
    Status: done
    Test Result: idle

    Description:
    We currently need to build and use with every release, e.g. Alpha or Beta, a new Mini-ISO for network booting.
    I propose to build one Mini-ISO that can be used for all versions.
    I've heard that kexec should be able to do this. But perhaps there are other solutions to do it. Please investigate and propose possible solutions.


    Proper product dependencies (Feature No: 301809)

    Category: CIM, YaST, zypp
    Status: done
    Test Result: idle

    Description:
  • construct proper 'product objects' with similar semantics as packages
  • satisfy product upgrades
  • support NCC registration
  • Bug 223406


    Possibility to find KDC server (Feature No: 301812)

    Category: not specified
    Status: done
    Test Result: idle

    Description:
    yast2-ldap-client has a feature to look for available LDAP servers (using slp), yast2-samba-client is able to find domain controllers. It would be nice if yast2-kertberos-client could find KDC, so the module could offer default configuration, which could be just confirmed by user.
    The default kerberos domain (if there is still none set) is guessed to be the same as domain name (""/bin/ypdomainname") and the realm is the domain in uppercase. With the domain name, it is possible to look into DNS SRV records for KDC record. Michael, is this process correct or should also the first part (looking for default domain) be more sophisticated?


    ext4 Support in Basesystem (Feature No: 301897)

    Category: Filesystems, Installation
    Status: implementation
    Test Result: idle

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


    Make Abort respond during package installation (YaST NCurses) (Feature No: 301899)

    Category: YaST
    Status: done
    Test Result: idle

    Description:
    "Abort" does not respond during package installation via text install. See the details in bugzilla.
    The root of the problem is that the UI doesn't run in its own thread.


    Whole software management stack should warn about missing/oudated update source (Feature No: 301904)

    Category: Installation sources, Package and patch sources, Product and Registration Handling, Update
    Status: implementation
    Test Result: idle

    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). For the latter a daily updated file with a timestamp should be created in the YOU repository which the stack checks on the mirror if it's more than X days old. In both cases the "Online Update Configuration" module should be offered to run (and the registration server should of course not assign outdated mirrors then).
    [1] http://lists.opensuse.org/opensuse/2006-12/msg04280.html
    [2] http://lists.opensuse.org/opensuse/2006-12/msg04144.html


    Offer 'verify installed resolvables' functionality in zypper (Feature No: 301918)

    Category: zypp
    Status: done
    Test Result: passed

    Description:
    Dependencies of installed resolvables (patterns, patches, products) might break by various means, making the system inconsistent.
    rug
    rug verify
    This functionality should be offered in zypper.
    Test Description
    rpm -e --nodeps libtheora0; zypper ve
    it restored the lib

    Fix GCC bug #23551: dwarf records for inlines appear incomplete (Feature No: 301921)

    Category: Debugging, Toolchain
    Status: implementation
    Test Result: idle

    Description:
    SystemTap and other debugging tools use dwarf debuginfo to gather type information and storage locations of variables. This should work for all kernel code.
    The GCC isn't emitting complete debuginfo when functions are inlined. Since the kernel is heavily using inline functions its often not possible to generate tap scripts for this functions.
    References:
    http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23551
    http://sources.redhat.com/bugzilla/show_bug.cgi?id=1155


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

    Category: Pattern Deployment
    Status: implementation
    Test Result: idle

    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.


    -fstack-protector for all packages (Feature No: 301940)

    Category: Base System, Security
    Status: done
    Test Result: idle

    Description:
    Red Hat according to their press statements builds all of their distribution using -fstack-protector, the heuristic stack overflow detection.
    While we use -D_FORTIFY_SOURCE=2, this one only covers known arrays.
    I think we should also enable -fstack-protector for all packages. If we enable it by default in the compiler, all software will automatically get the benefit too.


    Configure routing table for several interfaces (Feature No: 301948)

    Category: Device Handling, Network, YaST
    Status: done
    Test Result: idle

    Description:
    On systems with several interfaces YaST2 network configures the routing table to utilize only one network interface for the default route, even when several interfaces are connected to the same (sub) net.
    So when this interface goes down, the default route will be removed and the network is not available anymore.
    YaST2 should be extended to a) set the routing table correctly for several interfaces and b) to allow the user to modify the metric/priority for each interface.


    make _FORTIFY_SOURCE _chk functions work with C++ (Feature No: 301951)

    Category: Base System, Security
    Status: done
    Test Result: idle

    Description:
    Currently the _FORTIFY_SOURCE protected string
    functions are only protected in C.
    Due to C++ scoping / namespace problems they do not port easily.
    This feature would require porting them for use in C++ programs.


    screensaver/screenlock support for finger print authentification (Feature No: 301953)

    Category: Screensaver integration, Security, X.org
    Status: implementation
    Test Result: idle

    Description:
    At least the default screensaver/screenlock used should support the authentification by finger print instead of password.
    The best solution would be that the screensavers/screenlocks support authentification through the PAM mechanism.


    [Beta2] kdm requires support for PAM to allow authentification by finger print (Feature No: 301954)

    Category: Desktop, Screensaver integration, Security, X.org
    Status: implementation
    Test Result: idle

    Description:
    kdm should support the PAM authentification methode. This is required to allow users to simply authentificate by swiping their finger over a finger print reader/scanner.


    Autoyast must detect dm-raid disk devices automatically (Feature No: 301959)

    Category: AutoYaST
    Status: done
    Test Result: idle

    Description:
    Since 10.2 yast can handle dmraid clustered disks.
    Autyast also works fine, but you have to pass the exact device string, that gets generated during installation.
    E.g. after booting once and dmraid set up the disks, you know the device string and can e.g. pass:
    /dev/mapper/sil_ahabebbgfhfa
    and everything works fine. But the last part of the string is generated and even varies between different machines
    of same hardware (e.g. sil_ahabbhbjfaag on another machine).
    So we have a chicken and egg problem here and installing on a wide range of machines is a pain.
    Here another string of an nvidia based dmraid array: nvidia_eabaajbf
    Partitions have a "_partX" appended, e.g.: sil_ahabbhbjfaag_part1
    Autoyast should realize that it's a disk and start installation on it on some general tag that tells it, to install on the first disk.
    I expect we need to collect the sil_, nvidia_ and other prefixes the dmraid drivers do use to identify dmraid driven disk devices.
    AFAIK on PATA/SATA and SCSI it works with /dev/sda and /dev/hda, in both cases it starts installation whether it's sda or hda in the end.
    It would be prefect if this would also work with dmraid devices. In the end it should not matter whether you have e.g. a mixture of machines with ATA(hda), SATA/SCSI(sda), HP HW raid(/dev/cciss/c0d0p1, this works already) or dmraid(sil_,nvidia_,..) driven disks, you should only need one autoyast.xml file to be able to install all your machines.


    Enhance OpenOffice_org package wrt YOU updates (Feature No: 301975)

    Category: Maintenance, Package and patch sources
    Status: implementation
    Test Result: idle

    Description:
    The number of security bugs found in OpenOffice has increased and it can be expected that there will be many more in the future. That means the package has to be updated via YOU regularly. The OpenOffice package has a size of more than 100MB. At the moment the whole package has to be downloaded (resp reconstructed via delta) by the customer even if a security fix only affects only one out of many subsystems. It would be desireable to split up the package in a sensible way in order to reduce the bandwith requirements of OOo security updates.


    Support GWIM Chatrooms in Kopete (Feature No: 301984)

    Category: Applications
    Status: implementation
    Test Result: idle

    Description:
    Support GWIM Chatrooms in Kopete.


    "Installation Sources" Filter Option "<In No Installation Source>" (Feature No: 302004)

    Category: YaST
    Status: done
    Test Result: idle

    Description:
    When doing a distro upgrade you can choose to "delete all third party packages" (or alike). In a running system there is no possibility to view/delete packages which are not installed/maintained from configured installation sources.
    Suggestion: Add to the YaST package manager's "Installation Sources" filter an additional list entry "<In No Installation Source>" at bottom which lists all packages not being included in all other installation sources.


    yast2 kerberos-client should support more pam_krb5 options (Feature No: 302014)

    Category: YaST
    Status: done
    Test Result: idle

    Description:
    pam_krb5 has a lot of usefull options. yast2 kerberos-client should be able to support them in the "advanced options" dialog.
    A special page "pam_krb5 options" would be fine for this.
    man 5 pam_krb5
    There are some AFS options. I do not know if we still support AFS.
    Another question is V4 support. This is needed of AFS I think.
    Other options are:
  • debug
  • addressless
  • external
  • ccache_dir
  • forwardable
  • ignore_unknown_principals
  • keytab
  • mappings
  • minimum_uid
  • proxiable
  • renew_lifetime
  • ticket_lifetime
  • use_shmem
  • validate
  • afs_cells
  • ignore_afs
  • tokens
  • krb4_convert
  • krb4_convert_524
  • krb4_use_as_req
  • debug_sensitive
  • banner
  • existing_ticket
  • initial_prompt
  • subsequent_prompt

  • Yast nfs client modifications to support NFSv4 mounts (Feature No: 302031)

    Category: YaST
    Status: done
    Test Result: idle

    Description:
    Nfs client module needs to be changed to be able to cater to NFSv4 mounts.


    sle10 syslog-ng should summarized repeated syslog entries (Feature No: 302032)

    Category: Systems Management
    Status: done
    Test Result: passed

    Description:
    If an application (like VDR) runs into a panic loop, e.g. when devices are missing, the application can send a lot of syslog entries to syslog-ng in just a few seconds. All these messages may be the same one, but syslog-ng does not summarize them (just as syslog did). The old syslog writes something like (last message repeated n times). Using the syslog-ng report style does have some advantages over the syslog one, but if an application send tons of messages the var file system is effected

    Support for Installation of "Suggested:" Packages (Feature No: 302039)

    Category: YaST
    Status: implementation
    Test Result: idle

    Description:
    The package management tool(s), especially the YaST Software Management module, should support the "Suggests:" hints of packages and allow the users to easily install the suggested packages of the currently selected package ("Install Suggested Packages" in the context menu), the packages in the current list ("All In This List/Install Suggested Packages") and all installed packages.


    Support Gateway Tablets (Feature No: 302055)

    Category: Configuration, Mobility, X.org
    Status: done
    Test Result: idle

    Description:
    To support Gateway Tablet PCs we need this:
  • add the config for the tablet device to the SaX2 Tablet PC section
  • fix HAL to set the correct baud_rate
  • update the x11-input-fpit driver to work correct

  • YOU Beta Staging for Box Products (Feature No: 302060)

    Category: Maintenance, Package and patch sources
    Status: done
    Test Result: idle

    Description:
    We need a beta testing repository for openSUSE YOU patches. This should be driven mostly automatic.
    Main target is that the community is able to test easily our opensuse patches before we release them.
  • The patches currently in the box queue
  • all recommended and optional patches
  • security patches: if CRD is fulfilled (+1 Day)
  • To avoid going past CRDs, they should be summarized in a mail (generated by extra script) once a day. (Like "CRD for OpenOffice is going to expire tomorrow.").


    Change Gnome Keyring Password (Feature No: 302065)

    Category: Desktop
    Status: done
    Test Result: idle

    Description:
    There should be a way to change the keyring password in Gnome Keyring Manager.
    This is a lightweight alternative to more in-depth integration of gnome-keyring-manager and other systems.
    I don't know if the KDE key service needs this or not.


    iSCSI support in autoyast (Feature No: 302081)

    Category: AutoYaST, Storage and Partitioning
    Status: done
    Test Result: idle

    Description:
    it would be nice to have support for iSCSI in autoyast via XML profile. See also bug #259429


    Add isns support to yast2-iscsi initiator and target (Feature No: 302083)

    Category: Storage and Partitioning, YaST
    Status: done
    Test Result: idle

    Description:
    Add isns support to yast2 iscsi initiator.
  • add/edit /etc/iscsid.conf with the ip address of the isns server.
  • add/edit/ect/ietd.conf with the ip address of the isns server
  • add isns discovery to iscsi initiator via the command: iscsiadm -m discovery -t isns

  • UMTS card support (Feature No: 302102)

    Category: Hardware and Drivers, Mobility, Network, NetworkManager
    Status: done
    Test Result: idle

    Description:
    The current distrubtion of UMTS on laptops (seperate cards and build-in ones) forces us to support this as well.
    Goal is that our distribution supports UMTS out of the box in a simple way.
    Therefore we need:
    For the user space networkmanager needs to be enabled to support UMTS. Afaik 2
    approaches are possible
    a) write new code
    b) use existing code and adapt smpppd
    From my discussion with seife I learned that our kernel already is in a good
    shape and is able to support the major chipsets. Perhaps this need
    some more investigation.
  • support in NetworkManager (and KNetworkManager)
  • support for the most used chipsets

  • switch off paranoid ext3 fsck (Feature No: 302118)

    Category: Base System, Filesystems, Maintenance
    Status: done
    Test Result: idle

    Description:
    ext3 filesystems still get fsck'd after a certain number of mount operations or after a certain time. The intervals got increased but that just hides the problem. The lengthy fsck operation hits users at unexpected times.
    I'd assume that ext3 is sufficiently reliable to not require such paranoid checks. Therefore those checks should be switched off. The fs will still be fsck'd when not umounted properly.


    Load package selector and libzypp only when needed (Feature No: 302119)

    Category: YaST
    Status: implementation
    Test Result: idle

    Description:
    The YaST2 UI should load the code for the package selector and libzypp only when needed. Not all applications / YaST2 modules need package selection code, yet for all of them the respective code from the YaST2 UI and libzypp is loaded.


    Firmware installation while hardware configuration (Feature No: 302130)

    Category: Base System, Directory Services
    Status: done
    Test Result: idle

    Description:
    While configuring a WiFi NIC the YaST network module informs about the missing firmware files.
    This is a show stopper for inexperienced users. They don't know how to get the required files and where to store them.
    The bcm43xx-fwcutter packages shows how easy the firmware download and install could be. But this has to be available from the GUI.
    Therefore I suggest to install such a package as bcm43xx-fwcutter and to trigger the script to download and install the firmware on request by the user.
    As this might be a legal problem I suggest to discuss this with an lawyer before any inplementation starts.


    Redesign of YaST printer module (Feature No: 302133)

    Category: Printing, YaST
    Status: done
    Test Result: idle

    Description:
    The YaST printer module needs a redesign of its workflow and its design.
    In its current state it is highly confusing even for users with a technical background.
    E.g. CUPS settings are well hidden, edit printer queue dialog is a confusing, etc.


    Use editline instead of readline (Feature No: 302138)

    Category: Base System
    Status: done
    Test Result: passed

    Description:
    readline is GPL licensed, which means that many packages we ship cannot link against it. For example, we are unable to distribute the PHP readline extension.
    editline is a compatible reimplementation of the library under a BSD license, allowing many more packages to make use of the package.
    Test Description
    We have libedit0.rpm

    zypper - rug command parity (Feature No: 302148)

    Category: YaST, zypp
    Status: implementation
    Test Result: idle

    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


    Allow zypper to install local/remote RPM (Feature No: 302151)

    Category: YaST, zypp
    Status: done
    Test Result: idle

    Description:
    It would be really nice to have Zypper being able to handle local RPMs,
    as well as ones on a particular site. This is already handled in a similar way
    with the YaST installer, and of course I can directly use rpm, but then it
    won't be able to solve dependencies.
    If it's on a HTTP/FTP site, then it should download the RPM, then try to solve
    dependencies and install it. One should be able to do:
    zypper in http://somedomain.com/package.rpm packageonrepo somelocalpackage.rpm


    KDE 4 Integration into openSUSE (Feature No: 302155)

    Category: Desktop, Installation, Installation sources, Late Admission
    Status: implementation
    Test Result: passed

    Description:
    KDE 4 should be ready for openSUSE 11.0.
    - 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.0
    - we'll have a mix in icons as KDE4 comes with a new icon set (oxygen)

    Cache YaST Debugging Logs in Case of Failure (Feature No: 302166)

    Category: Installation, YaST
    Status: done
    Test Result: passed

    Description:
    YaST is killed
    without any obvious reason
    We often need reporter turned Y2DEBUG on, reproduced the error and attached logs again. This is inefficient and often also impossible (to exactly reproduce the behavior).
    debugging log into memory
    Currently y2base at least logs the command how it has been killed - thanks to a correct signal hanler (standing applause).

    Support root on encrypted filesystem (Feature No: 302191)

    Category: Base System, DATA Center Features, Linux Kernel, Multipathing, Storage and Partitioning
    Status: done
    Test Result: passed

    Description:
    LUKS provides the necessary infrastructure to use an encrypted filesystem. The system should be enhanced to handle root on a LUKS-encrypted filesystem.
    It works in Beta 2 if one sets it up like described at http://en.opensuse.org/Encrypted_Root_File_System (including an encrypted swap partition if setup with a fixed length key like described in the discussion tab).
    Sadly installing into an encrypted root filesystem still isn't supported by Yast. See https://bugzilla.novell.com/show_bug.cgi?id=386426 for a bug report / feature request.

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

    Category: YaST
    Status: done
    Test Result: passed

    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.

    Gnome - A new applet/tool to show system configuration info (Feature No: 302198)

    Category: Desktop
    Status: implementation
    Test Result: idle

    Description:
    Can we get a desktop applet to show critical system info? Something that shows the following types (more info could be better) : host name, logged in user, Linux version with kernel version, ip address, mask & gateway, network interface speed and duplex, disk utilization, CPU info, CPU utilization, memory utilization and maybe even the top 5 CPU-using processes. (There's probably a few more that would be good but those are the ones that come to mind at the moment.) I can go to different places to get this info but one place would be nice. Give me a hot key to press to show it like, Alt-F12, or maybe assign it to the seldom-used button next to the right-Control button. And/or, put it on the Computer menu. Add a "system info" option under the "Shutdown" option. Or make a link from the words, "System" or "Status" on the Computer menu that I can click on to show it. The OpenSuSE 10.2 KDE desktop shows the user and host name at the very bottom of the Computer menu. That is nice. Make that the active link to show system info.


    Clean up update selection (Feature No: 302239)

    Category: Installation, Update
    Status: implementation
    Test Result: idle

    Description:
    Current package selection for online update is not intuitive and has at least one bugs e.g. check beside of check box. The usability team should check the whole piece and provide suggestions (e.g. colour scheeme.


    Allow to set delivering root's mail to user's mailbox (Feature No: 302264)

    Category: YaST
    Status: done
    Test Result: passed

    Description:
    Currently it is possible during installation to set to deliver system mail (sent to root) to a mailbox of a regular user.
    Please, add this option also to installed system.

    Add possibility to install a package from Nautilus (Feature No: 302267)

    Category: YaST
    Status: done
    Test Result: idle

    Description:
    With ZMD, there was a GUI for installing RPM packages in Gnome when clicking on
    them in Nautilus.
    Because ZMD isn't installed by default anymore - there is no graphical
    replacement under Gnome. In KDE you can click in Konqueror on a RPM package and
    install it with YaST.
    But YaST itself does not handle single RPM packages.
    It would be great if you can embed YaST in Nautilus the same way it is embedded
    in Konqueror when clicking on single RPM packages.


    Explicit ALUA Support (Feature No: 302269)

    Category: Multipathing
    Status: implementation
    Test Result: idle

    Description:
    Please add a hardware handler for the DM-MPIO framework to enable explicit ALUA support (ALUA: T10 Asymmetric LUN Access or T10 ALUA).
    ALUA is a well defined industry standard (eg SPC-3) in the multipathing area, but the specs did not make it into the Linux kernel yet. For example, explicit ALUA support allows active/passiv mode and explizit enabling/disabling/preference of pathes to the storage service processors resulting in a smart failover configuration. More and more customers are asking for this functionality on the Linux platform. Today, path mapping is not implemented in the Linux kernel.
    EMC would like to develop the hardware handler together with Novell in the scope of a joint engineering project. It is the intention to get the new hardware handler be accepted and implemented upstream - no proprietary approach. EMC CLARiiON group would provide CLARiiON storage array loaners for testing and development purposes in Nuernberg. The estimated development engineering effort on Novell side is 2 man months.


    Show Release Notes during Package Installation (Feature No: 302342)

    Category: Installation, YaST
    Status: done
    Test Result: passed --Christian Boltz 23:04, 22 April 2008 (UTC)

    Description:
    Feature request based on bug report #175495
    On this page:
    http://www.linuxforums.org/reviews/review_of_suse_10.1_2.html
    "After a little while I was presented the release notes. Although it is always
    interesting to read release notes, I got used to read this type of
    documentation while I have nothing else to do. At this precise moment I
    couldn't wait to reboot the computer in order to see what my newly installed
    SUSE 10.1 was like and there was no way I was going to sit down and read
    through all these pages... I thought of the 30-40 minutes I spent doing nothing
    while the system was installing the packages. The notes would have been read by
    now, and I would actually have liked reading them. I clicked "Next"."
    Indeed why not present the release notes as soon as possible during the
    installation. Give the user an additional tab to select from:
    - slide show
    - instalation (packages and time)
    - Release notes

    YaST Installatiion GDB debugging turned on on request (commandline) (Feature No: 302346)

    Category: Installation, YaST
    Status: done
    Test Result: idle

    Description:
    gdb debugging
    Y2GDB=1
    y2base
    tee


    Offer also USB stick when choosing media source in YaST (Feature No: 302382)

    Category: YaST
    Status: done
    Test Result: idle

    Description:
    In the dialog where is user choosing the location of Addon product media during installation (now are URL, NFS, DVD and others) could be another option: USB stick.


    Full commandline support in YaST2 Product Creator (Feature No: 302395)

    Category: OEM Preload, Product and Registration Handling
    Status: done
    Test Result: idle

    Description:
    We need a full fletched command line capable version of the Product Creator.
    Right now you need to manually go through the GUI in order to create a configuration file that can then later be used to create the images or directoies with the command line capable part of Product Creator.
    For automated production environments, especially if they are certified by ISO or adhere to ITIL standards, this is not sufficient. The complete process including configuration file creation needs to be automated.
    : Command : create-config : Optionen: : name [string] Name of the configuration : sles_repos [string] Path to sles repository : configfile [string] Path to the configuration file (default is : /var/lib/YaST2/cd-creator/cdcreator.xml : autoinst [datei] Path to autoinst.xml file : isolinux_cfg [datei] Path to isolinux.cfg file : gpg_key [string] GPG key ID used to sign a product : output_dir [string] Path to the output directory : iso_output_dir [string] Path to the output directory : for ISO image : help Display this help screen : verbose Show progess bar :


    Have iscsi initiator start after target. (Feature No: 302415)

    Category: Storage and Partitioning
    Status: implementation
    Test Result: passed

    Description:
    The business case behind this is that I have found it nice to be able to use the iscsi initiator and target from the same box for testing purposes. However if you go an look in the /etc/init.d/rc3.d/ directory you will notice that both the target and the initiator startup at the same time. The problem this causes is that when the server is rebooted the target doesn't have a chance to start before the initiator tries to start. Therefore the initiator has can't discover the target. Simply changing it so that the initiator start script occurs after the target will allow you to use both the target and the source from the same box. This is very handy for Xen testing.

    Collecting hardware information (Feature No: 302445)

    Category: Hardware Components Database, Product and Registration Handling, Systems Management
    Status: done
    Test Result: idle

    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


    freshness checking of repositories (Feature No: 302454)

    Category: Installation sources, Maintenance, Package and patch sources, Security, Update
    Status: done
    Test Result: idle

    Description:
    The cryptographic signing of the update repositories already makes them secure to use, but is still lacking.
    One major problem is the one of outdated mirrors. These can be caused by either the ftp server stopping mirroring, or even worse the attacker controlling the server. This makes the attacker able to hold back important security updates and so perhaps break into the machine.
    The idea is now to mark the repository to specify a "must have refreshed in n days" and also specify a "discontinuation date" or "discontinued" tag.
    If the repository has a last modified of 4 weeks ago, but says "refreshed within 2 weeks"the installer / updater shoulld warn that it is outdated and the user should check if the mirror settings are correct.
  • TTL of product
  • refresh interval

  • zypper: Provide way to upgrade (Factory) (Feature No: 302460)

    Category: zypp
    Status: done
    Test Result: idle

    Description:
    We need a zypper way to replace the Factory upgrade feature of Yast.
    The feature is aimed to openSUSE developers that want to (have to) have an uptodate Factory installation. It doesn't have to be too intelligent about traps to avoid, but it should have good error reporting, so that the developer can avoid the traps itself.
    E.g. I want to upgrade from 10.3-Alpha4 to Factory and would call zypper upgrade. Then the tool tells me about the problems it can't solve itself, I deinstall 64bit OpenOffice, do the upgrade again and install the 32bit OpenOffice myself again.
    It would be good if upgrades Patterns too, but that's only desireable. This feature is about upgrade of packages.


    Package "Misc Console" font independent of KDE (Feature No: 302474)

    Category: Desktop
    Status: done
    Test Result: idle

    Description:
    While the font "Misc Console" has nothing to do with KDE from a technical point of view (IIRC it was designed by some KDE developer), it's packaged in the kdebase3 package.
    If that font would be packaged separately, it would be installed even without KDE.
    Maybe it would be good to package the fonts "Xos4 Terminus", "SGI Screen" and "Misc Console" in one package "console fonts" because all that three fonts are very good monospaced fonts for editing and command line usage.


    Be able to get software selection from AutoYaST file for installation into directory (Feature No: 302501)

    Category: YaST
    Status: done
    Test Result: idle

    Description:
    The YaST dirinstall module should provide the option to use an AutoYaST xml
    file to specify the package selection that has to be installed into a
    directory.
    This may make re-installations or multiple installations of the same OS across
    different servers into a directory more efficient.


    Integrate tcptraceroute into SLES10 or SLES11 (Feature No: 302509)

    Category: Network
    Status: done
    Test Result: passed

    Description:
    Intel/customer is asking to add tcptraceroute to the OS.
    tcptraceroute is a traceroute implementation using TCP packets.
    The more traditional traceroute(8) sends out either UDP or ICMP ECHO packets with a TTL of one, and increments the TTL until the destination has been reached. By printing the gateways that generate ICMP time exceeded messages along the way, it is able to determine the path packets are taking to reach the destination.
    The problem is that with the widespread use of firewalls on the modern Internet, many of the packets that traceroute(8) sends out end up being filtered, making it impossible to completely trace the path to the destination. However, in many cases, these firewalls will permit inbound TCP packets to specific ports that hosts sitting behind the firewall are listening for connections on. By sending out TCP SYN packets instead of UDP or ICMP ECHO packets, tcptraceroute is able to bypass the most common firewall filters, making it possible to trace the path to the destination.
    tcptraceroute RPMs already exist for openSUSE. They are in a YaST_package_repository "Guru's RPM site"
    http://linux01.gwdg.de/~pbleser/
    A Novell ftp mirror also lists packages for the last openSUSE versions:
    http://ftp.novell.hu/pub/mirrors/guru/rpm/packages/Network/tcptraceroute/?C=S;O=A
    The RPM install and work on SLES9 but the customer likes to have them integrated and supported in SLES.

    Combine software management with repository management (Feature No: 302517)

    Category: YaST
    Status: done
    Test Result: passed

    Description:
    Consider combining the repository manager with the software manager.
    One option may be to add a new entry to the "Extra" menu, which would run repository editor.

    Make more YaST modules firstboot-capable (Feature No: 302520)

    Category: YaST
    Status: done
    Test Result: idle

    Description:
    Currently only a limited set of YaST module is capable to run in firstboot environment, the other are either not tested or not capable.
    We should get a wide list of module in the default configuration, from which the vendor afterwards removes modules which he is not interested in.
    Currently we have a partner request (for SP1) for following modules:
    The ones which we already have should of course be kept
  • Welcome Screen
  • License(s)
  • Setting up timezone and system clock
  • Keyboard layout
  • Machine name and domain
  • Root password
  • Local user account creation
  • Try to register and activate
  • Include the Hardware Configuration step in (Sound, Printers, Bluetooth..)
  • Completed Installation screen

  • Use PackageKit for Updater Applets (Feature No: 302522)

    Category: Hardware Components Database, Systems Management
    Status: implementation
    Test Result: idle

    Description:
    PackageKit
    role based software management
    Role Based YaST


    Add "storage media" applet to KDE kicker (Feature No: 302545)

    Category: Desktop
    Status: done
    Test Result: idle

    Description:
    The "storage media" applet is extremely useful for handling temporary available media
    such as CD, DVD, camera, usb-stick, ipod...
    It is not shown as long as no media is attached and thus does not need space in the kicker bar,
    when media is attached it gives handy shortcuts for accessing them.


    Get fonts for exotic languages installed with minimal installation (Feature No: 302548)

    Category: YaST
    Status: done
    Test Result: idle

    Description:
    We often have the problem, that fonts for "exotic" languages
    are missing during the second phase of the installation because
    the packages containing these fonts are missing on CD1.
    During the first phase of the installation, everything works because
    the fonts are available in instsys (installation image).
    But after the installation of CD1 is finished, the initial reboot
    happens and the installation of the other CDs continues in the
    installed system.
    If the fonts for language X were missing on CD1, one will see boxes.
    In this bugreport I want to discuss the possible solutions for this
    problem.
    One possible way may be to copy the fonts from inst-sys to the target system so that at least fonts which had been used during installation are available in second stage as well.


    zypper: forced install (Feature No: 302551)

    Category: Systems Management, zypp
    Status: done
    Test Result: passed

    Description:
    Zypper should provide a way to forcefully (re)install a package e.g. through a --force, -f option of the install command.

    Self-sufficient Busy Indicator for YaST2 UIs (Feature No: 302559)

    Category: not specified
    Status: done
    Test Result: idle

    Description:
    The YaST2 UIs should get a busy indicator that runs by itself as long as some background action (package download etc.) shows activity every once in a while. It should terminate if the background action is stalled for some time so the user can see whether or not the machine is still actively doing something.
    Bug #296945 and follow-on bug #308231 show that we currently don't have any adequate mechanism for this.
    The general idea is:
  • Show some animation (might be some progress-bar-like widget, might be an MNG animation, might be something else) that shows the user that there is activity
  • Animate this for some time (to be determined upon the first start)
  • If there is feedback from the background action within some time frame, keep animating
  • If there is no feedback from the background action within that time frame, stop animating so the user can see that the background action is stalled

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

    Category: not specified
    Status: done
    Test Result: idle

    Description:
    Add DMRAID support to SLES installer. The SuSE autoyast installer needs to
    see and install SLES to SW RAID volumes, using DMRAID.


    Adding package key handling in YaST (Feature No: 302593)

    Category: YaST
    Status: done
    Test Result: mostly passed
    YaST got a nice key managemant inside the package manager.
    But: trust net information isn't displayed anywhere.
    --Christian Boltz 19:51, 26 May 2008 (UTC)

    Description:
    I think we need a YaST module to show and modify the accepted gpg keys for package installation.
    Esp. due to increasing number of gpg keys (The build service will provide one per project) we need to show and remove them later again.
    It would be also nice to show informations from a trust net, this means that pub keys are signed by other keys and make this visible.

    zypper: machine readable output(s) (Feature No: 302595)

    Category: Systems Management, zypp
    Status: done
    Test Result: idle

    Description:
    To further enable zypper to be used by scripts and GUIs, zypper must provide a machine-readable output. A suggestion has been made that we should continue using XML output and finish it's implementation, but other kinds of outputs might come in handy as well.
    For more details and discussion, see the opensuse-softwaremgmt mailing list thread shown in references


    Please include VMware network and harddisk drivers in standard Linux kernel (Feature No: 302626)

    Category: not specified
    Status: implementation
    Test Result: idle

    Description:
    The VMware userspace tools and Linux client drivers have been released as
    Open-Source under the GPL:
    http://www.heise.de/newsticker/meldung/95853
    http://open-vm-tools.sourceforge.net/index.php
    Could you please include at least the network and harddisk drivers in your
    standard Linux kernel, so that users of VMware can benefit from the
    performance.
    Graphic driver and mouse are not really important for SAP users, but they
    would be nice to have as well.


    Upgrade of NTP from 4.2.0 to 4.2.4 (Feature No: 302629)

    Category: not specified
    Status: implementation
    Test Result: idle

    Description:
    In the TSP system NTP is responsible for time synchronization. One or more external time servers and one undisciplined local clock (for backup purposes) are configured. If only one external time server is available, then the clock selection algorithm will sooner or later mark the external time server 'false ticker' and synchronize to the local clock. Afterwards it will never switch back to the external time reference.
    In the latest versions of NTP (4.2.2 or later) a new command ('true') has been introduced. If there is only one external time server configured, it can be designated 'true chimer' with this command and the problem will not raise.
    This solution has been tested at Ericsson.


    Installation should try to umount disks before rebooting to second stage (Feature No: 302647)

    Category: Installation
    Status: done
    Test Result: idle

    Description:
    Sometimes YaST is unable to umount disks before finishing the first stage installation. Some processes having some open files might be still running. There should be a fallback after YaST finishes to try to shut these processes down or even kill them and then reboot the system.
    It should be similar to /sbin/reboot, actually /sbin/reboot in Linuxrc (inst-sys) might help.


    System installation and upgrade workflow: kernel %post (Feature No: 302660)

    Category: Booting, Installation, Linux Kernel, Update, YaST
    Status: done
    Test Result: idle

    Description:
    The system installation and upgrade workflow currently goes like this:
    The kernel %post script has to skip creating an initrd and adding the kernel to the bootloader because the bootloader configuration is not guaranteed to exist at this point. (It checks for "$YAST_IS_RUNNING" == instsys).
    When a kernel is installed later, the kernel's %post script is responsible for creating the initrd and adding the kernel to the bootloader. This is necessary so that kernels installed with bare rpm will work, too.
    This separation duplicates functionality between the kernel's %post script and YaST, and has triggered nasty problems more than once now. Can we please get rid of this duplication of code, and handle the initrd creation and bootloader configuration update in the kernel's %post script exclusively? I could imagine several approaches to get there:
  • Select packages to install
  • Install packages, including the kernel(s).
  • Create bootloader configuration
  • Create initrd(s) referenced by the bootloader configuration
  • Defer installation of the kernel rpms until after the initial bootloader configuration has been written.
  • Install the kernel package(s) with --noscripts initially, and run their scripts only after the bootloader configuration has been written.
  • Install the kernel packages as we are doing now, checking for "$YAST_IS_RUNNING" == instsys, and re-run them without setting YAST_IS_RUNNING after the bootloader configuration has been written.
  • Select the bootloader type early during installation, before installing packages, and create a bootloader configuration. Let the kernel's %post script handle initrds and the bootloader configuration.

  • integrate "software repositories" with "community repositories" (Feature No: 302674)

    Category: Installation sources, YaST
    Status: done
    Test Result: passed

    Description:
    The existence of two modules for such simple (from user point of view) tasks is confusing. Instead of one place to manage repositories, you have to switch back and forth to manage them.
    Test Description
    "yast2 repositories" includes Community Repositories as one of the options after Add

    Replace pine by alpine and put alpine on the OSS media (Feature No: 302834)

    Category: Applications
    Status: done
    Test Result: passed

    Description:
    The University of Washington, authors and copyright holders of Pine, is transforming Pine into a new version called Alpine, with a more liberal license and enhanced features. This is a strict improvement over Pine, able to process the same command-line options and config files, and I have personally been using it for months with good success even though it is currently only at version 0.9999.
    We already have Alpine in Autobuild, and now, after the release of openSUSE 10.3 would be a good point to make the transition to get immediate feedback and maintain openSUSE at the leading edge, so I'd like to see this change in Alpha 1.
    Test Run Description
    alpine is present and has survived reading my 183M inbox. UTF-8 appears to work.

    Installer: Search and Load drivers from predefined location (Feature No: 302851)

    Category: not specified
    Status: implementation
    Test Result: idle

    Description:
    The SLES10 installer currently supports including drivers from floppy disks
    and other media. We would like you to include a feature to the installer where
    we can pass arguments (path that contains all required drivers) at boot time
    where the installer can scan for drivers and load them automatically. The
    drivers would be stored on USB flash storage device which would be permanently
    mounted inside the machine. This would help in automated installs where we can
    store the drivers before the installer is invoked.


    suggest convenient names for LDAP, Kerberos, NFS, NTP,... (Feature No: 302863)

    Category: YaST
    Status: done
    Test Result: idle

    Description:
    To allow easy maintenance of company networks, many companies (e. g. suse.cz) use convenient names for service providing servers, e. g.:
    Such configuration allows changes of dedicated servers only by changing of DNS records for these aliases.
    It would be nice, if local server lookup in the service configuration will probe for these names (aliases) and if they exist, propose them as first in order (or even propose them without lookup) and document these names in the administrators manual.
  • ntp.example.com, ntp1.example.com, ntp2.example.com
  • nfs.example.com
  • kdc.example.com or kerberos.example.com
  • ldap.example.com

  • Provide support for MHTML with Firefox (Feature No: 302866)

    Category: Applications, Desktop, Firefox
    Status: done
    Test Result: idle

    Description:
    Several customers have expressed interest for MHTML support.
    PSA in particular as a lot of microsites that are hosted on their intranet in MTHML format.
    From Nick:
    There is a repackaged version of the MAF extension written
    by Christopher Ottley that I was able to install on SLED Firefox and use
    to read a simple MHTML file. It can't _save_ MHTML files, however. Also,
    I haven't done extensive tests so it could be buggy in various ways.
    I downloaded the code for the extension and it's fairly weighty, at over
    eight thousand lines of Javascript (Mockingbird is about one thousand).
    There are also some native Windows libraries, so perhaps saving is only a
    matter of recompiling for SLED. It would probably take me a week to go
    over everything and give a more complete answer about what I could and
    could not do, exactly, and in what time frame. In the short term, though,
    I think we could provide a patch that people could test out.
    As for Mockingbird, I am still working on incorporating my findings from
    JPMC into the extension. I was about to send an update to the guys there
    at the end of my week two weeks ago, but I discovered a problem with the
    menu positioning code that I would like to nail before sending them an
    updated extension. I hope to have this done either today or tomorrow.
    From Nick on Sep. 20th 07:
    On a tangential note, I have also begun working on adding MHTML support to
    Firefox by trimming down the open-source MAF extension into something more
    manageable. I probably have another 5--8 days of work to get it to a point
    where I'd be happy to beta test it. I have a longer email I sent to Jared
    last month regarding MHTML support which I could share with you, but in
    short it's possible and I would recommend starting from the MAF codebase
    but building our own extension.


    Repository priorities (Feature No: 302872)

    Category: CIM, Systems Management, zypp
    Status: done
    Test Result: idle

    Description:
    Choosing betweeen multiple package alternatives (provided by different repositories) must be deterministic in the software management (resp. the dependency solver).
    best
    official


    GUI for synergy (quicksynergy) (Feature No: 302881)

    Category: Storage and Partitioning
    Status: done
    Test Result: idle

    Description:
    In openSUSE 10.2 and 10.3 we have synergy, a tool to share keyboard and mouse across machines (compare feature #301242). This is configured by commandline, we could add a gui tool which already exists, to make things easier. See http://quicksynergy.sourceforge.net/


    Have option in Yast to not overwrite /etc/hosts (Feature No: 302882)

    Category: Network, YaST
    Status: done
    Test Result: idle

    Description:
    A customer is unsatisfied because he observes that yast2's dns module (SLES10 SP1), if the network interface is set up with static IP address, always overwrites the hostname entry in /etc/hosts and he cannot unselect the "Write hostnames to /etc/hosts/" checkbox which is unsensitive (greyed) in that case.
    This checkbox, like others in the "DNS and hostname" configuration window, looks to be designed for DHCP purpose only. The box can be unchecked indirectly, as it reflects the status of WRITE_HOSTNAME_TO_HOSTS value in /etc/sysconfig/network/dhcp file, but I've observed that it as no impact in static IP mode and the dns module still read and write the hostname entry in /etc/hosts.
    Customer has had bad experience in previous versions of SLES where yast corrupted his hosts file. So he asks us to consider a modification allowing to block any write to /etc/hosts by yast.


    drop Sax2 X-VNC module (Feature No: 302884)

    Category: Systems Management, YaST
    Status: done
    Test Result: passed

    Description:
    Since the SaX2/X developers told me more than one time (in bugreports) to not use the VNC module of SaX2 to be able to connect to active X sessions via vncviewer because this would cause problems in X (and to use instead KDE/GNOME/YaST solutions), I request now to drop the module from Sax2 if it not work.
    Btw. I would prefer to get X/SaX2 fixed instead of drop, but if it doesn't work in general: drop it.

    add more Tablet PCs to SaX2 Tablet Section (Feature No: 302889)

    Category: Configuration, Desktop, X.org
    Status: done
    Test Result: idle

    Description:
    We need to extend the SaX2 Tablet Section with more entries for known Tablet PCs.
    I already provide a special SaX2 version in my OSBS home project since months which contains known and tested configs for TabletPCs. They all worked as tested last time.
    Instead of list them by vendor/Name I grouped them under one Vendor named "TABLET PCs" and the different configs in the 'Name' section as a string with "Laptop vendor/Model". This make it easier for the user to find the right config for a Tablet PC.
    You can get the src package with the patch here: http://download.opensuse.org/repositories/home:/dkukawka/openSUSE_Factory/src/


    openvpn with auth-pam (Feature No: 302893)

    Category: Compatibility libraries and binaries, Linux Kernel, Xen Virtual Machine Monitor
    Status: done
    Test Result: idle

    Description:
    Customer would like to see the openvpn package compiled with the auth-pam plugin.


    strongSwan IKEv2 (replacing openSwan) (Feature No: 302909)

    Category: Network, Security
    Status: done
    Test Result: idle

    Description:
    This is a detail of the overall IPv6 story.
    We need IKEv2, and the best option currently is to switch to strongSwan.


    Ntp server configuration and DHCP and DNS configuration (Feature No: 302916)

    Category: not specified
    Status: done
    Test Result: idle

    Description:
    As soon as a users enables NTP it should be possible to add the appropriate options to the DHCP and information to the DNS zone definiton (SRV records).
    With the corresponding features in the clients a better auto configuration is possible.
    In a first step this will only work if the involved services run on the same system.
    But for enterprise environments it's quite often required to split to dedicated and even multiple servers. Therefore the second step sould be support to read and modify servers which are part of the own scope or domain.


    Allow to one-time synchronize local clock with NTP server (Feature No: 302917)

    Category: YaST
    Status: done
    Test Result: idle

    Description:
    It would be greate if YaST time setup would allow to read the current clock setup from NTP server using ntpdate. The idea is to have a button to do that.
    The use case: if you get a new machine, the BIOS time is typically incorrect. Simply pressing the button would allow easy setup while avoiding using NTP all the time.
    The feature would be great at installation time but also on a running system.


    Improved argument handling for zypper (Feature No: 302919)

    Category: CIM, Systems Management
    Status: implementation
    Test Result: idle

    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: done
    Test Result: idle

    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).


    Installation In An IPv6 Environment (Feature No: 302926)

    Category: Booting, Installation
    Status: implementation
    Test Result: idle

    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.

  • Update the default SLED 'Save As' dialog - Round 2 (Feature No: 302929)

    Category: 3D Accelerated Desktop, Applications, Desktop, Look & Feel, OpenOffice.org
    Status: implementation
    Test Result: idle

    Description:
    This feature relates to fate feature #301826
    There has been at least one bug reported on this for SLED and openSUSE:
    https://bugzilla.novell.com/show_bug.cgi?id=228318
    The save file dialog remembers the folder location, but not the window placement or the window size.
    It's actually irritating a lot of users has they have to every time stretch the window and reposition it before they can use it.
    Tested on SLED10 SP1 with compiz at 1024x768.
    The objective of this fate entry: once the view is remembered to be shown as expected, it should remember the size and position of the window OR simply open much bigger (Width and Height) by default.
    For more details, please see:
    http://www.flickr.com/photos/guylunardi/sets/72157594404992242/


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

    Category: Package and patch sources, zypp
    Status: implementation
    Test Result: idle

    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'


    Split translations out of installation system (Feature No: 302955)

    Category: Desktop
    Status: done
    Test Result: idle

    Description:
    The translations of yast are the biggest part of the installation image.
    These should not be part of the image, but should be pulled in from the product media as the user selects them.


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

    Category: Installation, YaST
    Status: done
    Test Result: passed
    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.

    Take system load and power when checking for updates (Feature No: 302960)

    Category: Package and patch sources, zypp
    Status: done
    Test Result: idle

    Description:
  • system is running on batteries
  • system is running on high load
  • This could also be achieved by adjusting the "nice" leve of the checking process in these cases.


    Allow cancel during refresh of repositories. (Feature No: 302962)

    Category: YaST, zypp
    Status: done
    Test Result: idle

    Description:
    When I adding an installation source, YaST begins to downloads a repository
    description. If the description is large (like the one for oss installation
    source) it may take a long time... But there is no button "cancel" to cancel
    the download process.
    Note: it is just necessary to return false to the callback in libzypp. Also libzypp needs to be chacked to see what needs to be done for curl download progress.


    Unified Terminology: "repository", "patch", ... (Feature No: 302970)

    Category: Systems Management
    Status: done
    Test Result: idle

    Description:
    Standardize terminology: naming of software repositories with the term "repository" or "software repository"
    throughout. The terms "Installation source" (Yast) and catalog (ZLM) are deprecated as of plaform use.
    An exception is made within rug, where this would change the command line shorthands, and in general where
    SRM is concerned, as "catalog" has a very specific meaning to users of the enterprise product. But we endeavour
    to use "repository" wherever possible throughout the platform going forward


    relative URLs for autoyast profile+scripts (Feature No: 302973)

    Category: AutoYaST
    Status: done
    Test Result: idle

    Description:
    it would be nice to be able to use relative URLs in and for the autoyast profile.
    So that:
    autoyast=relurl://my.xml
    would look for the profile on the inst-source in the file my.xml
    for scripts it would be the "location" element that must be changed.
    There are two options to interpret the relative URL. Relative to the autoyast profile and relative to the installation source. Both should be implemented.


    yast modules need to be quicker to start (Feature No: 302975)

    Category: YaST
    Status: done
    Test Result: idle

    Description:
    We discussed this, but I want to see the effort tracked in the tools we have:
    yast modules are slow to start up and you notice if you're not a yast developer and haven't all yast libraries and modules in disc cache.
    I did an experiment and dropped _all_ caches (this of course drops more than what's fair as qt/gtk libs will be already cached for a desktop user) and ran a strace on y2base ntp-client qt.
    after that I'm not seeing anything generic.
    That's at least 10 seconds too much I'd think. But assuming that ntp-client does not need libzypp functionality to startup, it's even 13 seconds too slow.
    What I did:
    echo 3 > /proc/sys/vm/drop_caches
    strace -tt -T -efile /usr/lib/YaST2/bin/y2base ntp-client qt 2>&1 | grep -v ENOENT
  • 2 seconds - loading generic libraries (some of them will be in cache, see above)
  • 3 seconds - load libzypp and its dependencies
  • 2.5 seconds - load qt and its depdencies
  • 0.5 seconds - actually init the module
  • 10 seconds - read and init all scrs
  • 4 seconds - read and init all kind of yast modules, that might or might not be ntp-client specific

  • Calculate disk space requirements for package update (Feature No: 302978)

    Category: CIM, Package management, Systems Management, zypp
    Status: done
    Test Result: idle

    Description:
    When different versions of the same package are installable in parallel (e.g kernel or kernel-source), the disk space in zypp must take this into account.
    When RPM updates a package, the new package is installed first, then the old package is removed. This is unproblematic when the new replaces the old package. However, for parallel installable packages, the disk space requirement effectively doubles during update.
    Zypp should calculate accordingly and warn before the update starts.
    This probably needs such packages being flagged appropriately.


    Simplified user config during installation (Feature No: 302980)

    Category: Installation, YaST
    Status: done
    Test Result: 'passed
    Description:
    I want to simplify creating local users during installation. Namely:
    - make it easy to use local user's password also for root
    - move local user creation to first stage
    I talked about this requirements with Martin and his proposal is here: http://w3.suse.de/~coolo/user_install.odp
    Namely:
    - you are asked for a local user name with an option to
    skip that in favor of previous installations or more complex auth schemes.
    - you are offered (by default for opensuse) to use the password for root
    - while you type in the user name, the account name
    suggestion is autofilled, no longer an explicit button
    - if you configure NIS/LDAP/kerberos, you only skip
    local user creation and get prompted later (second
    stage) and the dialogs need to make this is clear
    - The option to go for blowfish, etc need to available for SLES I think, I don't think they need to be available for openSUSE, but I leave this open.

    Plug and Play support for 3G | UMTS cards (Feature No: 302983)

    Category: Hardware and Drivers
    Status: done
    Test Result: idle

    Description:
    Tracking feature request related to FATE #300518.
    Need to be able to plug in a UMTS card and have the system recognize the device and load the appropriate application to configure (such as YAST or Network Manager).


    Don't Zap by default (Feature No: 302988)

    Category: X.org
    Status: done
    Test Result: passed
    Description:
    We have this long standing issue that ctrl-alt-backspace is exiting the desktop without much the user can do about it, while every **** web site asks you if you want to discard random information if you browse away.
    While the zap functionality is useful for some and essential for some situations, where your X server is broken _and_ the keyboard combination is not _that_ easy to trigger, shutting it off completely is not preferred.
    So we discussed and what seems reasonable is press once -> beep, press twice -> zap. Egbert and Luc say this can be implemented in the X server and then we can leave the option on by default.

    Installation sources module should offer to automatically fetch an update source (Feature No: 302990)

    Category: Installation sources
    Status: done
    Test Result: idle

    Description:
    The "installation source" yast module should offer a button to automatically fetch an update source. Users look into "installation source" when they want to add an update source but do not know what do add. So this is the place where to offer this.
    This can be done by just calling the registration process which will add an update source.
    See as well: https://bugzilla.novell.com/show_bug.cgi?id=308832#c17


    Move media check out of installation workflow (Feature No: 302993)

    Category: Installation
    Status: done
    Test Result: idle

    Description:
    I think we should move the medium check out of the installation work flow and let those that want to verify their medium boot a direct option from the medium.
    The goal is to simplify the work flow and I don't think medium problems are _that_ often a problem and that people are having medium errors are not more likely to take the time in the work flow.


    edit udev rules with YaST (network) (Feature No: 303017)

    Category: YaST
    Status: done
    Test Result: passed

    Description:
    Make YaST (yast2-lan) able to edit /etc/udev/rules.d/70-persistent-net.rules file to change between ATTR{address} and KERNELS parameters to match
    MAC address or BusID (see bug #52520)

    Installing and updating software needs to be fast (Feature No: 303018)

    Category: zypp
    Status: implementation
    Test Result: passed

    Description:
    I don't think there is a feature associated to it, so here it is:
    with us adding feature on feature to the update stack, it
    became quite unbearibly slow.
    It's nice and featurerich, but terribily slow. And from my point
    of view it's _the_ feature for 11.0 at least.
  • Säubere Cache für Repository 'openSUSE-10.3-Updates'
  • Erzeuge Cache für Repository 'openSUSE-10.3-Updates'
  • Säubere Cache für Repository 'internal-updates'
  • Erzeuge Cache für Repository 'internal-updates'
  • Lese Cache für Repository 'openSUSE-10.3-Updates'
  • Lese Cache für Repository 'internal-updates'
  • Lese installierte Pakete [100%]
  • real 1m26.254s
    user 0m28.278s
    sys 0m3.144s
    90 Seconds for _checking_ if there are updates is _way_ beyond every
    expectation (this machine boots in 25 seconds).
    5 Seconds I would set as goal for that (taking that there are other people setting 5 seconds as goal for booting), my debian Virtualbox fetches 6MB in 9s and takes another 3s for local things.
    There are various changes for the sw management in the queue and this feature is here
    to give them legitimacy.

    Make YaST (installation) look cool (Feature No: 303027)

    Category: Installation, Look & Feel, YaST
    Status: done
    Test Result: passed
    Description:
    One of the often criticized things is the old-fashioned look of installation and YaST. Improving that should give us a feeling of being fresh and cool, something we desperately need.
    While it would be good to change complete YaST I suggest to start with the installation, as it's the first thing users see.
    There are some ideas floating around, for example this mockup:
    http://en.opensuse.org/Image:Os103-installer-mockup.png

    add trusted computing base libraries (Feature No: 303029)

    Category: Security, TPM/TCG
    Status: done
    Test Result: idle

    Description:
    TPM usage is increasing, there are now some userland packages that can facilitate the TPM.
    We should perhaps include the lowlevel libraries (trousers). The device driver should be in the mainline kernel already.


    reiserfsfsck: Support mount counts and check expiry (Feature No: 303030)

    Category: Filesystems
    Status: done
    Test Result: idle

    Description:
    Currently, reiserfsck -a runs a full scan of every file system on boot, negating one of the major advantages of implementing FATE #300716. The whole point of that patch was to stop reading the bitmaps on mount. Unfortunately, a full reiserfsck run reads all the bitmaps and more, causing multi-minute delays on boot with huge file systems. e2fsck supports a mount count and a last check timestamp that allow the user to specify how often they want the check to run.
    I've recently developed patches that I'm sending upstream today that implement support for setting the mount count in the kernel, and checking it in userspace, in addition to the setting and checking of the last time the file system was checked. Both options are fully configurable.
    I can backport the patches if needed, but it would be simpler to just update to reiserfsprogs 3.6.20, where I'm applying the patches upstream. For 11.0, this is the obvious solution. For SLE10 SP2, I need approval.


    AutoYAST: NIC bonding support (Feature No: 303039)

    Category: not specified
    Status: done
    Test Result: idle

    Description:
    NIC bonding configuration doesn't work with autoyast.


    YaST style guide (Feature No: 303041)

    Category: YaST
    Status: implementation
    Test Result: idle

    Description:
  • consistent layout
  • consistent wording
  • ease of maintainance
  • ease of creating existing new modules

  • Support for High Definition Audio Controller (Feature No: 303044)

    Category: Linux Kernel, Multimedia, Sound
    Status: implementation
    Test Result: idle

    Description:
    We have had several customers calling in with their sound cards only working through their head phone, or not working at all and these customers have the High Definition Audio Controller. Probably around a dozen customers so far. We also have the High Definition Audio Controller that is being used internally as well and we are having issues with those machine working properly. The internal machine number is probably around 200 machines so far. Some people have been able to work around the issue by going into the volume control and enable the pc speaker, but there are those who still don't work at all regardless of what they do. My understanding is that this involves the ICH6,7, and 8 chipsets.


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

    Category: Filesystems, Linux Kernel
    Status: implementation
    Test Result: idle

    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.


    Evaluate LZMA for RPM (Feature No: 303057)

    Category: Desktop, Package building
    Status: done
    Test Result: idle

    Description:
    LZMA seems to be a bit (about 5-15%) better than bzip2 for compressing binary packages. Decompression speed is better than bzip2. Compression speed is slower. Memory requirement can be kept roughly the same.
    see http://tukaani.org/lzma/benchmarks for some comparisons.
    it seems there are patches floating around to make squashfs support LZMA as well as for RPM payload being compressed in LZMA
    Focus should be on support in RPM first.
    Supporting that, possibly as default, would help the one CD media and/or the Live CD.


    MySQL needs to be version 5.0.37 or higher for teaming to work on SLES 10. (Feature No: 303163)

    Category: Storage and Partitioning
    Status: done
    Test Result: passed --Christian Boltz 23:05, 22 April 2008 (UTC)

    Description:
    http://www.novell.com/documentation/team_plus_conf/team10_instconfig/data/b9vchn5.html
    If you are going to use MySQL on Linux on the database it needs to be
    version 5.0.37 or higher. However SLES10 SP1 only comes with 5.0.26.
    The old version of MySQL or MySQL needs to be upgraded in SLES10 to at least 5.0.37. From reading the public forums it appears customers are having to manually upgrade MySQL by downloading the latest version directly from the mysql.com website.
    This is converted to a fate request from bug 345915.

    drop yast2-bluetooth (Feature No: 303167)

    Category: Mobility, Mongoose, YaST
    Status: done
    Test Result: passed

    Description:
    Drop package yast2-bluetooth in release stable
    Reason:
    It is obsoleted by the new bluez infrastructure
    Almost everything can be configured by the user via the desktop applets.
    Those settings are stored hcid in its own configuration database, and if it
    finds settings in there, it ignores e.g. hcid.conf (which is written by
    yast2 bluetooth).
    If somebody really wants to keep yast2-bluetooth alive, it would need to be
    rewritten to use the same dbus-methods to configure bluetooth services like
    e.g. kdebluetooth and bluez-gnome use, resulting in a third tool with the
    same functionality.
    Almost every configuration option in yast2-bluetooth is not working
    correctly right now.

    Upgrade syslog-ng to 2.x (Feature No: 303216)

    Category: Base System
    Status: implementation (as of Beta 3, syslog-ng is still V1.6.12)
    Test Result: idle

    Description:
    We ship a fairly outdated version of syslog-ng with all current products (even FACTORY as of 2007-12-12.)
    IBM Japan requests an upgrade to the current stable version of syslog-ng, which is right now 2.0.6), as it fixes numerous bugs.
    http://www.balabit.com/network-security/syslog-ng/opensource-logging-system/upgrades/changelogs/NEWS_syslog-ng_2.0.txt

    System upgrade: keep packages with no replacement (Feature No: 303267)

    Category: Package management, Systems Management, zypp
    Status: done
    Test Result: idle

    Description:
    From bugzilla
    Currently installer sets by default all packages with no replacement (upgrade)
    to delete.
    However not every package contains software -- package could contain
    wallpapers, icon set, man pages, fonts, etc.
  • must remove
  • can remove


    Remove left help window in ncurses UI (Feature No: 303291)

    Category: YaST
    Status: done
    Test Result: passed

    Description:
    Usually, screen space is limited in the ncurses UI of YaST. Because of this, the left help window is disturbing since the screen space could be used in a more efficient way otherwise (e.g. to avoid horizontal scrolling in the partitioner).
    YaST Gtk has no help on the left, and also the new Qt4 GUI doesn't have that feature. The F1 popup is sufficient. ncurses is mostly used by experienced users and system adminsitrators that want to manage their systems via SSH. They don't need the always visible help.

    VMware open source tools (open-vm-tools) (Feature No: 303293)

    Category: Virtualization
    Status: done
    Test Result: idle

    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

  • Consistent time zone labels in YaST (Feature No: 303296)

    Category: YaST
    Status: done
    Test Result: idle

    Description:
    Currently, europian time zones are "translated" into the counry names ("Europe/Berlin -> "Germany"), while most of the other ones are left as city names (
    "Asia/Calcutta" -> "Calcutta"), although not all of them ("Asia/Tokyo") -> "Japan"). In some countries it may have sense to have city names due to political correctness (Taipei vs. Beijing and Shanghai), but mostly it is a mess.


    YaST Firewall module shall show custom rules on Summary page (Feature No: 303304)

    Category: Configuration, Security
    Status: done
    Test Result: passed b1 -volkerkuhlmann

    Description:
    The YaST firewall module allows setting custom rules in addition to the more cosy user interface, which is a nice feature.
    With openSUSE 10.3 the Summary page, which is presented when finishing the module, does not indicate that any custom rules have been set, not even if one checks the "Details" checkbox.
    It would be good to address this. By default we could note that "Custom rules have been defined for this interface" as appropriate and list the specific custom rules when the user marks the "Details" checkbox.

    User interaction/feedback during autoyast scripts execution (Feature No: 303332)

    Category: AutoYaST
    Status: done
    Test Result: idle

    Description:
    customers often want to ask questions during their script execution or at least want to provide some kind of feedback like a progressbar for scripts with a long runtime.


    check answers to the ask-feature for sanity (Feature No: 303333)

    Category: AutoYaST
    Status: done
    Test Result: idle

    Description:
    the ask-feature in autoyast is heavily used. It would be useful to provide a way to let the customer check the answers to the ask-questions for sanity.


    udf 2.5 support (Feature No: 303336)

    Category: Linux Kernel, Multimedia
    Status: implementation
    Test Result: idle

    Description:
    New HD medias like, BlueRay and HD-DVD medias are mastered in UDF 2.5 format. The current kernel can not access it, since it does provide only UDF 2.0 functionality. Acctually it did crash for me when trying to access a UDF 2.5 media.
    The 2.5 patch is accessable at http://sourceforge.net/tracker/?group_id=295&atid=300295
    It needed only very small and obvious changes for the current kernel-source package and works fine for me.


    YaST2: Use NTFS-3g instead of kernel module (Feature No: 303339)

    Category: Filesystems
    Status: done
    Test Result: idle

    Description:
    Read-Write support in the kernel NTFS implementation cannot alter metadata, which really means its only useful for using as a backing store for loopback.
    The FUSE ntfs-3g, which we already ship, includes full read-write support and is considered the "official" NTFS support by the community.
    In order to make things easier for our users, automatically detected NTFS partitions should be configured to use NTFS-3g rather than the NTFS module.


    Move registration and online update to desktop (Feature No: 303359)

    Category: Desktop, Installation, YaST
    Status: implementation
    Test Result: idle

    Description:
    Move the "hook me up with online world" from end of installation into the desktop.
    The installation work flow needs to different between a server and a desktop install and if a desktop is installed, it skips the steps network test / registration / online update / congratulation.
    The desktop applets will check if these steps were done during installation (IMO: simply by checking if a file was touched by yast) and if not, offer a bubble "Complete your system from online repositories" as soon as they notify a working network.
    This work flow is then basically:
    - registration
    - community repos
    - online update
    - additional recommended software download


    Apply checksum to config files written by YaST (http-server) (Feature No: 303374)

    Category: YaST
    Status: done
    Test Result: idle

    Description:
    We still have reports (e.g. from DFS, 'Deutsche Flugsicherung') that YaST doesn't fully detect manual changes to config files.
    Config files written by YaST should be protected by checksums (md5, sha-1, sha-256)
    This esp. applies to more complex config files, e.g. apache config; bootloader config, which are hard to parse.
    If the checksum doesn't match on read, a warning should pop up (or appear in the initial dialog).


    Rename "User Management" into "User and Group Management" (Feature No: 303392)

    Category: YaST
    Status: done
    Test Result: passed b1 -volkerkuhlmann

    Description:
    User Management and Group Management are shown as two separate icons in the
    YaST control center. But they show the same content. So I suggest to rename one
    of them in "User and Group Management" and remove the entry of the second
    module from the YaST control center.

    Use kexec to avoid booting between first and second stage (Feature No: 303395)

    Category: Installation, YaST
    Status: done
    Test Result: idle

    Description:
    It would be good if we could reduce the reliance on the bootloader for the first boot and use kexec at the end of first stage.


    Make second stage non-interactive if possible (Feature No: 303396)

    Category: Installation, YaST
    Status: done
    Test Result: passed

    Description:
    As (simple) user creation is about to move into first stage (fate#302980) and registration+online update to move to desktop (fate#303358) I want to have the rest of the second stage to run unattended.
    We should continue configuring sound, printer and firewall as much as we can - but without the user having to ACK it. Most will not change anything in there and the remaining users can easily change the configs from the control center after installation.
    In cases where the first stage could not finish user config (e.g. because of requiring ldap installed), we of course still need to stop.
    This needs to be configureable in config.xml just as the "move registration out of workflow" as SLE will not follow there most likely.
    Test Run Description
    When I install, Automatic Configuration is checked by default and works.

    add a "back" button to ask-dialogs in autoyast (Feature No: 303397)

    Category: AutoYaST
    Status: done
    Test Result: idle

    Description:
    a customer asked if it's possible to add a "back" button in the ask-feature, to switch back to a previous dialog.
    I think it's not a bad idea.


    decision based "ask" in autoyast (Feature No: 303398)

    Category: AutoYaST
    Status: done
    Test Result: idle

    Description:
    customer asks:
    Can we do decision based ask? i.e. if the answer to one question is x, ask question a, if the answer is y, ask question b.
    I think that might be doable but I fear it blows up the complexity of the "ask"-dialog configuration in XML.
    Interactive autoyast scripts might be a solution for that too instead of using "ask" for that.


    Enable single sign-on for SSH on Windows domain join (Feature No: 303415)

    Category: YaST
    Status: done
    Test Result: idle

    Description:
    If you join a Windows domain with the YaST Samba client module, it should be possible to enable single sign-on support for SSH. You have to activate GSSAPI authentication (kerberos) in the ssh and sshd config file. Below are the options which need to be set to get single sign-on working.
    GSSAPIAuthentication yes
    GSSAPICleanupCredentials yes
    ChallengeResponseAuthentication yes
    UsePAM yes
    GSSAPIAuthentication yes
    GSSAPIDelegateCredentials yes
    /etc/ssh/sshd_config
    /etc/ssh/ssh_config

    [kdm] doesn't let PAM translate (Feature No: 303424)

    Category: not specified
    Status: implementation
    Test Result: idle

    Description:
    kdm's backend runs in english, so the reported errors are in english too.
    Problem is: if we fix that, then kdm will get serious problems because it does
    regexps on the pam prompt ;(


    Gnome print dialog should allow printing multiple logical pages on one physical page. (Feature No: 303427)

    Category: Desktop
    Status: done
    Test Result: idle

    Description:
    kprinter, the print dialog from KDE, lets me print 2 or 4 logical pages on a single physical page. It would be very nice if the gnome print dialog did the same.


    Firefox needs to use a different dialog for "Open with another program" (Feature No: 303430)

    Category: Firefox
    Status: implementation
    Test Result: idle

    Description:
    In the download dialog for firefox, when you want to use a different program to open the file than one that is associated by default, the dialog to select the program is a standard file browser. This is difficult to use for people who do not know the file system paths on Linux.
    In Gnome, there is a better dialog that could be used. (I think KDE has a similar one.) It's the dialog that comes up when you right-click a file in Nautilus, and then choose "Open with Other Application."
    I will attach a graphic that shows the Firefox download dialog, the file browser dialog that is currently used, and the dialog that would make this easier.


    beagle and firefox: "whitelist" of secure domains to index. (Feature No: 303431)

    Category: Firefox, Searching
    Status: done
    Test Result: idle

    Description:
    It would be nice to have a FF beagle extension setting:
    "Don't index secure pages, except from the following domains: ..."
    I would like for some secure domains to be indexed, but I don't want to explicitly list every secure domain except for the ones I want indexed (not would it be practical to do so).


    Add package python-ply (Feature No: 303432)

    Category: ZENworks
    Status: done
    Test Result: passed

    Description:
    The python-pywbem package now requires python-ply. We need to add python-ply to the distribution.
    There is a python-ply package in home:maw within OBS.
    Test Run Description
    zypper se python-ply -> 2.3-18

    Rework Progressbars of package installation (Feature No: 303437)

    Category: Installation, YaST
    Status: done
    Test Result: idle

    Description:
    We currently have some progress bars during package installation that do not follow any usual standard. I would like to have the big on on the right side replaced, a lot of people have been confused by it and do not know what it's purpose it. I would also suggest to look at the other progress bar and find a better solution for progress reporting during package installation.


    GNOME 2.22.2 (Feature No: 303441)

    Category: Desktop
    Status: implementation
    Test Result: idle

    Description:
    GNOME 2.22.1 will be release in time for beta 1 of openSUSE 11.0.:
    http://live.gnome.org/TwoPointTwentyone
    GNOME 2.22.2 will probably be just after the beta.
    GNOME has its own freezes and 2.22.2 will contain only bug fixes, translations and documentation updates.


    Rename System Settings Module in YaST (Feature No: 303464)

    Category: YaST
    Status: done
    Test Result: passed b1 -volkerkuhlmann

    Description:
    Currently the System Settings Module in YaST shows something about PCI ID settings.
    I personally don't have a single clue what this module does but it is certainly not something users will likely suspect to hide under "System Settings".
    I suggest to rename the module into "Device Settings". The final name is "Kernel Settings".

    Removing Routing and DNS/Hostnames Module because of Duplication (Feature No: 303470)

    Category: YaST
    Status: done
    Test Result: idle

    Description:
    The content of the "Routing" and "DNS/Hostname" module is included in the "Network Card" module.
    Therefore the "Routing" and "DNS/Hostname" module are duplicated. This is quite confusing for the user.
    Additionally to that I suggest to rename the "Network Card" module into "Network Settings". This is also the title the user gets when he opens the module.
    Furthermore I was very surprised that the "Network Card" module in SLES 10 SP1 uses the old and unusable UI and not the new redesigned one included in openSUSE 10.3 (and openSUSE 10.2).
    I would highly suggest to use openSUSE's network card module also in SLES.


    YaST Patch CD: enable selecting CD URL (Feature No: 303475)

    Category: YaST
    Status: done
    Test Result: idle

    Description:
    With current YaST Patch CD module, user must provide real CD/DVD with the patches. It would be nice if user could provide path to such CD, located e.g. on the network or in local directory. From YaST side, it doesn't matter which URL is used for source creation.
    Besides the usage by target customers, it could make testing easier and faster, as we have the network sources prepared before CDs are burned.
    Example of usage:
    yast2 online_update .cd_default cd_url=ftp://cml.suse.cz/netboot/find/SLES-10-SP2-DVD-i386-Build0034-DVD1 (if cd_url is not provided, YaST looks for cd:/// as usual)


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

    Category: Booting, Installation
    Status: implementation
    Test Result: idle

    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.


    Provide reliably a resolution of 80x25 for braille devices (Feature No: 303482)

    Category: Booting, Installation
    Status: implementation
    Test Result: idle

    Description:
    For a proper support of braille devices a terminal with a resolution of 80x25 characters. That requires booting with 'vga=normal'. But currently we don't provide an easy way to achieve this. What we need is to implement one of these possibilties:
  • Make sure that resolution is 80x25 characters when no monitor is attached.
  • Have a dedicated bootloader menu line with 'vga=normal'.
  • Would be nice if we can get optional beep when this line is selected.
    This is needed at installation and normal boot


    Drop "old LVM1 copmatible Metadata Format" from CreateVG dialog (Feature No: 303490)

    Category: Storage and Partitioning, YaST
    Status: done
    Test Result: idle

    Description:
    With SLE 11 we will not support creating this type of metadata format anymore, but the system is still able to understand it.


    Image based installation (Feature No: 303554)

    Category: Installation, YaST
    Status: done
    Test Result: passed

    Description:
    We talked very often about it, but so far lacked the information what's required for that. Fortunately to Jiri and Lukas investing their ITO, we have a much better picture of it though.
    The general idea is to preinstall our default patterns and ship them as images/tar files to speed up installation - hopefully dramatically.
    Retrieved from "http://en.opensuse.org/Testing:Features_11.0"