Feature Wishlist/YAST related

From openSUSE

Easy way to remove entire applications in Yast

Something like this: [1]

YaST Backup features

Currently we have to rely on using shell scripts and cron to tar and upload files to an FTP. Perhaps the backup tool can get a number of selections in the future, such as:

• Tape
• Local
• NFS
• FTP
• RSYNC
• SCP

(Maybe others too? I'm thinking SCP would be useful for *nix hosts not running rsync, rsync for servers not running FTP, NFS where available, local (obvious) and tape for those who have it.)

Thoughts? Gallwapa 00:47, 24 September 2007 (UTC)

YAST software management

There are too many software management tools. They should all be joined into one super-installations-tool (SIT).

Right now there are various tools:

• software management
• installation sources
• online update (system update)
• update configuration (auto-select opensuse update mirror)
• add-on product
• verify media integrity checker
• install into directory (download RPM files from removable media to disk.)
• Update with patch CD/DVD
• shedule automatic online updates

All of the features of the applications should be joined into one single application. The default interface could be Software Mangement section (installation, update, and delete of rpms)

There could be other tabs separating Software Management section with: "Schedule Automatic Updates" and "Configure Installation sources"

One could also include menu items at the top of the window displaying:

• update system online now
• removable media integrity checker
• install media into directory
• update system with patch CD/DVD

To update the whole system, one can push a "upgrade system" button on the toolbar.

Ideally, one could also manipulate settings of the "Zen-updater" via the SUPERSofwareManagment program. There could be a tab to one side saying "zen-updater Configuration"

The current implementation of 10 various programs is tedious and slow. It should be joined into one application. --Felipe1982 06:25, 11 February 2007 (UTC)

YAST Redesign

The Way That YAST Is Done Creates Many Windows And Makes It Harder To Add Repositories And Install Software Quickly. So We Could Keep YAST The Same Size But Give It A Main Overview Section Built Similarly To Konqueror's "My Computer" Tool, That Would Display Bubbles For Each Section ( "Software, Hardware, Networking & Sharing, Security ( Apparmour, Email Antivirus ), Etc. ) It Would Be A Different Colour Depending On It's Status ( The Modules ) (Green = Ok, Yellow = Attention Needed, Red = Critical Issue ). It Would Also Keep The Tabbed Side Bar But Put It At The Top.When You Clicked A Bubble From The Main One It Would Take You To The Appropriate One ( Software, Etc. ) Which Would List Sub-Sections ( Software Management, Software Sources, Update, Patch Disc ) These Modules Would Be Colour Coded As Well With It's Main Background Being The Sections Status. When You Clicked A Sub Section It Would Goto It In The Same Window. A Basic Update Checker And Installer Would Monitor And Install Updates Without Requiring YAST. YAST Would Configure It And Show It Through It's Interface When You Were Using YAST To Update. A Version Updater Could Also Be Added. ( 10.3 To 11 )

--Ben_Cook2, 8 June 2007

Faster YAST Software Management Repository update

Personally i feel that this process is to slow. As the manager uses a very long time on scanning for changes in the repository, how about a database and QL system to use for downloading meta data information to the client, rather than all those xml (hell) meta data files? As there is to much latency between every file poll, and that makes the process as it is, to slow.

--Rahmi Guldahl, 09 June 2007

Cron-Job setup

Useful and easy to add?

Useful but quite uneasy to add as there might be different crontabs for several users and several files under /etc/cron.* (* == daily, hourly, monthly, weekly, and d). Additionally, cron.d files can be written in too many forms (4, */8, ...).

Xinerama

YaST urgently needs an update to its monitor configuration utility. It has issues allowing resolutions set in X to be chosen for display, and it would be really, really, really nice if it had multi-monitor support.

Mail server & tools selection

It would be useful to have a selection of mail server tools and utilities, it seems only natural since we have web server & tools, etc...

Automatic installation of icon on install

One of the things I keep hearing from users is that they have a hard time in linux when they install a package from yast. They dont know how to launch it or where its installed. Would it be possible to autmatically create icons in the launch window when a package is installed? Obviously this would only be helpful if the app had a graphical interface. If not then maybe have a text doc open automatically after the install with a simple description of where the app is at and a basic idea of how to run it.

Dual boot options during the installation

Right now, when a user installs SUSE Linux, if Windows is already installed, it will automatically assume the user wants to dual boot, but what if the user actually wanted to get rid of Windows? Then he must go in and change the partitioning manually, which I don't believe is something people like my dad knows anything about.
So, how about this, when a user boots off of CD1 and the installer starts, it should check whether Windows is installed or not. If Windows is detected, the installer should tell the user something like this: "We've detected an installation of Microsoft Windows on your computer, you can do the following", " - Install SUSE Linux in addition to Microsoft Windows, so that you can use both", " - Remove Microsoft Windows and install SUSE Linux".
Maybe my example of what to tell the user needs to be polished a little, so that it doesn't confuse people, something that would be crucial to do, would be to have an explanation of it available if the user clicks on the "Help" button. --Tsuroerusu 15:56, 22 Jun 2006 (MDT)]

Packagemanager should use the download channel in full speed

When YAST installs an rpm it is not downloading other rpms. Maybe do something like two (almost) independent process of downloading and installing rpms?

And then it may be faster to download and install first small rpms, then large, or first large, then small. (Needs check by trying first one way, then another.) It depends on how many time will it be not downloading or not installing rpms.

Samba-LDAP-Plugin for YAST User-Module

When I had SUSE 9.2 installed, I somehow (probably by accident) had a Samba-LDAP-Plugin for the YAST User Module installed on my system. I think it is part of the SUSE Linux Enterprise Server. This plugin was very handy and I whish it was still available for SUSE. With this plugin you could very easily create/edit user accounts and setup their Samba-LDAP attributes. Doing this manually now takes ages and is a bit tricky.

YAST System Backup Tool To Tape Device

With the YAST System Backup Tool unfortunately it is not possible to directly backup to a tape device. The filename of the backup file is automatically amended with a .tar, so that e.g. /dev/nst0 becomes /dev/nst0.tar . It should be possible to backup directly to a device file.

Feature implemented in yast2-backup-2.13.3, see Bugzilla #185042.

YaST Package Manager keeping downloaded rpm's on hd

Well, after installing few packages from ftp sources I noticed, that YaST2 doesn't keep them anywhere on my harddisk. I believe there shall be an option (such in YOU) to keep the downloaded rpm's on hd. Maybe it would be specified for each source in Instalation Source module (in add/edit source menu: option to check that I want to do that and (maybe) field to specify folder, in which I want to keep rpm's). It would be helpful for example for networkless installation including programs not available on installation cd's.

[Comment:This has already been suggested by me under the head "Package Manager" here in above. I am happy to know lot other people feel the same way as I do. Hope the new package manager (I mean, the Red Carpet backend) will solve this problem. They have also mentioned that some repositories would have been enabled (or will be readily available there for us to enable). Great News - G Rajesh}

[ dido ] If you look at the forums this is a common request since it was broken in 10.1. Previously SuSE kept the rpms. In my situation, on a slow dial-up connection. If I can keep the downloaded rpms, I can burn them to a cd and use that to update the other systems on my lan. It also serves as a great backup and time saver for the updates. For this reason, since 10.1, I have been forced to change package managers. I would prefer to be able to come back to YaST, but cannot until this is again a feature.

[KAE] I am a system administrator at a research institution (approx. 100 computers) an we perform total transfer from Windows to SuSE 10.3. The problem is that all downloading is multiplied by 100. I would prefer a local repository with the following properties: 1) the repository is fed from other (upper) repositories listed in a configurable list; 2) the update is performed by cron job or manually; the corresponding utilities should exist; 3) not all PRMs should be kept; if a machine in the local network needs a file that is absent, it is downloaded from an upper repository, and later other machines get this file through the local network. I will therefore restrict my repository only by files that were really necessary. The problem is that the absent file may disappear from the upper repositories because of upgrades... 4) in implementation, this may be done by creating a special Repository File System (RFS) with the property that the absent (e.g., length=0) file is downloaded from the external source. During the planned update this file system is unmounted.

