OpenSimulator - User contributions [en]

User:MoHax

2010-11-11T06:47:20Z

MoHax:

Former contributor no longer active in project.

User:MoHax

2010-11-11T06:44:33Z

MoHax: Removing all content from page

User Documentation

2008-12-19T17:13:24Z

MoHax: /* Blogs about OpenSim */

{{Template:Quicklinks}}
__NOTOC__
==Initial Setup==
* [[Download]] - Download instructions
* [[Dependencies]] - The other packages you need to install that OpenSim relies upon
* [[Build Instructions]] - How to build and compile OpenSim from Source
* [[Configuration]] - How to configure your OpenSim server up and running
* [[Upgrading]] - How to upgrade your OpenSim version so that you can use your existing data
* [[Hypergrid]] - Information about how to configure the experimental hypergrid architecture
* [[Connecting]] - How to connect a compatible viewer to OpenSim
* [[Troubleshooting]] - How to trouble shoot your OpenSim installation.
* [[Tips]] - Useful tips from users like you
* [[FAQ]] - Frequently Asked Questions

==Administrator Guide==
* [[Server Commands]] - Commands to control OpenSim
* [[OpenSim Database support]] - Dealing with databases
* [[Logging]] - Logging in OpenSim
* [[Custom Libraries]] - Describes how to add custom content to your OpenSim server
* [[Automating Tasks]] - How to make administrating a walk in the park
* [[Network Settings]] - NAT, Ports, Services and more...
* [[Management]] - All about being an effective administrator/moderator
* [[Performance]] - How to tweak OpenSim's performance
* [[Console-less OpenSim]] - How to run OpenSim without console
* [[GridInfo]] - how to provide information about your grid to smart clients

==Facilities==
* [[OpenSim Archives]] - Loading and saving whole region archives with OpenSim
* [[IRCBridgeModule]] - A core OpenSim module for integrating IRC with a simulator.
* [[ModRex]] - How to setup the RealXtend server module

==Scripting==
* [[Scripting Documentation]] - Everything you need to know about OpenSim scripting
* [[Scripting Library]] - A list of example scripts

