I too am uncomfortable with the "behind scene" changes. Yast is a good tool for SuSE installed apps. But when you f.ex. prefer a newer Samba you are in trouble if you install from source and then accidentally run automatic online update. You hose your samba install. True, it would be MY mistake, but why allow it in the first place. On any scripts/pgms I write I take these kinds of things into consideration which makes it overall safer to administer. Installing from source brings you to hell - sooner or later. You should AT LEAST try to build your own RPM's that fit into the system's package management. And talking about online update: My YOU replacement (www.gaugusch.at/fou4s) supports notification and ignoring of named
On Mon, 6 May 2002, Steve wrote: packages. Maybe you should give it a try.
The best solution would be if you could turn off modules in Yast where you prefer to configure things manually. Then whatever you did, or some jr admin, it would not hose the system. This kind of problems always happen when you automate. You gain here and loose there. How about a decent backup system? SuSE is really pretty OK as long as you stick to their install. You should stick to their package system (RPM), and everything will be fine. For example, I compiled Gnome-Toaster 1.0Beta5 on my system (7.3). During update, I was asked if I wanted to replace it by 1.0Beta2 (which is delivered with 8.0) - of course not, but isn't it niiiiice? :) So I can easily agree with the desktop feel that previous email spoke about. I've been oscillating on going back to RH on servers for that reason. A few months ago I self-compiled a kernel on a redhat machine. The f*cking online update didn't want to update PHP4 because of broken dependencies! Those "§$)= people include the kernel in their online-update dependencies ... ha! very nice - NOT :(
Markus -- _____________________________ /"\ Markus Gaugusch ICQ 11374583 \ / ASCII Ribbon Campaign markus@gaugusch.at X Against HTML Mail / \