2c about the development of ubuntu
mdz at ubuntu.com
Mon Jan 2 15:07:18 GMT 2006
On Sun, Jan 01, 2006 at 04:47:33PM +0100, Udo 'Robos' Puetz wrote:
> But since then ubutu has taken too much in in my opinion. Edubuntu,
> ubuntu on the server, ltsp and also the amd64 part.
What amd64 work are you referring to here? amd64 has been an officially
supported Ubuntu port since the very first release, and will remain so.
> I even think I see and experience the problem already: breezy has exploded in
> my face on 5 machines. My laptop didn't work too well after the upgrade so I
> reinstalled - to also test how the installer worked (I *hate* reinstalling).
> After that, hibernation works only strange, if at all, and my wireless mouse
> doesn't work at plugin-time, I have to modprobe (-r) stuff to get it working.
> My machine at work can't log in with gdm or xdm, I have to use kdm. This is
> also after a normal upgrade. My main machine also didn't survive the upgrade
> too well so I reinstalled but that didn't help much. Burning software (like
> nautilus and gnomebaker) worked very bad so I thought, what the heck, let's
> try dapper on my main machine.
The best approach to this type of problem is to attempt to debug it and
report your findings as a bug. Sometimes when encountering a problem,
frustration leads to the temptation to blame the problem on abstract goals,
when in reality these are usually straightforward technical problems.
Especially when it comes to hardware support, the ONLY feasible way for
regressions to be found is through community participation in
testing well BEFORE the final release. By the time an Ubuntu release is
official, it's usually too late to fix such problems.
More information about the ubuntu-devel