Rick wrote:
> On Sat, 06 Jun 2009 13:05:14 +0100, Conor wrote:
>
>> In article <>, johannes says...
>>
>>> So adding all this up it will be a lot more than 6 minutes to get it to
>>> work properly.
>>
>> Indeed. Takes me about 30-40 minutes on a X2 4800+ with 2GB RAM desktop
>> and about the same on a 1.73 Ghz Core Duo lappy with 2GB RAM.
>>
>> And then you spend another couple of hours implementing the fixes to get
>> everything working properly as it did in previous versions.
>>
>> The problem with Ubuntu that doesn't exist in
>> Suse/Mandriva/Fedora/Debian etc is that in a rush to meet their self
>> imposed 6 month release schedule, they let some really whopping show
>> stoppers through which are usually caused by an omission in a config
>> file. Other distributions will hold back a release.
>>
>> Ubuntu sadly is the epitomy of shitty quality control. Even going with a
>> LTS release doesn't guarantee anything as both the hard drive load cycle
>> bug and the windows network browsing bug came into being with 8.04 LTS.
>
> From what I've read, the network browsing bug is a Gnome bug, as was the
> bug that wouldn't allow remotely managing users, and some other admin
> tasks.
>
>
And since Ubuntu uses gnome it really doesn't matter does it? The bottom
line is that someone who installs Ubuntu and wants to browse the network
won't be able to. It's broken plain and simple and Canonical released
Ubuntu with this bug that was obviously never tested. Because it's a gnome
bug vs a XYZ bug is of little consequence to the user who can't browse the
network.
|