Home | Content | Search | Navigation | Toolbox | Actions | In other languages

Testing:Features 11.0

From openSUSE

Contents

[edit]

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.

[edit]

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


[edit]

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.


[edit]

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

Category: Desktop
Status: done
Test Result: idle

Description:
Problem:
Solution:


[edit]

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.
[edit]

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.


[edit]

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.


[edit]

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


[edit]

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.
[edit]

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.


[edit]

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 ?


[edit]

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.


[edit]

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


[edit]

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.


    [edit]

    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
    [edit]

    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.


    [edit]

    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


    [edit]

    Respect taboo settings (Feature No: 120352)

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

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

    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.


    [edit]

    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.


    [edit]

    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.


    [edit]

    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)


    [edit]

    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.


    [edit]

    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.


    [edit]

    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)


    [edit]

    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.


    [edit]

    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


    • [edit]

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


    [edit]

    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


    [edit]

    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.


    [edit]

    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)


    • [edit]

    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.
    [edit]

    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.
    [edit]

    "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


    • [edit]

    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


    [edit]

    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


    [edit]

    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.


    [edit]

    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.


    [edit]

    Firewall support for SMB browsing (Feature No: 300970)

    Category: Directory Services
    Status: done
    Test Result: idle

    Description:
    Firewall support for SMB browsing


    [edit]

    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.


    [edit]

    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.


    [edit]

    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.


    [edit]

    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.


    [edit]

    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


    [edit]

    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.
    [edit]

    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.


    [edit]

    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.


    [edit]

    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.


    [edit]

    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.


    [edit]

    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.


    [edit]

    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.


    [edit]

    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.


    [edit]

    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.


    [edit]

    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


    [edit]

    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.


    [edit]

    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.


    [edit]

    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.


    [edit]

    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.


    [edit]

    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


    [edit]

    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


    [edit]

    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.
    [edit]

    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.
    [edit]

    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.


    [edit]

    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.


    [edit]

    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


    [edit]

    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?


    [edit]

    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.


    [edit]

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

    Category: YaST
    Status: done
    Test Result: idle</