Microsoft has this installation and upgrade style, why we can't?

Improved YaST2 network configuration

A lot of normal features to configure the network can not be used from YaST. IP setup is still complicated compared to MSWin. If you need a static ip for just one of several eth normal users are in trouble with the gateway setup.

Improved YaST2 touch mouse configuration

YaST2 only supports basic mouse configuration for mouse deviced. Yet basic is a relative term since developers already implemented configuration support for scrol features and third+ buttons. Still, while many laptops/notebooks are for years now shipped with touch-based devices the developers refuse to implement any configuration option for these devices. Laptop/notebook users are forced to find other software or even manual configure the hardware. There is no way to use YaST at manual setup/autoinstall at this point, nor after. Not user-friendly, not administrator-friendly.

OpenVPN Configuration in YaST2

OpenVPN is already shipped, but the configuration tool of choice is still vi. That is ok for tech professionals. OpenVPN has been positively reviewed in the german 'ct magazine. Smooth openVPN integration in Yast would make a difference for "road warriors".

Auto Refresh of Package Repositories in YaST

There should be some option in YaST installation source management for auto periodic refresh of installation source, i.e., update the list of packages from source once everyday. This is different from refresh On option currently available as that tries to refresh everytime I open Software Management to install package, and if number of repositories is large (say 6-7) this takes long time.

