Slashdot Mirror
Running .NET on FreeBSD?
Dan writes "Interesting read on running .NET on FreeBSD. Chip Morton thinks this could be very beneficial to FreeBSD or any OS to have a fully functional .NET CLR (Common Language Runtime) environment. With over 9,000 files, and including some 1300 public classes to pore through, the Shared Source CLI (Common Language Infrastructure) can teach you quite a bit about the internal workings of the CLR. This relevant MSDN article discusses some of the things you can learn from the source code facsimile of the CLR, like how JIT compilation works. One thing that the CLI specification does not mandate is that managed code has to run on Windows. To prove this point, Microsoft built the Shared Source CLI to compile and run on FreeBSD Unix as well as Windows XP."
And this is news because???? The article on MSDN was posted in July of 2002! Is there something new about Rotor on BSD that I am missing?
You can only run .net on BSD if you are emulating it under a licensed Windows .Net Server
Anyone else this there is going to be some kind of gotcha??
No I didnt spell check this post...
MS has finally decide to give back to the community after all these years of plunder, loot and pilllage out of *BSD. Good work!
Lucent made a product called Inferno
.NET should be but they aren't and it is
http://www.vitanuova.com/inferno
it virtualizes the whole of the OS, not just a few APIs
it had a graphics context as well
it hijacks the hosted environment, running in a window or runs natively on hardware either way they are the same.
Socket programming, pah who needs it, all we need are file descriptors and auto-selecting files
it's all there
the source code is only available for a fee
it's really what Java &
There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
Is because Microsoft needs FreeBSD to run Hotmail's backend.
Call me skeptical, but did occur to anyone else that Microsoft picked FreeBSD because
.NET. Here's why and here's why this is irrelevant.
1) they despise the GPL for what it represents and
2) Mono is being developed on Linux?
Don't get me wrong, I run several FreeBSD servers and prefer the ports system over RPM. It just unnerves me when the Microsoft marketing machine starts mucking around on my chosen platform.
As a postscript, you all should be aware that PHP may well become the best platform for deploying
http://tinyurl.com/4ny52
Next they will release the gcsp compiler.. for C#. sourceforge.NET will have a new meaning. Heck I even keep away from C++, building even GUIs with ANSI C 99 with function pointer arrays. Stick to traditions!
"Give orange me give eat orange me eat orange give me eat orange give me you." -Nim Chimpsky
Case Study on the migration of hotmail to Windows 2000
Could someone help me with this?
Isn't the reason Microsoft wants a common language runtime because it makes it easy to de-compile the programs from other companies, and therefore to compete without paying those companies anything?
[ed. note: in the following text, former FreeBSD developer Mike Smith gives his reasons for abandoning FreeBSD]
When I stood for election to the FreeBSD core team nearly two years ago, many of you will recall that it was after a long series of debates during which I maintained that too much organisation, too many rules and too much formality would be a bad thing for the project.
Today, as I read the latest discussions on the future of the FreeBSD project, I see the same problem; a few new faces and many of the old going over the same tired arguments and suggesting variations on the same worthless schemes. Frankly I'm sick of it.
FreeBSD used to be fun. It used to be about doing things the right way. It used to be something that you could sink your teeth into when the mundane chores of programming for a living got you down. It was something cool and exciting; a way to spend your spare time on an endeavour you loved that was at the same time wholesome and worthwhile.
It's not anymore. It's about bylaws and committees and reports and milestones, telling others what to do and doing what you're told. It's about who can rant the longest or shout the loudest or mislead the most people into a bloc in order to legitimise doing what they think is best. Individuals notwithstanding, the project as a whole has lost track of where it's going, and has instead become obsessed with process and mechanics.
So I'm leaving core. I don't want to feel like I should be "doing something" about a project that has lost interest in having something done for it. I don't have the energy to fight what has clearly become a losing battle; I have a life to live and a job to keep, and I won't achieve any of the goals I personally consider worthwhile if I remain obligated to care for the project.
Discussion
I'm sure that I've offended some people already; I'm sure that by the time I'm done here, I'll have offended more. If you feel a need to play to the crowd in your replies rather than make a sincere effort to address the problems I'm discussing here, please do us the courtesy of playing your politics openly.
From a technical perspective, the project faces a set of challenges that significantly outstrips our ability to deliver. Some of the resources that we need to address these challenges are tied up in the fruitless metadiscussions that have raged since we made the mistake of electing officers. Others have left in disgust, or been driven out by the culture of abuse and distraction that has grown up since then. More may well remain available to recruitment, but while the project is busy infighting our chances for successful outreach are sorely diminished.
There's no simple solution to this. For the project to move forward, one or the other of the warring philosophies must win out; either the project returns to its laid-back roots and gets on with the work, or it transforms into a super-organised engineering project and executes a brilliant plan to deliver what, ultimately, we all know we want.
Whatever path is chosen, whatever balance is struck, the choosing and the striking are the important parts. The current indecision and endless conflict are incompatible with any sort of progress.
Trying to dissect the above is far beyond the scope of any parting shot, no matter how distended. All I can really ask of you all is to let go of the minutiae for a moment and take a look at the big picture. What is the ultimate goal here? How can we get there with as little overhead as possible? How would you like to be treated by your fellow travellers?
Shouts
To the Slashdot "BSD is dying" crowd - big deal. Death is part of the cycle; take a look at your soft, pallid bodies and consider that right this very moment, parts of you are dying. See? It's not so bad.
To the bulk of the FreeBSD committerbase and the developer community at large - keep your eyes on the real goals. It'
One more crippling bombshell hit the already beleaguered *BSD community when IDC confirmed that *BSD market share has dropped yet again, now down to less than a fraction of 1 percent of all servers. Coming on the heels of a recent Netcraft survey which plainly states that *BSD has lost more market share, this news serves to reinforce what we've known all along. *BSD is collapsing in complete disarray, as fittingly exemplified by failing dead last in the recent Sys Admin comprehensive networking test.
You don't need to be a Kreskin to predict *BSD's future. The hand writing is on the wall: *BSD faces a bleak future. In fact there won't be any future at all for *BSD because *BSD is dying. Things are looking very bad for *BSD. As many of us are already aware, *BSD continues to lose market share. Red ink flows like a river of blood.
FreeBSD is the most endangered of them all, having lost 93% of its core developers. The sudden and unpleasant departures of long time FreeBSD developers Jordan Hubbard and Mike Smith only serve to underscore the point more clearly. There can no longer be any doubt: FreeBSD is dying.
Let's keep to the facts and look at the numbers.
OpenBSD leader Theo states that there are 7000 users of OpenBSD. How many users of NetBSD are there? Let's see. The number of OpenBSD versus NetBSD posts on Usenet is roughly in ratio of 5 to 1. Therefore there are about 7000/5 = 1400 NetBSD users. BSD/OS posts on Usenet are about half of the volume of NetBSD posts. Therefore there are about 700 users of BSD/OS. A recent article put FreeBSD at about 80 percent of the *BSD market. Therefore there are (7000+1400+700)*4 = 36400 FreeBSD users. This is consistent with the number of FreeBSD Usenet posts.
Due to the troubles of Walnut Creek, abysmal sales and so on, FreeBSD went out of business and was taken over by BSDI who sell another troubled OS. Now BSDI is also dead, its corpse turned over to yet another charnel house.
All major surveys show that *BSD has steadily declined in market share. *BSD is very sick and its long term survival prospects are very dim. If *BSD is to survive at all it will be among OS dilettante dabblers. *BSD continues to decay. Nothing short of a miracle could save it at this point in time. For all practical purposes, *BSD is dead.
Fact: *BSD is dying
Nobody uses BSD and why are we hearing about it? Start reporting about how .NET runs on VMS or Tru64, about the same level of relevance.
it was a joke. sometimes people don't get these things. sorry about that.
Does that make this .NetBSD?
Don't have any benchmarks for you, but I've run both Rotor and Mono on FreeBSD and found the latter much faster and much less buggy. It's nice that MS is making the effort to experiment on alternative platforms (particularly one that still forms a piece of the Hotmail infrastructure -- though I think the whole Rotor thing is borne more out of the researcher's intellectual curiosity). One interesting point though, even though Mono is still a long way from complete installing and using it was a breath of fresh air after struggling with Java on FreeBSD (among other platforms). Sun and the Java community still have alot of work to do in the areas of version control, performance and "packaging". No one should get too confident in Java's future.
.NET will not run on your computer.
-yours truely Mohamm3d Al-Sahaf
"All your *BSD are belong to us" ?
never mind..