diff options
author | Linus Torvalds <torvalds@ppc970.osdl.org> | 2005-04-17 02:20:36 +0400 |
---|---|---|
committer | Linus Torvalds <torvalds@ppc970.osdl.org> | 2005-04-17 02:20:36 +0400 |
commit | 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 (patch) | |
tree | 0bba044c4ce775e45a88a51686b5d9f90697ea9d /Documentation/mono.txt | |
download | linux-1da177e4c3f41524e886b7f1b8a0c1fc7321cac2.tar.xz |
Linux-2.6.12-rc2v2.6.12-rc2
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.
Let it rip!
Diffstat (limited to 'Documentation/mono.txt')
-rw-r--r-- | Documentation/mono.txt | 66 |
1 files changed, 66 insertions, 0 deletions
diff --git a/Documentation/mono.txt b/Documentation/mono.txt new file mode 100644 index 000000000000..6739ab9615ef --- /dev/null +++ b/Documentation/mono.txt @@ -0,0 +1,66 @@ + Mono(tm) Binary Kernel Support for Linux + ----------------------------------------- + +To configure Linux to automatically execute Mono-based .NET binaries +(in the form of .exe files) without the need to use the mono CLR +wrapper, you can use the BINFMT_MISC kernel support. + +This will allow you to execute Mono-based .NET binaries just like any +other program after you have done the following: + +1) You MUST FIRST install the Mono CLR support, either by downloading + a binary package, a source tarball or by installing from CVS. Binary + packages for several distributions can be found at: + + http://go-mono.com/download.html + + Instructions for compiling Mono can be found at: + + http://www.go-mono.com/compiling.html + + Once the Mono CLR support has been installed, just check that + /usr/bin/mono (which could be located elsewhere, for example + /usr/local/bin/mono) is working. + +2) You have to compile BINFMT_MISC either as a module or into + the kernel (CONFIG_BINFMT_MISC) and set it up properly. + If you choose to compile it as a module, you will have + to insert it manually with modprobe/insmod, as kmod + can not be easily supported with binfmt_misc. + Read the file 'binfmt_misc.txt' in this directory to know + more about the configuration process. + +3) Add the following enries to /etc/rc.local or similar script + to be run at system startup: + +# Insert BINFMT_MISC module into the kernel +if [ ! -e /proc/sys/fs/binfmt_misc/register ]; then + /sbin/modprobe binfmt_misc + # Some distributions, like Fedora Core, perform + # the following command automatically when the + # binfmt_misc module is loaded into the kernel. + # Thus, it is possible that the following line + # is not needed at all. Look at /etc/modprobe.conf + # to check whether this is applicable or not. + mount -t binfmt_misc none /proc/sys/fs/binfmt_misc +fi + +# Register support for .NET CLR binaries +if [ -e /proc/sys/fs/binfmt_misc/register ]; then + # Replace /usr/bin/mono with the correct pathname to + # the Mono CLR runtime (usually /usr/local/bin/mono + # when compiling from sources or CVS). + echo ':CLR:M::MZ::/usr/bin/mono:' > /proc/sys/fs/binfmt_misc/register +else + echo "No binfmt_misc support" + exit 1 +fi + +4) Check that .exe binaries can be ran without the need of a + wrapper script, simply by launching the .exe file directly + from a command prompt, for example: + + /usr/bin/xsd.exe + + NOTE: If this fails with a permission denied error, check + that the .exe file has execute permissions. |