GuTSy is slow!

[Derek Broughton]

Mario Vukelic wrote:

> 
> On Wed, 2007-10-17 at 10:02 -0300, Derek Broughton wrote:
> 
>> Great idea.  I'm really not stupid Mario.  I did that.  It got
>> reinstalled...
> 
> I know that you aren't, that's why it annoys me so that you pretend that
> removing the packages is impossible. How where they "reinstalled"? Must
> have been depended on by another package, I and I'm pretty sure you know
> that. Please explain if I misunderstand.

I don't know how, or when, they got reinstalled, because I don't use them. 
One day, after I'd previously removed all packages bluetooth related, I
discovered kbluetoothd was running.  I could, I suppose, have found what
package it's in (kdebluetooth) and found out when it got installed
from /var/log/aptitude, but at that point I just threw up my hands.  As I
pointed out to somebody here last week, most of those processes really
_aren't_ doing much and it's rarely worth the effort.  But it still irks me
that they're there.
> 
>>  I have two
>> laptops without bluetooth, and the damn things are still running the
>> bluetooth daemons.
> 
> So the solution is "fix/add the detection code and just run when
> hardware is there". 

Exactly.  I love that Ubuntu works on so many systems - I just find starting
things that it should be able to tell don't exist is sloppy.
> 
> Still, how hard is it to click menu System | Administration | Services,
> and remove the check mark from "bluetooth management"? 

OK, I take it back.  I AM stupid.  I've never spotted this one.  Works
perfectly ... :-)

>>  I've used _all_
>> the alternatives.  NM is the best of a bad lot.  As I said in a prior
>> post, I use it and I like it, but I can well understand why many don't,
>> and for a desktop machine, it _should_ be possible to use the much
>> simpler /etc/network/interfaces method
> 
> But that's what I said. Define the interface in /etc/network/interfaces,
> and NM will leave it alone.

And Kubuntu even came with an editor for that in System Settings (I think
it's still there), but no explanation of how changing it will completely
break NM's handling of interfaces, or why you should use one instead of the
other.  
> 
>> and never even start NM - _without_
>> needing my level of expertise.
> 
> IMHO no, they should not. They should be provided with a working NM that
> does all they need as transparently and efficiently as possible.

That would be fine - but unfortunately, it hasn't so far been the case.
> 
> You did not address this point of mine:
> 
>> > It's the logical result of a distro working automagically in all
>> > circumstances.

It seemed not necessary to comment - if it really did that, we wouldn't be
having this discussion!

> I should have added "... as long as it isn't perfect". I say, of course
> bluetooth should only be started if the hardware is there. Of course it
> would be nice if NM did not load any code needed only for wireless
> cards, when the NIC is plugged in. Etc. 

And I love that Ubuntu _does_ work for almost everybody, I just get
frustrated when apps that don't work right get replaced with more
complicated apps that STILL don't work any better.
-- 
derek