1 |
chrome://messenger/locale/messengercompose/composeMsgs.properties: |
2 |
> On Freitag 12 Februar 2010, Dale wrote: |
3 |
> |
4 |
>> chrome://messenger/locale/messengercompose/composeMsgs.properties: |
5 |
>> |
6 |
>>> On Donnerstag 11 Februar 2010, Dale wrote: |
7 |
>>> |
8 |
>>>> chrome://messenger/locale/messengercompose/composeMsgs.properties: |
9 |
>>>> |
10 |
>>>>> On Donnerstag 11 Februar 2010, Alan McKinnon wrote: |
11 |
>>>>> |
12 |
>>>>>> On Thursday 11 February 2010 13:50:54 Walter Dnes wrote: |
13 |
>>>>>> |
14 |
>>>>>>> On Thu, Feb 11, 2010 at 01:31:26AM +0100, Volker Armin Hemmann wrote |
15 |
>>>>>>> |
16 |
>>>>>>> |
17 |
>>>>>>>> On Donnerstag 11 Februar 2010, Roy Wright wrote: |
18 |
>>>>>>>> |
19 |
>>>>>>>>> IMO, mandatory semantic-desktop is a very good reason to find |
20 |
>>>>>>>>> another desktop manager (even after being my primary desktop for 7 |
21 |
>>>>>>>>> years). |
22 |
>>>>>>>>> |
23 |
>>>>>>>> yeah good luck with that. Because gnome is moving in that direction |
24 |
>>>>>>>> too. |
25 |
>>>>>>>> |
26 |
>>>>>>>> |
27 |
>>>>>>> There are other desktops besides GNOME and KDE. Actually I |
28 |
>>>>>>> prefer the |
29 |
>>>>>>> |
30 |
>>>>>>> ICEWM window manager. I was running a 1999 Dell 450mhz PIII with 128 |
31 |
>>>>>>> megs of *SYSTEM* ram until the summer of 2007. Let's just say that |
32 |
>>>>>>> GNOME and KDE were out of the question for me. On my current |
33 |
>>>>>>> desktop, ICEWM flies. But I also have a netbook, and again GNOME |
34 |
>>>>>>> and KDE are not usable. |
35 |
>>>>>>> |
36 |
>>>>>>> |
37 |
>>>>>>>> Seriously guys, you start sounding like luddites. Is new, must be |
38 |
>>>>>>>> bad. |
39 |
>>>>>>>> |
40 |
>>>>>>>> |
41 |
>>>>>>> Correction, is fat, bloated, and slow, must be bad. I wonder if |
42 |
>>>>>>> |
43 |
>>>>>>> Microsoft's anti-linux strategy is to have its agents infiltrate the |
44 |
>>>>>>> linux developer community, and turn linux into bloatware. |
45 |
>>>>>>> |
46 |
>>>>>> You have been corrected on this point so many times I now think you |
47 |
>>>>>> are just a stupid ass. |
48 |
>>>>>> |
49 |
>>>>>> It is not slow. |
50 |
>>>>>> |
51 |
>>>>>> You are the only one saying that. People who do use Nepomuk say that |
52 |
>>>>>> it is not slow and does not hog resources (initial scan excepted). |
53 |
>>>>>> |
54 |
>>>>> you can even tell nepomuk how much memory it is allowed to use ... |
55 |
>>>>> |
56 |
>>>> Can you nice the thing too? That would work. I set emerge to 5 and I |
57 |
>>>> can't even tell that emerge is running most of the time. There may be |
58 |
>>>> times when I can but it is rare. |
59 |
>>>> |
60 |
>>>> I just don't get this thing that indexing is a resource hog. I notice |
61 |
>>>> updatedb running at night. I have 329Gbs of "data" and updatedb only |
62 |
>>>> takes a few minutes. How is that a resource "hog"? My machine is not |
63 |
>>>> as old as some but it is slow going by the new machines that are out |
64 |
>>>> now. It's a AMD 2500+ with 2Gbs of ram. I have had Linux on machines |
65 |
>>>> as slow as 133MHz but never felt the need to disable indexing. |
66 |
>>>> |
67 |
>>> when updatedb runs your cache is shot afterwards. That is a known |
68 |
>>> problems. |
69 |
>>> |
70 |
>>> Nepomuk is only noticable once: the first indexing run. After that it |
71 |
>>> creates zero load. |
72 |
>>> |
73 |
>> So cache is bad? Heck, my cache is almost always full anyway. Nothing |
74 |
>> new there. If it is not updatedb then it will be something else. |
75 |
>> |
76 |
> no, cahce is great. That is the problem. Updatedb replaces the cached files |
77 |
> with stuff you probably don't care about. Which is bad. |
78 |
> |
79 |
> |
80 |
|
81 |
I don't think I have ever seen my cache change when running updatedb. |
82 |
Maybe it is so small that it doesn't matter. After all, I only have |
83 |
over 300GBs worth of files on the drives and 2Gbs of ram. This makes me |
84 |
want to stay up tonight and test this theory. o_O |
85 |
|
86 |
Dale |
87 |
|
88 |
:-) :-) |