On Monday 02 July 2007 10:38, Sunny wrote:
On 7/2/07, Randall R Schulz <rschulz@sonic.net> wrote:
So it appears Google Desktop works on SuSE Linux 10.0. It will no doubt be quite a while before indexing is complete. The indexing status report says 1.8% complete with 5.7 idle hours to go.
Finally, my decision to not try to organize my mountain of downloaded research papers appears to be vindicated.
Randall Schulz
Sorry for the hijack, but looks like related - does anybody has a list of the differences between GoogleDesktop and beagle? Including performance monitoring, etc.
I can tell you that on my 10.0 system, one key difference is that Google Desktop works while Beagle's lookup interface does not. I'm not saying the software is at fault, I may have managed to break it somehow, but as it stands, I cannot perform beagle queries, even though every morning I get those voluminous reports on the indexer's activities overnight. To wit: beagle-query "Unification" ** (beagle-query:32088): WARNING **: The following assembly referenced from /usr/lib/beagle/Util.dll could not be loaded: Assembly: gconf-sharp (assemblyref_index=7) Version: 2.8.0.0 Public Key: 35e10195dab3c99f The assembly was not found in the Global Assembly Cache, a path listed in the MONO_PATH environment variable, or in the location of the executing assembly (/usr/lib/beagle). ** (beagle-query:32088): WARNING **: The class GConf.Client could not be loaded, used in gconf-sharp, Version=2.8.0.0, Culture=neutral, PublicKeyToken=35e10195dab3c99f Could not connect to the Beagle daemon. The daemon probably isn't running. Beagle.ResponseMessageException: Connection refused System.Net.Sockets.SocketException: Connection refused in [0x000e0] System.Net.Sockets.Socket:Connect (System.Net.EndPoint remote_end) in [0x0000d] (at /usr/src/packages/BUILD/mono-1.1.13.2/mcs/class/Mono.Posix/Mono.Unix/UnixClient.cs:170) Mono.Unix.UnixClient:Connect (Mono.Unix.UnixEndPoint remoteEndPoint) in [0x0000d] (at /usr/src/packages/BUILD/mono-1.1.13.2/mcs/class/Mono.Posix/Mono.Unix/UnixClient.cs:177) Mono.Unix.UnixClient:Connect (System.String path) in [0x00019] (at /usr/src/packages/BUILD/mono-1.1.13.2/mcs/class/Mono.Posix/Mono.Unix/UnixClient.cs:59) Mono.Unix.UnixClient:.ctor (System.String path) in (wrapper remoting-invoke-with-check) Mono.Unix.UnixClient:.ctor (string) in <0x0002b> Beagle.Client:SendRequest (Beagle.RequestMessage request) in <0x00033> Beagle.Client:SendAsync (Beagle.RequestMessage request) Since I've never knowingly done anything with the Mono packages or configuration, whatever is wrong was an unintended consequence of some other action or a packaging / dependency problem somewhere.
-- Svetoslav Milenov (Sunny)
Even the most advanced equipment in the hands of the ignorant is just a pile of scrap.
If we're lucky... Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org