I've had cause to wonder just how deep a desktop should go into the system on several occasions. The latest one is kde automount. Mounting is usually buried in boot but in this case it results in 10 plus seconds of dead desktop - more than enough time to even access what ever is being mounted let alone something else. Vista for one is a bit like that as standard without any mounts but must we stare at the desktop guessing when it's likely to work like they have too?

Then there is kpackager. On 3.x I must admit I have used it on occasion to install apps that my disto's installer finds more dependencies. Often the apps still work. The kpackager version in 4.6 offered me a number of updates when my distro's software management had none to offer. I disabled it as a result and many others seem to have done the same.

I'm also tempted to mention kfind so will. My 1st linux install was suse pay for. KDE 3.1 I think. First time I used kfind up came a message "building index". There after searches were quick and no signs of creepy crawlies browsing around my discs causing continuous tinkling noises and interfering with disc accesses when I wanted them. The windoze indexing is completely transparent.

On the other hand in respect to the shell/bash good riddance to it as we should be able to do all from the desktop maybe even as root - if we are ever allowed too - even if a password has to provided when ever we choose to do what ever we want to do. Signs are that user capabilities are diminishing in this sort of area on security grounds that many users aren't really interested in. Shouldn't this sort of thing be decided at install not forced down peoples throats?

--

Personally I never experienced delays when mounting, unless the media had issues on its own (damaged CDs, etc).

I should have pointed out that I was referring to the network drive/server auotomounter. Not cd's

--