November 2008 - openSUSE Users - openSUSE Mailing Lists

[opensuse] SUSE SWAMP
by Ciro Iriarte 06 Apr '09

06 Apr '09

Anybody tried it?, is it actually being used on the Opensuse project?. Looks interesting.... Maybe it can replace workflow apps on Domino/Notes... Webpage: http://swamp.sourceforge.net/ SWAMP - The Workflow Platform SWAMP is a workflow processing platform. Workflows are processes with many people involved in many working steps. In a real world scenario these workflows are highly dynamic, but still many systems try to hardcode the business logic. That leads to raising efforts to adapt the system. Here is where SWAMP steps in: The workflow is designed in a XML based meta language in one file which is read by SWAMP. Workflows can be built from different workflow 'patterns' like simple actions, decisions, selections, loops, but also custom code and external events if required. SWAMP builds a HTML GUI from the workflow definition file that guides different users through the whole process, sends notifications if required, assembles overview pages over all running processes and much more. A SOAP interface can be used to integrate external systems into the workflow. These are SWAMPs main Features: * Support of many different workflow patterns * Flexibility in workflow design: A workflow can be specified in a single XML file * Workflow evolution: Workflows can be developed while in operation (versioning) * Ease of use: clear and straightforward XML based workflow definition language, no coding skills needed * Workflows can attach data and files * Automatic web-GUI generation for handling individual tasks and administrating workflows * Running on Linux + Windows with OS-independant tools: Java, Tomcat, MySQL * MySQL + LDAP authentication possible * User and Role management, workflows/tasks can be restricted * Mail notification system included * Unlimited amount of different workflow-types on one server * Scheduler to control time-critical workflow paths * SOAP interface allows interaction with external systems * Openness: Custom code allows unlimited functionality, event- and data gateways * Customizeable overview lists with filters -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

4 8

[opensuse] Is an update to KDE 3.5.10 OK?
by David C. Rankin 05 Apr '09

05 Apr '09

Listmates, Before I regret it, has anybody had any bad experience with an update to KDE 3.5.10. I seem to recall a week or so ago, there was a complaint about 3.5.10, but there was very little follow up. That leads me to believe all is safe. But getting older, I have learned to look before I leap. So anybody have any information on the update? -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

6 7

[opensuse] Controlling zypper's Timedout when it is updating -- REPOST
by Basil Chupin 06 Jan '09

06 Jan '09

When zypper is downloading upgrades in YaST2 (Online Update), a loss ofconnection to the internet can occur or some other hiccup where zypper either cannot connect to the URL or it cannot get the filename to download. When this occurs zypper sits around for seems like an eternity doing nothing and then announces that an error occurred; it expects a click of the mouse on the OK button after which another window comes up giving you the chance to Retry etc. In 99+% of cases simply clicking on Retry get zypper to get on with the job. This sitting around doing nothing is a PITA for 'hours' - and there is nothing that one can do except to wait until zypper decides to advise you that an error occurred. The ABORT button does not work so one just sits and waits. (Of course, there is always the drastic step of CTRL-ALT-ESC to exit zypper.) Somewhere there must be timer setting which controls how long zypper keeps trying to resume its task. Does anyone know where this setting is located so that the user can set the timeout period. Nothing I can see in zypper help and nothing shows up in /etc/zypp. Can anyone provide an answer, please? Ciao. -- Be nice to people on your way up - you'll see the same people on your way down. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

10 27

[opensuse] unsubscribe
by Mike Davis 27 Dec '08

27 Dec '08

Please unsubscribe me from maillist -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

2 1

[opensuse] Suse 11 to 11.1 upgrade
by Dave Feustel 22 Dec '08

22 Dec '08

How will users of Suse 11.0 upgrade to 11.1? Thanks. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

17 28

Re: [opensuse] 11.1 countdown
by Ionut Vancea 18 Dec '08

18 Dec '08

