openSUSE Factory June 2006

factory@lists.opensuse.org

64 participants
50 discussions

by jdd

Before I dig in YaST sources, does anybody know a simple way to skip the YaST partition module at install time. I mean, giving an already partitioned disk, install at first in a hard (compile time) given partition. it's this module that uses the most memory and block some memory disabled computers :-). autoyast uses always the hole disk, a solution could be to trigger autoyast to use a disk without erasing it :-) thanks jdd -- http://www.dodin.net http://dodin.org/galerie_photo_web/expo/index.html http://lucien.dodin.net http://fr.susewiki.org/index.php?title=Gérer_ses_photos --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory-help(a)opensuse.org

14 years, 4 months

SL 10.1 Floppy Drive mount not working

by Thorolf Godawa

Hi, I'm not able to get access to the floppy using SL 10.1 with Gnome. I get the following error: Operation Failed Method "Mount" with signature "ssas" on interface "org.freedesktop.Hal.Device.Volume" doesn't exist. I tried it as normal user and root and I get the problem on two different systems and an online-update (what was not working as expected too) didn't solve the problem too. Thanks a lot, -- Chau y hasta luego, Thorolf --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory-help(a)opensuse.org

14 years, 4 months

Package Management Design and Experience

by Andreas Jaeger

As discussed last week, I wanted to continue the discussion about the package management changes - but not concentrating on the real bugs we're fixing now but on general issues: With SUSE Linux 10.1 we have redesigned the way we handle software. We are proud to be able to announce our new software management backend which is based on the so-called library "libzypp" and which also integrates Novell's ZENworks technology. Also we decided to follow the repomd standard (sometimes known as "YUM repository") for our new software repositories. In fact we are now able to manage more than packages only. We have integrated flavors like patches, patterns and even products all of which are defined and handled equivalently to packages. This new framework allows for new ways to define system dependencies and to build more complex application stacks also considering certain patch levels, patterns or even products to depend on. Also we were able to fix the well known issue where one could compromise a system installation by installing outdated packages after already having applied patches. Using the new technology the system is now able to detect these kinds of package-patch dependency violations. By integrating Novell's ZENworks technology we enriched our distribution by a new command line tool called 'rug' and a daemon called 'zmd' which are able to keep your system up-to-date. Also we invented a new easy-to-use patch management user interface which is called 'zen-updater'. These new tools are also able to tie into a ZENworks Linux Management infrastructure in order to allow for centralized remote management. As these changes are also impacting the user experience regarding package and patch management we'd very welcome to start a discussion thread whether and how we still can further improve the current toolchain. One question we have is how the new tools rug, zen-updater and zmd compare to what we had before with YaST Online Update and suseWatcher. We are interested in every feedback ranging from architecture, design or used standards and their enhancements. As this topic is not a very easy one I guess we'll need several iterations for this discussion. Therefore I'll try to summarize the first discussion outcomes on http://en.opensuse.org/Libzypp/Design. After a couple of weeks we can then continue the discussion after everybody had the chance to work with - and love/hate - the new toolchain, Andreas -- Andreas Jaeger, aj(a)suse.de, http://www.suse.de/~aj/ SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

14 years, 4 months

control.xml info

by houghi

Is there any info availble on control.xml? I have found many references to the file, but not one explaining anythiong about the file. Changing the file sometimes can be obvious, like removing a module or changing a 'yes' into a 'no' or 'true' into 'false. Other things are less obvious what the alternatives might be: <ui_mode>simple</ui_mode> and there is no way of knowing if there are things that are not included in the file that could be. -- houghi Please to not toppost http://houghi.org My experience with SUSE You can have my keyboard ... if you can pry it from my dead, cold, stiff fingers --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory-help(a)opensuse.org

14 years, 4 months

Popup question when installing

by houghi

For some software (e.g. acroread or fortune) I am 'confonted' with a popup warning me about it. How is this achieved? I would like to add that info to the page I just made: http://en.opensuse.org/Making_a_SUSE_based_distribution -- houghi Please to not toppost http://houghi.org My experience with SUSE You can have my keyboard ... if you can pry it from my dead, cold, stiff fingers --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory-help(a)opensuse.org

14 years, 4 months

Idea for SuSEfirewall2

by Lukas Ocilka

> Just a little idea I stumbled upon... > > How about having a directory that allows dropping in files as part of > packages (e.g. /etc/sysconfig/SuSEfirewall2.d/). > > Those files could include stuff like > - a detailed description of the ports that are relevant to the package > - parsable data for SuSEfirewall2, to be able to open (or close) ports > based on that information > ---8<-------------------------------------------- > <susefirewall2-service id="xmpp"> > <summary>XMPP/Jabber</summary> > <description> > Open these ports to allow communication with an > XMPP/Jabber server hosted in your network. > </description> > <ports> > <port proto="udp" port="5222" /> > <port-range proto="tcp" range="5222-5223"/> > </ports> > <susefirewall2-service> > ---8<-------------------------------------------- > (of course, it should be capable of being localized) > I'd like to have that too :-) It's nothing SuSEfirewall2 should deal > with though. The YaST firewall module can make use of that > information instead. Currently the information about ports is > hardcoded in /usr/share/YaST2/modules/SuSEFirewallServices.ycp Hi, I like the proposal, that's almost exactly what I wanted to do. Additionally, using an XML format for storing this kind of information is even better than I planned. The only thing, I doubt, is the translation of <summary/> and <description/> but there definitely must be a way to do that somehow. Also the /path/ for storing these XML files has to be consulted with some LSB guru to follow the LSB standards (if such rule exists). Well, having these services well-defined by packages themselves seems to be a good idea, on the other hand too many defined services might make the UI almost unusable :) Lukas --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory-help(a)opensuse.org

