[Mono-list] mono in a marvell plug server
Hi, everyone. I imagine that most of you have read about this http://linuxdevices.com/news/NS9634061300.html Summarizing, it's a very small Linux server. With a size of a simple cell phone charger, it have an ARM CPU at 1.2 Ghz, 512 Mb RAM and 512 Mb of flash disk, USB ports, ethernet port, a Linux distribution (I don't know which distribution) with kernel 2.6, and other features. My question is... could be possible installing Mono 2.4 on this device? It would be fantastic if it is possible running asp.net applications on it. Regards. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] Attention all SoC students
To whom it may concern, If you haven't yet, please make sure you are subscribed for updates to your proposals, so you're notified when comments are added to them. andreia gaita ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] FileSystemWatcher on Linux to monitor a remote NTFS share
Then what you are saying is that this class is not a correct implementation of the .NET class. This is a COM event registration which uses COM communications, nothing whatsoever to do with CIFS/SMB/SAMBA. The UNC is just to tell the class where to connect the COM object to. Unfortunately, mounting the share locally will not work either, as the class will then just attempt to use inotify to monitor it which will not work. The only way around it would be to use the managed/polling option which would defeat the purpose as we are trying to get a "push" notification. thx anyway! Robert Jordan wrote: > > colinjones wrote: >> I don't think there is any point trying to mount the remote share, or >> anything like that because the FileSystemWatcher class needs to parse the >> UNC path to get the remote machine name so that it can connect to the >> same >> functionality on the remote machine using COM communications. > > Linux does not support UNC paths, nor Mono does. And CIFS does not > need COM :). > > You have to mount the Windows share with OS' machinery (smbmount). > Then you can use the share like a local path. > > Robert > > ___ > Mono-list maillist - Mono-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-list > > -- View this message in context: http://www.nabble.com/FileSystemWatcher-on-Linux-to-monitor-a-remote-NTFS-share-tp22836300p22898573.html Sent from the Mono - General mailing list archive at Nabble.com. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] mono-core problem
Mario Munda wrote: > > "WARNING **: _wapi_sendto: Need to > translate 64 [Host is down] into winsock error". > We have the same problem in a Unity project (I think that Unity is using mono 1.2.5): ** (process:186): WARNING **: _wapi_connect: Need to translate 64 [Host is down] into winsock error Get this a lot, is there a sollution or workaround? Is it a mono-version 1.2.5 issue? /Patrik -- View this message in context: http://www.nabble.com/mono-core-problem-tp7260646p22898412.html Sent from the Mono - General mailing list archive at Nabble.com. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] Deploy mono website on Debian - mono-develop required?
I plan to deploy an asp.net website on mono on Debian. I am uncertain whether I need to install the mono-2.0-devel packages, or just the mono runtime packages. I plan to deploy asp.net source code files, not binaries. (Unless I can get mono 2.4 installed, which is a separate question. With 2.4, I would deploy a pre-compiled version of my website.) My two main questions at this point: 1) Do I need to install mono-2.0-devel if I just plan to run the website on this server? 2) If I don't need to install mono-2.0-devel, specifically what mono package(s) do I need to install. Then, as a tangent: 3) The hosting company I am planning to use only offers Debian Etch (not Lenny). I've read on the "Binaries for other platforms (unsupported)" on this website how to use backports.org to install mono 1.9.1 on Etch. Is there a way, short of compiling from source code, to get mono 2.4 on Etch (again, not for development - just for deploying a website)? -- View this message in context: http://www.nabble.com/Deploy-mono-website-on-Debian---mono-develop-required--tp22896154p22896154.html Sent from the Mono - General mailing list archive at Nabble.com. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] [Kde-bindings] Mono/Kde-binding(qyoto) bug?
Ishwor Gurung wrote: > Hi, > > My setting: > - Qyoto version 4.4.0 > - Mono C# version 2.0.1.0 > > My qyoto widget has a small QTextEdit box to type messages in (which is > invoked when a user presses a button). They are all good and OK (the > user interface bits). [] > The application was terminated by a signal: SIGABRT > /// > > > Different bug again while running the same application - ^^^ Without change in source/compilation flags. Thought it was worth mentioning. Any help is appreciated. Thanks. -- Cheers, Ishwor Gurung smime.p7s Description: S/MIME Cryptographic Signature ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
[Mono-list] Mono/Kde-binding(qyoto) bug?
Hi, My setting: - Qyoto version 4.4.0 - Mono C# version 2.0.1.0 My qyoto widget has a small QTextEdit box to type messages in (which is invoked when a user presses a button). They are all good and OK (the user interface bits). However, at runtime if I type some text into the QTextEdit and move my mouse towards another window, I get a sigabort with the following output - /// Stacktrace: at (wrapper managed-to-native) Qyoto.SmokeInvocation.CallSmokeMethod (intptr,int,intptr,intptr,int) <0x4> at (wrapper managed-to-native) Qyoto.SmokeInvocation.CallSmokeMethod (intptr,int,intptr,intptr,int) <0x> at Qyoto.SmokeInvocation.Invoke (string,string,System.Type,object[]) [0x00399] in /build/buildd/qt-mono-bindings-4.2.1/csharp/qyoto/src/SmokeInvocation.cs:609 at Qyoto.QApplication.Exec () [0x0] in /build/buildd/qt-mono-bindings-4.2.1/csharp/qyoto/gui/QApplication.cs:278 at Rirc.Rirc.Main (string[]) [0x00013] in /home/ishwor/workspace/csharp/Rirc/Rirc.cs:16 at (wrapper runtime-invoke) Rirc.Rirc.runtime_invoke_void_string[] (object,intptr,intptr,intptr) <0x> Native stacktrace: /usr/bin/mono [0x806d954] /usr/bin/mono [0x80861bb] [0xb7fa6410] /usr/lib/kde4/plugins/styles/oxygen.so [0xb599e7bd] /usr/lib/libQtCore.so.4(_ZN23QCoreApplicationPrivate29sendThroughObjectEventFiltersEP7QObjectP6QEvent+0x9a) [0xb6b8404a] /usr/lib/libQtGui.so.4(_ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent+0x9a) [0xb62758ca] /usr/lib/libQtGui.so.4(_ZN12QApplication6notifyEP7QObjectP6QEvent+0x1196) [0xb627e806] /usr/lib/libsmokeqt.so.2 [0xb6dc5dab] /usr/lib/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0xb1) [0xb6b84e61] /usr/lib/libQtGui.so.4 [0xb62d63de] /usr/lib/libQtGui.so.4 [0xb630cbb0] /usr/lib/libQtGui.so.4 [0xb630ed26] /usr/lib/libQtGui.so.4(_ZN12QApplication15x11ProcessEventEP7_XEvent+0x735) [0xb62e5af5] /usr/lib/libQtGui.so.4 [0xb63107aa] /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x1e8) [0xb7ee7718] /usr/lib/libglib-2.0.so.0 [0xb7eeadc3] /usr/lib/libglib-2.0.so.0(g_main_context_iteration+0x71) [0xb7eeaf81] /usr/lib/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x58) [0xb6baf478] /usr/lib/libQtGui.so.4 [0xb630fea5] /usr/lib/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x4a) [0xb6b8352a] /usr/lib/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0xea) [0xb6b836ea] /usr/lib/libQtCore.so.4(_ZN16QCoreApplication4execEv+0xb5) [0xb6b85da5] /usr/lib/libQtGui.so.4(_ZN12QApplication4execEv+0x27) [0xb6275767] /usr/lib/libsmokeqt.so.2 [0xb6dbfafa] /usr/lib/libqyotoshared.so.1(_ZN5Qyoto10MethodCall10callMethodEv+0x17b) [0xb704705b] /usr/lib/libqyotoshared.so.1(_ZN5Qyoto10MethodCall4nextEv+0x74) [0xb7047474] /usr/lib/cli/kdebindings-4.4/libqyoto.so(CallSmokeMethod+0x81) [0xb709a261] [0xb708b9f5] [0xb792a432] [0xb59dbd47] [0xb791e27a] [0xb791e1b3] /usr/bin/mono(mono_runtime_exec_main+0xe5) [0x80d3695] /usr/bin/mono(mono_runtime_run_main+0x16b) [0x80d3e0b] /usr/bin/mono(mono_main+0x1737) [0x805c927] /usr/bin/mono [0x805ac62] /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7d19685] /usr/bin/mono [0x805aba1] Debug info from gdb: (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb7cd76d0 (LWP 31404)] [New Thread 0xb7527b90 (LWP 31411)] [New Thread 0xb791db90 (LWP 31406)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no deb
[Mono-list] Q: MONO on Linux - MONO_THREADS_PER_CPU
Dear all, i would need some clarification on MONO on Linux - MONO_THREADS_PER_CPU . I am involved with http://opensimulator.org , and we have a regularly reorcuring discussion about the MONO_THREADS_PER_CPU . I did read http://www.mono-project.com/ThreadPool_DeadLocks and it reads, like this is an very old issue. since 3D world can have a big span of resource usage (count of prim, textures, scripts, avatars in a instance) and opensim itself is in steady development, it is sometimes not easy to track down the limiting issues for scaling. the opensim user use MONO 1.2 , 2.0.1 (mostly, i would say), 2.2 and 2.4. It is sugeestet to use 2.x . We see a little bit more stable operations and higher capacity on .Net 3.x . --> is MONO_THREADS_PER_CPU still an issue in 2.0.1 /2.2 / 2.4 ? --> is this likely to be fixed in a next version ? --> is there any guidance to calculate the actual numer to set, based on hardware and target capacity ? any help and further information may be helpfull, as opensim attracts more and more user - so higher loads get´s more likely. Many user are close to opensource and prefer Linux. So - information from MONO archcitects and dev´s maybe helpfull, as well as from linux admins who have expirience with that topic. cheers, Ralf - --- opensouce 3D magazine - http://www.maxping.org german opensim howto - http://www.ralf-haifisch.biz/Opensim%20HowTo.shtml Linked in - http://www.linkedin.com/in/ralfhuelsmann osgrid location - Sharkland Tropical 1 -- View this message in context: http://www.nabble.com/Q%3A--MONO-on-LinuxMONO_THREADS_PER_CPU-tp22892502p22892502.html Sent from the Mono - General mailing list archive at Nabble.com. ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
Re: [Mono-list] FileSystemWatcher on Linux to monitor a remote NTFS share
colinjones wrote: > I don't think there is any point trying to mount the remote share, or > anything like that because the FileSystemWatcher class needs to parse the > UNC path to get the remote machine name so that it can connect to the same > functionality on the remote machine using COM communications. Linux does not support UNC paths, nor Mono does. And CIFS does not need COM :). You have to mount the Windows share with OS' machinery (smbmount). Then you can use the share like a local path. Robert ___ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
