[NTLUG:Discuss] opensuse and Beagle

Leroy Tennison leroy_tennison at prodigy.net
Fri Sep 26 15:16:54 CDT 2008


Ted Gould wrote:
> On Fri, 2008-09-26 at 14:04 -0500, Kenneth Loafman wrote:
>> Whatever the indexer's name, it causes the same problems as Microsoft's
>> indexer in that it gets loaded and started by default, and sucks up an
>> unreal amount of CPU and system resources in certain cases, especially
>> noticeable when you really need system response.
> 
> Well, all of them do things to try to alleviate that problem.  Most
> don't start indexing immediately on login, they wait a fixed amount of
> time to try and avoid when users are typically starting apps.  Almost
> all run nice'd so that any process that wants the CPU over them will get
> it.
> 
> The real issue here is IO.  Most users think of "need system response"
> as I want my applications to start fast.  And most of that IO bound.
> Most of login is IO bound.  And there is no way to 'nice' IO currently.
> That's a kernel issue and will hopefully be solved by some of the
> schedulers that are currently being worked on.
> 
> Indexing is an important feature for users.
> 
> 		--Ted
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> http://www.ntlug.org/mailman/listinfo/discuss

Unfortunately that hasn't been my experience.  Kbounce didn't just start
slow, it stayed slow.  I hope it's not continuing to load stuff in the
background as I'm trying to play the game.

I have to agree with a previous post, we haven't learned from M$
mistakes.  While I understand (and agree) that Linux needs to be similar
to Windows in some ways (primarily the GUI - hats off to KDE) to attract
non-UNIX users we need to have a fair amount of discretion about what we
emulate.

I was relieved to see that SuSE replaced the splash screen of K3B with
something a little more "business palatable".  There are some
"Linuxisms" which just don't make sense.  However, I am/will be
concerned at any point if Linux becomes restrictive (the "this is the
proper way to do it, stop complaining" attitude).

I am already somewhat concerned that the GUI utilities are hiding too
much of the details about Linux configuration.  I don't mind having them
available as a convenience but I always want to be able to understand
what's being done and why should I desire to do so (mainly for
troubleshooting).  This is (one of many) huge gripes I have about
Windoze, what part of the junk pile known as the Registry did they put
the settings in and what do those settings do?

Emulating failure is not a good thing, the Linux community needs to be
careful.



More information about the Discuss mailing list