Darren New wrote:
> Eero Ahonen wrote:
>>
>> What driver? What kernel does the system have?
> 
> I don't know. That was a while ago. It was apparently a known problem,
> not that it made it any easier to work around.  It sucks when youhave a
> bug in the software update software. :-)

Ah, ok. And yes, it does suck when software installer sucks.

> Actually, I may be confused. The USB problem was the USB kernel thingie
> going compute-bound at high priority.  Fixed after an update.

Ok.

> There was soemthing else about the install.

You remember Murphy? If something fails, also other things fail, even if
they aren't related. Unfortunately it's not uncommon to see that failed
installation has multiple problems.

>> distribution", but I still don't think it should be generalized to be a
>> *Linux* -feature.
> 
> I'm amused how whenever there's something good, it's a Linux thing, and
> whenever there's a problem, it's not Linux's fault but someone else's. ;-)

Yes and no. Yes, it IS a pretty common way handle things, but not
always. Noticed my words of Afterstep usability (Afterstep, not Linux
particular)? I can run Afterstep on *BSD, Irix, Solaris... But not on
Windows (well, actually I can, but I can't replace Explorer with it).
Nor this "install every driver" -thingie - it's generally a good thing,
but it depends on the distribution. If SuSE or Ubuntu does it (AFAIK
they both do), it doesn't apply on every Linux out there.

>> Nope, you install NIC drivers and download the rest from the Internet ;).
> 
> And from one place!

IF you have hardware that has working* drivers at Windows Update.

*) with your hardware combination


-- 
Eero "Aero" Ahonen
   http://www.zbxt.net
      aer### [at] removethiszbxtnetinvalid

Post a reply to this message