<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Actually, had I been informed of a fix (rev or patch) to that bug, I (or you, or we) could have put it into 0.6.3-post-fixes and poked people to 'update' that branch. Would probably had gone some way.<BR><BR>
In tortoise, It's really simple to merge a certain revision to another wc. Right-click on trunk, choose log, locate the rev, right click on the rev, choose 'merge revision to...' and locate the post-fixes wc (you need them both checked out) and press 'ok'. It will merge the rev into the post-fixes, taking the history of both branches into account when auto-merging.<BR>
<BR>
You might experience conflicts, but in a surprising number of cases you wont.<BR>
<BR>Best regards,<BR>Stefan Andersson<BR>Tribal Media AB<BR><BR><BR><BR> <BR>
<HR id=stopSpelling>
From: adam@deepthink.com.au<BR>To: opensim-users@lists.berlios.de<BR>Date: Wed, 1 Apr 2009 21:36:11 -0400<BR>Subject: Re: [Opensim-users] Safe use of OpenSim - was "Fw: Re: [SLED] Linden Lab Sells Second Life!"<BR><BR>
<STYLE>
.ExternalClass p.EC_MsoNormal, .ExternalClass li.EC_MsoNormal, .ExternalClass div.EC_MsoNormal
{margin-bottom:.0001pt;font-size:12.0pt;font-family:'Times New Roman','serif';color:black;}
.ExternalClass a:link, .ExternalClass span.EC_MsoHyperlink
{color:blue;text-decoration:underline;}
.ExternalClass a:visited, .ExternalClass span.EC_MsoHyperlinkFollowed
{color:purple;text-decoration:underline;}
.ExternalClass pre
{margin-bottom:.0001pt;font-size:10.0pt;font-family:'Courier New';color:black;}
.ExternalClass span.EC_HTMLPreformattedChar
{font-family:Consolas;color:black;}
.ExternalClass span.EC_EmailStyle19
{font-family:'Calibri','sans-serif';color:#1F497D;}
.ExternalClass .EC_MsoChpDefault
{font-size:10.0pt;}
@page Section1
{size:612.0pt 792.0pt;}
.ExternalClass div.EC_Section1
{page:Section1;}
</STYLE>
<DIV class=EC_Section1>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">My advice would be run both.</SPAN></P>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"> </SPAN></P>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">We don’t up the protocol version too often – so there’s nothing stopping you from running a handful of regions at trunk, and the remainder on stable. If you have customers involved, while we appreciate the feedback – I would probably say stick with stable there. </SPAN></P>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"> </SPAN></P>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">For your own testing purposes, running trunk isn’t a bad option – and it also gives you the flexibility that if something is broken majorly, you still have all your stable regions.</SPAN></P>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"> </SPAN></P>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">To be fair, the 0.6.3 release was not fantastic – the avatar bug should have probably been fixed before that was tagged. I think in future that complaint has registered pretty soundly and releases might be more thoroughly tested through release candidates.</SPAN></P>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"> </SPAN></P>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'">Adam</SPAN></P>
<P class=EC_MsoNormal><SPAN style="FONT-SIZE: 11pt; COLOR: #1f497d; FONT-FAMILY: 'Calibri','sans-serif'"> </SPAN></P>
<DIV style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0cm; BORDER-LEFT: blue 1.5pt solid; PADDING-TOP: 0cm; BORDER-BOTTOM: medium none">
<DIV>
<DIV style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0cm; BORDER-TOP: #b5c4df 1pt solid; PADDING-LEFT: 0cm; PADDING-BOTTOM: 0cm; BORDER-LEFT: medium none; PADDING-TOP: 3pt; BORDER-BOTTOM: medium none">
<P class=EC_MsoNormal><B><SPAN lang=EN-US style="FONT-SIZE: 10pt; COLOR: windowtext; FONT-FAMILY: 'Tahoma','sans-serif'">From:</SPAN></B><SPAN lang=EN-US style="FONT-SIZE: 10pt; COLOR: windowtext; FONT-FAMILY: 'Tahoma','sans-serif'"> opensim-users-bounces@lists.berlios.de [mailto:opensim-users-bounces@lists.berlios.de] <B>On Behalf Of </B>John Sheridan<BR><B>Sent:</B> Wednesday, 1 April 2009 6:32 PM<BR><B>To:</B> opensim-users@lists.berlios.de<BR><B>Subject:</B> Re: [Opensim-users] Safe use of OpenSim - was "Fw: Re: [SLED] Linden Lab Sells Second Life!"</SPAN></P></DIV></DIV>
<P class=EC_MsoNormal> </P>
<P class=EC_MsoNormal>Holy blog wars Batman! I can see emotions are running high, so I thread lightly while writing this... <BR><BR>For around six months now since I and my cohorts started building out our grid we've been more or less running off of the trunk. We have a weekly update process wherein every Sunday after the commit emails stop flying by I'll shut down, back up, then update everything to that Sunday's SVN. After the update is complete I'll go around in world, try a few tests to make sure that everything is in one piece and that basic functionality is there. So far there have only been a handful of times that I've had to cancel or roll back an update due to broken functionality or warnings on the mailing lists that heavy changes were taking place. <BR><BR>As far as data and content are concerned, we all realize that this is alpha software and that certain instabilities may exist from week to week. So far we've not had any major disasters as far as data and content save a few mangled, non-persisting, or overly persisting (where they won't go away) prims. However in most cases workarounds were available and all users were told how to go about utilizing them. As an added measure, just in case we rely on the weekly backups as well periodic dumps of our sims into OAR files. <BR><BR>My primary reason for choosing this sort of procedure is so that while we are building, creating, and using the grid we can also contribute back to OpenSim in the form of bug reports and feedback. (See a draft copy of our community standards for more on this: <A href="http://www.pseudospace.net/joomla/index.php?option=com_content&view=article&id=56&Itemid=60">http://www.pseudospace.net/joomla/index.php?option=com_content&view=article&id=56&Itemid=60</A>)<BR><BR>Regardless, we do consider our setup to be in quasi-production regardless of whatever minor glitches exist within the trunk. As well, we are sure to make it quite clear to the few users that we do have (albeit not many as we do not yet have any completed or usable environments other then Ellis) that both OpenSim as the underlying software and Pseudospace as the service itself are under heavy development and could be unstable at times. <BR><BR>Now as a software developer myself (albeit in a completely different realm then OpenSim as I do small scale database / windows apps) I can understand the risks of running untested software for production uses, however in this case I'm unsure as how to proceed. We like contributing back to the community in whatever way we can, and also enjoy testing or riding the bleeding edge of the wave, yet after reading the prior posts I'm suddenly not sure if simply backing up, exporting, and rolling back is as safe as I thought. From the standpoint of those who develop OpenSim, would you guys say what I'm doing is safe?<BR><BR>Thanks and good karma to you all,<BR><BR> - John Sheridan / Orion Pseudo<BR><BR>Frisby, Adam wrote: </P><PRE>Honestly, I think there's some disconnects between people here that need to be addressed.</PRE><PRE> </PRE><PRE>There are several different audiences here, and consequently several different reactions. There is the group of users attempting to put OpenSim into production environments - the harsher reactions I have seen tend to fall into this group. There is home users and hobbyists - the more positive reactions are from there.</PRE><PRE> </PRE><PRE>To the production users, we do as a team find it unfortunate you were badly impacted, however as a group a large portion of work on OpenSim comes from personal developers without sponsorship. As a team, we also make absolutely no guarantees about trunk releases at all (infact we often make the opposite), the best practices we publish on our website very clearly state that production users should stick to a tagged release, and even then you are operating alpha code.</PRE><PRE> </PRE><PRE>While we have generally been blessed with a reasonably well written and maintained codebase - trunk is not guaranteed to operate. Had there been an accident and the database became corrupted over time due to coding error - the outrage on this list would not have been as loud, however the impacts would have been significantly worsened.</PRE><PRE> </PRE><PRE>Often, developers need to break code and features in order to improve things, if we cannot make trunk unstable, then the ability to develop and continually improve the codebase is restricted. One recent example was some avatar appearance issues that showed up after the MXP stack - that one I caused by removing code which erroneously assumed an avatar utilized the LLUDP Stack.</PRE><PRE> </PRE><PRE>The short term result of that change was it broke avatar appearance in certain circumstances for a period of about 24 hours, the long term result was we got one step closer to more protocols, more neutrality and abstracted behaviour - all seen as good things to the codebase -- however another example of why we do not recommend anyone utilize trunk for production - it was still broken for a day, and this is a regular occurance.</PRE><PRE> </PRE><PRE>For instance, a patch not too long ago adjusted the asset database format - while fine on local systems with small asset counts, in a production environment (specifically osgrid), it caused the entire database to melt. OSGrid accepts that risk since they are a testing grid - but to another operator, you would have applied that same patch just as easily as osgrid did if today's example is the norm.</PRE><PRE> </PRE><PRE>Now the first response, I expect will be 'this was deliberate/vandalism' - yes there was an april fools joke in the codebase. However, please consider the following:</PRE><PRE> </PRE><PRE>* The impact was for the most part completely negligible - no permanent changes were made, the code deactivates automatically, a patch is available on mantis (and is no longer in trunk anyway).</PRE><PRE>* You are running a version of the codebase that is *explicitly marked as 'not suitable for production'*.</PRE><PRE>* You are receiving a product for free under an extremely liberal license on behalf of the generosity of others.</PRE><PRE> </PRE><PRE>That april fools joke was /only ever accessible in the developers and testers oriented release/. The intended audience was those two groups - developers and testers. Even the release candidate version had the offending code removed.</PRE><PRE> </PRE><PRE>If you want to put OpenSim into production, fantastic - we like to see it being used. However when you then do not follow the advice we post clearly on the website in multiple places and put trunk into production, then no - the responsibility for failure rests upon your shoulders - trunk is /not safe for production/.</PRE><PRE> </PRE><PRE>We do recognize the growing corporate demand for OpenSim - it's one of the reason that people such as Stefan have begun a back-patches version (post-fixes) which incorporates fixes into the last stable version. We spend the time maintaining that version because we recognise the need, it's also the reason we have been as a group moving towards more release-oriented packaging such as the installers and other easy-to-deploy packages.</PRE><PRE> </PRE><PRE>If you are a corporate user putting OpenSim into production, make sure you have the following preparations:</PRE><PRE> </PRE><PRE>1. Have a stable revision handy - currently that is 0.6.3-postfixes. Sometimes bugs show up randomly and break things badly. You should always have a backup system when working with OpenSim.</PRE><PRE> </PRE><PRE>2. Use our postfix releases normally - sometimes a feature patch is very tempting to upgrade to, but then ask yourself what the cost might be? If stick figure avatars are going to cause you to have issues with clients - ask yourself what random object destruction might cause. It's happened in the past on trunk - I have no doubts major unintended bugs will sneak into trunk in future.</PRE><PRE> </PRE><PRE>Only upgrade past post-fixes if you keep a very keen eye on SVN commit logs and are capable of testing hardened revisions.</PRE><PRE> </PRE><PRE>3. Keep backups. Too many OpenSim installs do not do this. OAR works well for content, however a full database backup is recommend (this varies from tool to tool, know your system.)</PRE><PRE> </PRE><PRE>4. Slow and steady is the name of the game. We actually keep several of our clients on a r6XXX release since we're able to confirm it works for their uses in the majority of cases and doesn't have unknown factors.</PRE><PRE> </PRE><PRE>Regards,</PRE><PRE> </PRE><PRE>Adam</PRE><PRE> </PRE><PRE> </PRE><PRE> </PRE>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt"><PRE>-----Original Message-----</PRE><PRE>From: <A href="mailto:opensim-users-bounces@lists.berlios.de">opensim-users-bounces@lists.berlios.de</A> [<A href="mailto:opensim-users">mailto:opensim-users</A>-</PRE><PRE><A href="mailto:bounces@lists.berlios.de">bounces@lists.berlios.de</A>] On Behalf Of Teravus Ovares</PRE><PRE>Sent: Wednesday, 1 April 2009 2:57 PM</PRE><PRE>To: <A href="mailto:opensim-users@lists.berlios.de">opensim-users@lists.berlios.de</A></PRE><PRE>Cc: <A href="mailto:jonathangreenlee@yahoo.com">jonathangreenlee@yahoo.com</A></PRE><PRE>Subject: Re: [Opensim-users] Fw: Re: [SLED] Linden Lab Sells Second</PRE><PRE>Life!</PRE><PRE> </PRE><PRE>One more reply to this. Have a look at some positive responses.</PRE><PRE> </PRE><PRE><A href="http://osgrid.org/forums/viewtopic.php?f=14&t=1051&start=10">http://osgrid.org/forums/viewtopic.php?f=14&t=1051&start=10</A></PRE><PRE> </PRE><PRE>Sincrerely</PRE><PRE> </PRE><PRE>Teravus</PRE><PRE> </PRE><PRE>On 4/1/09, Teravus Ovares <A href="mailto:teravus@gmail.com"><teravus@gmail.com></A> wrote:</PRE><PRE> </PRE>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt"><PRE>Now now, lets be reasonable. It's one thing to get April fooled..</PRE><PRE> it's another to gloat about it. Generally, I don't think it's a</PRE><PRE> </PRE></BLOCKQUOTE><PRE>good</PRE><PRE> </PRE>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt"><PRE>idea to gloat. It is what it is .. and we learn and continue on.</PRE><PRE> </PRE><PRE>Sincerely</PRE><PRE> </PRE><PRE>Teravus</PRE><PRE> </PRE><PRE> </PRE><PRE>On 4/1/09, Skidz Tweak <A href="mailto:skidz.tweak@gmail.com"><skidz.tweak@gmail.com></A> wrote:</PRE><PRE> </PRE>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt"><PRE>Don't let the door hit you in the butt!</PRE><PRE>Everyone bitching about this only has theirselves to blame!</PRE><PRE>If you can't live with that fact, keep making up crap in your head</PRE><PRE> </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE>saying it</PRE><PRE> </PRE>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt">
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt"><PRE>was someone else fault. That's it... the sweet feel of denial.</PRE><PRE> </PRE><PRE>-----Original Message-----</PRE><PRE>From: <A href="mailto:opensim-users-bounces@lists.berlios.de">opensim-users-bounces@lists.berlios.de</A></PRE><PRE>[<A href="mailto:opensim-users-bounces@lists.berlios.de">mailto:opensim-users-bounces@lists.berlios.de</A>] On Behalf Of</PRE><PRE> </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE>Jonathan</PRE><PRE> </PRE>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt">
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt"><PRE>Greenlee</PRE><PRE>Sent: Wednesday, April 01, 2009 4:07 PM</PRE><PRE>To: <A href="mailto:opensim-users@lists.berlios.de">opensim-users@lists.berlios.de</A></PRE><PRE>Subject: Re: [Opensim-users] Fw: Re: [SLED] Linden Lab Sells Second</PRE><PRE> </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE>Life!</PRE><PRE> </PRE>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt">
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt"><PRE> </PRE><PRE>I want to make sure you understand why my company is now</PRE><PRE> </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE>withdrawing our</PRE><PRE> </PRE>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt">
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt"><PRE>good will and support toward OpenSim,</PRE><PRE>And why we are withdrawing our financial support from several</PRE><PRE> </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE>OpenSim Grids</PRE><PRE> </PRE>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt">
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt"><PRE>we were supporting with our business.</PRE><PRE> </PRE><PRE>--- On Wed, 4/1/09, MW <A href="mailto:michaelwri22@yahoo.co.uk"><michaelwri22@yahoo.co.uk></A> wrote:</PRE><PRE> </PRE><PRE> </PRE>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt"><PRE>From: MW <A href="mailto:michaelwri22@yahoo.co.uk"><michaelwri22@yahoo.co.uk></A></PRE><PRE>Subject: Re: [Opensim-users] Fw: Re: [SLED] Linden Lab Sells</PRE><PRE> </PRE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE><PRE>Second Life!</PRE><PRE> </PRE>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt">
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt">
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt"><PRE>To: <A href="mailto:opensim-users@lists.berlios.de">opensim-users@lists.berlios.de</A></PRE><PRE>Date: Wednesday, April 1, 2009, 4:03 PM</PRE><PRE>While</PRE><PRE>Teravus did the april 1st joke, all of core (or certainly</PRE><PRE>most of it) knew about it. And we fully supported him</PRE><PRE>applying it. As he said it was never in a tagged version.</PRE><PRE> </PRE><PRE>--- On Wed, 1/4/09, Teravus Ovares</PRE><PRE><A href="mailto:teravus@gmail.com"><teravus@gmail.com></A> wrote:</PRE><PRE>From: Teravus Ovares</PRE><PRE><A href="mailto:teravus@gmail.com"><teravus@gmail.com></A></PRE><PRE>Subject: Re: [Opensim-users] Fw: Re: [SLED] Linden Lab</PRE><PRE>Sells Second Life!</PRE><PRE>To: <A href="mailto:jonathangreenlee@yahoo.com">jonathangreenlee@yahoo.com</A>,</PRE><PRE><A href="mailto:opensim-users@lists.berlios.de">opensim-users@lists.berlios.de</A></PRE><PRE>Date: Wednesday, 1 April, 2009, 9:59 PM</PRE><PRE> </PRE><PRE>FYI, the avatar stick bug April 1 joke was my idea.</PRE><PRE> </PRE><PRE>Also, I think it's really important to note that all of</PRE><PRE>the developers</PRE><PRE>of OpenSimulator have, since day one told people to avoid</PRE><PRE>SVN for</PRE><PRE>something that is production. That includes anything that</PRE><PRE> you want</PRE><PRE>to work.</PRE><PRE> </PRE><PRE>April 1st is a tradition in OpenSimulator and on April 1st</PRE><PRE>a sense of</PRE><PRE>humor is required when using SVN. We made sure that all</PRE><PRE>releases and</PRE><PRE>tags did *not* have the April fool's joke in it for</PRE><PRE>this very reason.</PRE><PRE> We make releases and tag revisions not for our benefit,</PRE><PRE>but for</PRE><PRE>yours.</PRE><PRE> </PRE><PRE>I know some people on this list don't spend time on</PRE><PRE>IRC, however, it's</PRE><PRE>been hinted upon since February that there would likely be</PRE><PRE>an April</PRE><PRE>fool's joke there. For those that argue that most</PRE><PRE>people don't sit in</PRE><PRE>IRC, see two paragraphs up.</PRE><PRE> </PRE><PRE>Now, if despite our warnings and hints, you continued to</PRE><PRE>use SVN, then</PRE><PRE>likely your avatar were stick-bugged.</PRE><PRE> </PRE><PRE>I reiterate what has been said all along. Direct SVN</PRE><PRE>revisions are</PRE><PRE>risky. They've always been, and it's always bad</PRE><PRE>practice to use them</PRE><PRE>unless you've thoroughly looked them over. A lot of</PRE><PRE>people thought</PRE><PRE>it was funny. The people who did not were in</PRE><PRE> the far minority.</PRE><PRE> </PRE><PRE> </PRE><PRE>Sincerely</PRE><PRE> </PRE><PRE>Teravus</PRE><PRE> </PRE><PRE> </PRE><PRE>On 4/1/09, Jonathan Greenlee</PRE><PRE><A href="mailto:jonathangreenlee@yahoo.com"><jonathangreenlee@yahoo.com></A> wrote:</PRE><PRE> </PRE>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt"><PRE> </PRE><PRE>This was funny.</PRE><PRE>Vandalising everyone's avatar was not.</PRE><PRE> </PRE><PRE> </PRE>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt"><PRE>On Wed, Apr 1, 2009 at 3:59 PM, S Collingwood</PRE><PRE> </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE><A href="mailto:collingwood.7@osu.edu"><collingwood.7@osu.edu></A></PRE><PRE> </PRE>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt">
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt"><PRE>wrote:</PRE><PRE>This is really BIG. A takeover! We can expect</PRE><PRE>panzer tanks rolling into shopping malls --</PRE><PRE> </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE>uniformed guards at sim</PRE><PRE>crossings</PRE><PRE> </PRE>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt">
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt"><PRE>-- dogs and cats living together -- it's the</PRE><PRE> </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE>END!!</PRE><PRE> </PRE>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt">
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt"><PRE>Linden Lab Sells Second Life!</PRE><PRE> </PRE>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt"><PRE> </PRE><PRE> </PRE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE></BLOCKQUOTE><PRE><A href="http://www.secondlifeupdate.com/news-and-stuff/linden-lab-sells">http://www.secondlifeupdate.com/news-and-stuff/linden-lab-sells</A>-</PRE><PRE> </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE>second-life/</PRE><PRE> </PRE>
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt">
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt">
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt">
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt">
<BLOCKQUOTE style="MARGIN-BOTTOM: 5pt"><PRE>--</PRE><PRE> </PRE></BLOCKQUOTE><PRE> </PRE><PRE> </PRE><PRE>_______________________________________________</PRE><PRE>Opensim-users mailing list</PRE><PRE><A href="mailto:Opensim-users@lists.berlios.de">Opensim-users@lists.berlios.de</A></PRE><PRE> </PRE><PRE> </PRE></BLOCKQUOTE><PRE> <A href="https://lists.berlios.de/mailman/listinfo/opensim-users">https://lists.berlios.de/mailman/listinfo/opensim-users</A></PRE><PRE> </PRE><PRE>_______________________________________________</PRE><PRE>Opensim-users mailing list</PRE><PRE><A href="mailto:Opensim-users@lists.berlios.de">Opensim-users@lists.berlios.de</A></PRE><PRE><A href="https://lists.berlios.de/mailman/listinfo/opensim-users">https://lists.berlios.de/mailman/listinfo/opensim-users</A></PRE><PRE> </PRE><PRE> </PRE><PRE> </PRE><PRE> </PRE><PRE> </PRE><PRE> </PRE><PRE>-----Inline Attachment Follows-----</PRE><PRE> </PRE><PRE>_______________________________________________</PRE><PRE>Opensim-users mailing list</PRE><PRE><A href="mailto:Opensim-users@lists.berlios.de">Opensim-users@lists.berlios.de</A></PRE><PRE><A href="https://lists.berlios.de/mailman/listinfo/opensim-users">https://lists.berlios.de/mailman/listinfo/opensim-users</A></PRE><PRE> </PRE><PRE> </PRE></BLOCKQUOTE><PRE> </PRE><PRE> </PRE><PRE>_______________________________________________</PRE><PRE>Opensim-users mailing list</PRE><PRE><A href="mailto:Opensim-users@lists.berlios.de">Opensim-users@lists.berlios.de</A></PRE><PRE><A href="https://lists.berlios.de/mailman/listinfo/opensim-users">https://lists.berlios.de/mailman/listinfo/opensim-users</A></PRE><PRE> </PRE><PRE>_______________________________________________</PRE><PRE>Opensim-users mailing list</PRE><PRE><A href="mailto:Opensim-users@lists.berlios.de">Opensim-users@lists.berlios.de</A></PRE><PRE><A href="https://lists.berlios.de/mailman/listinfo/opensim-users">https://lists.berlios.de/mailman/listinfo/opensim-users</A></PRE><PRE> </PRE><PRE> </PRE></BLOCKQUOTE></BLOCKQUOTE><PRE>_______________________________________________</PRE><PRE>Opensim-users mailing list</PRE><PRE><A href="mailto:Opensim-users@lists.berlios.de">Opensim-users@lists.berlios.de</A></PRE><PRE><A href="https://lists.berlios.de/mailman/listinfo/opensim-users">https://lists.berlios.de/mailman/listinfo/opensim-users</A></PRE><PRE> </PRE></BLOCKQUOTE><PRE>_______________________________________________</PRE><PRE>Opensim-users mailing list</PRE><PRE><A href="mailto:Opensim-users@lists.berlios.de">Opensim-users@lists.berlios.de</A></PRE><PRE><A href="https://lists.berlios.de/mailman/listinfo/opensim-users">https://lists.berlios.de/mailman/listinfo/opensim-users</A></PRE><PRE> </PRE>
<P class=EC_MsoNormal> </P></DIV></DIV></body>
</html>