==Tutorials==
* [http://chapter-and-metaverse.blogspot.com Chapter & Metaverse] - Full suite of tutorials, tips and tricks, for the Windows user (Windows)
* [[Wiimote]] - How to use a wiimote/nunchuk controller with the Secondlife viewer (Linux)
* [[Cacti]] - Generate Serverstats using the Cacti-Tool and SNMP (Linux)
* [[Linux Gridserver, the ubuntu way]] the quick and dirty way to install opensim under ubuntu (Linux)
* [[OSGrid Region Registration]] - Describes how to link your region into OS-Grid
* [[Hints & Tricks]] - A page for Hints and Tricks
* [[Getting Started with Region Modules]] - The Hello World of OpenSim application development
* [[Building a bot]] - Getting started with bot design using libomv from the client side.

==How to make custom terrains==

* [[Using L3DT]] - How to create custom terrains
* [[Detailed cross-region terrain making]] - A workflow for creating large cross-region custom terrains
* [http://update.multiverse.net/wiki/index.php/About_Terrain How to make a good Terrain (includes 4 programs to use]

==Gforge Projects==
* [[OpenSimSearch]] - Search for your OpenSim
* [[Linux Gridserver]] - Linux Gridserver using the Moo tool
* [[ServerStats]] - RRD/Proc serverstats using the OpenSim module for Berlios Serverstats (Linux)

==Blogs about OpenSim==
* [http://www.adamfrisby.com/blog/2008/08/resources-for-running-your-own-opensim Adam's OpenSim resources blog post] - a list of resources for running OpenSim
* [http://rock-vacirca.blogspot.com Rock Vacirca's Blog] - lots of tutorials, not only on OpenSim, but on MySQL, Hippo, Second Inventory, etc
* [http://justincc.wordpress.com justincc's blog] - A blog with a weekly OpenSim development update and regular articles on various OpenSim topics.
* [http://imohax.com Mo Hax] - posts and videos about OpenSim and Second Life from beginner perspective, focus on content previewing and educational use

==Contribution Policy==
* [[User_Wiki_Conventions|User Wiki Conventions]] - Read this carefully, before adding content to the wiki
[[Category:Users]]
<cleanpage title=hide cats=hide />

User Documentation

2008-12-19T17:10:23Z

MoHax: /* Blogs about OpenSim */

{{Template:Quicklinks}}
__NOTOC__
==Initial Setup==
* [[Download]] - Download instructions
* [[Dependencies]] - The other packages you need to install that OpenSim relies upon
* [[Build Instructions]] - How to build and compile OpenSim from Source
* [[Configuration]] - How to configure your OpenSim server up and running
* [[Upgrading]] - How to upgrade your OpenSim version so that you can use your existing data
* [[Hypergrid]] - Information about how to configure the experimental hypergrid architecture
* [[Connecting]] - How to connect a compatible viewer to OpenSim
* [[Troubleshooting]] - How to trouble shoot your OpenSim installation.
* [[Tips]] - Useful tips from users like you
* [[FAQ]] - Frequently Asked Questions

==Administrator Guide==
* [[Server Commands]] - Commands to control OpenSim
* [[OpenSim Database support]] - Dealing with databases
* [[Logging]] - Logging in OpenSim
* [[Custom Libraries]] - Describes how to add custom content to your OpenSim server
* [[Automating Tasks]] - How to make administrating a walk in the park
* [[Network Settings]] - NAT, Ports, Services and more...
* [[Management]] - All about being an effective administrator/moderator
* [[Performance]] - How to tweak OpenSim's performance
* [[Console-less OpenSim]] - How to run OpenSim without console
* [[GridInfo]] - how to provide information about your grid to smart clients

==Facilities==
* [[OpenSim Archives]] - Loading and saving whole region archives with OpenSim
* [[IRCBridgeModule]] - A core OpenSim module for integrating IRC with a simulator.
* [[ModRex]] - How to setup the RealXtend server module

==Scripting==
* [[Scripting Documentation]] - Everything you need to know about OpenSim scripting
* [[Scripting Library]] - A list of example scripts

==Tutorials==
* [http://chapter-and-metaverse.blogspot.com Chapter & Metaverse] - Full suite of tutorials, tips and tricks, for the Windows user (Windows)
* [[Wiimote]] - How to use a wiimote/nunchuk controller with the Secondlife viewer (Linux)
* [[Cacti]] - Generate Serverstats using the Cacti-Tool and SNMP (Linux)
* [[Linux Gridserver, the ubuntu way]] the quick and dirty way to install opensim under ubuntu (Linux)
* [[OSGrid Region Registration]] - Describes how to link your region into OS-Grid
* [[Hints & Tricks]] - A page for Hints and Tricks
* [[Getting Started with Region Modules]] - The Hello World of OpenSim application development
* [[Building a bot]] - Getting started with bot design using libomv from the client side.

==How to make custom terrains==

* [[Using L3DT]] - How to create custom terrains
* [[Detailed cross-region terrain making]] - A workflow for creating large cross-region custom terrains
* [http://update.multiverse.net/wiki/index.php/About_Terrain How to make a good Terrain (includes 4 programs to use]

==Gforge Projects==
* [[OpenSimSearch]] - Search for your OpenSim
* [[Linux Gridserver]] - Linux Gridserver using the Moo tool
* [[ServerStats]] - RRD/Proc serverstats using the OpenSim module for Berlios Serverstats (Linux)

==Blogs about OpenSim==
* [http://www.adamfrisby.com/blog/2008/08/resources-for-running-your-own-opensim Adam's OpenSim resources blog post] - a list of resources for running OpenSim
* [http://rock-vacirca.blogspot.com Rock Vacirca's Blog] - lots of tutorials, not only on OpenSim, but on MySQL, Hippo, Second Inventory, etc
* [http://justincc.wordpress.com justincc's blog] - A blog with a weekly OpenSim development update and regular articles on various OpenSim topics.
* [http://imohax.com Mo Hax] - posts and video tutorials about OpenSim and Second Life mostly from beginner and content creator perspective, focus on OpenSim for content previewing and educational use

==Contribution Policy==
* [[User_Wiki_Conventions|User Wiki Conventions]] - Read this carefully, before adding content to the wiki
[[Category:Users]]
<cleanpage title=hide cats=hide />

Main Page

2008-11-02T05:07:55Z

MoHax: /* Using OpenSimulator */

{{Template:Quicklinks}}
__NOTOC__
==Welcome to the '''OpenSimulator Wiki'''.==

=== What is OpenSimulator? ===
[[image:Opensim_Wright_Plaza.jpg|250px|thumb|right|Wright Plaza on OSGrid]]

OpenSimulator is a 3D Application Server. It can be used to create a 3D Virtual World (ala [http://www.secondlifegrid.net Second Life(tm)]), and includes facilities for creating custom avatars, chatting with others in the environment, building 3D content in world, and creating complex 3D applications in world. OpenSimulator can also be extended via [[Region_Modules|loadable modules]] or web service interfaces to build more custom 3D Applications. OpenSimulator is released under a [[BSD License]], making it both open source, and commercially friendly to embed in products.

Although OpenSimulator is still considered '''alpha software''', many people are [http://technorati.com/search/opensim?authority=a4&language=en doing exciting things with it].

=== Features ===
Even though OpenSimulator is realatively young software it already has many useful features
* Supports creating 1 or more 256x256 meter Regions, either on a single machine, or linked between multiple machines in grid mode
* Extensive ability to customize you avatar, both with custom clothing, skins, and attached objects
* The ability to create content real time in the environment using in world building tools
* Real time physics simulation built on top of the ODE physics library
* In world application development using a number of different languages, including LSL, C#, and/or Javascript.

=== Using OpenSimulator ===
The fastest way to get started using OpenSimulator is to create an account on [http://osgrid.org OSGrid], then download the [http://opensim-viewer.sourceforge.net/ Hippo Viewer] or [http://secondlife.com/support/downloads.php Linden Lab's Second Life viewer] (amongst others) to connect to OSGrid. This process should take no longer than 10 minutes, and will give you a flavor for what OpenSimulator is like.

You can also easily connect to any one of the many [[Grid_List|public grids]] on the internet.

Or you could run a simple standalone OpenSim on your Windows desktop to create and preview content. [http://blip.tv/file/1421954 Here is an eight-minute video showing how].

=== Running your own OpenSimulator ===
If you are interested in running you own OpenSimulator server, to host your own 3D environments you'll want to check out the following links:
* [[Download|Getting OpenSimulator]]
* [[Build_Instructions|Building OpenSimulator]]
* [[Configuration|Configuring OpenSimulator]]
* [[FAQ|Frequently Asked Questions in Running OpenSimulator]]

=== Participating in the OpenSimulator Community ===
OpenSimulator is an [http://en.wikipedia.org/wiki/Open_source open source] project, and is powered by the community members that devote time and energy to the effort. There are many ways to participate and contribute to the community:
* Participate via [http://en.wikipedia.org/wiki/Internet_Relay_Chat IRC] - [irc://irc.freenode.net/opensim #opensim] (for users) and [irc://irc.freenode.net/opensim-dev #opensim-dev]
* Contribute to this wiki, making the OpenSimulator documentation even better.
* Report Bugs, Submit Patches, or Submit Content contributions via our [http://opensimulator.org/mantis/ mantis bug tracker] (please read our [[Contributions_Policy|Contributions Policy]] prior to submitting patches)
* Create an OpenSimulator related project hosted on the [http://forge.opensimulator.org Forge] or [http://opensimulator.org/wiki/Related_Software elsewhere] on the web. In the forge there are over a dozen registered projects, and it's a great way to further extend the OpenSimulator community.
* Blog about OpenSimulator, and let us know about that blog on [irc://irc.freenode.net/opensim #opensim] so it can be added to [http://planet.opensim.us Planet OpenSim]
* Participate in one of the weekly [[Office Hours]] for OpenSimulator. We currently have weekly office hours for development, wiki work, and testing.

''Pages by Category:'' [[:Category:Users|User's Pages]], [[:Category:Development|Development Pages]], [[:Category:Scripts|Scripts]],[[Special:Recentchanges| Recent Wiki Changes]] 
''Wiki Translations:'' [[OpenSimSpanish | Spanish]], [[OpenSimGerman | German]], [[fr | Francais]], [[OpenSimItalian | Italian]], [[PT| Português]], [http://64.233.179.104/translate_c?hl=ja&langpair=en%7Cja&u=http://opensimulator.org/wiki/Main_Page Japanese]
[[Category:Main]]
[[Category:Getting Started]]
[[Category:Development]]
<cleanpage title=hide cats=hide />

Main Page

2008-11-02T05:06:55Z

MoHax: /* Using OpenSimulator */

{{Template:Quicklinks}}
__NOTOC__
==Welcome to the '''OpenSimulator Wiki'''.==

=== What is OpenSimulator? ===
[[image:Opensim_Wright_Plaza.jpg|250px|thumb|right|Wright Plaza on OSGrid]]

OpenSimulator is a 3D Application Server. It can be used to create a 3D Virtual World (ala [http://www.secondlifegrid.net Second Life(tm)]), and includes facilities for creating custom avatars, chatting with others in the environment, building 3D content in world, and creating complex 3D applications in world. OpenSimulator can also be extended via [[Region_Modules|loadable modules]] or web service interfaces to build more custom 3D Applications. OpenSimulator is released under a [[BSD License]], making it both open source, and commercially friendly to embed in products.

Although OpenSimulator is still considered '''alpha software''', many people are [http://technorati.com/search/opensim?authority=a4&language=en doing exciting things with it].

=== Features ===
Even though OpenSimulator is realatively young software it already has many useful features
* Supports creating 1 or more 256x256 meter Regions, either on a single machine, or linked between multiple machines in grid mode
* Extensive ability to customize you avatar, both with custom clothing, skins, and attached objects
* The ability to create content real time in the environment using in world building tools
* Real time physics simulation built on top of the ODE physics library
* In world application development using a number of different languages, including LSL, C#, and/or Javascript.

=== Using OpenSimulator ===
The fastest way to get started using OpenSimulator is to create an account on [http://osgrid.org OSGrid], then download the [http://opensim-viewer.sourceforge.net/ Hippo Viewer] or [http://secondlife.com/support/downloads.php Linden Lab's Second Life viewer] (amongst others) to connect to OSGrid. This process should take no longer than 10 minutes, and will give you a flavor for what OpenSimulator is like.

You can also easily connect to any one of the many [[Grid_List|public grids]] on the internet.

Or you could run a simple standalone OpenSim on your Windows desktop to create and preview content. [http://blip.tv/file/1421954 Here is an eight and a half video showing how].

=== Running your own OpenSimulator ===
If you are interested in running you own OpenSimulator server, to host your own 3D environments you'll want to check out the following links:
* [[Download|Getting OpenSimulator]]
* [[Build_Instructions|Building OpenSimulator]]
* [[Configuration|Configuring OpenSimulator]]
* [[FAQ|Frequently Asked Questions in Running OpenSimulator]]

=== Participating in the OpenSimulator Community ===
OpenSimulator is an [http://en.wikipedia.org/wiki/Open_source open source] project, and is powered by the community members that devote time and energy to the effort. There are many ways to participate and contribute to the community:
* Participate via [http://en.wikipedia.org/wiki/Internet_Relay_Chat IRC] - [irc://irc.freenode.net/opensim #opensim] (for users) and [irc://irc.freenode.net/opensim-dev #opensim-dev]
* Contribute to this wiki, making the OpenSimulator documentation even better.
* Report Bugs, Submit Patches, or Submit Content contributions via our [http://opensimulator.org/mantis/ mantis bug tracker] (please read our [[Contributions_Policy|Contributions Policy]] prior to submitting patches)
* Create an OpenSimulator related project hosted on the [http://forge.opensimulator.org Forge] or [http://opensimulator.org/wiki/Related_Software elsewhere] on the web. In the forge there are over a dozen registered projects, and it's a great way to further extend the OpenSimulator community.
* Blog about OpenSimulator, and let us know about that blog on [irc://irc.freenode.net/opensim #opensim] so it can be added to [http://planet.opensim.us Planet OpenSim]
* Participate in one of the weekly [[Office Hours]] for OpenSimulator. We currently have weekly office hours for development, wiki work, and testing.

''Pages by Category:'' [[:Category:Users|User's Pages]], [[:Category:Development|Development Pages]], [[:Category:Scripts|Scripts]],[[Special:Recentchanges| Recent Wiki Changes]] 
''Wiki Translations:'' [[OpenSimSpanish | Spanish]], [[OpenSimGerman | German]], [[fr | Francais]], [[OpenSimItalian | Italian]], [[PT| Português]], [http://64.233.179.104/translate_c?hl=ja&langpair=en%7Cja&u=http://opensimulator.org/wiki/Main_Page Japanese]
[[Category:Main]]
[[Category:Getting Started]]
[[Category:Development]]
<cleanpage title=hide cats=hide />

Download

2008-11-01T23:47:33Z

MoHax: /* Source code */

{{Template:Quicklinks}}
==Source code==
Here are the current released versions of OpenSim.

'''Please note:''' As OpenSim is still at an alpha code maturity stage, there is absolutely no guarantee that functionality works or is stable, even in the numbered releases. Certain features may not work either because the code is in rapid evolution, or because functionality expected by the Linden Labs Second Life viewer has simply not been implemented yet. However, constructive feedback is still welcomed.

Also, please be aware that OpenSim requires that you have a fair amount of technical knowledge in order to set it up - there is no point and click installer (and having one would probably be premature at this stage).

You may need to use the Subversion source code management system to obtain the code. For Windows you can install just [http://subversion.tigris.org/servlets/NewsItemView?newsItemID=1941 Subversion] or the often preferred [http://tortoisesvn.tigris.org Tortoise Subversion extension]. Mac OS X 10.l5 and above have Subversion built but OS. X 10.4.x can still [http://homepage.mac.com/martinott/Subversion-1.4.4.pkg.zip download Subversion].

Another option for obtaining the code is via [http://www.selenic.com/mercurial/wiki/ mercurial] from the [http://opensimulator.org/hg/opensim-trunk/ OpenSim repository].

* '''Latest Subversion revision version (bleeding edge)'''
svn co http://opensimulator.org/svn/opensim/trunk opensim

* '''Latest mercurial revision version (bleeding edge)'''
hg clone http://opensimulator.org/hg/opensim-trunk/ opensim

==Binaries==
'''Please Note:''' Binary releases not hosted by opensimulator.org are unofficial - they are not endorsed by the core OpenSimulator development team and so we cannot guarantee their authenticity. If you use them, please don't necessarily expect support from the community, especially if they are older versions than the current version. At this stage in our development, it is often be the case that many hundreds of revisions have occurred and a number of issues have been fixed since the binaries were released. Currently, the preferred (and recommended) method to get a working system is to build OpenSimulator from source.

* '''Official Nightly Build Binary (Recommended for quick testing)
http://builds.opensimulator.org

* '''Official Build (0.5.11)
http://osgrid.org/download/osgrid.opensim.v0.5.11.6676.zip

* '''Official DGP Build (0.5.11)
http://built-dgpgrid-org.s3.amazonaws.com/6814.zip

==Addons==
'''Openlibrary release v0.53''' (Oct 11) is a collection of Texures, Skins, Clothing etc Assets & Inventory Items common to all users when installed to your OpenSimulator Release. This library is provided under Creative Commons 2.5 by Attribution License courtesy of Openlifegrid.com. After install all users will see these items & assets in the Libraries->Openlibrary root folder.
* [http://openlifegrid.com/Downloads/tabid/67/Default.aspx Openlifegrid.com Downloads] (1 time registration required) contributions to the library are welcome.

To Use Replace your existing Assets & Inventory Library with the Assets & Inventory Folders contained in the downloaded .zip file.
*** PLEASE DO NOT ASK THE OPENSIMULATOR TEAM FOR SUPPPORT ABOUT THESE ADD-ON PACKAGES

''Pages by Category:''[[:Category:Users| User-pages]],[[:Category:Development| Developer-pages]],[[:Category:Scripts| Scripts]] 

[[Category:Users]]
[[Category:Developers]]
<cleanpage title=hide cats=hide />

Build Instructions

2008-11-01T15:26:29Z

MoHax: /* Ubuntu 8.04 / 8.10 */

[[Category:Users]]
This page covers building OpenSim from source code on multiple platforms. Please help us keep this page up to date as the project progresses.

==Download from SVN==
Check out the [[Download]] Section

==MS Windows==

OpenSim requires either the .Net framework version 2.0, or the latest Mono. It supports the following compilers:
* [http://msdn2.microsoft.com/en-us/express/aa700756.aspx Microsoft Visual C# Express Edition] (note: not Visual C++)
* [http://www.mono-project.com/ mono]

Note for people who just downloaded the sources from http://dist.opensimulator.org/ (the "Downloads" link on the left) be advised that some important things are missing (like MySQL template scripts). For such features, you must download using svn!

Additional note: any Microsoft C# Express edition should work (2005 or 2008)

=== Building ===

* In the top-level directory, run the '<tt>runprebuild.bat</tt>' file. This will create both a VS2005 solution file, and a nant build file.
* Open the resulting sln file with visual studio, and build it there, or if you prefer to use nant, run nant in the same top-level directory. This will build the executables.

If you don't care about physics (walking on prims, etc), ignore the rest of this section.

=== Running ===

Recent versions of OpenSim come without an <tt>OpenSim.ini</tt> file. Copy the <tt>OpenSim.ini.example</tt> file to <tt>OpenSim.ini</tt> before making any changes.

Double-click on the <tt>OpenSim.exe</tt> executable file in the <tt>bin</tt> directory. This will start up OpenSim in standalone mode.

The debugger in VS2005 C# may be used to step through the code. For those that use a Cygwin shell, you may find that one or more dll's have permissions that cause problems running. Most find that a "<tt>chmod 777 *</tt>" from the <tt>bin</tt> directory solves this.

Physics can be invoked by adding the appropriate line to the [Startup] section of <tt>OpenSim.ini</tt>. For ODE, that would be:

physics = OpenDynamicsEngine

You can also add a command line option to a shortcut, or run from a command prompt with:

-physics=OpenDynamicsEngine

'''''Windows Vista'''''

To run on Windows Vista, you must first disable Windows Firewall. Under the new "Start" button of Vista, select "Control panel". Then double-click "Windows Firewall". In the window that pops up, on the left column, select "Turn Windows Firewall on or off". You will have to give permission for this to run, then select the option "Off (not recommended)". Click "OK" and exit from the Windows Firewall window.

If you have McAfee SecurityCenter, see the description below.

Once all the security features are disabled, right click on <tt>OpenSim.exe</tt> and select "Run as administrator". This will pop up a window asking permission, select "Allow". Your OpenSim server should run in a DOS-like window and accept connections.

'''''McAfee Security'''''

McAfee Security does not allow applications to listen on ports not explicitly specified. You have two options: 1) disable firewall protection all together, 2) enable <tt>OpenSim.exe</tt> to be able to open ports.

''Disable firewall''

Open McAfee SecurityCenter. Select "Internet & Network". In the lower left corner is a small link to "Configure...". Select this. In the right side of the window, select the bar that says "Firewall protection is enabled". Here you can select "Off".

''Enable <tt>OpenSim.exe</tt> to open ports''

Open McAfee SecurityCenter. Select "Internet & Network". In the lower left corner is a small link to "Configure...". Select this. In the right side of the window, select the bar that says "Firewall protection is enabled". Select the "Advanced..." button. This will pop up a new window.

In the new window, on the left side, select "Program Permissions." In the middle on the right side of the window, select the "Add Allowed Program" button. Use the browser that pops up to find the OpenSim executable and select it.

Finally, select "OK" and exit the McAfee SecurityCenter window.

==Linux/Mac OS X/FreeBSD==

The easiest plaform to get running on the Linux side is Ubuntu 8.04, 32bit. This is what most of the developers running Linux use. If you are looking for the quick path, start there.

=== Ubuntu 8.04 / 8.10 ===

For Ubuntu 7.10 users '''you need''' to upgrade your mono to 1.9.1.

You can use the built in packages for mono. However, for better performance, you may want to [http://xyzzyxyzzy.net/2008/05/08/updated-mono-build-script-for-hardy-heron-and-mono-191/ upgrade mono to 1.9.1] ([http://tempvariable.blogspot.com/2008/04/installing-mono-191-on-ubuntu-804-hardy.html Other simple method])

sudo apt-get install subversion nant mono-gmcs libmono-microsoft8.0-cil \
libmono-system-runtime2.0-cil libgdiplus libmono-i18n2.0-cil ruby
svn co http://opensimulator.org/svn/opensim/trunk opensim
cd opensim
./runprebuild.sh
nant

=== openSUSE 10.3 and 11 ===

Install an openSUSE 11 or 10.3 with its default options, add the online repositories
when finished installing do an online update with all the latest packages.

In yast install these packages, for running Opensim in standalone mode.
(there is a slight diffrence between 10.3 and 11 but following should be same)
subversion
nant
mono-jscript
- check that mono-core is installed

If you just want to use SQLite then jump to last section
within this post.

* Optional mysql - for Opensim running in Grid mode:
Install these mysql packages via yast
mysql
mysql-client
mysql-administrator
mysql-gui-tools
mysql-query-browser

Before building create the mysql database.
/etc/init.d/mysql start
mysql -u root -p -h localhost
(when asked for password just hit enter)

mysql> create database opensim;
mysql> quit

set the configuration in bin/mysql_connection.ini
Or on later builds set the connection string inside bin/OpenSim.ini

Build after installation of above in bash terminal. i save it in /opt

su -
cd /opt
svn co http://opensimulator.org/svn/opensim/trunk opensim
cd opensim
./runprebuild.sh
nant

After this you should be able to continue on starting the diffrent Servers, look in the mysql-config section,or
just run your OpenSim as a Standalone. By - eagleFX

=== Mac OS X 10.5/10.4 ===
* OpenSim is now working on PowerPC Macs! Thanks to DrScofield and those who helped him. Current nightly builds for PowerPC are not working, not sure about Intel so use the 0.5 Build. OpenSim works on Intel Macs. I'm testing on PowerBook G4. Tested these step on 10.5, but not 10.4 but should work --[[User:Mokele|Mokele]] 22:36, 14 February 2008 (PST)
* Install XCode Developers Tools from DVD/CD Installation Disk or download from http://developer.apple.com/. You have to create an Apple account to access the downloads if you don't have an Apple account.
* Install X11 for 10.4 from the Optional Install from the DVD/CD Installation Disk. X11 for 10.5 is installed by default.
* Install Mono 1.2.5 from http://ftp.novell.com/pub/mono/archive/1.2.5/macos-10-universal/5/MonoFramework-1.2.5_5.macos10.novell.universal.dmg and in Terminal or X11 edit the .profile file and add the following line:
export PKG_CONFIG_PATH="/Library/Frameworks/Mono.framework/Versions/Current/lib/pkgconfig/:${PKG_CONFIG_PATH}"
* Compile OpenSim
svn co http://opensimulator.org/svn/opensim/tags/0.5.0-release opensim
cd opensim
./runprebuild.sh
nant

* Download and Compile libopenjpeg-libsl-2.1.2.0.dylib and libsecondlife.dll
* libopenjpeg-libsl-2.1.2.0.dylib:
svn co http://opensimulator.org/svn/opensim-libs/libsl1550 opensim-libs
cd opensim-libs/openjpeg-libsl
make -f Makefile.osx
cp libopenjpeg-libsl-2.1.2.0.dylib ../../opensim/bin
* Note: The Makefile that creates the libopenjpeg-libsl-2.1.2.0.so does not compile on PowerPC, but works properly on Intel Macs. Looks like a gcc issue with compile options.

* libsecondlife.dll: (for PowerPC Only, see details on this step [http://xyzzyxyzzy.net/2008/02/12/installing-opensim-on-powerpcor-of-eggs-and-virtual-worlds installing OpenSim on PowerPC…or: of eggs and virtual worlds])
cd .. (back into opensim-libs)
nant
cp bin/libsecondlife.dll ../opensim/bin

* Edit the libsecondlife.dll.config (PowerPC Only). Remove the cpu="x86" tag in the last dllmap line.

=== FreeBSD 6.2 ===
su
cd /usr/ports/devel/subversion/ && make install clean (you may also need to rebuild apr-svn if this step fails)
cd /usr/ports/lang/mono/ && make install clean
cd /usr/ports/devel/nant/ && make install clean
cd /usr/ports/databases/sqlite3/ && make install clean
cd /usr/ports/x11-toolkits/libgdiplus/ && make install clean
cd /opensim/installation/directory/
svn co http://opensimulator.org/svn/opensim/trunk opensim
cd opensim
./runprebuild.sh
nant

Note: [http://opensimulator.org/wiki/OpenSim:FAQ#System.DllNotFoundException:_..2Flibopenjpeg-libsl-2.1.2.0.so|Follow the instructions on the FAQ to fix the]
"System.DllNotFoundException: ./libopenjpeg-libsl-2.1.2.0.so" issue, but use "gmake" instead of "make"

For ODE Physics you must do the following:
cd /usr/ports/graphics/libGL/ && make install clean
cd /usr/ports/graphics/libGLU/ && make install clean
cd /opensim/installation/directory/
svn co http://opensimulator.org/svn/opensim-libs/trunk opensim-libs
cd opensim-libs/unmanaged/OpenDynamicsEngine2/
sh autogen.sh
./configure --enable-shared --enable-release --disable-demos
make
mv ./ode/src/libode.so /opensim/installation/directory/opensim/bin/

=== RedHat Enterprise Linux 4 ===
sudo vi /etc/yum.repos.d/mono.repo

[mono]
name=Mono for rhel-4-i386 (stable)
baseurl=http://ftp.novell.com/pub/mono/download-stable/rhel-4-i386/
enabled=1
gpgcheck=0

sudo yum install mono-complete monodoc-core nant
svn co svn co http://opensimulator.org/svn/opensim/trunk opensim
cd opensim
./runprebuild.sh
nant

=== Fedora 5 ===
* I needed to build latest mono and nant from sources to build OpenSim successfully, the ones available in yum repository didn't work so I had to uninstall and build and configure the packages.

For detailed instructions go [http://ruakuu.blogspot.com/2008/06/installing-and-configuring-opensim-on.html here]

=== Debian 4 ===

The following packages and their dependencies are required to run OpenSim on a default Debian 4 netinstall:
* mono
* libmono-corlib2.0-cil
* libmono-sqlite2.0-cil
* libmono-system-web2.0-cil
* libmono-microsoft8.0-cil
* libmono-system-runtime2.0-cil

=== 64bit ===
Please note that only 32bit binaries are provided in the bin/ directory of subversion. If you want to use 64bit, you'll need to rebuild these shared objects. See [[Installing and running on x86-64]]

=== Physics (Open Dynamics Engine ODE) ===
As installed from svn, ODE will work on most 32 bit platforms. If you get an ODE-related crash, and/or a libode.so not found type of error, you will need to build libode from source.

Remove <tt>libode.so</tt> from the <tt>./bin</tt> folder. (Note that subsequent svn updates may replace it again; best fix is to copy your built <tt>libode.so</tt> to <tt>bin</tt>). Do NOT remove <tt>ode.net.dll</tt>! Download the latest source from:

svn co http://opensimulator.org/svn/opensim-libs/trunk/unmanaged/OpenDynamicsEngine2

OpenSim requires a couple of patches on top of ODE which are not yet included upstream. When compiling, make sure to use the following configure options:

--with-trimesh=gimpact
--enable-shared

Make sure the configure script confirms these choices, and always compile with single precision (I believe that's the default). Try <code> make -k </code> if you get errors relating to drawstuff, test*, or openGL. <code> make install </code> should put <tt>libode.so</tt> in the proper place (usually <tt>/usr/local/lib</tt>), and it should be seen by opensim (<tt>ode.net.dll</tt>)

===Running===
Recent versions of OpenSim come without an <tt>OpenSim.ini</tt> file. Copy the <tt>OpenSim.ini.example</tt> file to <tt>OpenSim.ini</tt> before making any changes.
cd bin
mono OpenSim.exe

* To invoke ODE, add the option:
-physics=OpenDynamicsEngine
to the <tt>mono OpenSim.exe</tt> line

or add <code> physics = OpenDynamicsEngine </code> to the [Startup] section of <tt>OpenSim.ini</tt>. Same deal for other physics engines, when available.

On mono 1.2.6, some distributions may see
Unhandled Exception: System.NotSupportedException: CodePage 1252 not supported
on startup when using mysql. This can be resolved by installing the package libmono-i18n2.0-cil (see http://bugs.mysql.com/bug.php?id=33938).

=== Additional Items ===

* [[GC_NO_EXPLICIT|GC NO EXPLICIT]] - Enable Large Heap in Mono, this has been known to help performance and stability

[[Category:Users]]

REST

2008-10-10T03:51:29Z

MoHax: /* RestInventoryServices */

The following is taken from Alan M Webb's ''OpenSim REST Support'' Draft document dated 8/18/08. The information here and specification are works in progress but provide the basis for useful OpenSim integrations including content input and retrieval without direct DB access. --[[User:MoHax|MoHax]] 00:10, 10 October 2008 (UTC)

There are a number of REST interfaces1 implemented within OpenSim. This document describes the work done to support specific interactions required in support of external application integration. XML is used to encode the payloads associated with these requests. The specific XML used is documented as an appendix, this is an interim specification.

== What is REST? ==

The notion of Representational State Transfer (REST) was introduced by Roy Fielding in his doctoral dissertation in 2000. It is essentially an architectural concept rather than a protocol, and this has led to a variety of implementations, all of which might claim to be compliant REST implementations.

A REST interface is built upon the HTTP protocol, making use of the four principle methods defined therein: GET, PUT, POST, and DELETE. A fifth method HEAD is also supported, but that is really just a semantic variation of GET. The TRACE and OPTIONS methods have a less fundamental role. No other protocol is involved.

Note that REST does not specify the nature of the payload either sent or received. The interface associated with this document uses XML meta-data to manage an arbitrary payload. The need for a schema document to give form to this XML will be dealt with as a separate discussion.

Of particular significance is the understood meaning of the methods themselves, which is (and must be) as defined by the HTTP specification:

* '''GET''' retrieves the information identified by the associated URI and returns it to the requester. GET is idempotent. If the URI identifies a process, then it is the output of that process which is returned, and not the source text of that process. GET is conditional when the headers include any of the If headers. GET is partial if a range related header is included. The results of GET may be able to be cached.

* '''HEAD''' is functionally equivalent to GET except that the payload is not included in the response. The result of a HEAD request may be able to be cached.

* '''POST''' requests that the server accept the payload as a new entity, subordinate to the existing entity identified by the URI. POST places requirements upon session capabilities in the server insofar as it requires persistent connection and flow control capabilities.

* '''PUT''' indicates that the payload should be stored on the server under1 the resource named by the URI. If the named resource already exists, then the payload is considered to be a modified version of that resource. If the named resource does not exist, then it should be created by the server.

* '''DELETE''' requests that the server delete the resource identified by the URI.

Other methods (TRACE, OPTIONS, CONNECT) may be supported, but are not fundamental to the principles of REST. Use of these methods also implies specific requirements in terms of how the response codes should be used.

== REST Inventory Support ==

The REST support in OpenSim is separated into a number of functional components, all of which live in the OpenSim/ApplicationPlugins/Rest hierarchy.

# Plug-in management. E.g. RestPlugin.cs and Inventory/RestHandler.cs
# Service management: Inventory/RestHandler.cs
# REST implementation: RequestData.cs, Rest.cs
# Service implementations: Inventory/RestInventoryServices.cs, Inventory/RestAssetServices.cs, etc.

This separation serves a number of purposes:

* it limits the sensitivity of each component to implementation changes in the others
* it simplifies the task of service implementation by “hiding” infrastructure
* it helps make services consistent by sharing a single implementation of REST related tasks

The design intention is that each subdirectory in the REST hierarchy, I.e. Inventory, corresponds to a distinct REST handler assembly consisting of service management and one or more service implementations. The Inventory directory is one example of such an assembly.

=== Configuration Parameters ===

In order for the REST handlers to be loaded and effective, statements must be added to the OpenSim.ini file. OpenSim reads the initialization file during start-up. This file is partitioned into various functional domains, e.g.

<pre>
[Startup]
gridmode = false
physics = basicphysics

[RestPlugins]
enabled = false

[RestHandler]
enabled = false
</pre>

The <tt>RestPlugins</tt> partition affects REST handlers in general and supports the following entries:

<pre>
[RestPlugins]
enabled = true|false || false
god_key = <string> || “”
prefix = <string> || “/admin”
</pre>

Only <tt>enabled=true</tt> is necessary to enable REST processing.

Additionally, REST inventory processing currently requires that the following partition be defined:

<pre>
[RestHandler]
enabled = true|false || false
authenticate = true|false || true
extended-escape = true|false || true
realm = <string> || “OpenSim REST”
dump-asset = true|false || false
dump-line-size = int%8 || 32
path-fill = true|false || false
</pre>

The partition name corresponds to the <tt>ConfigName</tt> value specified in the plug-in subclass, I.e. RestHandler.cs.

Again, only the enabled=true entry must be provided to enable the inventory handler; all other defaults are acceptable for normal operation. The meanings of these values will become apparent in the rest of the document.

When the server starts, the REST handler will publish several messages indicating which configuration values are in effect.

=== Effective URI ===

From a REST perspective, the path component of the URI is viewed as a resource identification, the precise significance of which depends upon the HTTP method being used. There are subtleties here, in some cases a prefix of the path may be viewed as a functional qualification of the authority, with the remainder of the URI being a resource identification within the domain of that authority. In this document, the notion of a service corresponds to the functional qualification mechanism just described.

The <tt>prefix</tt> value in the configuration file is used to construct the server's base prefix for REST services, as illustrated in the description of the inventory services prefix shown below:

<pre>
http://<host>:<port>/admin/inventory
^^^^^
</pre>

In this URI <tt>/admin</tt> is the base prefix, and <tt>/inventory</tt> is a prefix extension that identifies the inventory service handler.

All requests that have an <tt>/admin/inventory</tt> prefix will be passed to the inventory handler. The prefix must be followed by the name of the avatar that owns the inventory in question. For example:

<pre>
http://localhost:9000/admin/inventory/Alan Webb
</pre>

Assuming the GET method, then this will return Alan Webb's inventory catalog, as XML data in the response payload, for example:

<pre>
<Inventory>
<Folder name = “My Inventory” uuid=”11111111-...-111111111111” ....
<Folder name=”Objects” uuid=....
....
</Folder>
</Folder>
</Inventory>
</pre>

In this case <tt>/admin/inventory</tt> identiifes the service, and <tt>/Alan Webb</tt> is the resource specification component of the path.

== Implementation Overview ==

The REST implementation being described is manifest in a subset of the files contained in the <tt>ApplicationPlugins/Rest</tt> file hierarchy. It is logically partitioned into three domains:

* Plugin and configuration management
* REST implementation services
* REST service providers

The objective here being to separate functionality so that the task of the service provider is made as straightforward as possible while ensuring that all services implemented using the interface are consistent in both approach and behavior.

[[Image:RESTOverallDataFlowModel.jpg|center|thumb|400px|Illustration 1: Overall Data Flow Model]]

As shown in Illustration 1: Overall Data Flow Model all requests originate, and are eventually returned to, the OpenSim HTTP server. The handler is isolated from this implementation by the <tt>IHttpAgentHandler</tt> interface and the OSHTTP data-types. After matching, the request is passed to the appropriate handler; this relationship is defined by the <tt>IRest</tt> interface and the <tt>RequestData</tt> data-type.

=== Changes to BaseHttpServer ===

The existing OpenSim HTTP server class was modified to support plug-in modules that conform to the <tt>IHttpAgentHandler</tt> interface. Three new subroutines were added: <tt>AddHttpAgentHandler</tt>, <tt>RemoveHttpAgentHandler</tt>, and <tt>TryHttpAgentHandler</tt>; this is consistent with the way in which existing handlers are managed.

Additionally, the <tt>HandleRequest</tt> method was extended to include support for the <tt>IHttpAgentHandler</tt> interface.

The processing of existing handlers is not affected by the new support.

=== Plugin and Configuration Management ===

<tt>IHttpAgentHandler</tt> describes the interface between OpenSim's base HTTP server and the REST implementation, a plug-in must implement this interface. Any class that exports this interface, and that registers its handlers using the appropriate (not defined by an interface1) methods in the base HTTP server can act as a handler. Note that while the usage described here is intended to support REST, the interface itself is agnostic and may be used as the basis for any HTTP request handler.

<tt>'''RestPlugin.cs'''</tt> provides a basic agent-handling superclass. An implementation of this class represents a handler from the point of view of the base HTTP server. This class implements the <tt>IHttpAgentHandler</tt> interface. A given implementation class need only be differentiated from the others in terms of the agent name it uses when it registers. At present, a duplicate agent (based upon supplied agent name) will not be registered; how such a failure is handled depends upon the implementation class. Aside from the name used, a given handler should be differentiated in terms of the set of request patterns that it will match; overlap is undesirable as the first match will win, and at present the order in which OpenSim loads modules is non-deterministic. The <tt>RestHandler</tt> class in the Inventory sub-directory is an example of an implementation class for ''RestPlugin.cs''.

<tt>'''Inventory/RestHandler.cs'''</tt> implements the plug-in interface described above, and also implements a local model of integrating a set of services within a single handler instance. It does this by scanning the classes included in the assembly for those that implement the <tt>IRest</tt> interface; each such class is then initialized. This provides implementation independence from a development standpoint (adding a new service is as simple as adding a single class) whilst avoiding unnecessary overt modularization in OpenSim. This class also takes care of global configuration and initialization of the basic REST environment, i.e. It sets basic references for the OpenSim communications manager, user services, inventory services, and asset management.

For performance reasons, and as an obligation to the <tt>IHttpAgentHandler</tt> definition, this class also implements the Match function, using pattern information registered by the individual services when they were initialized1.

This class contains no REST specific, or service specific functionality beyond some basic initialization. This class can be used in multiple assemblies without change.

<tt>'''Rest.cs'''</tt> provides both state and functionality in support of the REST implementation. Most of the state is static and constant, a small set of static values are initialized by the <tt>RestHandler</tt> when the plug-in is loaded. This class will only change as the REST implementation evolves and becomes more complete. I''t must not contain any service sensitive elements.'' This class may be sub-classed by a given assembly to provide global additions required by a specific set of services.

<tt>'''RequestData.cs'''</tt> serves as a carrier for the state associated with a request. It may be sub-classed by a given service provider in order to add service specific state and functionality, for example the inventory services currently utilize an XML extension to handle inventory specific payload interpretation and generation.

The remaining classes in the Inventory directory provide different classes of service.

=== Adding A New REST Service To An Existing Handler ===

The process for adding a new service is straightforward. The file <tt>RestTestServices.cs</tt> serves as an example1 of what a new services class must minimally include. Key points to note are:

# Each service class should have an associated value for <tt>qPrefix</tt>. This should be unique for each service, as it represents the relative extension of the URI that will be matched by this service. The value supplied here may be absolute, but this is discouraged. The constructor will automatically update a relative value to reflect the absolute prefix set globally during initialization.
# In the case of test services the constructor loads a set of classes from a sub-directory, each of which represents a specific service implementation. For example, these may be method-related, or based upon other values contained in the supplied URI.
# The services constructor must register itself with the <tt>RestHandler</tt>. It provides three values at registration time: a reference to the service method, the URI prefix that this service will match, and a reference to an <tt>RequestData</tt> allocation method that will return an appropriately sub-classed instance of the <tt>RequestData</tt> class.
# Implementation of the service and allocation methods described above must be provided.

Other methods definitions are simply part of the overall infrastructure and would be unique to a given service implementation.

''Note that a given services class may implement zero or more services, according to its intended function. A class providing shared functionality to other services may be loaded but not register any actual handling methods. Similarly, a single services class could register multiple handling methods.''

== REST Implementation Classes ==

This section provides additional documentation of the state and services provided by <tt>Rest.cs</tt> and <tt>RequestData.cs</tt> files.

=== Rest.cs ===

The eponymous class provides a collection of ''request independent'' services and state definitions. Any functions directly dependent upon the HTTP request and response elements are provided in <tt>RequestData.cs</tt>.

==== State ====

The <tt>Log</tt> declaration provides local access to the <tt>log4net</tt> facility. Though apparently complex it simply resolves to a static, read-only reference that can be used to pass messages to the logging facility.

The value of <tt>DEBUG</tt> reflects whether or not debug messages have been enabled in the OpenSim log. If they have, then <tt>DEBUG</tt> will be enabled, if not, then they will not. Being a static declaration it is anticipated that the JIT compiler will be able to make efficient code generation assumptions. This is only of real significance where some substantial operation is performed solely in support of debugging.

The <tt>Plugin</tt> reference is set by <tt>RestHandler</tt> during initialization. It eliminates the need for a services class to have direct awareness of how it was activated. For example, this reference is used to locate the <tt>AddPathHandler</tt> method needed to register its interface.

The main reference is set by the <tt>RestHandler</tt> during initialization. Its value is a reference to the simulator's base class. It is provided to the plug-in interface and is stored for that reason. It is not currently used except by <tt>RestHandler</tt> to locate the communications manager during initialization.

<tt>Comms</tt> provides a globally accessible reference to the simulator's communications manager. It is initialized by <tt>RestHandler</tt> during initialization and is currently only used by <tt>RestHandler</tt> to locate other, commonly needed, simulator services.

<tt>InventoryServices</tt>, <tt>UserServices</tt>, and <tt>AssetServices</tt> are references to the corresponding simulator service interfaces. This list may grow as common service requirements expand.

<tt>Prefix</tt> is the common URI prefix associated with all handlers within a given assembly. In the case of inventory services it is obtained from the global REST configuration. It is currently /admin. This is a configurable attribute. Typical this should be set to whatever is considered to be the standard prefix for REST services in a given URI, it will be combined with scheme and authority information to construct a valid URL.

<tt>Config</tt> is a saved reference to the configuration file used by this assembly. The configuration partition is identified by the <tt>ConfigName</tt> string supplied by the <tt>RestHandler</tt> implementation. This is currently only used by the <tt>RestHandler</tt>, but it could be used by a service implementation to access attributes unique to the service.

<tt>GodKey</tt> is a string obtained from the configuration file which contains the password for the God user. This user has unfettered access to all administrative functions. This is a temporary mechanism and will eventually be replaced by something more secure. This is a configurable attribute.

<tt>Authenticate</tt> indicates whether or not user authentication is required by this handler. This is a configurable attribute, true by default.

<tt>Secure</tt> indicates whether or not the HTTP session should be secured. Secure sessions are currently not available to OpenSim. This is a configurable attribute, true by default.

<tt>ExtendedEscape</tt> controls whether or not the URI is processed for parsing extensions such as “+” in place of spaces. This is a configurable attribute, true by default.

<tt>DumpAsset</tt> controls whether or not the content of an incoming asset should be dumped to the trace file after decoding has completed. This is only intended to be used when there is some indication of a problem with the decoding process. It may produce a significant amount of trace output depending upon the quantity of asset data being uploaded. This is configurable and is normally false.

<tt>Fill</tt> controls whether or not the server will automatically generate intermediate folder names when handling a POST request; it is not currently considered appropriate for PUT. This is not presently implemented.

<tt>FlushEnabled</tt> indicates that the server will completely flush an inbound data stream before responding. This accommodates clients that can not handle the case where a socket error is generated as a result of an early termination of the inbound data stream (due to an authentication failure for example). This mechanism is vulnerable to DOS attacks and can be selectively enabled/disabled.

<tt>Realm</tt> is a string that may be used to distinguish the authentication realm associated with the handler, in place of the URI prefix. This corresponds directly to the realm token included in the WWW-Authenticate response header. This is a configurable option, and is set to 'OpenSim REST' by default. Clients may use this value to determine if additional authentication is necessary, or to select appropriate cached credentials.

<tt>DumpLineSize</tt> indicates the line length to use for any data dumps (e.g. <tt>DumpAsset</tt>) during runtime. The default is 132. This is a configurable option.

<tt>statusHead</tt> contains the standard HTML header used for reporting request status. Similarly, <tt>statusTail</tt> is used to provide a standard suffix. These are both used by the standard status reporting mechanisms.

<tt>HttpStatusDesc</tt> is an array which, when indexed by an appropriate HTTP status code, will return a corresponding status description.

<tt>CreationDate</tt> (property) provides a single consistent reference for creation data value needed when introducing new items into the inventory.

<tt>MsgId</tt> (property) provides a consistent message prefix for log messages generated by the handler. Although static, the value is thread specific, so it is actually unique per request.

<tt>RequestId</tt> (property) provides a unique, monotonically incrementing request counter for processed requests.

<tt>Encoding</tt> provides a standard encoding reference (UTF8) for all data handled by the handler.

<tt>Version</tt> and <tt>Name</tt> are intended to uniquely identify the REST implementation represented by this particular class. Version information should be updated if any significant changes to the REST interface are implemented. This is not currently exploited, but should be. We should have an extended header that indicates the REST version that the client is expecting, and the Match process should be sensitive to this. In this way we can provide concurrent support for multiple REST versions.

The extensive list of constant values are all held to be self-explanatory and should be used wheresoever the value they represent is required in a service implementation. This ensures consistency between the REST implementation and the REST service implementations.

==== Functions ====

<tt>StringToBase64</tt> provides a standard Base64 encoding mechanism for service implementations.

<tt>Base64ToString</tt> provides a standard Base64 decoding mechanism for service implementations.

<tt>Hex2Int</tt> provides a standard mechanism for converting a hexadecimal string of arbitrary length into an integer.

<tt>Int2hex8</tt> converts an integer into an 8 character hexadecimal number. This is not currently used, and as such should not be trusted.

<tt>NonceGenerator</tt> is a simple nonce producer that ensures uniqueness by simply converting a newly generated UUID into a Base64 string. This function is called each time the user is called upon to authenticate, which is not necessarily that often, provided the client caches credentials based upon realm.

<tt>Dump</tt> provides a general purpose facility for generating an interpreted hexadecimal data dump to the log file. It is currently used by the DumpAsset debug facility. But it may be used by anybody requiring such data dumping services.

=== RequestException ===

This class provides an extended exception that can be distinguished from regular, system generated, exceptions. A <tt>RequestException</tt> does not indicate a programming failure, rather it indicates that the received request could not be validly processed, for example, the URI was invalid. This exception should only be used in those cases where request processing is to be immediately terminated in conjunction with normal response processing. Principally it allows the handler to differentiate between a failure in processing, which should be logged, and a normal response to an invalid request, which should not.

=== RequestData.cs ===

This file, and its eponymous class provides consistent support for request specific REST processing. When the <tt>RestHandler</tt> has successfully matched a handler to a request, the registered allocate method for that service interface is called to allocate an instance of this class either directly, or as a super class of some service specific extension. This description deals only with the base implementation.

With a single instance of a service class per handler, it is necessary to encapsulate request/response specific data in this way. Those functions that operate over that data are included here for convenience and represent part of the previously mentioned REST implementation encapsulation.

==== Members ====

When an instance of this class is created, the constructor always does the following:

# The parameters are not validated. Their validity is considered to be a precondition and as such the natural exception mechanism is an efficient and effective way to deal with invalid argument values.
# The supplied request and response object references are cached, as is the supplied request prefix.
# The effective encoding is obtained from the supplied request if possible, or the Rest default (UTF8) is applied.
# A lower case copy of the request method is stored.
# <tt>InitUrl</tt> is called to decompose the supplied URI into its basic components: query, path, host name, and port.
# <tt>InitParameters</tt> is called to create an array of strings, each of which represents a separated portion of whatever URI remains after the handler's selection prefix is removed. This list may be empty.

In the interests of laziness, constructor processing is kept to a minimum.

The <tt>IsAuthenticated</tt> property checks to see if the user is currently authenticated, and if not, then invokes that authentication mechanism. This allows a service request handler so simply test this boolean and reject the request if the result is false. This is an example of a failure that should not normally be logged, as the client is expected to respond to the challenge with an appropriate set of credentials.

The <tt>PathNodes</tt> property is an array that contains a normalized list of elements in the absolute path provided in the URI. It does not differentiate the elements.

The <tt>Parameters</tt> property is an array that contains only those URI path elements that are not a part of the service selection prefix (i.e. <tt>/admin/inventory</tt>). This simplifies service processing by providing a prefix-independent base for request parameter indeces.

<tt>Complete</tt> allows a service provider to indicate the manner in which a request has completed. Called with no arguments, this corresponds to a status code of 200 indicating a normal completion. In many cases the service provider must necessarily indicate a more specific code. The message associated with this call may be arbitrarily complex, it is used, as-is, as the message body in the response.

<tt>Redirect</tt> allows a service provider to indicate that the requester should be redirected to an alternative URL. Redirection may be permanent or temporary as indicated by the boolean argument.

Variations on <tt>Fail</tt> allow a service to abandon request processing. This call constructs an appropriate HTTP failure response, including any specified message body, generates the response, adds request information to an instance of <tt>RestException</tt> and finally throws the exception. It is important that a service provider allow <tt>RestException</tt> events to pass through transparently, (i.e. re-throw any that are inadvertently trapped).

<tt>Reject</tt> encapsulates whatever processing is appropriate for requests that attempted processing that is not implemented.

<tt>Respond</tt> allows a service provider to generate a response and complete processing with respect to the current HTTP request and response. This call is mandatory for any request that is considered to have been processed successfully.

<tt>AddHeader</tt> allows a service provider to add a header to the set of response headers that will be included when the response is finally generated. The Rest constants should be used when specifying the header name. The header value is treated as an arbitrary string.

<tt>RemoveHeader</tt> allows a service provider to remove a header that was previously added to the response header set.

<tt>DumpHeaders</tt> causes a list of the currently effective headers to be sent to the log. This is a DEBUG option.

== RestInventoryServices ==
This file, and the classes it contains, provide a monolithic implementation of all of the services provided in support of inventory processing. If required, authentication is established before any processing of inventory data. The following abnormal completion codes may be returned:

* 301 indicating that a permanently applicable alternative URI for a specified resource has been provided.
* 400 indicating a bad request. Information about the nature of the request error is included in the status information returned to the client. Currently this is textual, but when a proper schema document for the interface is established, a more quantitative status will be returned.
* 401 indicating that the client must authenticate.
* 409 indicating that an ambiguous or conflicting request was received.

=== Inventory Resource Identification ===

An avatar's inventory is a catalog of the assets 'owned' by the avatar; the inventory contains only of meta-data and depends upon the asset data base for whatever actual data represents the perceived content. References to inventory in this document normally refer to the meta-data rather than the content. An inventory consists of two types of element: ''folders'' and ''items''. In both cases, a given element is uniquely identified by an assigned UUID. An associated name is also provided for human convenience, but such names are not required to be unique and are insufficient to ensure an exact identification. The URI used in inventory related requests allows either UUID or name to specified for each element in a resource identification path, ''if any ambiguity arises then the request will be failed''.

The avatar's inventory can contain a private catalog, and one or more shared, or public, catalogs. Currently only the private catalog is processed. When support for the shared catalogs is introduced it will do so by adding by prefixing any path as follows:

<pre>
/admin/inventory/shared/[<libname>]/
</pre>

This allows all global inventory, or a specific library to be referenced.
For all requests, specifying an avatar name implies the private inventory.
In all cases, if additional path information is provided, then the root directory name may be inferred (but accepted if specified explicitly). So

<pre>
/admin/inventory/Alan Webb/My Inventory/Clothing
</pre>

and

<pre>
/admin/inventory/Alan Webb/Clothing
</pre>

are semantically equivalent. This is a convenient and harmless special case. Where no additional path information is provided, as in

<pre>
/admin/inventory/Alan Webb
</pre>

then the root directory may still be inferred for GET and POST, but can not be allowed for PUT. PUT requires the URI to identify the element that is being updated, so inference in this case could be extremely damaging. Explicit specification of the root inventory name is therefore required for all PUT requests. Given that this is an interface normally used only by programmed clients, the additional verbosity is not expected to be an issue. If this proves to be contentious, then the only viable approach would be to drop the inference altogether.

=== Supported Services ===

==== GET ====

<tt>GET</tt> allows the client to retrieve all, or some sub-tree of, the inventory associated with a specified avatar's inventory. Inventory information is returned in an XML payload. This request is guaranteed not to affect the state of the avatar's inventory. Possible normal completions are:

* 200 indicating normal completion of the request. The payload will contain an XML representation of the avatar's inventory.

==== PUT ====

<tt>PUT</tt> allows a resource, explicitly nominated in the URI, to be created or replaced. I.e. the URI identifies an instance rather than a context. Possible normal completions are

* 200 if the nominated resource was successfully updated
* 201 if the nominated resource was successfully created.
* 204 if no content change (but the resource was recognized and valid)

==== POST ====

<tt>POST</tt> allows a new resource to be created in the context identified by the URI. It follows from this that the resource identified by a POST request should always be a folder. Normal completions are:

* 200 if some portion of the context was modified.
* 201 if the new data was entirely new.

==== DELETE ====

<tt>DELETE</tt> allows a named resource to be deleted. If the resource is a folder, then the entire sub-tree will be removed. Normal completion codes are:

* 200 if the specified resource was deleted.

Both PUT and POST allow any assets upon which the inventory catalog depends, to be included in-line with the XML catalog data.

REST

2008-10-10T03:42:53Z

MoHax: /* Functions */

REST

2008-10-10T03:31:40Z

MoHax: /* REST Implementation Classes */

REST

2008-10-10T03:18:22Z

MoHax: /* Adding A New REST Service To An Existing Handler */

REST

2008-10-10T03:18:05Z

MoHax: /* Adding A New REST Service To An Existing Handler */

REST

2008-10-10T03:14:57Z

MoHax: /* Changes to BaseHttpServer */

REST

2008-10-10T01:01:33Z

MoHax:

REST

2008-10-10T00:57:01Z

MoHax:

{{update}}

The following is taken from Alan M Webb's ''OpenSim REST Support'' Draft document dated 8/18/08. The information here and specification are works in progress but provide the basis for useful OpenSim integrations including content input and retrieval without direct DB access. --[[User:MoHax|MoHax]] 00:10, 10 October 2008 (UTC)

There are a number of REST interfaces1 implemented within OpenSim. This document describes the work done to support specific interactions required in support of external application integration. XML is used to encode the payloads associated with these requests. The specific XML used is documented as an appendix, this is an interim specification.

== What is REST? ==

The notion of Representational State Transfer (REST) was introduced by Roy Fielding in his doctoral dissertation in 2000. It is essentially an architectural concept rather than a protocol, and this has led to a variety of implementations, all of which might claim to be compliant REST implementations.

A REST interface is built upon the HTTP protocol, making use of the four principle methods defined therein: GET, PUT, POST, and DELETE. A fifth method HEAD is also supported, but that is really just a semantic variation of GET. The TRACE and OPTIONS methods have a less fundamental role. No other protocol is involved.

Note that REST does not specify the nature of the payload either sent or received. The interface associated with this document uses XML meta-data to manage an arbitrary payload. The need for a schema document to give form to this XML will be dealt with as a separate discussion.

Of particular significance is the understood meaning of the methods themselves, which is (and must be) as defined by the HTTP specification:

* '''GET''' retrieves the information identified by the associated URI and returns it to the requester. GET is idempotent. If the URI identifies a process, then it is the output of that process which is returned, and not the source text of that process. GET is conditional when the headers include any of the If headers. GET is partial if a range related header is included. The results of GET may be able to be cached.

* '''HEAD''' is functionally equivalent to GET except that the payload is not included in the response. The result of a HEAD request may be able to be cached.

* '''POST''' requests that the server accept the payload as a new entity, subordinate to the existing entity identified by the URI. POST places requirements upon session capabilities in the server insofar as it requires persistent connection and flow control capabilities.

* '''PUT''' indicates that the payload should be stored on the server under1 the resource named by the URI. If the named resource already exists, then the payload is considered to be a modified version of that resource. If the named resource does not exist, then it should be created by the server.

* '''DELETE''' requests that the server delete the resource identified by the URI.

Other methods (TRACE, OPTIONS, CONNECT) may be supported, but are not fundamental to the principles of REST. Use of these methods also implies specific requirements in terms of how the response codes should be used.

== REST Inventory Support ==

The REST support in OpenSim is separated into a number of functional components, all of which live in the OpenSim/ApplicationPlugins/Rest hierarchy.

# Plug-in management. E.g. RestPlugin.cs and Inventory/RestHandler.cs
# Service management: Inventory/RestHandler.cs
# REST implementation: RequestData.cs, Rest.cs
# Service implementations: Inventory/RestInventoryServices.cs, Inventory/RestAssetServices.cs, etc.

This separation serves a number of purposes:

* it limits the sensitivity of each component to implementation changes in the others
* it simplifies the task of service implementation by “hiding” infrastructure
* it helps make services consistent by sharing a single implementation of REST related tasks

The design intention is that each subdirectory in the REST hierarchy, I.e. Inventory, corresponds to a distinct REST handler assembly consisting of service management and one or more service implementations. The Inventory directory is one example of such an assembly.

=== Configuration Parameters ===

In order for the REST handlers to be loaded and effective, statements must be added to the OpenSim.ini file. OpenSim reads the initialization file during start-up. This file is partitioned into various functional domains, e.g.

<pre>
[Startup]
gridmode = false
physics = basicphysics

[RestPlugins]
enabled = false

[RestHandler]
enabled = false
</pre>

The <tt>RestPlugins</tt> partition affects REST handlers in general and supports the following entries:

<pre>
[RestPlugins]
enabled = true|false || false
god_key = <string> || “”
prefix = <string> || “/admin”
</pre>

Only <tt>enabled=true</tt> is necessary to enable REST processing.

Additionally, REST inventory processing currently requires that the following partition be defined:

<pre>
[RestHandler]
enabled = true|false || false
authenticate = true|false || true
extended-escape = true|false || true
realm = <string> || “OpenSim REST”
dump-asset = true|false || false
dump-line-size = int%8 || 32
path-fill = true|false || false
</pre>

The partition name corresponds to the <tt>ConfigName</tt> value specified in the plug-in subclass, I.e. RestHandler.cs.

Again, only the enabled=true entry must be provided to enable the inventory handler; all other defaults are acceptable for normal operation. The meanings of these values will become apparent in the rest of the document.

When the server starts, the REST handler will publish several messages indicating which configuration values are in effect.

=== Effective URI ===

From a REST perspective, the path component of the URI is viewed as a resource identification, the precise significance of which depends upon the HTTP method being used. There are subtleties here, in some cases a prefix of the path may be viewed as a functional qualification of the authority, with the remainder of the URI being a resource identification within the domain of that authority. In this document, the notion of a service corresponds to the functional qualification mechanism just described.

The <tt>prefix</tt> value in the configuration file is used to construct the server's base prefix for REST services, as illustrated in the description of the inventory services prefix shown below:

<pre>
http://<host>:<port>/admin/inventory
^^^^^
</pre>

In this URI <tt>/admin</tt> is the base prefix, and <tt>/inventory</tt> is a prefix extension that identifies the inventory service handler.

All requests that have an <tt>/admin/inventory</tt> prefix will be passed to the inventory handler. The prefix must be followed by the name of the avatar that owns the inventory in question. For example:

<pre>
http://localhost:9000/admin/inventory/Alan Webb
</pre>

Assuming the GET method, then this will return Alan Webb's inventory catalog, as XML data in the response payload, for example:

<pre>
<Inventory>
<Folder name = “My Inventory” uuid=”11111111-...-111111111111” ....
<Folder name=”Objects” uuid=....
....
</Folder>
</Folder>
</Inventory>
</pre>

In this case <tt>/admin/inventory</tt> identiifes the service, and <tt>/Alan Webb</tt> is the resource specification component of the path.

== Implementation Overview ==

The REST implementation being described is manifest in a subset of the files contained in the <tt>ApplicationPlugins/Rest</tt> file hierarchy. It is logically partitioned into three domains:

* Plugin and configuration management
* REST implementation services
* REST service providers

The objective here being to separate functionality so that the task of the service provider is made as straightforward as possible while ensuring that all services implemented using the interface are consistent in both approach and behavior.

[[Image:RESTOverallDataFlowModel.jpg|center|thumb|400px|Illustration 1: Overall Data Flow Model]]

As shown in Illustration 1: Overall Data Flow Model all requests originate, and are eventually returned to, the OpenSim HTTP server. The handler is isolated from this implementation by the <tt>IHttpAgentHandler</tt> interface and the OSHTTP data-types. After matching, the request is passed to the appropriate handler; this relationship is defined by the <tt>IRest</tt> interface and the <tt>RequestData</tt> data-type.

=== Changes to BaseHttpServer ===

REST

2008-10-10T00:55:46Z

MoHax: /* Implementation Overview */

File:RESTOverallDataFlowModel.jpg

2008-10-10T00:54:19Z

MoHax:

REST

2008-10-10T00:52:07Z

MoHax: /* Implementation Overview */

REST

2008-10-10T00:49:39Z

MoHax: /* Implementation Overview */

REST

2008-10-10T00:45:38Z

MoHax: /* Effective URI */

REST

2008-10-10T00:44:48Z

MoHax: /* Effective URI */

REST

2008-10-10T00:43:53Z

MoHax: /* Effective URI */

REST

2008-10-10T00:39:08Z

MoHax: /* Configuration Parameters */

REST

2008-10-10T00:37:28Z

MoHax:

Help

2008-10-10T00:30:01Z

MoHax:

The best way to learn about and contribute to the project is to log into our IRC channel, located on irc.freenode.net in [irc://irc.freenode.net/opensim #opensim] (for users) and [irc://irc.freenode.net/opensim-dev #opensim-dev] (for developers).

Perhaps you were looking for [http://www.mediawiki.org/wiki/Help:Formatting#Other_formatting help with MediaWiki formatting].

Help

2008-10-10T00:27:53Z

MoHax:

REST

2008-10-10T00:10:33Z

MoHax:

REST

2008-10-09T23:52:02Z

MoHax:

REST

2008-10-09T23:47:10Z

MoHax: New page: The following is taken from Alan M Webb's OpenSim REST Support Draft document dated 8/18/08. The information here and specification are works in progress but provide the basis for useful O...

The following is taken from Alan M Webb's OpenSim REST Support Draft document dated 8/18/08. The information here and specification are works in progress but provide the basis for useful OpenSim integrations including content input and retrieval without direct DB access.

== What is REST? ==

Configuration

2008-10-07T19:17:36Z

MoHax: /* Standalone vs. Grid */

==OpenSim configuration file==
The simulator configuration is managed using a file called [[OpenSim.ini]]. This file is used regardless of whether the sim is running in standalone or grid mode. Detailed information on the options available for setttings in this file can be found [[OpenSim.ini|here]].

==Database==
Opensim's supports the following database-engines:
* SQLite (default - a lightweight database that comes bundled with OpenSim and can be used without requiring any extra configuration. It is mostly intended to get you up and running quickly, not for production use.)
* MySQL (fully supported)
* MSSQL (partially supported - some recent OpenSim features may not yet be implemented)

More information on database support can be found on the [[OpenSim Database support]] page.

==Script engine==
OpenSim supports multiple script engines. See [[ScriptEngines]] for details

==Standalone vs. Grid==
We recommend that you first get OpenSim running in standalone mode before you attempt to connect it to a grid, either your own grid or a public grid. An OpenSim configuration consists of regions (run by region simulators) and 5 core backend services (which manage users, the grid, assets, inventories, and grid-wide messaging, collectively known as UGAIM).

A system running in '''standalone mode''' (that is, one with OpenSim.ini configured such that gridmode = false) -- also known as "sandbox mode" -- runs everything (all UGAIM services and one or more regions) in a single executable (OpenSim.exe). External regions cannot be added to an OpenSim running in this mode.

In '''grid mode''', the five services ([[User Server|User]], [[Grid Server|Grid]], [[Asset Server|Asset]], [[Inventory Server|Inventory]], [[Messaging Server|Messaging]], or UGAIM) are each started as separate executables. This means that they can be run either on the same machine or spread out across multiple computers. In this mode, OpenSim.exe serves one or more regions, which communicate with the core servers. This mode even allows region servers run by other people on their own machines to connect, if you wish.

Naturally, this means that running in grid mode is somewhat more complicated than running in standalone mode. It requires an understanding of UUID, X,Y location, server handshake passwords, master avatars, and a couple of other settings. These are not difficult, but do require a little more care in setting things up.

If you want to run a grid of your own (either private or public) you would start the core services up before connecting a region simulator. If you want to connect your region server to a grid that someone else is running, you need only start the region server in grid mode (with the necessary security keys and location information mentioned in the last paragraph).

OpenSim.exe responds to various command line arguments. These include "-inifile", "-configfile", "-gridmode", "-physics", "-config" & "-noverbose". When starting OpenSim in either Windows or Linux, one could, for example, add "-physics=OpenDynamicsEngine" to run the OpenDynamicsEngine instead of basicphysics, or use "-gridmode=true" to force opensim.exe to run as a region server (the rest of the grid services have their own executables). As many of these settings are normally controlled by OpenSim.ini, most users (especially in standalone mode) will not add any command line arguments.

===Standalone mode===

When you start OpenSim in standalone mode, it will ask you several questions at the console. The first set of prompts that start with "NETWORK SERVERS INFO", you can just hit return to accept the defaults if you will be running in standalone mode. The prompts that start with "DEFAULT REGION CONFIG" are where you need to start paying attention. Some are self-explanatory. Here are explanations for the others: 
* Grid Location. OpenSim regions can be placed anywhere on a 65536 by 65536 grid. In standalone mode, it is safe to leave these X and Y locations at their defaults for the first region (additional regions will need different coordinates, of course).
* Filename for local storage. Safe to leave at default.
* Internal IP address; This should always be 0.0.0.0 (0.0.0.0 means "listen for connections on any interface", basically a wildcard)
* Internal IP port for incoming UDP client connection. You can make this any port you want, but it is safe to leave at the default 9000.
* External host name. If you will only be attaching to your sim from a SecondLife client on the same machine, you can leave this at the default 127.0.0.1. If you will be wanting to connect to it from a client on another machine, this should be the IP address or hostname of the machine you are running this sim on. N.B - It appears that this must actually be the External Host IP Address, not the Domain Name.
To connect to your new sim, start up secondlife with the following command line switches:
-loginuri http://127.0.0.1:9000/ -loginpage http://127.0.0.1:9000/?method=login
This assumes you are running the secondlife client on the same box. If you are running it on a separate box, substitute the IP address of your sim machine. 
To create a user: 
type ''create user <first> <last> <password> <x_loc> <y_loc>'' in the server console.

===Grid mode===
You want to run your own grid. Great! Assuming that you already got your sim running in standalone mode, here is what you need to do: 
1. Current builds of OpenSim grid mode are using mysql to store the grid information. You must have this installed and configured if you want to run your own grid. See [[mysql-config]] for more information. 
2. Four of the servers should be started in a certain order. UGAI: UserServer, GridServer, AssetServer, InventoryServer. The MessagingServer can be started at any point after the GridServer, and the RegionServer(s) should always come last. These are all found in the bin directory. In windows, you can just double-click on the executables to start them. In Linux and Mac OS X type "mono filename" from a prompt. The executable names, in order, are:
OpenSim.Grid.UserServer.exe
OpenSim.Grid.GridServer.exe
OpenSim.Grid.AssetServer.exe
OpenSim.Grid.InventoryServer.exe
OpenSim.Grid.MessagingServer.exe
OpenSim.exe
3. Start the UserServer. If you will be running the GridServer on the same box, hit enter to accept the defaults, until it gives you the prompt
OpenUser#
This is the main prompt for the user server. If you will be running the GridServer on another box, change the Default Grid Server URI as appropriate. 
4. Start the GridServer. Again, you can hit return at all the prompts if you are running them all on the same machine. If not, change the URIs for the Asset Server and User server to point to where you are running them. You will finally get to the console prompt for the GridServer which looks like this:
OpenGrid#
5. Start the AssetServer. The console prompt for this server will be:
OpenAsset#
6. Start the InventoryServer. The console prompt for this server will be:
INVENTORY#
7. Start the MessagingServer. The console prompt for this is:
Messaging#
8. If you are running all of these servers on the same box, which would be the normal configuration, you should be ready to start up your sim. The mode that OpenSim.exe starts in is normally controlled by a setting in your OpenSim.ini. It defaults to standalone mode if that setting is not specified or the file is not found. If you wish, you can force opensim to start in gridmode on the command line as follows:
OpenSim.exe -gridmode=true
or:
mono OpenSim.exe -gridmode=true
With any luck, everything will come up without too many errors. 
9. Go to the UserServer console, and type 'create user' to create a new avatar. It will prompt you for the name and password, and the X and Y of the sim that should be his home location. Use 1000 and 1000, or wherever you told your sim to live when you brought it up in standalone mode. At the console of any of these servers, you should be able to type 'help' to get a list of commands.

You should now be able to connect to your new grid with your secondlife client. You need to tell your client to point at the UserServer rather than directly at the sim, though:
secondlife -loginuri http://127.0.0.1:8002/
8002 is the default port for the UserServer, and that IP address should be changed to the server you are running the UserServer on, if they are not all on the same box. Happy OpenSimming! 
''Note: if you are using Windows Vista, remember to start servers as Admin. If not it will prompt you an error in console like "Error - Access denied"''

==Multiple regions==

Using Physical Prim with the OpenDynamicsEngine on *nix, it's recommended that you set your stack reserve level higher then default with the following command;
<tt>ulimit -s 262144</tt> Or, run the opensim-ode.sh to start up OpenSimulator.

A powerful region generator is available at: [[RegionGenerator]]

For running multiple regions on the same box, you simply make multiple copies of the 'default.xml' file inside the <tt>bin/Regions/</tt> directory. You can do this using the script <tt>make.php</tt> in <tt>share/regions</tt>, or you can generate the files by hand.

If you want to create the files by hand:

:first copy the default.xml file in the <tt>bin/Regions</tt> directory, and name them anything you want (I name mine region.x.y.xml, where region is the name of the region, and x and y are the grid coords.)
:Open each xml file and edit the uuid (a generator can be found at [http://www.famkruithof.net/uuid/uuidgen uuidgen webpage] or on unix, use the uuidgen command), region name, x & y positions, and internal ip port. IMPORTANT! The UUID, name, and grid coordinates ''must'' be unique for each region on a grid. The port assignment must be unique for each region that is running on a particular machine. 

Note that <tt>sim_location_x</tt> and <tt>sim_location_y</tt> should be adjacent integers if you want your regions to be adjacent, so you can run back and forth between them. '''IMPORTANT: THESE GRID COORDINATES ARE ''NOT'' IN METERS. THEY ARE SIM POSITIONS.''' (1000, 1000) is next to (1001,1000), (1000, 1001), and so forth. 1256, 2000, 2048 and similar values are '''not''' adjacent to 1000, they are very far away, so you would not see your sims from one another.

Once you have 2 or more xml files in the bin/Regions folder, running a ''single'' copy of <tt>OpenSim.exe</tt> will start up all of your sims! If you come across any errors, there is most likely an error in your xml files.

As of 6-Feb-2008, take care NOT to leave editor backup copies of the files in this directory e.g. emacs style backup names like Regionname.xml~. These are loaded by opensim.exe as if they are legitimate region descriptions, and will therefore give errors indicating you are trying to re-use the socket for that region.

==Attaching your sim to someone else's grid==
To set up the region server (i.e., <tt>OpenSim.exe</tt>) to connect to an external grid, you should edit the <tt>OpenSim.ini</tt> file in the <tt>bin</tt> directory. In that file, there is a <tt>[Network]</tt> section with URLs for the grid, user, and asset servers, as well as send and receive keys (for a basic level of security). The addresses and send/receive keys will vary depending on the grid you are connecting to, and the grid operator should tell you what values to use.

The other file you may have to change is in your <tt>bin/Regions</tt> directory. This is where your individual region config files are. If you only have one region, it will by default be called <tt>default.xml</tt>.

This can be edited with any text editor. The grid owner may tell you what X and Y location you can place your sim at (you can't have multiple sims at the same location on the grid). If so, the fields you will need to change in this file are <tt>sim_location_x</tt> and <tt>sim_location_y</tt>. And the <tt>external_host_name</tt> should be set to the hostname or IP address of your simulation server (i.e., the machine that is running <tt>OpenSim.exe</tt>).
A list of public grids that you can attach your sim to is at [[OpenSim: Grids]]

==Running==

===StandAlone===
'''Windows'''
cd bin
OpenSim.exe
On Windows Vista, it may be necessary to explicitly "Run as administrator" for opensim.exe to accept connections from a client, even when running as an administrator user. Navigate to the opensim\bin directory, right click opensim.exe, and select "Run as administrator".
Connect: opensim://localhost:9000 , or opensim://127.0.0.1:9000, or opensim://myipadress:9000

'''Linux'''
cd bin
mono OpenSim.exe

'''OSX'''
cd bin
mono OpenSim.exe

===Local Grid===
'''Windows'''
cd bin
OpenSim.Grid.UserServer.exe
OpenSim.Grid.GridServer.exe
OpenSim.Grid.AssetServer.exe
OpenSim.Grid.InventoryServer.exe
OpenSim.Grid.MessagingServer.exe
OpenSim.exe

'''Linux'''
cd bin
mono OpenSim.Grid.UserServer.exe
mono OpenSim.Grid.GridServer.exe
mono OpenSim.Grid.AssetServer.exe
mono OpenSim.Grid.InventoryServer.exe
mono OpenSim.Grid.MessagingServer.exe
mono OpenSim.exe

'''OSX''''
cd bin
mono OpenSim.Grid.UserServer.exe
mono OpenSim.Grid.GridServer.exe
mono OpenSim.Grid.AssetServer.exe
mono OpenSim.Grid.InventoryServer.exe
mono OpenSim.Grid.MessagingServer.exe
mono OpenSim.exe
Connect: opensim://myipaddress:9000

Configuration

2008-10-07T19:07:43Z

MoHax: /* Standalone vs. Grid */

==OpenSim configuration file==
The simulator configuration is managed using a file called [[OpenSim.ini]]. This file is used regardless of whether the sim is running in standalone or grid mode. Detailed information on the options available for setttings in this file can be found [[OpenSim.ini|here]].

==Database==
Opensim's supports the following database-engines:
* SQLite (default - a lightweight database that comes bundled with OpenSim and can be used without requiring any extra configuration. It is mostly intended to get you up and running quickly, not for production use.)
* MySQL (fully supported)
* MSSQL (partially supported - some recent OpenSim features may not yet be implemented)

More information on database support can be found on the [[OpenSim Database support]] page.

==Script engine==
OpenSim supports multiple script engines. See [[ScriptEngines]] for details

==Standalone vs. Grid==
We recommend that you first get OpenSim running in standalone mode before you attempt to connect it to a grid, either your own grid or a public grid. An OpenSim configuration consists of regions (run by region simulators) and 5 core backend services (which manage users, the grid, assets, inventories, and grid-wide messaging, collectively known as UGAIM).

A system running in '''standalone mode''' (that is, one with OpenSim.ini configured such that gridmode = false) -- also known as "sandbox mode" -- runs everything (all UGAIM services and one or more regions) in a single executable (OpenSim.exe). External regions cannot be added to an OpenSim running in this mode.

In '''grid mode''', the five services (User, Grid, Asset, Inventory, Messaging, or UGAIM) are each started as separate executables. This means that they can be run either on the same machine or spread out across multiple computers. In this mode, OpenSim.exe serves one or more regions, which communicate with the core servers. This mode even allows region servers run by other people on their own machines to connect, if you wish.

Naturally, this means that running in grid mode is somewhat more complicated than running in standalone mode. It requires an understanding of UUID, X,Y location, server handshake passwords, master avatars, and a couple of other settings. These are not difficult, but do require a little more care in setting things up.

If you want to run a grid of your own (either private or public) you would start the core services up before connecting a region simulator. If you want to connect your region server to a grid that someone else is running, you need only start the region server in grid mode (with the necessary security keys and location information mentioned in the last paragraph).

OpenSim.exe responds to various command line arguments. These include "-inifile", "-configfile", "-gridmode", "-physics", "-config" & "-noverbose". When starting OpenSim in either Windows or Linux, one could, for example, add "-physics=OpenDynamicsEngine" to run the OpenDynamicsEngine instead of basicphysics, or use "-gridmode=true" to force opensim.exe to run as a region server (the rest of the grid services have their own executables). As many of these settings are normally controlled by OpenSim.ini, most users (especially in standalone mode) will not add any command line arguments.

===Standalone mode===

When you start OpenSim in standalone mode, it will ask you several questions at the console. The first set of prompts that start with "NETWORK SERVERS INFO", you can just hit return to accept the defaults if you will be running in standalone mode. The prompts that start with "DEFAULT REGION CONFIG" are where you need to start paying attention. Some are self-explanatory. Here are explanations for the others: 
* Grid Location. OpenSim regions can be placed anywhere on a 65536 by 65536 grid. In standalone mode, it is safe to leave these X and Y locations at their defaults for the first region (additional regions will need different coordinates, of course).
* Filename for local storage. Safe to leave at default.
* Internal IP address; This should always be 0.0.0.0 (0.0.0.0 means "listen for connections on any interface", basically a wildcard)
* Internal IP port for incoming UDP client connection. You can make this any port you want, but it is safe to leave at the default 9000.
* External host name. If you will only be attaching to your sim from a SecondLife client on the same machine, you can leave this at the default 127.0.0.1. If you will be wanting to connect to it from a client on another machine, this should be the IP address or hostname of the machine you are running this sim on. N.B - It appears that this must actually be the External Host IP Address, not the Domain Name.
To connect to your new sim, start up secondlife with the following command line switches:
-loginuri http://127.0.0.1:9000/ -loginpage http://127.0.0.1:9000/?method=login
This assumes you are running the secondlife client on the same box. If you are running it on a separate box, substitute the IP address of your sim machine. 
To create a user: 
type ''create user <first> <last> <password> <x_loc> <y_loc>'' in the server console.

===Grid mode===
You want to run your own grid. Great! Assuming that you already got your sim running in standalone mode, here is what you need to do: 
1. Current builds of OpenSim grid mode are using mysql to store the grid information. You must have this installed and configured if you want to run your own grid. See [[mysql-config]] for more information. 
2. Four of the servers should be started in a certain order. UGAI: UserServer, GridServer, AssetServer, InventoryServer. The MessagingServer can be started at any point after the GridServer, and the RegionServer(s) should always come last. These are all found in the bin directory. In windows, you can just double-click on the executables to start them. In Linux and Mac OS X type "mono filename" from a prompt. The executable names, in order, are:
OpenSim.Grid.UserServer.exe
OpenSim.Grid.GridServer.exe
OpenSim.Grid.AssetServer.exe
OpenSim.Grid.InventoryServer.exe
OpenSim.Grid.MessagingServer.exe
OpenSim.exe
3. Start the UserServer. If you will be running the GridServer on the same box, hit enter to accept the defaults, until it gives you the prompt
OpenUser#
This is the main prompt for the user server. If you will be running the GridServer on another box, change the Default Grid Server URI as appropriate. 
4. Start the GridServer. Again, you can hit return at all the prompts if you are running them all on the same machine. If not, change the URIs for the Asset Server and User server to point to where you are running them. You will finally get to the console prompt for the GridServer which looks like this:
OpenGrid#
5. Start the AssetServer. The console prompt for this server will be:
OpenAsset#
6. Start the InventoryServer. The console prompt for this server will be:
INVENTORY#
7. Start the MessagingServer. The console prompt for this is:
Messaging#
8. If you are running all of these servers on the same box, which would be the normal configuration, you should be ready to start up your sim. The mode that OpenSim.exe starts in is normally controlled by a setting in your OpenSim.ini. It defaults to standalone mode if that setting is not specified or the file is not found. If you wish, you can force opensim to start in gridmode on the command line as follows:
OpenSim.exe -gridmode=true
or:
mono OpenSim.exe -gridmode=true
With any luck, everything will come up without too many errors. 
9. Go to the UserServer console, and type 'create user' to create a new avatar. It will prompt you for the name and password, and the X and Y of the sim that should be his home location. Use 1000 and 1000, or wherever you told your sim to live when you brought it up in standalone mode. At the console of any of these servers, you should be able to type 'help' to get a list of commands.

You should now be able to connect to your new grid with your secondlife client. You need to tell your client to point at the UserServer rather than directly at the sim, though:
secondlife -loginuri http://127.0.0.1:8002/
8002 is the default port for the UserServer, and that IP address should be changed to the server you are running the UserServer on, if they are not all on the same box. Happy OpenSimming! 
''Note: if you are using Windows Vista, remember to start servers as Admin. If not it will prompt you an error in console like "Error - Access denied"''

==Multiple regions==

Using Physical Prim with the OpenDynamicsEngine on *nix, it's recommended that you set your stack reserve level higher then default with the following command;
<tt>ulimit -s 262144</tt> Or, run the opensim-ode.sh to start up OpenSimulator.

A powerful region generator is available at: [[RegionGenerator]]

For running multiple regions on the same box, you simply make multiple copies of the 'default.xml' file inside the <tt>bin/Regions/</tt> directory. You can do this using the script <tt>make.php</tt> in <tt>share/regions</tt>, or you can generate the files by hand.

If you want to create the files by hand:

:first copy the default.xml file in the <tt>bin/Regions</tt> directory, and name them anything you want (I name mine region.x.y.xml, where region is the name of the region, and x and y are the grid coords.)
:Open each xml file and edit the uuid (a generator can be found at [http://www.famkruithof.net/uuid/uuidgen uuidgen webpage] or on unix, use the uuidgen command), region name, x & y positions, and internal ip port. IMPORTANT! The UUID, name, and grid coordinates ''must'' be unique for each region on a grid. The port assignment must be unique for each region that is running on a particular machine. 

Note that <tt>sim_location_x</tt> and <tt>sim_location_y</tt> should be adjacent integers if you want your regions to be adjacent, so you can run back and forth between them. '''IMPORTANT: THESE GRID COORDINATES ARE ''NOT'' IN METERS. THEY ARE SIM POSITIONS.''' (1000, 1000) is next to (1001,1000), (1000, 1001), and so forth. 1256, 2000, 2048 and similar values are '''not''' adjacent to 1000, they are very far away, so you would not see your sims from one another.

Once you have 2 or more xml files in the bin/Regions folder, running a ''single'' copy of <tt>OpenSim.exe</tt> will start up all of your sims! If you come across any errors, there is most likely an error in your xml files.

As of 6-Feb-2008, take care NOT to leave editor backup copies of the files in this directory e.g. emacs style backup names like Regionname.xml~. These are loaded by opensim.exe as if they are legitimate region descriptions, and will therefore give errors indicating you are trying to re-use the socket for that region.

==Attaching your sim to someone else's grid==
To set up the region server (i.e., <tt>OpenSim.exe</tt>) to connect to an external grid, you should edit the <tt>OpenSim.ini</tt> file in the <tt>bin</tt> directory. In that file, there is a <tt>[Network]</tt> section with URLs for the grid, user, and asset servers, as well as send and receive keys (for a basic level of security). The addresses and send/receive keys will vary depending on the grid you are connecting to, and the grid operator should tell you what values to use.

The other file you may have to change is in your <tt>bin/Regions</tt> directory. This is where your individual region config files are. If you only have one region, it will by default be called <tt>default.xml</tt>.

This can be edited with any text editor. The grid owner may tell you what X and Y location you can place your sim at (you can't have multiple sims at the same location on the grid). If so, the fields you will need to change in this file are <tt>sim_location_x</tt> and <tt>sim_location_y</tt>. And the <tt>external_host_name</tt> should be set to the hostname or IP address of your simulation server (i.e., the machine that is running <tt>OpenSim.exe</tt>).
A list of public grids that you can attach your sim to is at [[OpenSim: Grids]]

==Running==

===StandAlone===
'''Windows'''
cd bin
OpenSim.exe
On Windows Vista, it may be necessary to explicitly "Run as administrator" for opensim.exe to accept connections from a client, even when running as an administrator user. Navigate to the opensim\bin directory, right click opensim.exe, and select "Run as administrator".
Connect: opensim://localhost:9000 , or opensim://127.0.0.1:9000, or opensim://myipadress:9000

'''Linux'''
cd bin
mono OpenSim.exe

'''OSX'''
cd bin
mono OpenSim.exe

===Local Grid===
'''Windows'''
cd bin
OpenSim.Grid.UserServer.exe
OpenSim.Grid.GridServer.exe
OpenSim.Grid.AssetServer.exe
OpenSim.Grid.InventoryServer.exe
OpenSim.Grid.MessagingServer.exe
OpenSim.exe

'''Linux'''
cd bin
mono OpenSim.Grid.UserServer.exe
mono OpenSim.Grid.GridServer.exe
mono OpenSim.Grid.AssetServer.exe
mono OpenSim.Grid.InventoryServer.exe
mono OpenSim.Grid.MessagingServer.exe
mono OpenSim.exe

'''OSX''''
cd bin
mono OpenSim.Grid.UserServer.exe
mono OpenSim.Grid.GridServer.exe
mono OpenSim.Grid.AssetServer.exe
mono OpenSim.Grid.InventoryServer.exe
mono OpenSim.Grid.MessagingServer.exe
mono OpenSim.exe
Connect: opensim://myipaddress:9000

User Documentation

2008-10-07T19:03:22Z

MoHax: /* Initial Setup */

{{Template:Quicklinks}}
__NOTOC__
==Initial Setup==
* [[Download]] - Download instructions
* [[Build Instructions]] - How to build and compile OpenSim from Source
* [[Configuration]] - How to get your OpenSim server up and running
* [[Connecting]] - How to connect a compatible viewer to OpenSim
* [[Troubleshooting]] - How to trouble shoot your OpenSim installation.
* [[Tips]] - Useful tips from users like you
* [[FAQ]] - Frequently Asked Questions

==Administrator Guide==
* [[Server Commands]] - Commands to control OpenSim
* [[OpenSim Database support]] - Dealing with databases
* [[Logging]] - Logging in OpenSim
* [[Custom Libraries]] - Describes how to add custom content to your OpenSim server
* [[Automating Tasks]] - How to make administrating a walk in the park
* [[Network Settings]] - NAT, Ports, Services and more...
* [[Management]] - All about being an effective administrator/moderator
* [[Performance]] - How to tweak OpenSim's performance
* [[Console-less OpenSim]] - How to run OpenSim without console
* [[GridInfo]] - how to provide information about your grid to smart clients

==Facilities==
* [[OpenSim Archives]] - Loading and saving whole region archives with OpenSim

==Scripting==
* [[Scripting Documentation]] - Everything you need to know about OpenSim scripting
* [[Scripting Library]] - A list of example scripts

==Tutorials==
* [[OSGrid Region Registration]] - Describes how to link your region into OS-Grid
* [[Hints & Tricks]] - A page for Hints and Tricks
* [[Using L3DT]] - How to create custom terrains
* [[Detailed cross-region terrain making]] - A workflow for creating large cross-region custom terrains
* [[Linux Gridserver]] using 'moo' - How to setup a Gridserver on a Linux machine using 'moo'
* [[Linux Gridserver, the ubuntu way]] the quick and dirty way to install opensim under ubuntu
* [http://www.adamfrisby.com/blog/2008/08/resources-for-running-your-own-opensim Adam's OpenSim resources blog post] - a list of resources for running OpenSim
* [http://rock-vacirca.blogspot.com Rock Vacirca's Blog] - lots of tutorials, not only on OpenSim, but on MySQL, Hippo, Second Inventory, etc

==Contribution Policy==
* [[User_Wiki_Conventions|User Wiki Conventions]] - Read this carefully, before adding content to the wiki
[[Category:Users]]
<cleanpage title=hide cats=hide />

Mysql-config example

2008-10-03T12:53:39Z

MoHax:

{{obsolete}}

[Startup]
gridmode = false

; Select a mesher here. ZeroMesher is save and fast.
; ZeroMesher also means that the physics engine models the physics of prims
; sticking to the basic shapes the engine does support. Usually this is only a box.
; Meshmerizer gives a better handling of complex prims by using triangle meshes.
; Note, that only ODE physics currently deals with meshed prims in a satisfactoring way
;
;meshing = ZeroMesher
meshing = Meshmerizer

; Choose one of the physics engines below
;physics = basicphysics
;physics = POS
physics = OpenDynamicsEngine
;physics = modified_BulletX

; *** Prim Storage - only leave one storage_plugin uncommented ***
; --- The NullStorage stores nothing - effectively disabling persistence:
; storage_plugin = "OpenSim.Data.Null.dll"

; --- To use sqlite as region storage:
;storage_plugin = "OpenSim.Data.SQLite.dll"
;storage_connection_string="URI=file:OpenSim.db,version=3";

; --- To use MySQL storage, supply your own connectionstring (this is only an example):
; note that the supplied account needs create privilegies if you want it to auto-create needed tables.
storage_plugin="OpenSim.Data.MySQL.dll"
storage_connection_string="Data Source=localhost;Database=opensim;User ID=root;Password=******;";

startup_console_commands_file = "startup_commands.txt"
shutdown_console_commands_file = "shutdown_commands.txt"
serverside_object_permissions = true

; Select the type of database to use for asset storage
;asset_database = "db4o"
;asset_database = "sqlite"
;asset_database = "grid"
;asset_database = "mssql"
asset_database = "mysql"

verbose = true

; ScriptEngine
script_engine = OpenSim.Region.ScriptEngine.DotNetEngine.dll
;Experimental remote ScriptServer plugin:
;script_engine = OpenSim.Region.ScriptEngine.RemoteServer.dll

; if you would like to allow prim to be physical and move by physics with the physical checkbox in the client set this to true.
physical_prim = true

; To run a script every few minutes, set the script filename here
; timer_Script = "filename"

[StandAlone]
accounts_authenticate = true
welcome_message = "Your welcome message"
;inventory_plugin = "OpenSim.Data.SQLite.dll"
inventory_plugin = "OpenSim.Data.MySQL.dll"
;userDatabase_plugin = "OpenSim.Data.SQLite.dll"
userDatabase_plugin = "OpenSim.Data.MySQL.dll"
default_location_x = 1000
default_location_y = 1000
dump_assets_to_file = false

[Network]
http_listener_port = 9000
remoting_listener_port = 8895

; Uncomment below to enable llRemoteData/remote channels
; remoteDataPort = 20800

grid_server_url = "http://127.0.0.1:8001"
grid_send_key = "null"
grid_recv_key = "null"

user_server_url = "http://127.0.0.1:8002"
user_send_key = "null"
user_recv_key = "null"

asset_server_url = "http://127.0.0.1:8003"

inventory_server_url = "http://127.0.0.1:8004"

[Chat]
whisper_distance = 10
say_distance = 30
shout_distance = 100

; Uncomment the following for IRC bridge
; experimental, so if it breaks... keep both parts... yada yada
; also, not good error detection when it fails
;[IRC]
server = irc.freenode.net
nick = OSbot
channel = #innovatieproject

; Uncomment the following to control the progression of daytime
; in the Sim. The defaults are what is shown below
[Sun]
; number of wall clock hours for an opensim day. 24.0 would mean realtime
day_length = 0.5

; send a Sun update ever frame_rate # of frames. A lower number will
; make for smoother sun transition at the cost of network
;frame_rate = 100
[[Category:Configuration]]
[[Category:Users]]

User:MoHax

2008-05-12T01:49:07Z

MoHax: New page: [http://imohax.com http://imohax.com]

[http://imohax.com http://imohax.com]

Development Team

2008-05-12T01:47:42Z

MoHax: /* Additional Developers/Testers/Contributors */

== OpenSim Core Developers ==
These people have commit access to our central SVN server and are regular contributors to the codebase.

(please add in as much info as you like for your name)

<table border="1" cellpadding="2" cellspacing="0" class="sortable">
<tr>
<th>Photo </th>
<th>IRC Nick </th>
<th>Name</th>
<th>SL Avatar</th>
<th>Other Grid</th>
<th>Time Zone (UTC)</th>
<th>Org</th>
<th>Areas of Interest</th>
</tr>
<tr>
<td />
<td>[[User:MW / Michael Wright |MW / Michael Wright ]]</td>
<td>Darren</td>
<td>Wright Juran</td>
<td></td>
<td>0</td>
<td>Tribal Media AB</td>
<td>everything</td>
</tr>
<tr>
<td />
<td>[[User:Adam Frisby|Adam Frisby]]</td>
<td>Adam Frisby</td>
<td>Adam Zaius</td>
<td></td>
<td>+8</td>
<td>DeepThink Pty Ltd</td>
<td>Terrain, Performance</td>
</tr>
<tr>
<td />
<td>[[User:MingChen|MingChen]]</td>
<td>Mike/Michael Ortman</td>
<td>Ming Chen</td>
<td></td>
<td>-6 (-5 in Summer)</td>
<td>DeepThink Pty Ltd</td>
<td>Estate/Parcel Support/Modules/Keeping things all neat and tidy.</td>
</tr>
<tr>
<td> </td>
<td>[[User:lbsa71|lbsa71]]</td>
<td>Stefan Andersson</td>
<td>PierreJoseph Proudhon</td>
<td>OSG:Stefan Andersson OLG:Stefan Andersson</td>
<td>+1</td>
<td>Tribal Media AB</td>
<td> 3D and Web Integration</td>
</tr>
<tr>
<td />
<td>[[User:SeanDague|sdague]]</td>
<td>Sean Dague</td>
<td>Neas Bade</td>
<td></td>
<td>-5</td>
<td>IBM</td>
<td>Database, Linux, Testing, Misc</td>
</tr>
<tr>
<td />
<td>[[User:babblefrog|babblefrog]]</td>
<td>Brian McBee</td>
<td>Dogen Coldstream</td>
<td>Babblefrog Ballistic (osgrid)</td>
<td>-8</td>
<td>Disorganized</td>
<td> </td>
</tr>
<tr>
<td />
<td>[[User:Tedd|Tedd]]</td>
<td>Tedd Hansen</td>
<td>Tedd Maa</td>
<td></td>
<td>+1</td>
<td>Tedd Hansen</td>
<td>Programming/Scripting/Architecture</td>
</tr>
<tr>
<td />
<td>[[User:danx0r|danx0r]]</td>
<td>Dan Miller</td>
<td>Albert Pascal</td>
<td></td>
<td>-8</td>
<td>squiggle.com</td>
<td>PHEEZIKS; everything</td>
</tr>
<tr>
<td />
<td>[[User:dalien|dalien]]</td>
<td>Dalien Talbot</td>
<td>Dalien Talbot</td>
<td></td>
<td>+1</td>
<td>Mostly TCP-based</td>
<td>Small fixes; rev.eng./prototyping; nightlies; git-keeper </td>
</tr>
<tr>
<td />
<td>Tleiades</td>
<td> </td>
<td>Tleiades Hax</td>
<td></td>
<td>+1</td>
<td> </td>
<td>Grid servers/Database</td>
</tr>
<tr>
<td />
<td>ckrinke</td>
<td>Charles Krinke</td>
<td>Charlesk Bing</td>
<td></td>
<td>-8</td>
<td> </td>
<td>Reliability/Grid servers/ll-functions</td>
</tr>
<tr>
<td />
<td>[[User:chi11ken|chi11ken]]</td>
<td>Jeff Ames</td>
<td>Chillken Proto</td>
<td></td>
<td>+9</td>
<td>3Di http://www.3di.jp/</td>
<td> </td>
</tr>
<tr>
<td />
<td>[[User:Darok|Darok]]</td>
<td> </td>
<td>Darok Kaminski</td>
<td></td>
<td>+1</td>
<td> </td>
<td>Physics engines (especially BulletX)</td>
</tr>
<tr>
<td />
<td>[[User:adjohn|adjohn]]</td>
<td>Adam Johnson</td>
<td>Zeuz Zenovka</td>
<td></td>
<td>+9</td>
<td>3Di http://www.3di.jp/</td>
<td> </td>
</tr>
<tr>
<td />
<td>[[User:joha1|joha1]]</td>
<td>Johan Berntsson</td>
<td>Joppi Brandenburg</td>
<td></td>
<td>+9</td>
<td>3Di http://www.3di.jp/</td>
<td>Performance, packet handling/libSL</td>
</tr>
<tr>
<td />
<td>[[User:Teravus|Teravus]]</td>
<td>Teravus</td>
<td>Teravus Ousley</td>
<td></td>
<td>-5</td>
<td>W3z</td>
<td>Physics & Admin tools, A working sim.</td>
</tr>
<tr>
<td />
<td>[[User:Justincc|Justincc]]</td>
<td>Justin Clark-Casey</td>
<td>Lulworth Beaumont</td>
<td>Justin Clark-Casey (osgrid)</td>
<td>0</td>
<td>IBM</td>
<td>Grid, performance & reliability, inventory (avatar and object), assets, scenes.</td>
</tr>
<tr>
<td />
<td>[[Alondria]]</td>
<td></td>
<td>Alondria LeFay</td>
<td>Alondria LeFay (OSGrid)</td>
<td>-8</td>
<td>Independent</td>
<td>Implementation of LSL functions and other scripting tidbits.</td>
</tr>
</table>

== Additional Developers/Testers/Contributors ==
These people have contributed bug reports, patches or other contributions to OpenSim.

<table border="1" cellpadding="2" cellspacing="0" class="wikitable sortable">
<tr>
<th>IRC Nick </th>
<th>Name</th>
<th>SL Avatar</th>
<th>Other Grid</th>
<th>Time Zone (UTC)</th>
<th>Org</th>
<th>Areas of Interest</th>
</tr>

<tr>
<td>[[User:Nebadon|Nebadon]]</td>
<td>Michael Cerquoni</td>
<td>Nebadon Izumi</td>
<td>Nebadon Izumi</td>
<td>-7 Arizona</td>
<td>Oni Kenkon Creations</td>
<td>Building, Scripting, Testing</td>
</tr>
<tr>
<td>[[User:jtclark48|jclark4]]</td>
<td>Jay Clark</td>
<td>Jay Clarke</td>
<td></td>
<td>-5</td>
<td>IBM</td>
<td>Physics, Grid Host, AI, Scripting, Testing</td>
</tr>
<tr>
<td>Gareth</td>
<td> </td>
<td> </td>
<td></td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td>[[User:AdamStevenson|BigFootAg]]</td>
<td>Adam Stevenson</td>
<td>Adamus Petrov</td>
<td></td>
<td>-6</td>
<td>Texas A&M University</td>
<td>AI, Skynet, Evolving Systems, Biology</td>
</tr>
<tr>
<td>[[User:Vicero Lambert|Vicero Lambert]]</td>
<td> </td>
<td> </td>
<td></td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td>Ldvoipeng</td>
<td> </td>
<td> </td>
<td></td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td>idoru</td>
<td> </td>
<td> </td>
<td></td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td>simsim</td>
<td> </td>
<td> </td>
<td></td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td>[[User:Magi|Magi]]</td>
<td>Andy Agnew</td>
<td>Magi Merlin</td>
<td></td>
<td>+10</td>
<td>Spun Pty Ltd</td>
<td>3D Web Integration, Database stuff and playing with the odds and ends box.</td>
</tr>
<tr>
<td>john_</td>
<td>John Moyer</td>
<td>VAJohn GeekSquad or Matthew Kendal</td>
<td></td>
<td>-5</td>
<td>Best Buy/Geek Squad</td>
<td>Tester</td>
</tr>
<tr>
<td>[[User:ClarkZone|ClarkZone]]</td>
<td>Troy Admin(@ClarkZone)</td>
<td>Troy Childs</td>
<td>Troy Admin (ClarkZone)</td>
<td>-5</td>
<td>Http://clarkzone.dyndns.org</td>
<td>Tester and Grid Host</td>
</tr>
<tr>
<td>[[User:aiaustin|aiaustin]]</td>
<td>Ai Austin</td>
<td>Ai Austin</td>
<td>Ai AIAI (AIAI Grid)</td>
<td>+0</td>
<td>AIAI, University of Edinburgh http://www.aiai.ed.ac.uk/~ai/ http://vue.ed.ac.uk/openvue/</td>
<td>Windows Vista tests Content testing Use of multiple VWs</td>
</tr>
<tr>
<td>[[User:balthazar|balthazar]]</td>
<td>Trevor Brooks</td>
<td>Balthazar Sin</td>
<td></td>
<td>-5</td>
<td>None</td>
<td>Terrains, testing and some small coding tasks</td>
</tr>
<tr>
<td>[[User:jimbo2120|jimbo2120]]</td>
<td>Michael Osias</td>
<td>Illuminous Beltran</td>
<td></td>
<td>-5</td>
<td>IBM</td>
<td>Grid, AI, Skynet, coding and testing</td>
</tr>
<tr>
<td>[[User:Sakai|Sakai]]</td>
<td>Steve S</td>
<td></td>
<td>Sakai Openlife (OpenlifeGrid)</td>
<td>+10</td>
<td>http://www.openlifegrid.com</td>
<td>Grid, Hardware, Testing, Contribution</td>
</tr>
<tr>
<td>ZeroPoint</td>
<td> </td>
<td>Guilderoy Dench</td>
<td></td>
<td>-5</td>
<td> </td>
<td>Programming/Database</td>
</tr>
<tr>
<td>MaltosSosa</td>
<td>Maltos Sosa</td>
<td>Maltos Sosa </td>
<td>Maltos Sosa (Central Grid)</td>
<td> </td>
<td>Central Grid</td>
<td>Grid Operator, Central Grid Project Manager. Anything we can offer, just ask.</td>
</tr>

<tr>
<td>[[User:DerekTang|DerekTang]]</td>
<td>Derek Tang</td>
<td>Derek Timeless</td>
<td>Derek Tang (ChineseGrid)</td>
<td>+8</td>
<td>http://ChineseGrid.net</td>
<td>Running a public WINDOWS sim for testing, Docs, Helping Chinese users to enjoy OpenSim; building Chinese OpenSim communities. In construction...</td>
</tr>

<tr>
<td>[[User:TayB|TayB]]</td>
<td>Earl B</td>
<td>Taylor Boyau</td>
<td></td>
<td>-10</td>
<td>ViziGrid</td>
<td>Grid Host,Networking,Contributions & Testing.</td>
</tr>
<tr>
<td>[[User:JamieDav|JamieDav]]</td>
<td>Jamie David</td>
<td>Jamie David</td>
<td></td>
<td>+7</td>
<td>Forum</td>
<td>Grid, Sim, Avitar, Functionality</td>
</tr>
<tr>
<td>[[User:Krtaylor|Krtaylor]]</td>
<td>Kurt Taylor</td>
<td>Kurt Stringer </td>
<td></td>
<td>-6</td>
<td>IBM</td>
<td>Grid, Networking, Monitoring, Scripting, Inventory, Testing</td>
</tr>
<tr>
<td>[[User:Nink|Nink]]</td>
<td>Peter Finn</td>
<td>Nink Noonan</td>
<td></td>
<td>-5</td>
<td>IBM</td>
<td>Disruptive Influence.</td>
</tr>
<tr>
<td>[[User:Bruce|Bruce]]</td>
<td>Bruce Meerson</td>
<td>Bruce Meerson</td>
<td></td>
<td>+8</td>
<td>HiPiHi</td>
<td>Watching.</td>
</tr>
<tr>
<tr>
<td>[[User:Darb|Darb]]</td>
<td>Brian B. Quinn</td>
<td>Darb Dabney</td>
<td>regions near Berkeley</td>
<td>-8</td>
<td>City of Berkeley, CA http://blog.simgis.org</td>
<td>Testing large standalones, real-world terrain, pursuit of civic paraverses </td>
</tr>
<tr>
<td>[[CharlieO]]</td>
<td>Dan</td>
<td>Charlie Omega</td>
<td></td>
<td> </td>
<td> </td>
<td>Mild coding/tweaking/simple feature adds, Stress testing/break stuff, Testing limits of existing code. Making sure [[LSL Status]] is up to date</td>
</tr>
<tr>
<td>oobscure</td>
<td> </td>
<td>Opensource Obscure</td>
<td></td>
<td>+1</td>
<td>http://www.opensim.it</td>
<td>Running a public Linux sim for testing, Docs, Helping italian users, Building opensim communities, Watching</td>
</tr>
<tr>
<td>pitman</td>
<td>Mike Pitman</td>
<td>Rez Tone</td>
<td></td>
<td> </td>
<td>IBM</td>
<td>Scientific visualization schemes, virt world product design, persistant workspaces, virt world based big biz</td>
</tr>
<tr>
<td>cmu</td>
<td>Christopher Mumme</td>
<td>Snook Destiny</td>
<td></td>
<td>+1</td>
<td>http://www.cmu-develop.de/ and research group "Collaboration Systems and CSCW" at Clausthal University of Technology</td>
<td>Testing OpenSim, translating the OpenSim Wiki into German and reporting on OpenSim</td>
</tr>

<tr>
<td>[[Silpol]]</td>
<td>Andriy Tymchenko</td>
<td>Andy Tir</td>
<td></td>
<td>EET (+2/3)</td>
<td> http://silpol.blogspot.com/ (also visible at Nokia)</td>
<td>highly uncoordinated mess with elements of palace games, under-table diplomacy, rebellion, coup d'état and mutiny. optionally pirate</td>
</tr>
<tr>
<td>[[User:Grumly|Grumly]]</td>
<td></td>
<td>Forest Klaar</td>
<td>Grumly TheBear</td>
<td>GMT+1</td>
<td>.NET MCAD Dev/Arch/Trainer http://www.devoteam.com</td>
<td>Trying to get into OpenSim code for now. Particularly interrested in data persistence. blog (Hello, Avatar!): http://lslblog.free.fr</td>
</tr>
<tr>
<td>[[daTwitch]]</td>
<td>James G. Stallings II</td>
<td> Lazarus Longstaff</td>
<td>Hiro Protagonist (OSGrid)</td>
<td>-5</td>
<td>House Husband</td>
<td>OSGrid Region owner, OSGrid Operator, Forum Admin, sometime wiki editor</td>
</tr>

<tr>
<td>gryc</td>
<td>Gryc Ueusp</td>
<td>Gryc Uriza</td>
<td>Gryc Uriza(OSGrid)</td>
<td>-6</td>
<td></td>
<td>PHP scripting, web interfaces, interconnectivity, cross-platformedness</td>
</tr>

<tr>
<td>[[User:Phrearch|Phrearch]]</td>
<td>Jeroen van Veen</td>
<td>Phrearch Miles</td>
<td>Phrearch Miles(OSGrid)</td>
<td>Amsterdam/Paris</td>
<td></td>
<td>Documentation, scripts(perl/lsl), RIA(flex) mashup, testing</td>
</tr>

<tr>
<td>[[User:Burnman|Burnman]]</td>
<td>Allen Wilkins</td>
<td>Burnman Bedlam</td>
<td>Sid Green (United Grid)</td>
<td>Boston, USA</td>
<td>United Grid</td>
<td>Testing, testing, and more testing! Getting familiar with the source, interested in all aspects of the project.</td>
</tr>

<tr>
<td>[[User:krisbfunk|krisbfunk]]</td>
<td>Kris Bulman</td>
<td>krisbfunk Vought</td>
<td>Krisbfunk Nocturnal(OSGrid)</td>
<td>PE, Canada (-4)</td>
<td>Edactive Technologies NocturnalEye Productions UPEI</td>
<td>Currently: Testing, bug reports, wiki updating, building on OSGrid</td>
</tr>

<tr>
<td>[[User:HashBox|HashBox]]</td>
<td>Zane Ashby</td>
<td>Sibariel Darkstone</td>
<td>Sibariel Darkstone (OSGrid)</td>
<td>New Zealand (+12)</td>
<td></td>
<td>Testing, bug reports, and updating the wiki.</td>
</tr>

<tr>
<td>[[User:Kinoc|Kinoc]]</td>
<td>Kino Coursey</td>
<td>Daxxon Jaxxon</td>
<td>Daxxon Kinoc (OSgrid)</td>
<td>-6</td>
<td>Daxtron Laboratories http://www.daxtron.com University of North Texas</td>
<td>AI, Semantic web, Ontologies, Natural Laanguage Processing, Cyc, Bots, NPC </td>
</tr>
<tr>
<td>[[User:trapuh|trapuh]]</td>
<td>Pedro Ribeiro</td>
<td>Vaiten Forder</td>
<td></td>
<td>GMT</td>
<td>University Student, Escola Superior de Educação de Viseu, Portugal </td>
<td>Testing, eventual bug reports and wiki. Music, web/digital arts and php+sql.</td>
</tr>
<tr>
<td>[[User:SonicViz|SonicViz]]</td>
<td>Paul Cohen</td>
<td>Komuso Tokugawa</td>
<td></td>
<td>+9</td>
<td>Http://sonicviz.com</td>
<td>Audio/Music, Interactive Music, Control Protocols, Interfaces, VisualFX, Procedural animation/Generative systems + testing and general dev</td>
</tr>
<tr>
<td>[[User:Mokele|mokele]]</td>
<td>Scott Norman</td>
<td>Mokelembembe Mokeev</td>
<td></td>
<td>-8 (Southern California)</td>
<td>Web Developer (PHP and MySQL)</td>
<td>Interested in seeing running on PowerPC Macs which it is. So, when I can, I'll compile and test on PowerPC Mac (PowerBook G4) and submit reports and then update the wiki if need on installing on Mac. Also have a Ubuntu 7.10 server that I can do testing on too.</td>
</tr>

<tr>
<td>[[User:devalnor|devalnor]]</td>
<td>Devalnor</td>
<td>M. Watkin</td>
<td></td>
<td>+1 (Belgium)</td>
<td></td>
<td>Small Patch code, bug reports, and updating the wiki.</td>
</tr>

<tr>
<td>[[User:Ezekiel|Ezekiel]]</td>
<td>Ezekiel</td>
<td>Ezekiel Zabelin</td>
<td></td>
<td>+1 </td>
<td>http://www.yosims.com </td>
<td>Concepts, business aspects of virtual worlds - web developer (PHP, MySQL, Javascript, LSL) </td>
</tr>

<tr>
<td>[[User:Diva|diva]]</td>
<td>Crista Lopes</td>
<td>Diva Canto</td>
<td>Diva Canto or Crista Lopes in as many grids as possible</td>
<td>-8 </td>
<td>UC Irvine and http://metaverseink.com </td>
<td>Search, general architecture</td>
</tr>

<tr>
<td>[[User:Buggmaster|Buggmaster]]</td>
<td>Mike D</td>
<td>Bug Master</td>
<td>None</td>
<td>-8 </td>
<td>http://www.adultmetaverse.com</td>
<td>Grid, Data/Web PHP/PERL/MySQL</td>
</tr>

<tr>
<td>[[User:Nixnerd|nixnerd]]</td>
<td>Richmund</td>
<td>Dangerously Moody</td>
<td>None</td>
<td>GMT </td>
<td>http://www.integratedtechnologies.eu</td>
<td>Cross Platform Testing, Feedback, Bug Reporting</td>
</tr>

<tr>
<td>[[User:MoHax|mohax]]</td>
<td>Mo Hax</td>
<td>Mo Hax</td>
<td></td>
<td>-5 Eastern</td>
<td>IBM</td>
<td>Testing, Feedback, Content Contributions, Bug Reporting, Documenting, Development</td>
</tr>

</table>
[[Category:Main]]
[[Category:Development]]

Development Team

2008-05-12T01:46:48Z

MoHax: /* Additional Developers/Testers/Contributors */

== OpenSim Core Developers ==
These people have commit access to our central SVN server and are regular contributors to the codebase.

(please add in as much info as you like for your name)

<table border="1" cellpadding="2" cellspacing="0" class="sortable">
<tr>
<th>Photo </th>
<th>IRC Nick </th>
<th>Name</th>
<th>SL Avatar</th>
<th>Other Grid</th>
<th>Time Zone (UTC)</th>
<th>Org</th>
<th>Areas of Interest</th>
</tr>
<tr>
<td />
<td>[[User:MW / Michael Wright |MW / Michael Wright ]]</td>
<td>Darren</td>
<td>Wright Juran</td>
<td></td>
<td>0</td>
<td>Tribal Media AB</td>
<td>everything</td>
</tr>
<tr>
<td />
<td>[[User:Adam Frisby|Adam Frisby]]</td>
<td>Adam Frisby</td>
<td>Adam Zaius</td>
<td></td>
<td>+8</td>
<td>DeepThink Pty Ltd</td>
<td>Terrain, Performance</td>
</tr>
<tr>
<td />
<td>[[User:MingChen|MingChen]]</td>
<td>Mike/Michael Ortman</td>
<td>Ming Chen</td>
<td></td>
<td>-6 (-5 in Summer)</td>
<td>DeepThink Pty Ltd</td>
<td>Estate/Parcel Support/Modules/Keeping things all neat and tidy.</td>
</tr>
<tr>
<td> </td>
<td>[[User:lbsa71|lbsa71]]</td>
<td>Stefan Andersson</td>
<td>PierreJoseph Proudhon</td>
<td>OSG:Stefan Andersson OLG:Stefan Andersson</td>
<td>+1</td>
<td>Tribal Media AB</td>
<td> 3D and Web Integration</td>
</tr>
<tr>
<td />
<td>[[User:SeanDague|sdague]]</td>
<td>Sean Dague</td>
<td>Neas Bade</td>
<td></td>
<td>-5</td>
<td>IBM</td>
<td>Database, Linux, Testing, Misc</td>
</tr>
<tr>
<td />
<td>[[User:babblefrog|babblefrog]]</td>
<td>Brian McBee</td>
<td>Dogen Coldstream</td>
<td>Babblefrog Ballistic (osgrid)</td>
<td>-8</td>
<td>Disorganized</td>
<td> </td>
</tr>
<tr>
<td />
<td>[[User:Tedd|Tedd]]</td>
<td>Tedd Hansen</td>
<td>Tedd Maa</td>
<td></td>
<td>+1</td>
<td>Tedd Hansen</td>
<td>Programming/Scripting/Architecture</td>
</tr>
<tr>
<td />
<td>[[User:danx0r|danx0r]]</td>
<td>Dan Miller</td>
<td>Albert Pascal</td>
<td></td>
<td>-8</td>
<td>squiggle.com</td>
<td>PHEEZIKS; everything</td>
</tr>
<tr>
<td />
<td>[[User:dalien|dalien]]</td>
<td>Dalien Talbot</td>
<td>Dalien Talbot</td>
<td></td>
<td>+1</td>
<td>Mostly TCP-based</td>
<td>Small fixes; rev.eng./prototyping; nightlies; git-keeper </td>
</tr>
<tr>
<td />
<td>Tleiades</td>
<td> </td>
<td>Tleiades Hax</td>
<td></td>
<td>+1</td>
<td> </td>
<td>Grid servers/Database</td>
</tr>
<tr>
<td />
<td>ckrinke</td>
<td>Charles Krinke</td>
<td>Charlesk Bing</td>
<td></td>
<td>-8</td>
<td> </td>
<td>Reliability/Grid servers/ll-functions</td>
</tr>
<tr>
<td />
<td>[[User:chi11ken|chi11ken]]</td>
<td>Jeff Ames</td>
<td>Chillken Proto</td>
<td></td>
<td>+9</td>
<td>3Di http://www.3di.jp/</td>
<td> </td>
</tr>
<tr>
<td />
<td>[[User:Darok|Darok]]</td>
<td> </td>
<td>Darok Kaminski</td>
<td></td>
<td>+1</td>
<td> </td>
<td>Physics engines (especially BulletX)</td>
</tr>
<tr>
<td />
<td>[[User:adjohn|adjohn]]</td>
<td>Adam Johnson</td>
<td>Zeuz Zenovka</td>
<td></td>
<td>+9</td>
<td>3Di http://www.3di.jp/</td>
<td> </td>
</tr>
<tr>
<td />
<td>[[User:joha1|joha1]]</td>
<td>Johan Berntsson</td>
<td>Joppi Brandenburg</td>
<td></td>
<td>+9</td>
<td>3Di http://www.3di.jp/</td>
<td>Performance, packet handling/libSL</td>
</tr>
<tr>
<td />
<td>[[User:Teravus|Teravus]]</td>
<td>Teravus</td>
<td>Teravus Ousley</td>
<td></td>
<td>-5</td>
<td>W3z</td>
<td>Physics & Admin tools, A working sim.</td>
</tr>
<tr>
<td />
<td>[[User:Justincc|Justincc]]</td>
<td>Justin Clark-Casey</td>
<td>Lulworth Beaumont</td>
<td>Justin Clark-Casey (osgrid)</td>
<td>0</td>
<td>IBM</td>
<td>Grid, performance & reliability, inventory (avatar and object), assets, scenes.</td>
</tr>
<tr>
<td />
<td>[[Alondria]]</td>
<td></td>
<td>Alondria LeFay</td>
<td>Alondria LeFay (OSGrid)</td>
<td>-8</td>
<td>Independent</td>
<td>Implementation of LSL functions and other scripting tidbits.</td>
</tr>
</table>

== Additional Developers/Testers/Contributors ==
These people have contributed bug reports, patches or other contributions to OpenSim.

<table border="1" cellpadding="2" cellspacing="0" class="wikitable sortable">
<tr>
<th>IRC Nick </th>
<th>Name</th>
<th>SL Avatar</th>
<th>Other Grid</th>
<th>Time Zone (UTC)</th>
<th>Org</th>
<th>Areas of Interest</th>
</tr>

<tr>
<td>[[User:Nebadon|Nebadon]]</td>
<td>Michael Cerquoni</td>
<td>Nebadon Izumi</td>
<td>Nebadon Izumi</td>
<td>-7 Arizona</td>
<td>Oni Kenkon Creations</td>
<td>Building, Scripting, Testing</td>
</tr>
<tr>
<td>[[User:jtclark48|jclark4]]</td>
<td>Jay Clark</td>
<td>Jay Clarke</td>
<td></td>
<td>-5</td>
<td>IBM</td>
<td>Physics, Grid Host, AI, Scripting, Testing</td>
</tr>
<tr>
<td>Gareth</td>
<td> </td>
<td> </td>
<td></td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td>[[User:AdamStevenson|BigFootAg]]</td>
<td>Adam Stevenson</td>
<td>Adamus Petrov</td>
<td></td>
<td>-6</td>
<td>Texas A&M University</td>
<td>AI, Skynet, Evolving Systems, Biology</td>
</tr>
<tr>
<td>[[User:Vicero Lambert|Vicero Lambert]]</td>
<td> </td>
<td> </td>
<td></td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td>Ldvoipeng</td>
<td> </td>
<td> </td>
<td></td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td>idoru</td>
<td> </td>
<td> </td>
<td></td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td>simsim</td>
<td> </td>
<td> </td>
<td></td>
<td> </td>
<td> </td>
<td> </td>
</tr>
<tr>
<td>[[User:Magi|Magi]]</td>
<td>Andy Agnew</td>
<td>Magi Merlin</td>
<td></td>
<td>+10</td>
<td>Spun Pty Ltd</td>
<td>3D Web Integration, Database stuff and playing with the odds and ends box.</td>
</tr>
<tr>
<td>john_</td>
<td>John Moyer</td>
<td>VAJohn GeekSquad or Matthew Kendal</td>
<td></td>
<td>-5</td>
<td>Best Buy/Geek Squad</td>
<td>Tester</td>
</tr>
<tr>
<td>[[User:ClarkZone|ClarkZone]]</td>
<td>Troy Admin(@ClarkZone)</td>
<td>Troy Childs</td>
<td>Troy Admin (ClarkZone)</td>
<td>-5</td>
<td>Http://clarkzone.dyndns.org</td>
<td>Tester and Grid Host</td>
</tr>
<tr>
<td>[[User:aiaustin|aiaustin]]</td>
<td>Ai Austin</td>
<td>Ai Austin</td>
<td>Ai AIAI (AIAI Grid)</td>
<td>+0</td>
<td>AIAI, University of Edinburgh http://www.aiai.ed.ac.uk/~ai/ http://vue.ed.ac.uk/openvue/</td>
<td>Windows Vista tests Content testing Use of multiple VWs</td>
</tr>
<tr>
<td>[[User:balthazar|balthazar]]</td>
<td>Trevor Brooks</td>
<td>Balthazar Sin</td>
<td></td>
<td>-5</td>
<td>None</td>
<td>Terrains, testing and some small coding tasks</td>
</tr>
<tr>
<td>[[User:jimbo2120|jimbo2120]]</td>
<td>Michael Osias</td>
<td>Illuminous Beltran</td>
<td></td>
<td>-5</td>
<td>IBM</td>
<td>Grid, AI, Skynet, coding and testing</td>
</tr>
<tr>
<td>[[User:Sakai|Sakai]]</td>
<td>Steve S</td>
<td></td>
<td>Sakai Openlife (OpenlifeGrid)</td>
<td>+10</td>
<td>http://www.openlifegrid.com</td>
<td>Grid, Hardware, Testing, Contribution</td>
</tr>
<tr>
<td>ZeroPoint</td>
<td> </td>
<td>Guilderoy Dench</td>
<td></td>
<td>-5</td>
<td> </td>
<td>Programming/Database</td>
</tr>
<tr>
<td>MaltosSosa</td>
<td>Maltos Sosa</td>
<td>Maltos Sosa </td>
<td>Maltos Sosa (Central Grid)</td>
<td> </td>
<td>Central Grid</td>
<td>Grid Operator, Central Grid Project Manager. Anything we can offer, just ask.</td>
</tr>

<tr>
<td>[[User:DerekTang|DerekTang]]</td>
<td>Derek Tang</td>
<td>Derek Timeless</td>
<td>Derek Tang (ChineseGrid)</td>
<td>+8</td>
<td>http://ChineseGrid.net</td>
<td>Running a public WINDOWS sim for testing, Docs, Helping Chinese users to enjoy OpenSim; building Chinese OpenSim communities. In construction...</td>
</tr>

<tr>
<td>[[User:TayB|TayB]]</td>
<td>Earl B</td>
<td>Taylor Boyau</td>
<td></td>
<td>-10</td>
<td>ViziGrid</td>
<td>Grid Host,Networking,Contributions & Testing.</td>
</tr>
<tr>
<td>[[User:JamieDav|JamieDav]]</td>
<td>Jamie David</td>
<td>Jamie David</td>
<td></td>
<td>+7</td>
<td>Forum</td>
<td>Grid, Sim, Avitar, Functionality</td>
</tr>
<tr>
<td>[[User:Krtaylor|Krtaylor]]</td>
<td>Kurt Taylor</td>
<td>Kurt Stringer </td>
<td></td>
<td>-6</td>
<td>IBM</td>
<td>Grid, Networking, Monitoring, Scripting, Inventory, Testing</td>
</tr>
<tr>
<td>[[User:Nink|Nink]]</td>
<td>Peter Finn</td>
<td>Nink Noonan</td>
<td></td>
<td>-5</td>
<td>IBM</td>
<td>Disruptive Influence.</td>
</tr>
<tr>
<td>[[User:Bruce|Bruce]]</td>
<td>Bruce Meerson</td>
<td>Bruce Meerson</td>
<td></td>
<td>+8</td>
<td>HiPiHi</td>
<td>Watching.</td>
</tr>
<tr>
<tr>
<td>[[User:Darb|Darb]]</td>
<td>Brian B. Quinn</td>
<td>Darb Dabney</td>
<td>regions near Berkeley</td>
<td>-8</td>
<td>City of Berkeley, CA http://blog.simgis.org</td>
<td>Testing large standalones, real-world terrain, pursuit of civic paraverses </td>
</tr>
<tr>
<td>[[CharlieO]]</td>
<td>Dan</td>
<td>Charlie Omega</td>
<td></td>
<td> </td>
<td> </td>
<td>Mild coding/tweaking/simple feature adds, Stress testing/break stuff, Testing limits of existing code. Making sure [[LSL Status]] is up to date</td>
</tr>
<tr>
<td>oobscure</td>
<td> </td>
<td>Opensource Obscure</td>
<td></td>
<td>+1</td>
<td>http://www.opensim.it</td>
<td>Running a public Linux sim for testing, Docs, Helping italian users, Building opensim communities, Watching</td>
</tr>
<tr>
<td>pitman</td>
<td>Mike Pitman</td>
<td>Rez Tone</td>
<td></td>
<td> </td>
<td>IBM</td>
<td>Scientific visualization schemes, virt world product design, persistant workspaces, virt world based big biz</td>
</tr>
<tr>
<td>cmu</td>
<td>Christopher Mumme</td>
<td>Snook Destiny</td>
<td></td>
<td>+1</td>
<td>http://www.cmu-develop.de/ and research group "Collaboration Systems and CSCW" at Clausthal University of Technology</td>
<td>Testing OpenSim, translating the OpenSim Wiki into German and reporting on OpenSim</td>
</tr>

<tr>
<td>[[Silpol]]</td>
<td>Andriy Tymchenko</td>
<td>Andy Tir</td>
<td></td>
<td>EET (+2/3)</td>
<td> http://silpol.blogspot.com/ (also visible at Nokia)</td>
<td>highly uncoordinated mess with elements of palace games, under-table diplomacy, rebellion, coup d'état and mutiny. optionally pirate</td>
</tr>
<tr>
<td>[[User:Grumly|Grumly]]</td>
<td></td>
<td>Forest Klaar</td>
<td>Grumly TheBear</td>
<td>GMT+1</td>
<td>.NET MCAD Dev/Arch/Trainer http://www.devoteam.com</td>
<td>Trying to get into OpenSim code for now. Particularly interrested in data persistence. blog (Hello, Avatar!): http://lslblog.free.fr</td>
</tr>
<tr>
<td>[[daTwitch]]</td>
<td>James G. Stallings II</td>
<td> Lazarus Longstaff</td>
<td>Hiro Protagonist (OSGrid)</td>
<td>-5</td>
<td>House Husband</td>
<td>OSGrid Region owner, OSGrid Operator, Forum Admin, sometime wiki editor</td>
</tr>

<tr>
<td>gryc</td>
<td>Gryc Ueusp</td>
<td>Gryc Uriza</td>
<td>Gryc Uriza(OSGrid)</td>
<td>-6</td>
<td></td>
<td>PHP scripting, web interfaces, interconnectivity, cross-platformedness</td>
</tr>

<tr>
<td>[[User:Phrearch|Phrearch]]</td>
<td>Jeroen van Veen</td>
<td>Phrearch Miles</td>
<td>Phrearch Miles(OSGrid)</td>
<td>Amsterdam/Paris</td>
<td></td>
<td>Documentation, scripts(perl/lsl), RIA(flex) mashup, testing</td>
</tr>

<tr>
<td>[[User:Burnman|Burnman]]</td>
<td>Allen Wilkins</td>
<td>Burnman Bedlam</td>
<td>Sid Green (United Grid)</td>
<td>Boston, USA</td>
<td>United Grid</td>
<td>Testing, testing, and more testing! Getting familiar with the source, interested in all aspects of the project.</td>
</tr>

<tr>
<td>[[User:krisbfunk|krisbfunk]]</td>
<td>Kris Bulman</td>
<td>krisbfunk Vought</td>
<td>Krisbfunk Nocturnal(OSGrid)</td>
<td>PE, Canada (-4)</td>
<td>Edactive Technologies NocturnalEye Productions UPEI</td>
<td>Currently: Testing, bug reports, wiki updating, building on OSGrid</td>
</tr>

<tr>
<td>[[User:HashBox|HashBox]]</td>
<td>Zane Ashby</td>
<td>Sibariel Darkstone</td>
<td>Sibariel Darkstone (OSGrid)</td>
<td>New Zealand (+12)</td>
<td></td>
<td>Testing, bug reports, and updating the wiki.</td>
</tr>

<tr>
<td>[[User:Kinoc|Kinoc]]</td>
<td>Kino Coursey</td>
<td>Daxxon Jaxxon</td>
<td>Daxxon Kinoc (OSgrid)</td>
<td>-6</td>
<td>Daxtron Laboratories http://www.daxtron.com University of North Texas</td>
<td>AI, Semantic web, Ontologies, Natural Laanguage Processing, Cyc, Bots, NPC </td>
</tr>
<tr>
<td>[[User:trapuh|trapuh]]</td>
<td>Pedro Ribeiro</td>
<td>Vaiten Forder</td>
<td></td>
<td>GMT</td>
<td>University Student, Escola Superior de Educação de Viseu, Portugal </td>
<td>Testing, eventual bug reports and wiki. Music, web/digital arts and php+sql.</td>
</tr>
<tr>
<td>[[User:SonicViz|SonicViz]]</td>
<td>Paul Cohen</td>
<td>Komuso Tokugawa</td>
<td></td>
<td>+9</td>
<td>Http://sonicviz.com</td>
<td>Audio/Music, Interactive Music, Control Protocols, Interfaces, VisualFX, Procedural animation/Generative systems + testing and general dev</td>
</tr>
<tr>
<td>[[User:Mokele|mokele]]</td>
<td>Scott Norman</td>
<td>Mokelembembe Mokeev</td>
<td></td>
<td>-8 (Southern California)</td>
<td>Web Developer (PHP and MySQL)</td>
<td>Interested in seeing running on PowerPC Macs which it is. So, when I can, I'll compile and test on PowerPC Mac (PowerBook G4) and submit reports and then update the wiki if need on installing on Mac. Also have a Ubuntu 7.10 server that I can do testing on too.</td>
</tr>

<tr>
<td>[[User:devalnor|devalnor]]</td>
<td>Devalnor</td>
<td>M. Watkin</td>
<td></td>
<td>+1 (Belgium)</td>
<td></td>
<td>Small Patch code, bug reports, and updating the wiki.</td>
</tr>

<tr>
<td>[[User:Ezekiel|Ezekiel]]</td>
<td>Ezekiel</td>
<td>Ezekiel Zabelin</td>
<td></td>
<td>+1 </td>
<td>http://www.yosims.com </td>
<td>Concepts, business aspects of virtual worlds - web developer (PHP, MySQL, Javascript, LSL) </td>
</tr>

<tr>
<td>[[User:Diva|diva]]</td>
<td>Crista Lopes</td>
<td>Diva Canto</td>
<td>Diva Canto or Crista Lopes in as many grids as possible</td>
<td>-8 </td>
<td>UC Irvine and http://metaverseink.com </td>
<td>Search, general architecture</td>
</tr>

<tr>
<td>[[User:Buggmaster|Buggmaster]]</td>
<td>Mike D</td>
<td>Bug Master</td>
<td>None</td>
<td>-8 </td>
<td>http://www.adultmetaverse.com</td>
<td>Grid, Data/Web PHP/PERL/MySQL</td>
</tr>

<tr>
<td>[[User:Nixnerd|nixnerd]]</td>
<td>Richmund</td>
<td>Dangerously Moody</td>
<td>None</td>
<td>GMT </td>
<td>http://www.integratedtechnologies.eu</td>
<td>Cross Platform Testing, Feedback, Bug Reporting</td>
</tr>

<tr>
<td>[[User:Mohax|mohax]]</td>
<td>Mo Hax</td>
<td>Mo Hax</td>
<td></td>
<td>-5 Eastern</td>
<td>IBM</td>
<td>Testing, Feedback, Content Contributions, Bug Reporting, Documenting, Development</td>
</tr>

</table>
[[Category:Main]]
[[Category:Development]]

Build Instructions

2008-04-24T14:48:22Z

MoHax: Added build steps for RedHat

[[Category:Users]]
=Installing from source=

==Download from SVN==
Check out the [[Download]] Section

==MS Windows==

OpenSim requires either the .Net framework version 2.0, or the latest Mono. It supports the following compilers:
* [http://msdn2.microsoft.com/en-us/express/aa700756.aspx Microsoft Visual C# Express Edition] (note: not Visual C++)
* [http://www.mono-project.com/ mono]

Note for people who just downloaded the sources from http://dist.opensimulator.org/ (the "Downloads" link on the left) be advised that some important things are missing (like MySQL template scripts). For such features, you must download using svn!

=== Building ===

* In the top-level directory, run the '<tt>runprebuild.bat</tt>' file. This will create both a VS2005 solution file, and a nant build file.
* Open the resulting sln file with visual studio, and build it there, or if you prefer to use nant, run nant in the same top-level directory. This will build the executables.

If you don't care about physics (walking on prims, etc), ignore the rest of this section.

==== Physics ====

===== Open Dynamics Engine (ODE) =====
If you want to implement collision-based physics, OpenDynamicsEngine (ODE) is the furthest along at the moment (9/07). It is not fully supported, but is starting to work somewhat reliably using a small number of regions per sim.

As installed from svn, ODE does not work on all platforms. If you get an ODE-related crash, and/or an ode.dll not found type of error (which can occur even though the dll is present!), try to build ode from source, follow the directions on [[PhysicsEngines]].

Be sure you don't already have a system library version of libode.so that's being used instead of the one in the bin folder of your opensimulator distribution

=== Running ===

Recent versions of OpenSim come without an <tt>OpenSim.ini</tt> file. Copy the <tt>OpenSim.ini.example</tt> file to <tt>OpenSim.ini</tt> before making any changes.

Double-click on the <tt>OpenSim.exe</tt> executable file in the <tt>bin</tt> directory. This will start up OpenSim in standalone mode.

The debugger in VS2005 C# may be used to step through the code. For those that use a Cygwin shell, you may find that one or more dll's have permissions that cause problems running. Most find that a "<tt>chmod 777 *</tt>" from the <tt>bin</tt> directory solves this.

Physics can be invoked by adding the appropriate line to the [Startup] section of <tt>OpenSim.ini</tt>. For ODE, that would be:

physics = OpenDynamicsEngine

You can also add a command line option to a shortcut, or run from a command prompt with:

-physics=OpenDynamicsEngine

'''''Windows Vista'''''

To run on Windows Vista, you must first disable Windows Firewall. Under the new "Start" button of Vista, select "Control panel". Then double-click "Windows Firewall". In the window that pops up, on the left column, select "Turn Windows Firewall on or off". You will have to give permission for this to run, then select the option "Off (not recommended)". Click "OK" and exit from the Windows Firewall window.

If you have McAfee SecurityCenter, see the description below.

Once all the security features are disabled, right click on <tt>OpenSim.exe</tt> and select "Run as administrator". This will pop up a window asking permission, select "Allow". Your OpenSim server should run in a DOS-like window and accept connections.

'''''McAfee Security'''''

McAfee Security does not allow applications to listen on ports not explicitly specified. You have two options: 1) disable firewall protection all together, 2) enable <tt>OpenSim.exe</tt> to be able to open ports.

''Disable firewall''

Open McAfee SecurityCenter. Select "Internet & Network". In the lower left corner is a small link to "Configure...". Select this. In the right side of the window, select the bar that says "Firewall protection is enabled". Here you can select "Off".

''Enable <tt>OpenSim.exe</tt> to open ports''

Open McAfee SecurityCenter. Select "Internet & Network". In the lower left corner is a small link to "Configure...". Select this. In the right side of the window, select the bar that says "Firewall protection is enabled". Select the "Advanced..." button. This will pop up a new window.

In the new window, on the left side, select "Program Permissions." In the middle on the right side of the window, select the "Add Allowed Program" button. Use the browser that pops up to find the OpenSim executable and select it.

Finally, select "OK" and exit the McAfee SecurityCenter window.

==Linux/Mac OS X/FreeBSD==

Please note that the current (as of 2007-11-23) SVN will not work on 64bit linux systems when built. You will need to use the binary build further down the page.
[[Installing and running on x86-64]]

===Building===

Steps to get packages that are needed to compile the source.

'''FreeBSD 6.2'''
su
cd /usr/ports/devel/subversion/ && make install clean (you may also need to rebuild apr-svn if this step fails)
cd /usr/ports/lang/mono/ && make install clean
cd /usr/ports/devel/nant/ && make install clean
cd /usr/ports/databases/sqlite3/ && make install clean
cd /usr/ports/x11-toolkits/libgdiplus/ && make install clean
cd /opensim/installation/directory/
svn co http://opensimulator.org/svn/opensim/trunk opensim
cd opensim
./runprebuild.sh
nant

Note: [http://opensimulator.org/wiki/OpenSim:FAQ#System.DllNotFoundException:_..2Flibopenjpeg-libsl-2.1.2.0.so|Follow the instructions on the FAQ to fix the]
"System.DllNotFoundException: ./libopenjpeg-libsl-2.1.2.0.so" issue, but use "gmake" instead of "make"

For ODE Physics you must do the following:
cd /usr/ports/graphics/libGL/ && make install clean
cd /usr/ports/graphics/libGLU/ && make install clean
cd /opensim/installation/directory/
svn co http://opensimulator.org/svn/opensim-libs/trunk opensim-libs
cd opensim-libs/unmanaged/OpenDynamicsEngine2/
sh autogen.sh
./configure --enable-shared --enable-release --disable-demos
make
mv ./ode/src/libode.so /opensim/installation/directory/opensim/bin/

'''Ubuntu 7.10'''
sudo aptitude install subversion nant mono mono-gmcs libmono-microsoft8.0-cil libmono-system-runtime2.0-cil
svn co http://opensimulator.org/svn/opensim/trunk opensim
cd opensim
./runprebuild.sh
nant

* The above steps are for just running OpenSim. If you want to use MySQL either install during the installation process or install later. For development you'll need to install gcc, gc++, and whatever other modules are needed.
* The above steps work on running OpenSim 0.4 on Ubuntu Server 7.10. I did a new install and everything worked fine for me. During the installation process I had Ubuntu install MySQL. --[[User:Mokele|Mokele]] 11:41, 9 February 2008 (PST)

'''openSUSE 10.3'''

Install an openSUSE 10.3 with its default options, add the online repositories
when finished installing do an online update with all the latest packages.

In yast install these packages, for running Opensim in standalone mode.
subversion (1.4.4)
nant (0.85)
mono-jscript
- check that mono-core is installed

* optional mysql - for Opensim running in Grid mode:
Install these mysql packages via yast
mysql
mysql-client
mysql-administrator
mysql-gui-tools
mysql-query-browser

Before building create the mysql database.
/etc/init.d/mysql start
mysql -u root -p -h localhost
(when asked for password just hit enter)

mysql> create database opensim;
mysql> quit

set the configuration in bin/mysql_connection.ini

Build after installation of above in bash terminal.

su -
svn co http://opensimulator.org/svn/opensim/trunk opensim
cd opensim
./runprebuild.sh
nant

After this you should be able to continue on starting the diffrent Servers, look in the mysql-config section.

'''Mac OS X 10.5/10.4'''
* OpenSim is now working on PowerPC Macs! Thanks to DrScofield and those who helped him. Current nightly builds for PowerPC are not working, not sure about Intel so use the 0.5 Build. OpenSim works on Intel Macs. I'm testing on PowerBook G4. Tested these step on 10.5, but not 10.4 but should work --[[User:Mokele|Mokele]] 22:36, 14 February 2008 (PST)
* Install XCode Developers Tools from DVD/CD Installation Disk or download from http://developer.apple.com/. You have to create an Apple account to access the downloads if you don't have an Apple account.
* Install X11 for 10.4 from the Optional Install from the DVD/CD Installation Disk. X11 for 10.5 is installed by default.
* Install Mono 1.2.5 from http://ftp.novell.com/pub/mono/archive/1.2.5/macos-10-universal/5/MonoFramework-1.2.5_5.macos10.novell.universal.dmg and in Terminal or X11 edit the .profile file and add the following line:
export PKG_CONFIG_PATH="/Library/Frameworks/Mono.framework/Versions/1.2.5/lib/pkgconfig/:${PKG_CONFIG_PATH}"
* Compile OpenSim
svn co http://opensimulator.org/svn/opensim/tags/0.5.0-release opensim
cd opensim
./runprebuild.sh
nant

* Download and Compile libopenjpeg-libsl-2.1.2.0.dylib and libsecondlife.dll
* libopenjpeg-libsl-2.1.2.0.dylib:
svn co http://opensimulator.org/svn/opensim-libs/libsl1550 opensim-libs
cd opensim-libs/openjpeg-libsl
make -f Makefile.osx
cp libopenjpeg-libsl-2.1.2.0.dylib ../../opensim/bin
* Note: The Makefile that creates the libopenjpeg-libsl-2.1.2.0.so does not compile on PowerPC, not sure about Intel. Looks like a gcc issue with compile options.

* libsecondlife.dll: (for PowerPC Only, see details on this step [http://xyzzyxyzzy.net/2008/02/12/installing-opensim-on-powerpcor-of-eggs-and-virtual-worlds installing OpenSim on PowerPC…or: of eggs and virtual worlds])
cd .. (back into opensim-libs)
nant
cp libsecondlife.dll ../../opensim/bin

* Edit the libsecondlife.dll.config (PowerPC Only). Remove the cpu="x86" tag in the last dllmap line.

'''RedHat'''
sudo vi /etc/yum.repos.d/mono.repo

[mono]
name=Mono for rhel-4-i386 (stable)
baseurl=http://ftp.novell.com/pub/mono/download-stable/rhel-4-i386/
enabled=1
gpgcheck=0

sudo yum install mono-complete monodoc-core nant
svn co svn co http://opensimulator.org/svn/opensim/trunk opensim
cd opensim
./runprebuild.sh
nant

=== Physics ===
If you want to implement collision-based physics, OpenDynamicsEngine (ODE) is the furthest along at the moment (9/07). It is not fully supported, but is starting to work somewhat reliably using a small number of regions per sim.

==== Open Dynamics Engine (ODE) ====
As installed from svn, ODE does not work on all platforms. If you get an ODE-related crash, and/or a libode.so not found type of error, you will need to build libode from source.

Remove <tt>libode.so</tt> from the <tt>./bin</tt> folder. (Note that subsequent svn updates may replace it again; best fix is to copy your built <tt>libode.so</tt> to <tt>bin</tt>). Do NOT remove <tt>ode.net.dll</tt>! Download the latest source packages from http://www.ode.org/. When compiling, make sure to use the following configure options:

--with-trimesh=gimpact
--enable-shared

Make sure the configure script confirms these choices, and always compile with single precision (I believe that's the default). Try <code> make -k </code> if you get errors relating to drawstuff, test*, or openGL. <code> make install </code> should put <tt>libode.so</tt> in the proper place (usually <tt>/usr/local/lib</tt>), and it should be seen by opensim (<tt>ode.net.dll</tt>)

===Running===
Recent versions of OpenSim come without an <tt>OpenSim.ini</tt> file. Copy the <tt>OpenSim.ini.example</tt> file to <tt>OpenSim.ini</tt> before making any changes.
cd bin
mono OpenSim.exe

* To invoke ODE, add the option:
-physics=OpenDynamicsEngine
to the <tt>mono OpenSim.exe</tt> line

or add <code> physics = OpenDynamicsEngine </code> to the [Startup] section of <tt>OpenSim.ini</tt>. Same deal for other physics engines, when available.

On mono 1.2.6, some distributions may see
Unhandled Exception: System.NotSupportedException: CodePage 1252 not supported
on startup when using mysql. This can be resolved by installing the package libmono-i18n2.0-cil (see http://bugs.mysql.com/bug.php?id=33938).

===Dependencies===
The following packages and their dependencies are required to run OpenSim on a default Debian 4 netinstall:
* mono
* libmono-corlib2.0-cil
* libmono-sqlite2.0-cil
* libmono-system-web2.0-cil
* libmono-microsoft8.0-cil
* libmono-system-runtime2.0-cil
[[Category:Users]]