DotNet Core on FreeBSD

Russell Haley russ.haley at gmail.com
Mon Sep 11 05:10:00 UTC 2017


Does anyone here run Unity? Unity is a very popular gaming engine that
is cross platform and provides a C# API.

https://en.wikipedia.org/wiki/Unity_(game_engine)

https://mellinoe.wordpress.com/2017/01/18/net-core-game-engine/

Kaboom! (Head exploded again. This is getting messy)

Russ

On Sun, Sep 10, 2017 at 10:03 PM, Russell Haley <russ.haley at gmail.com> wrote:
> On Sun, Sep 10, 2017 at 9:59 PM, Russell Haley <russ.haley at gmail.com> wrote:
>> Hey Marcin,
>>
>> So I just read the Contribution License Agreement and I didn't see
>> anything untoward.
>>
>> https://cla2.dotnetfoundation.org/cladoc/net-foundation-contribution-license-agreement.pdf
>>
>> Just remember all these projects are MIT, Apache 2 or CC license. I
>> think bringing this code into FreeBSD is a bonkers good idea. (Kaboom!
>> lolz). Especially if you think about how much proprietary code is out
>> there on Windows that people will want to protect. A FreeNAS style
>> management console would make FreeBSD a particularly attractive offer
>> over GPL licensed OSes for companies to create appliance style systems
>> (physical or virtual, a-la FreeNAS). Jails become yet another great
>> way to distribute proprietary code.
>>
>> Sony PS 3&4, NetApp and now Nintendo Switch are all great examples of
>> what you can do with FreeBSD in a proprietary system.
>>
>> Dot Net Core also opens up Arm based systems on FreeBSD in some ways
>> because it's specifically designed do be modular. I don't think Mono
>> has built on Arm for a long time and the performance of Mono has been
>> a problem of note.
>>
>> Russ
>
> I'm trying to perform due diligence because I want to throw some time
> into this. Avoiding GPL and other encumbering licenses is important to
> me. I had to know myself so I made this list of licenses:
>
> https://github.com/dotnet/csharplang - Microsoft
> https://github.com/dotnet/cli -
> https://www.microsoft.com/net/dotnet_library_license.htm
>
> https://github.com/dotnet/source-build - MIT
> https://github.com/dotnet/core-setup - MIT
> https://github.com/dotnet/corefx - MIT
> https://github.com/dotnet/coreclr - MIT
> https://github.com/dotnet/sdk - MIT
> https://github.com/dotnet/dotnet-docker - MIT
> https://github.com/dotnet/standard - MIT
> https://github.com/dotnet/sdk - MIT
> https://github.com/dotnet/netcorecli-fsc - MIT
>
> https://github.com/nuget/home - A2
> https://github.com/aspnet/home - A2
> https://github.com/dotnet/roslyn - A2
>
> https://github.com/aspnet/Docs - CC
> https://github.com/dotnet/docs - CC
>
> Russ
>
>> On Sun, Sep 10, 2017 at 8:52 AM, Russell Haley <russ.haley at gmail.com> wrote:
>>> Sorry for the top post,
>>>
>>> Marcin, can you expand on your thoughts about the contributor license? This has been one of the concerns of mine‎ (part of the pedanticism). I didn't get a chance to read the doc itself yet.
>>>
>>> Russ
>>>
>>> Sent from my BlackBerry 10 smartphone on the Virgin Mobile network.
>>>   Original Message
>>> From: Marcin Cieslak
>>> Sent: Sunday, September 10, 2017 1:13 AM
>>> To: Russell Haley
>>> Cc: David Naylor; Geoffrey Huntley; Freebsd-mono; freebsd-advocacy at freebsd.org; freebsd-ports at freebsd.org
>>> Subject: Re: DotNet Core on FreeBSD
>>>
>>> On Sun, 10 Sep 2017, Russell Haley wrote:
>>>
>>>> Hey guys,
>>>>
>>>> I am talking to Karel and Tomas at Microsoft's DotNet Core Team about
>>>> putting together a "proposal" for community involvement, which will be
>>>> followed by more information on this list. Most of the talk has been
>>>> me blowing air and being pedantic about nothing (I get excited and
>>>> type alot).
>>>
>>> I was tinkering around FreeBSD support when dotnet core was first published.
>>> Stack unwinding for exceptions was very hacky at the time, and there were
>>> some unnecessary discussions about how to implement some FreeBSD sepecific
>>> sysctl's. I got a bit frustrated with that (a whole porting effort is about
>>> coercing Unix to offer part of Win32 APIs).
>>>
>>> It was somewhat running on FreeBSD natively back then, haven't checked
>>> recently.
>>>
>>> I have also decided not to sign their bad contributor agreement
>>> and some of the sysctl code I decided to put in mono instead :)
>>>
>>> Marcin
>>> saper on github


More information about the freebsd-mono mailing list