April 2007 - YaST Development - openSUSE Mailing Lists

[yast-devel] Updater applet for Gnome and KDE
by Duncan Mac-Vicar Prett 12 Apr '07

12 Apr '07

The openSUSE updater is a desktop applet which shows the user the available updates (patches). It is very light and simple as the real work is done by the YaST solver. This allows us to provide one applet per desktop, much like you have a a NetworkManager applet per desktop. The KDE applet was born last year as a Google SoC project. Today I imported the opensuseupdater KDE applet sources from berlios to svn.opensuse.org/svn/zypp. The gnome applet was already in the zypp repository. There is a new wiki page for both the KDE and Gnome applet. * http://en.opensuse.org/Updater_Applet The sources for both applets are located here: * http://svn.opensuse.org/svn/zypp/trunk/updater-gnome/ * http://svn.opensuse.org/svn/zypp/branches/SuSE-Linux-10_2-Branch/updater-kd… Also, there is a work branch for the KDE applet where a major refactoring is going on to cleanup legacy code from SoC, use cmake as build system and load the backends as KDE plugins. It will become trunk once it works: http://svn.opensuse.org/svn/zypp/branches/work/updater-kde-refactoring/upda… Just email me for any question! cheers -- Duncan Mac-Vicar Prett Novell :: SUSE R&D, Maxfeldstr. 5, 90409 Nürnberg GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

4 12

[yast-devel] Editing Configuration of SuSEfirewall2 Services Defined by Package (FATE #300687)
by Lukas Ocilka 12 Apr '07

12 Apr '07

Hi, About: ------ YaST Firewall can already work with services defined by packages for several weeks, nevertheless is had just a read-only access. Some of you (for instance, ftp-server or http-server maintainers) allow users to configure ports on which the services listens or operates but enabling or disabling these services (ports) in firewall was quite limited. New Feature: ------------ Now, there is a new functionality in 'SuSEFirewallServices' module: * GetNeededPortsAndProtocols returns map of the current definition of the service * SetNeededPortsAndProtocols immediately changes the definition in configuration file You can find this new functionality in yast2-2.15.28 or SVN. Example of Usage: ----------------- - Services defined by package are stored in the /etc/sysconfig/SuSEfirewall2.d/services/ directory, copy the attached 'abc' file there - Save services-dbp.ycp script somewhere and run it by `/sbin/yast2 /path/toservices-dbp.ycp` - See the /var/log/YaST2/y2log Bye Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic { import "SuSEFirewallServices"; string service = "service:abc"; map <string, list <string> > ports_used = SuSEFirewallServices::GetNeededPortsAndProtocols (service); y2milestone ("----------------------------------------------"); y2milestone ("GetNeededPortsAndProtocols: %1", ports_used); y2milestone ("----------------------------------------------"); list <string> tmp = ports_used["tcp_ports"]:[]; ports_used["tcp_ports"] = ports_used["udp_ports"]:[]; ports_used["udp_ports"] = ports_used["rpc_ports"]:[]; ports_used["rpc_ports"] = ports_used["ip_protocols"]:[]; ports_used["ip_protocols"] = ports_used["broadcast_ports"]:[]; ports_used["broadcast_ports"] = tmp; y2milestone ( "SetNeededPortsAndProtocols: %1", SuSEFirewallServices::SetNeededPortsAndProtocols ( service, ports_used ) ); ports_used = SuSEFirewallServices::GetNeededPortsAndProtocols (service); y2milestone ("----------------------------------------------"); y2milestone ("GetNeededPortsAndProtocols: %1", ports_used); y2milestone ("----------------------------------------------"); } # Do not edit this file as it's just a template and will be # overwritten on package updates! Copy to a new file instead. # # Only the variables TCP, UDP, RPC, IP and BROADCAST are allowed. # More may be supported in the future. # # For a more detailed description of the individual variables see # the comments for FW_SERVICES_*_EXT in /etc/sysconfig/SuSEfirewall2 # ## Name: abc service (probably) ## Description: opens ports for xx in order to allow dd # space separated list of allowed TCP ports TCP="was tcp" # space separated list of allowed UDP ports UDP="was udp" # space separated list of allowed RPC services RPC="was rpc" # space separated list of allowed IP protocols IP="was ip" # space separated list of allowed UDP broadcast ports BROADCAST="was broadcast"

1 0

[yast-devel] netcat dependency of yast2-core and -printer
by Marcus Meissner 12 Apr '07

12 Apr '07

Hi, We had yet another complaint that a customer does not want to install "netcat" for security reasons (no need to discuss), but we cannot even tell him to rpm -e it to quieten his paranoia because it is required by yast2-core and yast2-printer. yast2-core has a netcat dependency because it uses it to do some connect tests in the ag_hostnames agent. Is this specific agent still in use? yast2-printer has it in some tools, where it is unclear to me if they are run during regular usage. I wonder if we can get rid of the hard netcat dependency here. Ciao, Marcus -- Working, but not speaking, for the following german company: SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

4 4

[yast-devel] YCP exit code
by Benji Weber 11 Apr '07

11 Apr '07

Hi, Is it possible to return an exit code from a YCP module? I've tried returning a value from the top level block but exit code always remains 0. Use case: I would like to return a value from a module running as root to one not running as root. Thanks in advance. _ Benjamin Weber -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 3