Mailinglist Archive: opensuse (3232 mails)
| < Previous | Next > |
Re: [SLE] Why does SuSE tweak software so much that it no longer work with other programs?
- From: John Andersen <jsa@xxxxxxxxxxxxxx>
- Date: Mon, 21 Aug 2006 07:00:30 +0000 (UTC)
- Message-id: <200608202300.21352.jsa@xxxxxxxxxxxxxx>
On Sunday 20 August 2006 22:34, Mark H. Harris wrote:
> On Monday 21 August 2006 01:07, John Andersen wrote:
> > > 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).
Seems to me those OTHER distros are back level. I was under the
impression modprobe.d etc were part and parcel of the later kernels
and none of SuSE's doing.
> I recently had a royal pain trying to
> install 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
You want red hat, run red hat!
I like having one place to look for command line options etc...
It doesn't break anything, because if you install some non-suse pacakge
it won't use that area anyway.
> 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.
The Linux Filesystem? Or you had to Unlearn Red Hat?
> 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...
Start with Intel's web site.
I've build Mplayer, xine, and MythTv from tarball source, including drivers
for tha Hauppage tuners and had no particular problem adopting red hat
centric directions to SuSE.
No more trouble than I would have had adopting them to Ubuntu.
I build a lot of stuff from source tar balls, and also install the
occasional binary tarball (Vmware etc) with no particular problem.
That's why I was surprised that you said you couldn't do tar-ball installs.
I do it fairly frequently.
--
_____________________________________
John Andersen
> On Monday 21 August 2006 01:07, John Andersen wrote:
> > > 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).
Seems to me those OTHER distros are back level. I was under the
impression modprobe.d etc were part and parcel of the later kernels
and none of SuSE's doing.
> I recently had a royal pain trying to
> install 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
You want red hat, run red hat!
I like having one place to look for command line options etc...
It doesn't break anything, because if you install some non-suse pacakge
it won't use that area anyway.
> 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.
The Linux Filesystem? Or you had to Unlearn Red Hat?
> 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...
Start with Intel's web site.
I've build Mplayer, xine, and MythTv from tarball source, including drivers
for tha Hauppage tuners and had no particular problem adopting red hat
centric directions to SuSE.
No more trouble than I would have had adopting them to Ubuntu.
I build a lot of stuff from source tar balls, and also install the
occasional binary tarball (Vmware etc) with no particular problem.
That's why I was surprised that you said you couldn't do tar-ball installs.
I do it fairly frequently.
--
_____________________________________
John Andersen
| < Previous | Next > |