Taking MicroBSD for a Test Run
LiquidPC writes "In this article Jeremy Reed of BSDNewsletter.com talks about installing MicroBSD, what features make it special, troubles and successes I encountered, and the beauty of the BSD license."
← Back to Stories (view on slashdot.org)
I don't see what is 'micro' about the distro. The default installation takes 160M. Back when I have my AT&T 3b1 running, the whole thing fit on a 10M disk with 3M left for my files. No tcp/ip tho, but does that really take 150M?
-dB
"It if was easy to do, we'd find someone cheaper than you to do it."
The BSD license is pretty beautiful, if you are MS and you need a TCP/IP stack to steal.
I think it's great that Microsoft can and does use the BSD stack. At least now they are using something that is well designed and follows the RFCs to the letter. Anything cooked up and "optimized" by M$ themselves would in all likelyhood have brought down the Internet in a catastrophic congestion collapse.
"I have opinions of my own, strong opinions, but I don't always agree with them." -- George H. W. Bush
So?
What you need to understand: it isn't your code, they can do what they want with their code. release your code with whatever license you want.
The developers of code released under BSD style license are just fucking generous. plain and simple.
It's not that they have never considered "Gee, what if someone uses this in a closed source system? Gee, what if someone or some Corp. rips off our code and we get nothing back?". They have considered that possibilty, and they dont care.
Here is the flaming part of this post:
Ideally: "we release completely free source"
Realistically: "People rip off our shit"
BSD style license is Ideals living despite Reality. GPL is Ideals living to confront Reality. You decide what the right lifestyle is for you and let me live the way i want.
We've already established that MS ignored the advertising clause of the BSD license when it used the BSD TCP/IP stack. What makes you think that they wouldn't just ignore all of the clauses of the GPL?
It agree on all three counts. OpenBSD could be easier for first time users, but is simple and fast the second and nth time around. FreeBSD and its menus can be confusing. You need the Handbook right in front of you. Even then I seem to install something a little different each time. Haven't used NetBSD recently. I had trouble with the installer, but that was a while ago I hope things have changed.
:-) The installer is not friendly to the first time user. My first install was wiped in about 3 minutes as I started my second install. My second install worked well. My third and nth installs are great. The install is very quick. The defaults are sane and not a lot of questions are asked. There are only a handfull of packages that I install from precompiled instead of ports. When I need a *nix I install OpenBSD.
OpenBSD is my favorite *nix. It is perfect. It is a simple clean install that comes with everything that should be in a default unix install. (Except BASH!
OpenBSD may be for a more advanced user. Anyone willing to learn, read a little, make some mistakes, should have no trouble working with OpenBSD. I encourage any *nix admin to make some time and learn OpenBSD. Call it professional development. I am sure that you won't turn around and install OpenBSD everywhere. However I am confident that you will find uses for OpenBSD where its quick and simple install will save you time and stress.