Quick and dirty way to have OpenBSD running on Linode
forum.linode.com
forum.linode.com
How, for instance, most of the cool stuff in FreeBSD comes from OpenBSD (pf, OpenSSH, OpenSMTPD, OpenNTPD, LibreSSL, http://itwire.com/business-it-news/open-source/62641-crypto-...). How, for instance, one cannot protect oneself properly using FreeBSD's outdated version of pf.
He's expressed his utmost sympathy, and it is my belief that he's slowly but surely realizing OpenBSD's worth.
To say that most cool stuff in FreeBSD comes from OpenBSD is pretty misleading. Certainly, FreeBSD has lots of cool things that come from other operating systems. :)
Apologies if my curiosity is misinterpreted as ignorance.
Choose OpenBSD for your Unix needs. OpenBSD -- the world's simplest and most secure Unix-like OS. Creator of the world's most used SSH implementation OpenSSH, the world's most elegant firewall PF, the world's most elegant mail server OpenSMTPD, the OpenSSL rewrite LibreSSL, and the NTP rewrite OpenNTPD. OpenBSD -- the cleanest kernel, the cleanest userland and the cleanest configuration syntax.
The biggest problem with OpenBSD has been lack of support for hardware and virtualization, though a lot of the reason for this has been the OpenBSD team's own hostility towards virtualization. I get their reasoning (virtualization is a security issue), but the economic consequences have been devastating to their userbase.
The cost difference and ability to run on cheaper hardware was a big reason Linux won out over Windows. It's important to make operating systems accessible to everyone, even those that can't afford full dedicated servers.
If you watch the the ruBSD 2013 interview video with Theo de Raadt[1] at the 6:36, he states that they should take a shot at dealing with modern x86 VMs. That gives me quite a bit of hope along with the work on vmware related drivers in each release.
I use VMware at work, seems to do ok.
-- PF (which, in my system-administrating experience, is way nicer than any GNU/Linux firewall to date) is only available on BSD-derived systems (including OS X and - IIRC - Solaris), and originated on OpenBSD.
-- OpenBSD has a very strong security track record over the last 1 1/2 decades or so.
-- OpenBSD has been the source of a lot of really nice bits of software [0], and tends to be the first and preferred platform for quite a bit of that software. My own use cases revolve around PF, OpenSSH, tmux, httpd/relayd, spamd, and OpenSMTPD. httpd and relayd in particular are currently exclusive to OpenBSD last I checked.
This isn't to say that OpenBSD is right for everyone (notably, upgrading between releases and getting the latest patches for a given release can be... involved, to say the least), but there are certainly reasons to prefer it over GNU/Linux or the other BSDs.
Not to mention that some Linux-only software will happily run on the mainstream BSDs - OpenBSD included - thanks to a binary compatibility layer. Even things that rely heavily on Linuxisms - like Docker - can run on at least FreeBSD [1], and doing the same for OpenBSD, while probably more involved (OpenBSD notably prefers chroots over newfangled virtualization techniques like containers and jails; in the opinion of its authors and users, containers/jails/etc. only provide an illusion of isolation, and chroots provide equivalent functionality without dishonesty. While I don't entirely agree with this, I can see where the attitude comes from and understand the rationale.), might very well be possible sometime in the not-so-distant future.
[0]: https://en.wikipedia.org/wiki/OpenBSD#OpenBSD_component_proj...
Though, I understand why someone who already has a Linode investment would want to do this instead of changing providers, kudos to the author for sharing!
For the sake of example, say I already have my system built and configured just the way I like it, as a "raw" ffs image file. And FWIW the kernel on that image is multiboot compatible and can run as a Xen guest.
I also have my own non-GRUB bootloader. But I realize that it may not be feasible for the hosting provider to let me use it.
Download file to /boot (or anywhere accessible from grub)
Reboot / boot OpenBSD installer
Did that on my cloudcost machine to experiment with OpenBSD services.
I don't really like preinstalled images, because I don't trust them. They usually tinker with network settings, sometimes with other things. I prefer official installer.
I had the issue with FreeBSD on kimsufi (2To UFS-formatted drive...). The great thing however was how good their recovery system was: they provide a Linux and BSD live rescue boot that you can use to chroot-install your system. There are just so many parameters that will get badly set with a pre-installed image: FS, size, hostname, routes, adresses, packages not in base (!!!)...
IMO, a reliable rescue mode along the preinstalled images would have all users happy, as either you are in command of the install or are just getting started anyway and don't mind the default settings.
* they like OpenBSD
* they want to learn OpenBSDThat said, I currently just run my personal mail server. However, I'd reckon latency to be pretty decent from the East Coast (of North America) or western Europe. Not sure about the whole rest of the world, though.
That's the main reason I wouldn't do it, when there are other hosting companies that explicitly do support it.