[Klug-general] Now here's a funny thing.

[Michael E. Rentell]

Many thanks for that Dan. I think I have a clearer idea of what is going 
on now.

I tried the advice in that web reference but when (as root) I typed 
modprobe binfmt I got a 'FATAL: module binfmt not found' so I'm back to 
being baffled.

But as I can run what Paul Hudson's Coding Academy book produces by 
typing mono filename.exe (and that works) then I will be OK.

Nothing is ever easy is it?

MikeR

On 02/03/10 15:35, Daniel Ellis wrote:
> On Linux a .NET application is not loaded directly by OS.  Think of a 
> .NET application just like java.  But instead of using java to load a 
> .jar file, you use mono to load the .exe file.
>
> If the OS knows about the content of an exe it can automatically pass 
> it to mono.  See this link to configure Linux to detect a .NET exe and 
> start it automatically:-
>
> http://www.mono-project.com/Guide:Running_Mono_Applications#Registering_.exe_as_non-native_binaries_.28Linux_only.29
>
> Regards,
> Dan Ellis
>
> On 2 March 2010 15:12, Michael E. Rentell 
> <michael.rentell at ntlworld.com <mailto:michael.rentell at ntlworld.com>> 
> wrote:
>
>     Well that's the first thing that went through my mind and I've
>     done the second suggestion in konqueror and it didn't work so I've
>     then done the first suggestion in a konsole and that doesn't work
>     either. The properties of the file still show me as the user with
>     read/write permissions and the execute box is ticked. In a konsole
>     it shows up as  - rws rwx r-x 1
>
>     When I try to run it with ./filename.exe it says 'cannot execute
>     binary file'
>
>     Something funny going on here. Is there any particularly mono
>     dependency I should have to execute a .exe file? Never seen that
>     in Linux before, I always thought .exe was strictly something from
>     the realm of the Boy God.
>     MikeR
>
>
>
>     On 02/03/10 14:20, Dan Attwood wrote:
>>     try 'su chmod +x filename.exe'
>>
>>     that will make the file executable and should let you run it
>>
>>     the other way if just to find the file in nautilus of the kde
>>     file manager right click and select permissions - you can tick on
>>     the execute box there
>>
>>     On 2 March 2010 14:17, Michael E. Rentell
>>     <michael.rentell at ntlworld.com
>>     <mailto:michael.rentell at ntlworld.com>> wrote:
>>
>>
>>         On 02/03/10 13:24, Kevin Groves wrote:
>>         > I think the * is high lighting by the command line shell
>>         you are using.
>>         > Check the perms on the file.
>>         >
>>         > Kev,
>>         >
>>         >
>>         > _______________________________________________
>>         > Kent mailing list
>>         > Kent at mailman.lug.org.uk <mailto:Kent at mailman.lug.org.uk>
>>         > https://mailman.lug.org.uk/mailman/listinfo/kent
>>         >
>>         Ah, I never thought of that. Don't use the cli much so not
>>         sure how to
>>         identify which shell I'm using.
>>
>>         I typed 'shell' into the PCLOS konsole and it returned 'bash'
>>         which I
>>         recognise although the system also said it didn't recognise
>>         the command.
>>
>>         I did the same with the ubuntu under VirtualBox and it
>>         hesitated for a
>>         few seconds and suggested I'd made a mistake and offered a
>>         few choices.
>>         But it didn't identify the shell.
>>
>>         I'm sure it is all very easy - if you just know. But I don't.
>>
>>         Some pointers about tinkering with perms would also help.
>>
>>         MikeR
>>
>>         _______________________________________________
>>         Kent mailing list
>>         Kent at mailman.lug.org.uk <mailto:Kent at mailman.lug.org.uk>
>>         https://mailman.lug.org.uk/mailman/listinfo/kent
>>
>>
>
>
>     _______________________________________________
>     Kent mailing list
>     Kent at mailman.lug.org.uk <mailto:Kent at mailman.lug.org.uk>
>     https://mailman.lug.org.uk/mailman/listinfo/kent
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.lug.org.uk/pipermail/kent/attachments/20100303/5f5d9246/attachment.htm