14 years, 4 months

YOU works only every second run

by Andreas Vetter

Hi, whenever there is a update, the first run of you does not show the update. I have to run you again a second time to see the updates. The updates are on NFS, rsynced from gwdg.de. Any ideas? Known behaviour? Bug? Regards, -- Andreas Vetter --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory-help(a)opensuse.org

14 years, 4 months

Idea for SuSEfirewall2

by Pascal Bleser

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Just a little idea I stumbled upon... How about having a directory that allows dropping in files as part of packages (e.g. /etc/sysconfig/SuSEfirewall2.d/). Those files could include stuff like - - a detailed description of the ports that are relevant to the package - - parsable data for SuSEfirewall2, to be able to open (or close) ports based on that information - ---8<-------------------------------------------- <susefirewall2-service id="xmpp"> <summary>XMPP/Jabber</summary> <description> Open these ports to allow communication with an XMPP/Jabber server hosted in your network. </description> <ports> <port proto="udp" port="5222" /> <port-range proto="tcp" range="5222-5223"/> </ports> <susefirewall2-service> - ---8<-------------------------------------------- (of course, it should be capable of being localized) Those ports could then show up in "Allowed Services" and "Masquerading". Currently, SuSEfirewall2 has a fixed set of "well-known" (not in a sense of /etc/services) ports it can put names on (HTTP, SSH, rsync). But those ports don't include a description, that could be really valuable for beginners. Also, SuSEfirewall2 doesn't provide names for other ports, that are not in that fixed set, e.g. for gnutella, jabber/xmpp, ... and you have to go through [Advanced...] A system like above could be useful, to include port definitions for SuSEfirewall2 as part of RPM packages (e.g. jabberd). Well, just an idea, off the top of my head. What do you guys think, would it be useful ? feasible ? Post/discuss on another list ? cheers - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <pascal.bleser(a)skynet.be> <guru(a)unixtech.be> _\_v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFEpMeKr3NMWliFcXcRAuKDAJ9BLw5rhYnyuThfMVNaq9rus2Y5xwCgjp6I kVZmPXpltue+du3rGYGKnfA= =jqFo -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory-help(a)opensuse.org

14 years, 4 months

RE: [opensuse-factory] Idea for SuSEfirewall2

by Robison, Jonathon (M.)

One thing I would add is that yast, when it writes the .xml files, should ALWAYS include a nice commented block at the top explaining the possible <x></x> entries so that if needed, one could hand edit the xml files using the information presented in the comments. Jonathon M. Robison Infrastructure Architect ET, ITI 313-323-9529 -----Original Message----- From: Richard Bos [mailto:radoeka@xs4all.nl] Sent: Friday, June 30, 2006 3:17 AM To: opensuse-factory(a)opensuse.org Subject: Re: [opensuse-factory] Idea for SuSEfirewall2 Op vrijdag 30 juni 2006 08:41, schreef Pascal Bleser: > <summary>XMPP/Jabber</summary> > <description> > Open these ports to allow communication with an > XMPP/Jabber server hosted in your network. > </description> > <ports> > <port proto="udp" port="5222" /> > <port-range proto="tcp" range="5222-5223"/> > </ports> > <susefirewall2-service> > ---8<-------------------------------------------- > (of course, it should be capable of being localized) Perhaps with: <summary lang="XX_xx">XMPP/Jabber</summary> <description lang="XX_xx"> Open these ports to allow communication with an XMPP/Jabber server hosted in your network. </description> -- Richard Bos Without a home the journey is endless --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory-help(a)opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory-help(a)opensuse.org

14 years, 5 months

New makeSUSEdvd tool

by houghi

I have made an additional script to makeSUSEdvd http://houghi.org/script/makeSUSErsync What it does is rsync and then add those new RPMs to the ISO, removing the old ones. This means that you have the latest version available for software. At this moment I see only one problem. In "Installation Setting", you get an error with "Software", so you select that, then "Details". A popup with a warning comes up about 'kdebase3-SuSE-...." Select "do not install "kdebase3-SuSE" and then "OK -- ry again". Accept, and the installation works for the rest as normal. I am not sure wether this is due to the script or due to the packages itself (or a combination of both). Any insight will be welcome. I am also woring on something else. Somebody gave an idea (and some code) to use autorp¹m on a 'factory' system. That way you can make a DVD iso from any factory. Working on it now. Any insight on wether this would be a good.bad idea is as welcome as info on the kdebase3-SuSE issue. ¹http://www2.autorpm.org:8080/ Unfortunatly ity does not have a maintainer anymore. Any other idea on how to do this is welcome as well. -- houghi They say pesticides have been linked to low sperm counts. In my opinion if you have bugs down there that are so bad you need to use a pesticide, you're not gonna get laid anyway. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory-unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-factory-help(a)opensuse.org

14 years, 5 months

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

openSUSE Factory June 2006