Hi, On Thu, Nov 13, 2008 at 7:54 PM, jdd <jdd(a)dodin.org> wrote: > Ionut Vancea a écrit : > >> ok, now try to put the following: >> >> [[http://en.opensuse.org/OpenSUSE_11.1|http://counter.opensuse.org/11.1/large]] >> >> and it will work, I hope :) > > nope, already tried > > http://dodin.org/wiki/index.php?n=Main.HomePage > > (look above the opensuse 11 banner) > > :-( > > this should works, but I'm not confident about the crontab (is the > time correct?) > > script to dl the image each day (this image is loaded in the wiki) > > (opensuse.sh) > #!/bin/sh > cd /home/www/htdocs/wiki/uploads/Main > wget http://counter.opensuse.org/small > rm small.png > mv small small.png > > crontab > > 30 12 * * * sh /root/bin/opensuse.sh > > noon each day, with 30 minutes delay? > > jdd So, there are two different things: 1. To place an image into a page 2. To have an image link to another location The differences between them are explained very well here: http://pmwiki.org/wiki/PmWiki/Images So, now what you tried and didn't work, was the second method, but you have to use the first method "To place an image into a page", and I see that the syntax to use is (example from above link): http://pmichaud.com/img/misc/pc.jpg"Paper clips" | [- %newwin% [[ (Wikipedia:Paper_clips | Paper clips ]] are ''fun'' to work with. -] so, in your case has to be: "To place an image into a page, enter the address (url) of the image into the markup text" http://counter.opensuse.org/11.1/large"OpenSUSE Counter" cheers, Ionut -- === Ioan Vancea http://www.vioan.ro -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

6 12

[opensuse] KDE3-4 did teams change?
by David C. Rankin 12 Dec '08

12 Dec '08

List, At novell, are the same people that did KDE3 development, bug squashing, etc. (support) the same folks that are supporting KDE4 or were separate teams used? -- David C. Rankin, J.D.,P.E. | openSoftware und SystemEntwicklung Rankin Law Firm, PLLC | Countdown for openSuSE 11.1 www.rankinlawfirm.com | http://counter.opensuse.org/11.1/small -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

39 220

[opensuse] Various Novell clients for Linux
by Roger Oberholtzer 12 Dec '08

12 Dec '08

Anyone know the status of the Novell IPrint Client and Netware Clients for openSUSE? The IPrint client does seem to work ok. But it is never included with openSUSE. The Netware client is more of a mystery. http://www.novell.com/coolsolutions/tip/19968.html implies that with fiddling it can work with 10.2, 10.3 and 11.0. But why not a proper package for the releases of openSUSE? I understand that Novell would like to sell things. I work at a place with a Netware site license - we have already bought everything. It is everywhere. Except on any openSUSE clients. Is the idea that folk who want to work in a strictly MS environment are fine with openSUSE (Novell +MS deal helps ensure that), but folk who want to work in a Netware environment are not in as good a position to be integrated with Netware? Something seems odd about that. I can only interpret the continued lack of real releases of these clients for the releases of openSUSE to mean that Novell are not as interested in Netware integration of openSUSE as they are of MS integration. I can join a Windows active domain via Yast. I can do nothing to integrate with Netware. How odd. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden Office: Int +46 8-615 60 20 Mobile: Int +46 70-815 1696 -- "On two occasions I have been asked (by members of Parliament!), 'Pray, Mr. Babbage, if you put into the machine wrong figures, will the right answers come out?' I am not able rightly to apprehend the kind of confusion of ideas that could provoke such a question. - Charles Babbage 1791-1871) English computer pioneer, philosopher And remember: It is RSofT and there is always something under construction. It is like talking about large city with all constructions finished. Not impossible, but very unlikely. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

6 17

[opensuse] Security Updates
by Donald D Henson 11 Dec '08

11 Dec '08

I keep getting notified that a security update is available for python and postfix. However, when I click the update button, I get the following error: Dependency resolution failed A package could not be found that allows the task to complete. More information is available in the detailed report. More details patch:esound-138.noarch conflicts with pavucontrol.i586 < 0.9.6-4.1 provided by pavucontrol-0.9.6-0.pm.1.i586 Would some kind soul tell me what I need to do to clear this thing? -- Don Henson

9 10

[opensuse] Of software RAID on SUSE Linux
by Tero Pesonen 08 Dec '08

08 Dec '08

Hi all! I've been pondering some options for how to set up my next SUSE system, and have come to the conclusion that software RAID would most likely serve my needs best. I've only had non-RAIDed, "regular" desktop systems till now, since the days of SuSE 8.0 or thereabout, but have of late become fed up with the reliability issues the typical IDE/SATA drives suffer from and the stress test they pose on one's backup policies. So now that I've decided to have my next box assembled for me from components I select, I've also decided to discard the traditional "one or two primary disks + a backup disk" approach; as despite how often or well I backup, if, or rather when, the disk where the OS lies dies, there's awfully lot of trouble and work anyway. I first looked at SCSI disks as a more reliable alternative -- if a disk can withstand server-level I/O for a few years, it sure as hell will stand up to anything I can throw at it on my humble desktop -- but there still exists a single point of failure unless I RAID-1 two decent-sized SCSI disks. This, with the controllers etc., would be very expensive, at least based on my I've seen thus far. The SCSI drives are also said to be noisy beasts -- a no-no for a desktop at which I will have to spend quite a few hours every day. Next I read about RAID controllers and the possibility of putting a few standard SATA disks into one, thus gaining fault tolerance for simple hardware failures (i.e. a disk dies). Of course, a RAID won't help against other kinds of data loss, such as the power supply's failing and killing other components with some mighty spike; or from fire, or flood, or what ever. That is OK. That's why I backup. Next I learnt that decent RAID controllers are supposedly very expensive. Worse, some people have reported of the controllers themselves breaking down unexpectedly, taking with them all the disks or, with luck, simply failing to function correctly, having to be replaced. The hardware controlled RAID is, so I learnt, often incompatible with other controllers, requiring it to be replaced with one from the same manufacturer or even with the exact same model which may or may not still be readily available, keeping the system down till one is found. This seemed more difficult than I had anticipated. However, based on what I last read about software RAIDs, it seems I actually need not make this more difficult than it has to be. I do not need performance but mere reliability. It seems the Linux software RAID would be able to provide this. I'd like to know if I've understood this correctly, and whether the proposed-below setup would work as expected on the to-be openSUSE 11.1 system. (I've also considered Enterprise Desktop for longer support, but the base system is getting a tad old while the next version won't still be out anytime soon, I'd think. Luckily the regular 11.1 will still include KDE 3.5) So, I would acquire for the system, say, four disk, three of which would be "online" as a RAID-1 setup at any given time, representing together a single virtual disk with x number of partitions, seen by the system as a single block device, while the fourth could sit as an online spare disk that upon the Linux RAID's learning of one disk's failure, would become online as part of the array and would be integrated / reconstructed accordinly. A fifth disk could be kept offline as a spare disk for the one that would get removed, and thus becoming the new online spare disk, and so forth. Or I could have just an offline spare disk that I would insert in the failed one's place during a power off, after which I would have it partitioned as necessary and have it then become part of the RAID array and to be reconstructed. And all would be well again and peace would reign. If this is indeed true, and based on what I read at openSUSE's guide on this at http://en.opensuse.org/How_to_install_SUSE_Linux_on_software_RAID it should be, will it matter at all what kind of (SATA) disks I use for the array as long as they all meet the minimum disk size as dictated by the virtual disk they present? In other words, may I combine disks from different manufacturers, with different specs, etc. without affecting the RAID somehow negatively? I.e. the disks need not be identical; this would be preferred to avoid an unlikely-but-not-unheard-of situation where a defect is shared by a batch of drives from the same manufacturer; or that they wear down the exact same speed and fail close to one another, etc. If one disk is slower than the others, will it impose the speed limit onto the RAID virtual block device? Meaning, that all disks will have to return some kind of "I/O done" before the Linux RAID will request further I/O? (Seems most logical for reliability.) On the other hand, replacing disks later with larger capacity ones will cause no problem as they only need to meet the minimum size criterion. Hence, I could replace them one-by-one such that each new disk, replacing a removed old one, is first let to fully integrate/reconstruct; finally, after all disk have been replaced, I could enlarge a partition or two, for example, as allowed by the new shared minimum, thus increasing the capacity of the virtual device that is being RAIDed. And there would, of course, be regular other backup routines in place, such as rsyncing the RAIDed block device to an external disk via USB/Firewire etc. Also, I presume the kernel would not mind a non-RAIDed internal SATA disk(s) being part of the system as well. Would it be possible to have two separate RAID arrays? (as long as all the disk can be connected and there is space and power available...) Is it really true that the system may still boot gracefully after the disk where the MBR was dies and is replaced during a power down? How exactly will this work -- is the MBR too mirrored on all disks? To me this kind of setup seems now the most convenient one, especially with the guide available on how to install openSUSE with a software RAID and how to monitor it. I'd presume there would be no other benefits in going for SCSI over this except better performance? I also believe hardware RAID controllers would only improve performance, too, while possessing no other relevant factors affecting typical desktop use? It seems I could get five or six 320GB SATA drives for the price of a single 146GB SCSI one, and I would need at least two of those for RAID-1 and a controller too, and extra capacity elsewhere. A lot of money, that is, with no improvement in reliability, it would seem, as three or four SATA's in a RAID with spare disks at hand would seem quite enough despite however unlucky I happened to be with picking the disks. One more question: Will I be able to access each disk's (that make the RAID) SMART data still with hdparm or even though the system would see them as a single block device? (Or so I presume, as they share the same mount points) I'd like to hear if the general ideas and arguments made above are more or less correct. I'm not going to order my new system just yet -- it is still a few weeks away at minimum, as is 11.1 too, I think -- but I'd like to think these issues through well beforehand. Thanks for all comments! Regards, Tero Pesonen -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse+help(a)opensuse.org

4 4