[Comment: How about a big button in the YaST package manager itself that says "Refresh all sources" or something? I have all my sources set to not update, because then it takes A WHILE to bring up the package manager, but it's a pain go in and make them update every time I want them updated.

Better handling of multiple harddisks / Installing on LVM by default

On installation YaST2 is able to detect multiple harddisks. What I would like to see is that YaST2 is giving me a good guess on how to handle these disks. --Macmewes 11:47, 14 Aug 2005 (MDT)

Example:

[Comment: The problem with this is that it's difficult to come up with a general solution for partitioning that works for everybody. The questions are what to do in case of a new installation with unpartitioned disks and what with partitioned ones? If somebody comes up with a verbal algorithm on how to handle the general problem, I'll get our partitioner team on board for discussion. Does anybody have such general algorithm? --A jaeger 05:19, 27 Sep 2005 (MDT)]

• As the proposer of this item I think YaST should indeed come up with "Do the right thing (tm)" ;-). In first instance YaST should know about "Usage-Profiles". The follwing examples are just what they are and subject to talk about. These examples could apply on systems with already partitioned HDDs as well. --Macmewes 07:20, 27 Sep 2005 (MDT)

In general /home should always be mounted on the HDD with the most available disk space to my intention.

a) Standard-Usage (2 HDDs unformatted)

       /dev/hda
               /dev/hda1       /boot   100M
               /dev/hda2       swap    (2 times RAM)
               /dev/hda3       /       (Rest of hda)
       /dev/hdb
               /dev/hdb1       /home   (complete disk space)

b) Advanced-Usage (3 HDDs unformatted)

       /dev/hda
               /dev/hda1       /boot   100M
               /dev/hda2       swap    (2 times RAM)
               /dev/hda3       /       (Rest of hda)
       /dev/hdb
               /dev/hdb1       /home   (complete disk space)
       /dev/hdc
               /dev/hdc1       /opt    (50% of disk space)
               /dev/hdc2       /usr    (Rest of hdc)

