Suse/NovellThis Forum is for the discussion of Suse Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
A 10.2 installation, working well on Shuttle 3ghz P4 x64. The update icon had the 'red x'. When trying to update the software, configuring the update sources, etc. the following error appears:
Server stack trace:
at Novell.Zenworks.Zmd.Packaging.PackageManager.GetUp dates (Novell.Zenworks.Zmd.Catalog catalog) [0x00000]
at Novell.Zenworks.Zmd.Packaging.PackageManager.GetUp dates () [0x00000]
I've tried various yum, yumex, Suse updater and two things happen: the above error appears, or the Yast will show a progress bar that downloads available packages, etc. then the GUI quits, nothing happens. Logged in as root, tried the shell versions of the above.
For amusement, I installed the 10.3 Alpha, as an 'update'. All went well, the usual stuff I use is fine, but the update error continues.
Someone suggested the smart package manager... there is some instruction on the suse wiki, though it refers to 10.2. Worth trying that or may I be doomed for the 10.3 update?
I've looked at other update error related posts here and they seem a bit different.
Thanks for looking.
Also... new to linux, have only enough experience to be dangerous.
The problem with the ZEN update is that it is based on mono-core. Mono is a unix implementation of the .Net framework developed by Microsoft. Mono as an interpreted language is still slow compared to apps coded under C++, Java, and Python. The problem with ZEN has existed since it was introduced with Suse 10.1. You can speed up your system and save some resources by removing ZEN, and ZMD. The Suse updater will still check for available updates when an authorized user logs in.
As far as Smart is concerned, it will not be reliable for Suse 10.3 as that is an unreleased, version for "testing" purposes. SMART is very similar to the way synaptics works and is therefore dependent on stable up to date repositories. You DO NOT want to use a 10.2 repository with the 10.3 alpha. You might be better off using the YaST online updater.
Zen is the Suse installer that is to take the place of YaST. You are using 10.3 alpha, so maybe Suse is working on the issue and making some progress. I have not tried 10.3 yet, but in versions 10.1 and 10.2 there were some major problems associated with ZEN and its mono base.