Novell/SuSE does things strikingly different than the rest of the Linux community lately... which prevents tar-ball installs,
What do you mean by that? Well, as a for instance... SuSE uses modprobe.d, modprobe.conf, and modprobe.conf.local. Some of the rest of the Linux world is still using modules.conf (or conf.modules). I recently had a royal pain trying to install
On Monday 21 August 2006 01:07, John Andersen wrote: the new Alsa drivers (from RealTek, and from the Alsa project) because the instructions (and Makefile) did not match the SuSE distro... so I had to manually tweak everything to get it to work... this is just one example. The configuration etc/sysconfig tree is anther example... completely differnt from RedHat (for instance, not that its totally a bad thing), but basically, when I switched over to SuSE I had to relearn almost everything I had learned about how things are configured maintained in the linux filesystem. Some of what I mean (as well as Avi, I think) is that Novell/SuSE customizes almost everything they touch (I am learning) which is great as long as Yast and YOU work--- but when things have to be done manually, oh boy what a pain. As an example, after installing the Alsa drivers for my Intel HD Audio, now if I start Yast and touch the 'sound' config button Yast crashes... don't know why, and don't know how to fix it... but Yast is definitely not happy with my manual install of the Alsa drivers... which was the only thing I could do to get my sound working on this new HP box (S7400N). That's what I meant .... -- Kind regards, Mark H. Harris <>< harrismh777@earthlink.net