c) Server-Usage (4 HDDs unformatted)

       /dev/hda
               /dev/hda1       /boot   100M
               /dev/hda2       swap    (2 times RAM)
               /dev/hda3       /       (Rest of hda)
       /dev/hdb
               /dev/hdb1       /home   (complete disk space)
       /dev/hdc
               /dev/hdc1       /opt    (50% of disk space)
               /dev/hdc2       /usr    (Rest of hdc)
       /dev/hdd
               /dev/hdd1       /var    (complete disk space)

Wouldn't it make more sense to put all the disk space into LVM? --Wmerriam 12:17, 30 Sep 2005 (MDT)

Using LVM instead of plain partitions would be my preference, too - I filed this as an enhancement request in the Novell Bugzilla already -- LenzGr 11:24, 7 Jun 2006 (CET)

Possibility to choose the update source

Since i'm connected with gigabit to a official update source i'd like to choose this one. But YOU chooses one for me. If i don't use the right locale then it chooses a probably very far update source.

There are a list of avalible update servers located at YUM_servers Don't run the 'Online Update Setup' and add one of these servers in the 'Installation Source' --Startail 15:51, 20 October 2006 (UTC)

Possibility to create a update server

It would be nice for users that have no highspeed internet connection to dedicate a local server as update source. This server would have to work like a caching proxy. The admin could also control the patches that can be installed (example: excluding kernel patches until they are fully tested with local hardware), making automatic installation of patches more controllable.

The Addition of a way to update suse linux distributions from within YAST would be a benefical time saver to all users. Small updates and a new distribution can be a pain to download and burn iso's to disk, only then to process an upgrade.

YOU should mark already installed patches

At the moment you shows all patches - even if most are already applied. Very unhandy.

Various without description

• Easy VLAN configuration with YaST2. VLAN works great by adding an /etc/sysconfig/network/ifcfg-vlan<n> file. However it' be easier if a new device could be installed from YaST2/Network devices/Network card/Add/Type VLAN.
• Gtk/GNOME-only YaST for users who only install GNOME and no Qt libs! Also non-Qt SuSEplugger/SuSEwatcher.
  • Definately would be nice. Qt looks a little klunky in Gnome.
• Yast modules for configure MySQL and phpMyAdmin so you can setup a LAMP server without using the console.
• Harddrive partitioning on PPC computers (avoid having to use pdisk)
• Package selection and/or system settings based on specific hardware scenario - meaning selection for e.g. low memory systems or a system geared towards maximum powersaving or selection to create an Audio workstation etc. .

- For a computer used at home low electricity requirements might not mean much but I would imagine if a general purpose OS install fully & allways activly exploited the powersaving possibilities available then it could be another selling point to a business using many computers.

- SuSE can use lower memory if the user knows what packages to use. A prettification of fvwm comes to my mind to achieve a good looking low memory desktop. Its fast & uses little memory & very configurable : http://en.opensuse.org/MiniSUSE

Clean Sweep Function

Possibility to delete automaticaly library RPM's, for those there is no more requirements by other packages.

System Beep on Disk

It's not major, but when YAST finishes installing a cd, I would like it if it made a system beep. Sometimes I am in a different room than my computer and will not know if a cd is done.

Keyboard and time zone settings

The first two questions YaST asks are the main language and the location, but time zone and keyborad mapping are always default to US. If the country selected is Germany, the time zone will most probably be GMT+1, plus daylight savings if summer, and the keyboard be German, or Swiss-German (like mine). A guess list can be easily set-up for this purpose.

OpenAFS and Kerberos configuration (ssh too)

For schools and other organizations that use OpenAFS/KRB5/KRB4 it would be nice to have configuration via Yast. Kerberos stuff is

already there for the most part, however it would be nice to add afs (this depends on AFS packages, which is now in the package wishlist)

YAST support for encrypting the root file system

