Mailinglist Archive: opensuse (2058 mails)

["Michel Salim" <michel.sylvan@xxxxxxxxx>]

On 13/08/07, joe <joe@xxxxxxxxxx> wrote:
>
>
> Philipp Thomas wrote:
> > On Sun, 12 Aug 2007 16:43:53 -0700, joe wrote:
> >
> >> You're much more likely to have success resolving any driver issues
> >> on the 32-bit install.
> >
> > That's just not true! The only case where a 64 bit Linux can be a
> > problem is when you need to use a binary only driver and the
> > manufacturer doesn't supply it. My experience shows that open source
> > drivers are mostly just as bad or good on a 32 bit Linux as they are
> > on a 64 bit one.
>
> Hence my statement about "3rd party drivers or programs", which you snipped.
>
> I did say that linux64 is great for generic server roles on largish hardware,
> where you can do everything using what ships from the linux vendor, and where
> the hardware is big enough to benefit from the 64-bit OS.
>
> > So if a driver doesn't work under 64 bit Linux chances are very low
> > it'll suddenly start to work as a 32 bit version.
>
> Many vendors make only a 32-bit version of their linux offerings, or if they
> do make a 64-bit version, it's not well tested, and buggy. I speak from bitter
> experiences in the trenches, and can cite examples.
>
At least RPM supports multilib, meaning you can happily run 32- and
64-bit applications side-by-side.

The binary driver situation is all the more reason to support vendors
that have more enlightened driver policies. Or, failing that, those
that can provide reliable 64-bit drivers (grudging lift of the hat to
nVidia on this).

-- 
Michel
-- 
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx