Metawire.org Admin On OpenBSD Hosting
hext0r writes "Open Hosting provider metawire.org administrator Daniel Selans recently wrote an informative article for the OpenBSD Journal about the difficulties and successes in running a free hosting provider using OpenBSD. It's an informative read for anyone considering starting any type of hosting company using free technologies."
Maybe *BSD died back then... but it's most surely coming back! Just take a look at the latest NetCraft survey and you'll see that they have come back a little.
I think this article confirms it. Just check where it's posted: http://undeadly.org/, doesn't that light some lights!?
One thing that I can most definatelly note is that with the use of OpenBSD, the experience was made by far simpler, and headache free. The common belief out there is that OpenBSD is best used for security gateways, firewalls, routers and etc. Well, I personally do not believe so. The capability of this OS is only admin deep. The more you know, the more you can achieve. I have personally ran OpenBSD in large enterprise environments as web servers, file servers, database servers, and frankly, it's resource management and speed is uncomparable to most other operating systems out there, multiply that with the security standards, and you've got an amazing OS.
I feel like installing OpenBSD!
I didn't see anything negative in that article. Nor any major "difficulties". He made it sound like it was a breeze - just put together a bunch of scripts and it's all done.
PS: I love OpenBSD. Like Daniel, I also use it as both a server and a desktop workstation. I just wish people would RTFA.
Because of the way ports and packages are designed this complation issue of yours does not happen.
You do not need to configure anything to compile a port, you need to run "make install" after enabling root permissions or getting sudo setup.
Packages are not the norm by any stretch of the imagination for anyone I know that uses a BSD. Installing a pkg works fine as long as you also have the dependancies it will just install the same as if you made from a port and I have never found a port in the 3.3 release that installs broken not bad for the 193 I use for my desktop.
The only messed up compile I've ever seen is xmame+xmess, which my machine could not handle cause it doesn't have enough resources to compile it.
OpenBSD is equally able to use the ports and pkgs in it's system because the system was designed for Open.
I'm sick of following my dreams - I'm just going to ask them where they're going and hook up with them later.
I would just like to echo that Metawire is by far the best shell hosting I have ever used. I think I was one of the first signups, and since the beginning they allow alot of trust to their users and aren't restrictive.
Metawire is simply exactly what it says on the tin. Free, and amazing shell hosting, have them for an email account, or your website, for hosting scripts and whatever else you can think of.
Great service.
The cost is picked up by the administrators themselves, and it's ran extremely professionally with complete regard for their users.
Simply by the services they allow you can see that OpenBSD is a great OS for just about anything and everything.
Metawire.org, my precious server, slashdotted!
:)
:P
I guess we can consider the fact that it's still up a testament to OpenBSD
In all seriousness, though, OpenBSD has been a blessing for running Metawire. I joined the admin team a few months ago, after having been a lowly user and an active member of the community since last year, and have found (as Danny put so well in his article) that the biggest challenges in terms of maintaining a secure and stable server with thousands of users are well met by a system with a philosophy like OpenBSD's.
The challenges that OpenBSD and a proper user management system (which I have been an active developer on since I was made an admin) can not handle are those that plague any provider of a free service, namely the ages-old Tragedy of the Commons.
Garret Hardin's prophetic essay deals mainly with the human tendency for one to maximize the usage of any communal space for his own personal gain, and at the same time to shirk the responsibilities of its upkeep since it is not "his". As this applies to being a free shell provider on the Internet, you have to deal constantly with users who apply, abuse the service, are given the boot, and then show up again. As far as they are concerned it is a common space, freely available, for which they are not responsible. Since they do not take ownership in any sense, what responsibility to they have to keep things OK for others?
The "tragedy of the commons" manifests itself in the biggest administrative headaches the team has had to face so far. People signing up to use bandwidth-hogging psyBNCs/IRC proxies to get past bans on networks or keep nicknames alive, people using our service to mailbomb, people using it to host illegal materials... Had they been using a paid shell (which are widely available) for which they had some degree of "ownership" and at least an implied responsibility to follow the rules, their behavior might be less destructive, but because they are using a free resource, they feel unburdened by any responsibility towards other users and the administrative staff.
I could let these failings of human nature get me down, but thankfully there is another tool which can fill in where OpenBSD fails. Perhaps even the vagaries of man can be overcome...
by Perl
They also place very little restrictions on what you can do. SSL access to webmail will be online soon too.
I just signed up for an account and have been very pleased. It sounded to good to be true, but its been great. But if people don't eventually donate, it may not be able to continue in the long run, so please consider that. They seem fine now, but lets keep it that way.
Sign up, contribute, and eventually donate if you like at:
http://metawire.org/donate.php