Mailinglist Archive: opensuse-factory (175 mails)

[Sid Boyce <sboyce@xxxxxxxxxxxxxxxx>]

Alexey Eremenko wrote:
> > I have now tried 11.0 on 3 machines and it fails miserably on all the
> > networking sucks wifi is a joke boot problems   . 10.3 blows the living crap[
> > out of 11.0
I have a friend who would share such sentiments and is consequently 
running 10.3. The area of wifi seems one of the main sticking points but 
there are others - I suppose it possibly depends on the hardware.

> > even 10.0 is less problematic  and that is on fairly new hardware   both 32
> > bit and 64 bit .
I have 5 11.0 boxes using wifi quite happily. I am using these boxes 
behing a Smoothwall 3 firewall to a cable modem, with the wifi used as 
backup during cable outages which on occasions occurs. A total of 6 11.0 
boxes, 5 64-bit and 1 32-bit. Would I consider a 10.x box? Certainly not 
and I'm using AMD hardware with NVidia cards/driver on 4 boxes.
For all the problems I have heard of with 11.0, I keep asking myself why 
I'm not seeing these problems and what am I doing wrong. I use quite a 
number of apps that I have built myself (the FlightGear suite and lots 
else) or that are provided as binaries and I'm running vanilla kernels 
on 5 and openSUSE kernels on the x86 box - a mix which you'd think would 
be more likely to be problematical.

> Well, openSUSE has new bugs/ and regressions from version to version.
> The only way to combat this is to participate during BETA process. For
> me, I was able to eliminate about 50% of the most serious bugs, that
> affect my user experience out of any openSUSE release.
>
> I did it by simply reporting them in bugzilla, and making follow-up.

Wise words, during Alpha and Beta I submitted a number of bug reports 
which have all been resolved and not present in 11.0. Such bug reports 
are vital, if they are not forthcoming, then those bugs may be there at 
GM release.
Same goes for any piece of software, I have one example where there was 
a mistake in a kernel source file that had been there for a very long 
time and only bit when I went past a certain -rc kernel release, causing 
Linus to wonder why it didn't cause a problem in all that time until I 
hit it. When I initially reported it as a kernel problem, the response 
from one developer was that it was a problem I should push to openSUSE 
rather than the kernel, but I insisted it was a kernel problem 
repeatable on a number of boxes with a development kernel at and after a 
certain -rc release. After more than 3 weeks one other user hit the same 
problem on a laptop and another distro. It got fixed when the developer 
of a file noticed he used ">=" instead of "!=".
Regards
Sid.
--
Sid Boyce ... Hamradio License G3VBV, Licensed Private Pilot
Emeritus IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support 
Specialist, Cricket Coach
Microsoft Windows Free Zone - Linux used for all Computing Tasks

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