For laptop users, data encryption is becoming an important topic. While YAST does support encrypting non-root file systems, it does not have support for encrypting the root file system. The later is an important point because data has a tendency to leak out of the user file system and into root areas such as /tmp, /var and swap. The HOWTO describing one such approach is useful, but it would be more useful if YAST supported this procedure.

YAST LDAP Server

A good easy to use GUI, so admins can register, or set the users and their rights. And if we could Export the current local users list to the LDAP list with one click will be great too. Something like a wizard with no more than 3 clicks on it.

UPDATE openSUSE 10.2: There is now a server module in Yast. LDAP handling is broken in to three part. A LDAP server module, client module and a viewer module. It be beneficial with a more integrated view on how to set up LDAP authentication and automounting of directories. (/home /share etc.)

UPDATE openSUSE 11.0: The LDAP-Server module in Yast work rather well. Considering that the Samba module is capable of configuring a BDC using LDAP, it would be a great idea if the LDAP-Server module would also be enabled to configure a slave LDAP-Server, including the necessary syncrepl directives.

Easy UPS Setup Via YAST

Setting up a UPS on SUSE via YAST should be as simple as click & click and I'm done. Though you would think something like this should have been added long ago. It's not like UPS is a new technology. ;) I might suggest "nut" as the primary package to be used.

Addition: A selection between 'nut' and 'apcupsd' would be nice. I have multiple systems on a 2200VA unit, it would be wonderful if YaST could handle setting up the network communication between the directly connected (serial) machine and the others.

More YAST Modules for Other Services

I would like to be able to easily setup other services (irc server for example) via yast. I know how to do some of the config files by hand. But being able to use a GUI would be nice.

Poor OS installation

I'm strongly dissapointed with the new system installation (10,1) based on Yast. There have been changes in the interface which supposed to make installation easier. However - as opossed to previous linux installations where you could access all options from one main page - you have to open many windows in order to find the option you are looking for. This is visible from the very first moment: When you are asked if you want to install the system or update it, boot and repair options are in a submenu even though they could be easily under the update option. This confuses the both inexperienced and experienced users. Inexperienced ones may choose default options which are far from suitable: the system tends to eliminate all other OSes (format the entire hard disk) and even if kept they are not automatically included in the bootloader. Atidute of a Microsoft OS: Delete everything and use the whole harddisk. In previous versions (9.3) advanced options were easier to acess, interface was less confusing and automatic configuring more intelligent. Furthermore, initrd and bootloader were impossible to be installed resulting in an unbootable system. In conclusion i'm very strongly dissapointed and i'm thinking of moving to Ubuntu.

[Comment: I agree with the author above. I am an experience Windows user but I am a SUSE newbie. Installation but especially updating is confusing. Having panel->SW update is a great solution! But what is confusing is that I also have all those YaST icons: YaST->OnlineUpdate, YaST->SystemUpdate, YaST->OnlineUpdateConfig. When updating/patching my SUSE online ... shall I use panel->SW update, YaST->OnlineUpdate or YaST->SystemUpdate!? Are they doing the same thing or are there any difference between them? Then YaST have more icons YaST->Configure Online Updates, Change Installation media. After initial installation there is alot of packages that is not installed. As a newbie I am not sure if I have to install more packages to have a safe and functional system. I dont know if AppArmor is up and running and if the firewall is up.

Solution: Why not only do all online updates from panel->SW Updates (which is great!) and remove those YaST icons doing the same thing from YaST. 1. Let YaST have an icon called InstallationStatus where I can check first, what programs I have installed from my installation disks and second, I can also check what programs on all installation DVD's I have not installed. 2. It would be great if there where an icons in the panel to the right for AppArmor and also Firewall, soo I can see that they are up and running, and if I after installation dont want to see those icons in the panel I can easy configure that they are invisible.

One more thing, if I install a program (game or what ever) does SUSE allways put an program icon for that program in my panel->ProgramMenu? I am not sure. //Mats B]

YaST configuration of pam_mount

It would be great if pam_mount could be configured along with NT domain authentication during installation, since anyone authenticating against a domain is going to want to have their home directory mounted when they login.

YaST software installation / source performance increase

The software management utilities inside of YaST seem to be unrealistically slow. 5-10 minutes to load the software management utility with only one active source is WAY too long! I am coming from a .deb background, and it seems that when the repositories are queried, the package header information is transferred in a matter of seconds for a list of 10 - 20 sources. Can this performance be matched using the ZEN / YaST management combo?

Are all of the scripts that run after software installation necessary? This seems to take a good 30 seconds as well...

YaST desktop environment detection

With the integration of desktop indexing applications, such as Beagle, when doing a search for a configuration utility such as "keyboard", or "printer", the search results don't indicate which desktop environment the item corresponds to. The results will list "Printer", "Printer", "Manage Printers", etc. Some are KDE, some are Gnome, some are environment agnostic. Ideally, the utilities not applying to the running DE would be hidden from the results.

Along with this, why not GTK bindings for a Gnome desktop? And why "F3" for search - why not "Ctl + F"? I think this is in the works, but I am voicing my support for it here if it is not.

YaST System Backup and System Restore replacement - Includes backup to tape

'CPIO" is included in the current distro of openSuse Linux 10.1. This application is comprehensive and includes the ability to backup to tape, which is on this list above. The application needs only a GUI interface. The usage of this application from a command line is difficult due to the complex nature and flexibility and options available. This makes a good replacement for the current System Back and System Restore and would address the issues in bugs https://bugzilla.novell.com/show_bug.cgi?id=214892 and https://bugzilla.novell.com/show_bug.cgi?id=214889 and https://bugzilla.novell.com/show_bug.cgi?id=214896 more information about cpio can be found at http://www.gnu.org/software/cpio/manual/html_mono/cpio.html I think this application with a GUI interface would be an excellent replacement for the functionality it offers. Scott 10 October 2006 08:57 GMT+10

Option to add mirrors to YaST Installation and Update sources

I feel that some servers run slower than other at different times of day. Software such as SMART is able to negotiate different mirrors and remember which are the fastest. It will only use the fastest mirrors for downloading.

• I second this. Felipe1982 04:55, 9 January 2007 (UTC)

Combine the "Online Update", "Software Managment", "System Update", "Installation Source"

This wish is the same like #2 The four programs could be all bunched into one. For dial-up users, this would result in greater efficiency. For ordinary users, one could add the sources, and immediately see what is available for download or upgrade on those new servers.

• I second this. Felipe1982 04:56, 9 January 2007 (UTC)

Option to create md5-/sha1sums for created backups (YaST Backup)

After a backup is created, why not calculate the md5-/sha1sum and provide it in the same directory as the backup itself? Could be helpful in order to check a backup file which is restored from tape. This would be a quick solution, which would already help alot. A complete solution would be to include the md5-/sha1sum in the autoyast xml file (in addition to the seperate md5-/sha1sums files mentioned above) and have them checked by the backup module upon restore as well as during autoyast installation with activated System Restore.--Uranellus 09:32, 11 November 2006 (UTC)

Change default YaST repository protocol to smart (YaST Install/Update)

I'am using SuSE 10.2 and it's really good only thing that bothers me is slowness of repository sync. Also the zypper is nice can you add smart to it and create smart indexes for repositories?

support for sensors

With modern high powered computers there is a need to monitor temperatures, fans speeds, voltages, etc. To do this I have to run /usr/sbin/sensors-detect then copy the file it produces to /etc/init.d/lm_sensors. I used to have to enable lm_sensors in System Services (Runlevel) but that seems to have changed in openSUSE10.2 and that seems to happen automatically now? What I would like is the ability to do all of this from within YaST including running lm_sensors, etc. Even better would be support for programs that actively control computer fans. I think this is related to YaST-->System--> Power Management, its also related to control of UPS.

- MJB

Crontab File creator/editor module in YaST

It would be nice to create a module to configure the crontab file to allow easy settings of scheduled items for example, a timed virus weep with a command line scanner and other cron jobs. it may be a small request but it would make the job a lot easer that manual inserts in to the crobtab file and limit user error and vauge settings.

Easy text-only option for installation

I have a number of servers running SuSE, most of which are ancient Pentium II/III desktops with low ram (~ 128Mb). It takes forever to run the graphical install. It would be great to have an option at the initial install CD boot like "Press F6 for text mode" that gets rid of the graphical stuff and goes right to the text-only YaST (not YaST2) installation. -JA

This feature was already implemented years ago. When Installation (from CD/DVD) starts, just select Video Mode -> Text Mode, press [Enter]. That's all...

Change Mail Transfer Agent to allow better settings for AMaVIS

although I have just been able to configure /etc/amavisd.conf, it would be so much easier to configure basic spamassassin settings e.g. spam score levels and being able to set the action (Kill, bounce, discard, etc). It would be so much easier to be able to set virus scanning to more than just ClamAV, I use AntiVir for example and I'm sure that there are loads more that could be accommodated such as AVG, Avast etc

YAST Groupware Module

There are already eGroupware packages available for openSUSE. There are modules to adminstrate LDAP and Apache and there is a yast mail module. The next step should be to make an installation and administration of a Groupware Server (like eGroupWare) as easy as possible with openSUSE. The yast module shoule make it possible to set up and administrate an (e)Groupware server. At least it should be possible to install and configure the needed components for an Groupware Server (like IMAP, LDAP, a Webserver etc...). At the moment it is only possible to use the given Yast modules separately and even then these modules will not guide you through the steps needed for the groupware server installation.

UPnP Support in YaST Firewall

The YaST Firewall needs a feature to support UPnP in routers. When I open ports in my firewall I should be presented an option to open those ports in my router's UPnP software. An example feature could be something like clicking a checkbox saying "Forward Ports in router via UPnP" or something along those lines. Here are some possible places to get the code.

Ability to modify settings for all installation sources at once

In Installation Source I have many sources listed. I don't always have an Internet connection, so Refresh is off. When I manually refresh them, I have to do it one source at a time. I select "Refresh Now...", then wait a while, over and over. I would like to able to refresh all of them at once. Instead of adding new buttons, you could add a source called "All", which the Source Settings button would operate on.

http://linux-igd.sourceforge.net http://pupnp.sourceforge.net

YAST Remote Administration Module (for VNC and FreeNX)

It would be very useful to create a yast module (or modify the existing one) so that it helps in the configration of FreeNX and VNC. There should be options to choose if one wants to install a terminal server or just wants to share the desktop. Furthermore, it a possibility to apply a password to the sessions and one will need the possibility to add or remove users for the terminal service(for FreeNX). Terminal servers become more and more important and in openSUSE there should be a yast based configuration do make it as easy as possible to configure such a server. The current module is not very helpful in setting up a real terminal server.

Export / Import package list during install

During install, I sometimes create my custom list of packages, then I remember something I had to do on the old system, or I ran out of time and need to abort. YAST offers the possibility to export the package list to a text file. (indirectly, through, by going to complete list and saving that, that also should be impoved.) However, I could find no way to import that file back, and I had to recreate the whole list.

YAST repository update retry on fail

When yast is downloding package info from repository previous to update or new software install it fails a lot when using proxy (at least for me) and it would be nice that yast retry a number of times (defined by user) before user intervention

[Yes, my broadband supplier (VirginMedia) throttles the DNS lookup channel, causing a ridiculous number of failures when trying to start the Software Management module. This ISP also blocks immediate retries on the same location. An automatic retry combined with automatic skipping to the next repository(ies) and then coming back to check the failed one would be a great help. I then could go and do something else (rather than repeatedly clicking on the retry button) for the next 20 minutes or so!]

Enhancing YaST SSHD Module

See YaST_SSHD_Server/Enhancements_WIP

YAST Suggested install option?

When selecting certain applications in Software Management, YAST automatically suggests installing all required dependancies. I think something to help new users could be an additional screen of Suggested Extra's or the like. For example, when selecting Apache2 from the package groups section, the yast module is not automatically installed. For some users this could be an annoyance, so a sugestion box saying "Install Yast2-http?" would be nice.

YaST Integration into Desktop Environment Settings Manager

Currently YaST exists as a standalone program. This should probably remain. However, both KDE and Gnome have their own settings programs. Gnome has Gnome Control Center, KDE 3 has Kcontrol, while KDE 4 has System Settings. I know both Kcontrol and System Settings can be expanded with additional functionality and it appears Control Center can as well. So in addition to the traditional YaST intergace it would be extremely useful to have the various YaST modules integrated as modules in these settings programs. I know both Kcontrol and System Settings have the option to render modules inaccessible without administrator privileges, implemented by graying out the settings and having and "Adminstrator" button where you can input your password. For people who want YaST available I would keep it, but since we already have programs to control settings in the two most widely-used *nix desktop environments, I don't see the reason to force people to jump back and forth between two settings managers that in many cases duplicate the same functionality.

fsck check of existing filesystems

See bug#361728.
Summary: it would be nice if YaST would fsck existing filesystems when these are to be mounted during install (e.g. a /home filesystem). If not, and the filesystem is not clean, the installation will abend and start over. --Pjessen 16:55, 21 February 2008 (UTC)

Option for RCS control of config files

Add an option in YaST configuration to check all changed config files in to RCS after modifying them. Ideally, would create a new RCS directory in any directory with config files that doesn't have one, and automatically check the config files into RCS when they're changed, to keep a full record of all changes that's easily used with manual changes, and also allow integration (since RCS is a standard format) with config file change control software.

YaST improvements to assist Disk Imaging/Cloning

Cloning/Imaging remains the fastest deployment mechanism for even modest roll-outs. While OpenSuSE is pretty easy to deploy in this way, there are still traces of the original machine remaining which can cause problems and require adjustment even if the base hardware is identical. It should be possible to take some of the YaST code for initial installation and use this as a sysprep equivalent for pre/post disk cloning. For example, 'yast --post-clone' would repeat the hardware scan and update all the hard-coded hardware attributes to reflect the current machine, like the MAC address for eth0, the udev rules, xorg.conf etc. Or 'yast --pre-clone' would put the hooks in place for a once off rescan on reboot. Perhaps an 'autoyast' to update/correct an existing installation would be another way of thinking of this.

It would be even better of there was a nice utility for handling images and deployment, a la Clonezilla.

-- John Pelan - April 2008 -

Make it possible to switch from Software Installation Window to Full Yast

If you open the "install software" application you have to login as root. When this app has finally loaded you ca not switch to the full yast mode. You have to close the sw installation window and than you have to find and start YAST from the start menu. I want a possibility to switch from the sw-installation window to the YAST window, without search, start and login in again. --KFleischer 11:28, 16 April 2008 (UTC)

Resume downloads in YAST

i wish to be capable to pause and resume downloads in yast software management module, ex openoffice which is nearly 100mb in size

Software management module

I want to be able to refresh a certain repository within this module (instead of going to software repos module) provided i disabled the automatic refresh...

YaST2: hierachical view for package groups (like in 10.3 and earlier)

In 11.0 in YaST2 software-management the hierarchical view of software packages was substituted by a view with big icons with no subcategories. This makes package-selection out of extensive groups like programming or multimedia tedious and time-consuming.

I also don't understand the reason for changing the established user-interface. Do you think your users incapable of managing a hierarchical list? (opened a bug report bug #396245)