What are
/r/BSD's
favorite Products & Services?
From 3.5 billion Reddit comments
The most popular Products mentioned in /r/BSD:
The most popular Services mentioned in /r/BSD:
OpenBSD
FreeBSD
NetBSD
GhostBSD
Lobsters
DragonFly BSD
MidnightBSD
pfSense
GitHub
OPNsense
runit
Darling
SourceForge
Amazon Web Services
GNU Emacs
The most popular reviews in /r/BSD:
Unix, it is a direct descendent of the original BSD sources. Although it cannot call itself Unix because it is a trademark for which you need to pass certification, which costs money.
See also http://www.freebsd.org/doc/en/articles/explaining-bsd/what-a-real-unix.html
FreeBSD will be the easiest to get you started, OpenBSD will be the most secure, NetBSD will boot on absolutely anything. This is all I know since I've only worked with FreeBSD.
Almost all software released for Linux should be able to compile on a FreeBSD. It's most probably in ports anyway. Just go to /usr/ports/category/softwarename && make install
The FreeBSD Handbook covers 99.9% of everything you will want to know for the first half year of using FreeBSD. After that you are either googling for very specific answers or you're in a situation nobody has ever been in.
Use the ports system. On a newly installed system, run "portsnap fetch extract" to get the newest ports tree. "portsnap fetch update" whenever you have to install software again.
System-stuff is in /etc, userland stuff is in /usr/local/etc.
Example: If you install nginx, the config files will be in /usr/local/etc/nginx and the init script to start/stop service will be in /usr/local/etc/rc.d/nginx
If you will want to enable the provided nfs daemon, you will add your share to /etc/exports and start nfsd with /etc/rc.d/nfsd start.
FreeBSD comes with a few basic network services pre-installed. These are ftpd, nfsd, opensshd, named, and I've probably forgotten some. They are not enabled by default but are very easy to set up.
All services, network configuration, etc, is controlled through /etc/rc.conf
Use net-mgmt/portmaster to install ports. It's much smoother.
It will be a bit confusing in the beginning but worth it in the long run. FreeBSD is a good stable operating system.
Have fun :)
>First question. It seems AOSP is open but they develop and then release instead of having a repo where you can see development happening. What is this style called where you develop openly vs waiting till its complete and then releasing? Are the BSD's developed in the open or are they like Android?
This is actually OpenBSD’s raison d’être. The “open” in the name refers not to the license, but the development methodology. OpenBSD pioneered this by inventing anonymous CVS, letting you download the latest source code, view commit logs, make diffs, and so forth without a developer account. We take that for granted today, but in 1996 it was a revolutionary concept.
I would suggest FreeBSD. It is the most supported and documented of the available flavors and therefore will be the easiest to transition to. The FreeBSD Handbook will pretty much tell you ANYTHING you need to know. Between that and googling (which actually leads you to the handbook most of the time anyways) you can figure out most everything. What I would suggest is to come up with some purpose for it and then set out to fulfill that purpose. For instance, setting up a web server or a DNS server. It's not really designed to be a desktop OS so if that is your intention than you may want a different flavor. I wouldn't even recommend installing the GUI.
*EDITED for additional clarity
Linux distros all use the linux kernel with slight modifications. BSD on the other hand has a few branches, FreeBSD, NetBSD etc.. which all have their own kernels and source trees. I recommend you read this: http://www.freebsd.org/doc/en/articles/explaining-bsd/comparing-bsd-and-linux.html
All the firmware distributed as part of OpenBSD is freely redistributable, see the -license files in /etc/firmware. This firmware would otherwise be in ROM or flash, and may comprise the core functionality of the device.
Stop conflating the term blob, which OpenBSD has long history of fighting against.
It's hard to steal something that is BSD licensed.
They are freely giving credit on their website as well: https://opnsense.org/about/legal-notices/
(Note, I am a pfSense user currently but this drama is the root cause of me switching to an Ubiquiti solution for my next firewall/router purchase in January.)
DragonFly was forked from FreeBSD around version 4.8 of FreeBSD - that was 10 years ago, so there's a lot changed since then.
Both of them using the same ports system and pkg tools is the major similarity at this point. I think DragonFly was actually using pkg first, which is mostly an accident of timing. Look hard enough and you'll see shared elements between all the BSDs, really.
FreeBSD uses a more complex locking system, where multiple layers of locks need to be tracked. DragonFly uses a token system, which is much simpler. The payoff for DragonFly has been a simpler programming model and a generally more responsive system. (see the performance page on dragonflybsd.org. )
Disclaimer: I have been working on DragonFly for most of its existence and run the DragonFly BSD Digest, so of course I would have these opinions.
How would Arm get better if it's prohibited from doing business with a good chunk of its customers?
Do you know where OpenBSD and OpenSSH are based, and why? Do you know which country both cannot move into?
The man page:
> The httpd program first appeared in OpenBSD 5.6. httpd is based on relayd(8).
The intial commit:
> Add httpd(8), an attempt to turn the relayd(8) codebase into a simple web server
Dragonfly exists because FreeBSD revoked Matt Dillon's FreeBSD commit rights.
He had been the technical lead of FreeBSD during a time period in which FreeBSD improved a lot. Disagreements on architecture eventually led to this fork.
Dragonfly's there to prove a point: Matt was right. And it has already proved that point. Despite the small team, it is scaling far better than the other BSDs.
The only tutorial you need to get started is to follow the suggestions in "man afterboot" and to use this FAQ from the OpenBSD site, which has an example ruleset at the bottom. http://www.openbsd.org/faq/pf/index.html
Pf is enabled by default to pass traffic outbound from the host itself. You only need to write rules if you are wanting something to come in. The rules have a simple yet powerful syntax, so most people familiar with Linux should be fine as long as they read the main FAQ and the man pages (which, unlike most Linux distros, are accurate, have regular use case examples at the bottom, and are kept up to date).
The best way to convert from -stable to -current is, by far, to download a bsd.rd snapshot from a mirror, verify its authenticity with signify(1), boot from it, and go through the upgrade process, then follow the steps in the -current FAQ.
I don't really understand the confusion here. The base system hasn't suddenly stopped including an HTTP client.
OpenBSD's ftp(1) utility supports both HTTP and HTTPS. It's the backend used by the package tools and the system installer.
It was decided the base system didn't need a text-mode HTML parser/renderer, which, also just happened to bundle a bunch of obsolete network protocol clients.
I'm not sure about the answer to your question, but I just want to point out that Linux is perfectly capable of booting an NFS root without an initrd/initramfs. All you need to do is compile the network/NFS code into the kernel (not in a module) and then use the nfsroot=/ip= kernel command line options in your bootloader (which can, of course, be done through PXE). I boot a number of diskless computers this way.
>I don't think it is in OP's case - he's using Arch Linux, which has [1] a sysv style init, which I'm pretty sure is what FreeBSD's is classified as (though I'm a FreeBSD zealot who just woke up, and it's going to be pretty embarrassing if it turns out I'm wrong on something so elementary).
Actually Arch currently is switching/switched over to systemd as the new init system.
See - https://www.archlinux.org/news/systemd-is-now-the-default-on-new-installations/
I wouldn't use openssl enc having looked at it - it's looks more like a crappy example of the API than a suitable serious encryption tool. The most obviously awful bit:
if (!EVP_BytesToKey(cipher,dgst,sptr, (unsigned char *)str, strlen(str),1,key,iv))
That hardcoded 1 near the end is the iteration count to the (obsolete) key derivation function, which is what turns your passphrase into an encryption key (using MD5, by default). Quoth RFC2898, 14 years ago:
> For the methods in this document, a minimum of 1000 iterations is recommended.
For perspective, the old Xeon in my home server can pump out over 5 million MD5's per second per core. The old GPUs gathering dust on the shelf next to it can pump out over 5 billion per second, each.
I tend to use scrypt for this sort of thing:
> On modern hardware and with default parameters, the cost of cracking the password on a file encrypted by scrypt enc is approximately 100 billion times more than the cost of cracking the same password on a file encrypted by openssl enc; this means that a five-character password using scrypt is stronger than a ten-character password using openssl.
As for "like tarsnap", one of the nicest bits about tarsnap, on top of it actually using modern crypto primitives, is the key management system. You can allocate each machine its own unique passphraseless append-only keys which can only create new archives, while keeping keys to delete or restore separate, either passphrased or even air-gapped. How easily can you replicate that with S3?
And of course, deduplication, mumble mumble, even if S3's 10x cheaper.
You have Homura and linux-steam-utils on FreeBSD for options. They both use wine, and you will have varying success. BSD isn't really your best option for gaming, though. OpenBSD has r/openbsd_gaming community, they have FNA and have a decent number of games working. No wine on OpenBSD, though.
Unfortunately, there is now no single "killer app" thing that BSD does better than Linux, as Linux has matured much in the last decade. Nowadays it comes down to small differences and preferences. Someone described it as "BSD is more comprehensible" in the sense that it is much easier to avoid treating parts of it as a black box: since it encourages a more low-level approach to using it than modern Linuxes, people using it tend to learn more details of what is going on behind the scenes and can respond better to problems. (don't get me wrong: both Linux and the BSDs are still MUCH more technically oriented than Windows and Mac OS X).
This is a large reason of why I use it: I've found too many cases when Linuxes try to outsmart the users, don't come with proper diagnostic tools, are too stubbornly "NIH-crippled", etc. FreeBSD also comes with quite modern tools (GEOM, Netgraph, ZFS) which do complex tasks in a very simple way, something which the GNU folks have never really learned. See e.g. the command line examples for http://linux.die.net/man/8/iptables and for http://www.freebsd.org/cgi/man.cgi?ipfw .
As for performance, etc. then no, you probably won't see much difference in the common case (not discussing edge cases).
Apparently you were downvoted as well, again without explanation. I'm curious as to the reasons, too.
My guess is that it has to do with ideological differences between OpenBSD and, say, the FSF when it comes to how they define "free". It's interesting that LibreBSD wants to shoot for something that could be the first FSF-approved BSD, though whether it's a real step forward is debatable (I'm pretty sure the FSF will come up with some new contrived reason for rejecting a BSD from their approved OS list, and said reason will probably have to do with copyleft v. the lack thereof, but hey, worth a shot, right?). There's an increasingly-long history of contention between the GNU and BSD camps over that exact subject among others, including ideological debates over whether including support for non-free software in a collection of free compilation/install scripts (what pretty much all BSDs do in their ports trees) constitutes "endorsing non-free software" while distributing Windows ports for software (what the FSF does under the GNU banner in some cases, like with Emacs) is for some reason all hunky-dory.
Needless to say, the downvotes are quite possibly a knee-jerk reaction to the idea that OpenBSD needs to conform to the FSF's hypocritical definition of "free" in order to be considered "free". Or perhaps there's something wrong with the project itself (I'm not seeing anything of particular egregiousness at first glance, but perhaps I'm just not observant). Or maybe it's because the official download link seems to be broken (or maybe just really slow), or that it only supports two architectures out of the dozens that upstream OpenBSD supports. Or perhaps people just like pufferfish. Whatever the case, I, too, am interested in the actual reasons so that I don't have to speculate.
> There's no UEFI support yet. (...) How is the development of this going for NetBSD?
> Also, there's no USB 3.0(+) support
There is (as you can see behind your link), but it's experimental yet. Feel free to help them debug it.
> Will (easy) full disk encryption come in the future?
We can't answer that without clarifications what "easy" means. Which part is too uneasy for you?
> I noticed it downloaded many files from other places than NetBSD
That's called "mirroring", basically meant to lower the load and make things faster.
> Why do all BSD have separate ISOs for optical media and images for storage volumes?
Because most people know which kind of media they have so they won't have to download giant "hybrid ISOs" when they only need a small one.
> Why is there no ext3 and ext4 support?
You can do that with FUSE. The reason why there is no kernel-side ext4 yet is that no one has done it yet.
>Simple: no scripts playing the role of the user.
Don't quite know what you mean by this
>Simple init (bsd init ...)
FreeBSD has that also
>Package management practical and painlessly, with an option to install >from sources.
pkg_add -r bash to install bash or cd /usr/ports/shells/bash/ && make install to install from source
>AUR: Community repository of packages.
FreeBSD currently has 22840 ports available.
>Easy creation of new packages (to not get files around the disk without >a source).
Got that also: FreeBSD Porter's Handbook
>Stability: system once installed does not need frequent maintenance.
Ditto: 3:44PM up 895 days, 22:51, 3 users, load averages: 15.27, 14.36, 15.26
Not according to the NetBSD website:
http://www.netbsd.org/gallery/products.html#darwin
https://news.ycombinator.com/item?id=4375857
> OS X is not really a BSD. True, its userland comes from a mish-mash of NetBSD, FreeBSD, classic big-U Unix, and OpenBSD, in roughly that order, but xnu is not a BSD kernel, and while it supports many FreeBSD APIs (e.g., kqueue), that's done by reimplementing those APIs in xnu, frequently via gratuitous copy and paste, but definitely not by using a BSD kernel.
So that was my understanding at the beginning OS X was:
* - xnu (mach) kernel
* - FreeBSD kernel APIs grafted on
* - Mostly NetBSD userland
* - NeXTStep programming libs and tools (thus everything starting with ns in the Cocoa libs)
> which BSD should I use - I like Gnome which I understand is available.
GhostBSD is a preconfigured FreeBSD desktop OS with a GNOME-like (MATE) desktop. Other than that, please list your requirements first. Do you need more (NetBSD) or less (OpenBSD) technical details during installation? Do you want security (OpenBSD) or performance (FreeBSD)? How important is Linux or Wine compatibility (FreeBSD)? Et cetera.
> why will I like BSD over Linux?
No systemd!
> don't necessarily need n, g would work.
Well, that's good! :-) OpenBSD doesn't support 802.11n yet, such cards only operate in b/g or a modes.
It is difficult recommending products as vendors often change the underlying chipset while retaining the name. The best way to test if a device works, is to plug it in and see if it works.
You can use apropos(1) to search for drivers, some of the man pages do still contain product names anyway.
PCBSD has a lot of bells and whistles. (e.g GUI package management, I promise you don't need that)
You shouldn't be afraid to use freebsd. Use the relivent sections of the handbook, and you will have exactly the system you need. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/
> read the handbook
This can't be emphasized enough. There are sooo many Linux people converting to FreeBSD yet aren't referring enough to the handbook and aren't used to excellent documentation and, in partricular, consistency not found in Linux.
It saved lots of money and headaches at my old job (migrated OpenVMS cluster functions to OpenBSD servers).
It makes me an efficient and happy programmer (most of the time) by being the operating system for my laptop, and provides a secure environment for internetting.
It made me money when I was doing OpenBSD support contracts which also brought in freelance software development jobs.
It makes my product/service secure and reliable by running on all of its servers, making my life easier as the person responsible for keeping the service running.
It has introduced me to many great friends and fellow developers through ChiBUG and OpenBSD hackathons.
I would just donate it to a project that could actually benefit from the use of an ultrasparc machine. Then get a low powered machine or use a virtual machine to learn linux/bsd/whatever.
The architecture matters little unless you're doing architecture specific programming/testing. You're probably spend most of your time trying to figure out what software is compatible with your flavour of UNIX & UltraSPARC. For example, one of my favourite tools for development is valgrind, but don't expect to see your favourite OS on SPARC support it.
I suggest linux from scratch. The book is well written and you can just follow the instructions step by step. After that you'll probably appreciate that distributions (BSD, linux, whatever) do a lot of work for you and you'll be in a better position to decide which way to go.
... The whole world doesn't revolve around systemd. I was talking about tools like Runit, S6 and OpenRC. Runit, for example, can be used as a service manager on top of an existing init system.
I am running DragonFly on my C720 and like it. It's not speedy by any stretch, but it was cheap and works well. The Chromebook page on the DragonFly site will help if you haven't seen it:
http://www.dragonflybsd.org/docs/newhandbook/ConfigChromebook/
Also the AUTODEEP setting for processor states will help:
http://www.dragonflydigest.com/2014/12/10/15218.html
Suspend/resume isn't supported, but you can save a lot with that and other settings.
Try the dd commands shown here
http://www.ghostbsd.org/11.1_beta1
Make sure the of=/dev/sdX part of the command is the usbdrive, because you will irreversibly change whatever you use for /dev/sdX
Not tested but for nVidia cards there is only vesa(4) and nv(4) drivers, nv(4) mentions dual-head support.
But nv(4) seems to not be maintained, because nVidia is very uncooperative. So you may try, but you are better off with Intel or ATI/AMD graphics.
http://www.openbsd.org/cgi-bin/man.cgi/OpenBSD-current/man4/nv.4?query=nv
Your ethernet/wireless interfaces are almost certainly not supported by OpenBSD due to Apple using hardware from vendors who don't provide access to source code or docs for writing drivers. The solution is to purchase a wireless USB dongle that is supported by OpenBSD. Off the top of my head, I know many Ralink ones are supported. See here for a brief list http://www.openbsd.org/faq/faq6.html#Wireless
> What? How to I check the signature of an iso file or a sha string?
You check the signature with signify(1). Where do you get signify? Your package mirror, or the CD, or someone you trust can email you a copy via PGP…
> I really don't think I'm asking for the moon here; I mean you guys write the new standard library for TLS.
So? If the installer is signed, there’s no need for HTTPS to guarantee integrity.
OpenBSD's FAQ has a section dedicated to multibooting, there's very little that needs to be done. Both the kernel and fdisk(8) support extended partitions.
Installing to a second or third disk is no different from the first, it just requires you change your BIOS boot order when you reboot.. or have something else that can chainload OpenBSD's MBR/PBR bootloaders.
OpenBSD has no official support channel on any IRC network, those are all community operated. Again, it's easy to say the operating system's at fault for your perceived "problems", but the reality is you're making large assumptions without any experience.
I recently installed a couple VMs of openBSD at work, both 5.4 and snapshot of 5.5. It took a little bit of time for me to find the right iso because it was about 8MB and the install was about 10 minutes. Of course, that's giving me only cli but that's damn fast!
The documentation to install is laid out fairly well, I just followed the FAQ
Pick up a shirt to both support and promote openBSD: https://https.openbsd.org/cgi-bin/order
I can't wait for the 5.5 shirt to be released this spring!
Linux emulation is possible for x86 programs on FreeBSD and OpenBSD. Never used it with OpenBSD, but FreeBSD's has a nice chapter on it:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/linuxemu.html
I've used it to run flash inside Firefox before, but I don't use Flash anymore.
BSD also has a linux 'binary compatibility', anything you run on Linux can be natively run on BSD with no code revisions.
Also, YES ports is a repository if you will, it differs in the fact that software is actually COMPILED on your machine when you 'install' it from the ports tree.
It's really quite interesting, if you're looking for a prepackaged setup, try pkg_add.
Wow, my mod inbox was full today! I'd like to point out that FreeBSD distributes its software via FreeBSDMall - http://www.freebsd.org/where.html, which in turn helps to support the effort. It's no different nor is it bad. Part of me wishes I had been collecting these discs since I first got hooked (2001). :)
I'm late to this thread, but you can use mdconfig to create file-backed md disks, which you can then use to play around with zfs and zpool. Create arrays, examine upgrade paths, etc. It's a very good way to experiment with your intended setup without actually purchasing or stressing hardware.
I'm in a similar boat, but have some bit of experience with FreeBSD. I'm an everyday Arch user as well and recently used FreeBSD as a DNS server (BIND9) and enjoyed myself. Their handbook is wonderful, but does assume a certain level of knowledge. As you plan on using it as a server, read into their implementation of jails and I'd suggest reading into user experiences with the services you choose to install. Ports is a great system, and if you've used Arch's AUR, you should have a leg up on how things function. No yaourt (or similar tool) here, but it works similarly.
You're probably familiar with Bash, so the shell will take a little bit of getting used to. I still miss some of the features when I'm on my Linux boxes.
I'd still be using FreeBSD, but I wanted a server that could handle virtual machines (I use KVM), so I migrated back to Linux. As my experience was short (about a month), there's really no practical knowledge that I can pass on beyond reading that handbook and keeping a log of your activities on the server. Keeping that log really helped me organize my thoughts and keep track of my activities.
Have fun!
tl;dr: this is the source-code and the documentation for a 3d graphics chip that's similar in design to the one used in Raspberry PI.
The R PI release on the happening: http://www.raspberrypi.org/archives/6299.
Not as much as varnish, because it stores all of its contents in a memory mapped file, my application needs to manage larger amounts of information than RAM. (It's like Squid, for example, but has more specific cache algorithms)
An application that runs on other Unix clones (like Linux or illumos) might need few or no changes to run on BSD. The best way to support BSD is to provide the source code of an application. Each BSD can build the code and provide a binary package.
For example, GNU Emacs comes in an archive like emacs-26.1.tar.gz (or .tar.xz). The code of Emacs is in C language and works with several systems. Each BSD can patch and compile Emacs for their system: FreeBSD builds the FreeBSD package, NetBSD builds the NetBSD package, and so on. The same happens with hundreds of other packages.
Each BSD system is different: FreeBSD can't run a NetBSD package. Each architecture is different: an ARM processor can't run Intel x86 code. Each system or architecture needs a different package. OpenBSD doesn't keep backward compatibility, so OpenBSD 6.3 can't run some applications from OpenBSD 6.2. FreeBSD and NetBSD have some Linux compatibility, so they can run some Linux applications.
I've let my BSD skills wither the last few years, but I'm coming back to it at home and at work. If you use ports a lot you won't really need anything else. Sometimes it requires a good day's worth of digging around to get certain upgrades working but the rest of the time it's taken care of for you.
I would provision a staging area for testing and have one box update the ports and then create packages from it. After testing the packages throw it on an nfs share and install it with bash scripts. I think the new school thing to do for deployment is to run capistrano.
Is there a reason you have a heterogeneous mix of BSD servers? I've lightly used all three but I always come back to FreeBSD because ports had quicker updates or more software.
I collect old stuff...... Old BSD install images/tapes etc. They will run in either SIMH or various other emulators.
Hopefully this will help someone in the future - I found this on php.net after Xipher sent me off the sqli fix!!
http://php.net/manual/en/migration51.databases.php
Changes in MySQL support
In PHP 4, MySQL 3 support was built-in. With the release of PHP 5.0 there were two MySQL extensions, named 'mysql' and 'mysqli', which were designed to support MySQL < 4.1 and MySQL 4.1 and up, respectively. With the introduction of PDO, which provides a very fast interface to all the database APIs supported by PHP, the PDO_MYSQL driver can support any of the current versions (MySQL 3, 4 or 5) in PHP code written for PDO, depending on the MySQL library version used during compilation. The older MySQL extensions remain in place for reasons of back compatibility, but are not enabled by default.
> Better compliance with POSIX
Not anymore: http://lwn.net/Articles/625506/
Not that this is a bad thing by any measure, but not all standards are perfect.
> Marginally greater freedom from Millennial programmers and their mal-engineered, excessively complex shit
I can assure you there are COBOL programs written 30 years ago that are used in production, but are not well understood. Making things simple/complex is hardly a generational barrier. If you want simple programs, then you should run FreeDOS, not OpenBSD.
I like runit. Very similar to daemontools. It's used as PID1 in Void Linux, so it's well tested. Service scripts are usually one liners (not including the shebang). AFAIK it works as an init replacement on most *NIX systems.
another good contender for a user-friendly BSD is ghostbsd http://www.ghostbsd.org/ it automates install and has a lot of goodies per-installed such as media codecs etc. I have run PCBSD before and I prefer GhostBSD.
I download the sets beforehand to a fixed directory. Then I download bsd.rd, patch it to include a pre-configured auto_upgrade.conf file. Reboot, chose bsd.rd in the bootloader, sit back and watch and 2 minutes later I'm back at the login prompt of my recently upgraded system.
- I have a script to do the heavy lifting, plus this is for following -current, so always read http://www.openbsd.org/faq/current.html beforehand. Also sysmerge and/or pkg_add -u need to be run manually.
It is hard to diagnose what is the problem from your response. ~~is iwn appearing in dmesg?~~ can you ifconfig iwn0 up?
if so, it is not a driver problem, but a configuration problem.
else, we will need to confirm you installed the firmware correctly.
the OpenBSD FAQ may help you with X and other questions.
edit: unfortunately I will need to go soon. if you are not getting responses to your questions here, try #openbsd on freenode or a mailing list.
1.) No, I'm running it as my main Desktop OS, as well as server OS. OpenBSD will always go with doing it correct even if it means being somewhat "slower" but you rarely will notice anything. 2.) There is a OpenJDK 1.7 package. I run JDownloader and SweetHome3D with it. Also LibreOffice uses some Java and runs fine. 3.) Well FreeBSD I hear tries hard to always be backwards compatible. OpenBSD will throw away backwards compatibility if there is a good reason. That said in OpenBSD init/rc go way back (so 1980) and FreeBSD at least talks about launchd to maybe replace their init?
Try OpenBSD, and PC-BSD (Preconfigured FreeBSD for the Desktop)
Differences between OpenBSD 5.6 and 5.7: http://www.openbsd.org/faq/upgrade57.html and http://www.openbsd.org/57.html
Old (supported) software ports with security vulnerabilities generally have patches backported if affected. As long as you're checking for security updates, you should be fine using the older software, unless you need the newer version.
Sometimes even more secure because new features tend to introduce bugs, whereas old software that receives security updates doesn't have the new features, only security-related patches.
It wouldn't hurt necessarily. There's certainly some crossover between Free/Open/NetBSD. However, they're not identical, so you might find yourself frustrated by slight (and often not-so-slight) differences in how one BSD does things relative to another (for example, reading about jails will you do jack all for OpenBSD).
I recommend looking through OpenBSD's manpages and FAQ. Much like how Arch has its plethora of information on the Internet, OpenBSD has a plethora of information already installed on your own machine (and on the Internet, too).
Oh, and welcome aboard.
Edit: Google/Bing/DuckDuckGo/whatever is also your friend. That's a cheap answer, I know, but it's amazing how much will turn up, especially from OpenBSD's mailing lists. Chances are, if you've run into an issue, so has someone else.
http://www.openbsd.org/faq/faq1.html#HowAbout
Basically the main significance of a program being in base is it's covered under the extensive security auditing process the OpenBSD team does whereas ports are not.
Okay, I worded it wrongly - OpenBSD is the only one discouraging building from source and recommending using binary. And if you ask for whatever problem with your non-GENERIC kernel, you'll be immediately shot down.
> In general, you are highly advised to use packages over building an application from ports. The OpenBSD ports team considers packages to be the goal of their porting work, not the ports themselves.
> 5.6 - Why do I need a custom kernel? > Actually, you probably don't.
On FreeBSD, you boot totally diskless (you don't need a local drive), you usually don't need anything except DHCP-Daemon which points to where to load PXE bootcode from. This is normally a TFTP-Server (yet TFTP, not FTP!) where you can download the kernel from. PXE boot will try to mount bootfs or rootfs where /boot is also on the filesystem from an NFS server. After finding the boot part, the usual /etc/fstab does the rest.
More about it on: diskless(8) or in the Handbook
(Also, watch how cool they solved varying configurations and how almost everything works out-of-the-box after the generic setup.)
Edit: You can also have /boot on your disk or USB thumbdrive. You just need to tell the loader where to mount root from. This is done in loader.conf with vfs.root.mountfrom.
Seriously, I like FreeBSD very much, but I don't like this book. It's better to read the online Developer's Handbook and the sources in /usr/src.
And remember, all this is about FreeBSD and not about operating systems in general. Check the materials students get at universities to know about useful books.
It is also advisable that you learn C first, because FreeBSD already uses pretty advanced concepts. And by learning I mean: write a lot of code and read a lot of code. Don't just read about it, do it. Make useful stuff that improves your life and what you really like, it's the quickest way you to feel rewarding success with your own programs.
Quick Google search brings up this from the FreeBSD handbook. Probably what you're looking for: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/current-stable.html
Edit: and here's from OpenBSD: http://www.openbsd.org/faq/faq5.html#BldGetSrc
Edit2: If it means anything, I've found FreeBSD to be much easier to work with, in my experience. FreeBSD's ports are also a lot more up to date (although some will argue on whether that is a good thing or not).
i'm not sure if you've seen this, it's been posted around here at various times.
your init system is going to be more like slackware than arch, but it's not that difficult to figure out.
the only thing that keeps me from running *BSD fulltime is the lack of wireless network managment tools. i don't mind connecting through the CLI, but i don't want to have to do that everytime i go somewhere. well, that and i have centOS on my server because i'm half ass studying for RHCE.
good luck, keep us posted.
>It's hard to steal something that is BSD licensed.
>They are freely giving credit on their website as well: https://opnsense.org/about/legal-notices/
"giving credit" is not the same as respecting copyrights. OPNsense has been stripping out almost all pfSense copyrights from the code, uploading it as their own. Example: https://pbs.twimg.com/media/CVCceq2VAAAHZ4T.png:large
>One question - if OPN is behind the opnsense.com "parody" site, then why is it registered through a U.S. Registrar and the name behind it is assoficated with pfSense/Netgate?
I didn't say that. However OPNsense conveniently includes pfSense in the title, to portray the whole project badly. Just as they attempt to portray WIPO as an actual court.
I think you'd want to use
chroot ALL /Volumes/website_hdd/WEB/website_com/FTP/%u/FTP homedir ALL /Volumes/website_hdd/WEB/website_com/FTP/%u/FTP
%u being their username, %d is the full home directory
Does the FTP subdirectory exist in either situation?
I'd also recommend not using the built-in ftp daemon. If your users only need FTP access then having to create a real user for them is a pain and a possible security problem if you accidentally open up access to SSH or something similar.
ProFTPD (and others) let you create virtual users, you can store them in a LDAP directory, SQL database, or just a flat file. It supports all the same chroot options so you'd still get what you want, but you wouldn't have to create system users for your clients.
http://www.proftpd.org/docs/howto/VirtualUsers.html
edit: it should also be mentioned that ProFTPD can do SFTP (SSH File Transfer Protocol) and FTPS (ftp over SSL/TLS)
No that's unrelated. Due to a recent wave of spambots flooding Freenode channels like ours, we set the channel mode +S. This means that only TLS-wrapped IRC connections can /join the channel. If your IRC client doesn't support TLS/SSL, then clearly you're still in 1998 and I'd really encourage you to buy a few key stocks.
For dealing with the spambots, there were 3 stopgap measures a channel could take:
- +r Require all users to have a registered (with NickServ) nickname before they could join. We felt this blocked too many potential users such as those looking to quickly drop-in and ask a question.
- +i invite-only requires every user be explicity invited before they can join. This obviously wouldn't work for us.
- +S As I explained above, this simply requires that IRC clients use SSL/TLS when connecting. We felt this would have minimal impact on those joining the channel as it is 2018 and who isn't using TLS these days, either explicitly or automatically, anyways? The one caveat to this, as Freenode documents, is any user connecting using their webchat client. This was seen as a necessary and minor inconvenience to counter the spambots. (Besides, we've blocked webchat users many times before for other spam-related reasons.)
I found this on amazon https://www.amazon.com/Edimax-EW-7811Un-150Mbps-Raspberry-Supports/dp/B003MTTJOY/ that a lot of people say works with the raspberry pi, so this should probably work with FreeBSD right?
Larry-the-BSD-guy is a former print journalist and now freelance technical documentation writer.
https://www.linkedin.com/in/larrycafierowordsmith
There are differences between Linux and BSD environments. A burn-rubber speed differential is not one of them.
When moving to Unix/OpenBSD/Linux it's generally two phases: migrating the workflows and migrating the infrastructure. Infrastructure is pretty straightforward and pretty easy.
If your users are editing documents you need to very carefully consider options. LibreOffice, Calligra Office, Google Docs (G-Suite), or maybe cloud Windows desktops like AWS WorkSpaces.
You need to be very wise and cunning about this, and not come off as a brash young hot-head with a utopian prescription, or your users will draw the wrong conclusions and push back hard. Do a lot of careful thinking and gentle talking before you make any moves.
The only game I really remember using ScummVM was one of the [Myst]() games.
The most emulation I'd do is probably for systems for older games (or hell maybe even Switch emulation would work just fine).
Out of curiousity: Does OpenBSD have much troubles with modern hardware used for gaming? Like with AMD CPUs/GPUs, or even some motherboards? I'm just curious if there's anything egregious.
Down for me. Google to the rescue: http://webcache.googleusercontent.com/search?q=cache:blather.michaelwlucas.com/archives/994
EDIT: It's only some basic install instructions. Maybe http://www.dragonflybsd.org/ is a better place for an introduction to the OS.
Well good question. https://archive.fosdem.org/2020/schedule/event/netbsd_not_just_for_toasters/
Fosdem talk about NetBSD plus pkgsrc which is actively being used by NASA :)
Some intro to NetBSD http://netbsd.org/gallery/presentations/nia/campplusplus2020/slides.html
And they say it's not embedded based on OpenRC? In intertet there is information.
Submitted by ericbsd on Wed, 05/02/2018 - 11:44 You might have seen the discussion about this subject on the GhostBSD forums. So yes GhostBSD will release a version in the future with TrueOS as the base system. We have not yet decided if we will continue releasing a version with FreeBSD as the base operating system. For some time we have discussed problems that GhostBSD is facing in the long run. Some of our community have asked for improvements including a better rc such as OpenRC. We all have thought of OpenRC, but for a small team, it is a hard thing to do on our own as a project. After a lot of discussions, we decided to join TrueOS effort. Since then it is now making more sense as both of the main developers of GhostBSD work for iXsystems. TrueOS is becoming more mature as an appliance building platform making it appealing for the goal of creating reproducible builds of GhostBSD. Security-enhancing features such as LibreSSL integration and improved service management with OpenRC are just a few examples of some the improvements the switch will bring. http://www.ghostbsd.org/GhostBSD_is_switching_its_system_base
by ericbsd » Fri May 25, 2018 10:07 am TrueOS will no longer offer a Desktop, TrueOS is becoming an embedded, system that we can build quality appliances with and systems like GhostBSD and new projects that will emerge of that change. GhostBSD will stay about the same it has always been, but we will have a comfortable way to upgrade from version to version. The significant difference will be the boot time compared to the current release, OpenRC will be in base, Software wise it will be similar to the previous version.
If there are any other Linux users who decide to read this I'd encourage you to check out GhostBSD. It makes use of the FreeBSD userland, and it's still makes it dead easy to create a ZFS partition (doing it manually still alludes me). You can have your fancy tiling window managers (i3, bspwm, etc) or lightweight floating/stacking window managers (XFCE which comes standard in an .iso, Fluxbox, etc).
The only think I can see anyone gripe about is "no gaemz" but you could setup a virtual machine of some Linux distro and play the "gaemz."
I haven't done a detailed measuring of it. For day-to-day use, it doesn't seem to be a killer. I'm pretty certain that most of the major pain points have improved since this thread from 2011. Though I also know that certain utilities like PF don't take advantage of multi-core/CPU. For better or worse.
systrace is probably the best you'll get on OpenBSD for now:
Even then, it's not the be-all and end-all and has a bunch of problems (much like MAC as a whole).
> I spent a long while sitting and trying to filter through the documentation on what I should do to actually use my whole disk, instead of having a bunch of assorted partitions for things I don't care about having as special partitions.
Here's the thing: On OpenBSD, the defaults are usually the defaults for a reason. The bunch of assorted partitions for things I don't care about add to the security of the system, because they allow for mount flags such as "nodev" and "nosuid". It is obvious that you have not read the FAQ.
"w" for "whole disk", followed by "w" and "q" to write the partitions to the disk and quit disklabel will not kill you.
That's not true, see rc.d(8).
Many things don't need a daemon_flags= line, unless you need to specify non-default options.
I'm unsure how a GUI would help you given being dyslexic; however not being dyslexic myself, I won't speculate. I will, however, ask if you've read any of the relevant man pages? The fastest way to learn your way around OpenBSD is to read the man pages. This isn't linux; the manual pages in OpenBSD are generally very well written, complete, and always helpful.
You have two options I can think of off the top of my head: writing a disklabel file before hand and applying that, or keep it simple and rock defaults until you're more familiar with your needs.
PXEboot + http://www.openbsd.org/faq/faq4.html#site ? I haven't tried it, and I don't know whether it would prompt you for the installation settings.
http://people.cs.uchicago.edu/~brendan/howtos/openbsd_install/ seems to be another approach.
Using svnd to do encrypted volumes is the old and not as maintained way of doing it. Softraid is much newer and easier to use. I've run my home partition encrypted on OpenBSD for a few years using svnd and almost a year now using softraid. To setup softraid just do 'bioctl -c C -l /dev/sd1e softraid0' where /dev/sd1e is a partition with the RAID type. Svnd is still useful for mounting drive image files but for encryption I wouldn't bother with it.
Unfortunately this card isn't compatible with FreeBSD AFAIK. Many threads on the FreeBSD and FreeNAS forums with similar reports, and it's not listed on the FreeBSD hardware support page (nor is the underlying Marvell 9480 chipset)
If you're new to BSD, I would probably recommend trying out Free first, before going to some of the more exotic distros. The main reason why is because FreeBSD has a lot of good documentation, such as the handbook.
So if you install that with Virtualbox (although I use vmWare Player, which I prefer, because it lets me access my files in Windows 7 if you have the free addons installed) then you can read along in the handbook and learn all about it.
I would also recommend learning about shell scripting if you don't know it, as well. That will really help you on any UNIX system.
> All of the BSDs listed have x86 support
And much, <strong>much</strong> more including ARM, Raspberry Pi and others.
> For instance, Sony and Apple, even when using BSD code in their products, do not give all their improvements back to the community.
Of course not, and it's not required. Which is a big point for me.
Working with a system on which I know that if I can contribute something back, it'll be appreciated (well as long as it satisfies formal styling guidelines...), and if I don't, no one minds.
Because why should they be entitled to my work?
Of course, this is a matter of philosophy and I really like my bikeshed transparent.
freebsd-update is only for binary updates to the base system. Information on updating and upgrading is in the handbook. Personally, I use portmaster but portupgrade is also popular and there are other tools in ports/ports-mgmt.
There is an article about this in the FreeBSD handbook. I'd recommend geli instead of gdbe since it's the newer subsystem.
Well, consider how to install a jail:
- FreeBSD Handbook: fetch source, buildworld, sleep, coffee, etc, installworld
- Much faster: fetch install sets, set DESTDIR, extract
...
I can hear "then submit patch" from far away.
But then again ezjail requires buildworld, too. Or so I heard (never actually checked - I always create jails from binary sets).
Now tell me that FreeBSD discourages building from source.
If it's for home use, and you're just understandably fed up with DD-WRT, and your primary concern is the quality/price relation; then why not go for one of the recent midrange TP-Link gigabit+wireless routers, and stick to OpenWRT.
That's of course Linux-based for drivery reasons, but the cooperating UI and CLI configuration tools, prepared packages, and builtin IPv4+IPv6 routing capabilities are exceptionally useful. While of course, I'd also like to see OpenBSD suing OpenWRT for name slander, or forking it into, oh let's say, "LibreWRT" - it's already quite useful as firewall/router and mini server.
I find zoneedit to be a fairly simple, good option - first two zones are free, after which each zone is 1$ per zone per month.
It supports dynamic dns without any subdomain bullshit - I do not like the idea of sharing my domain.
UFW is not a firewall. It is a simplified command line interface for managing netfilter. I think the hierarchy looks like this:
user -> ufw -> netfilter -> iptables
EDIT: I may have that a bit out of order, but read more about it at ufw in Launchpad
TarBalls are....ok? Is there an executable file format that works on BSD? Similar to AppImages or Flatpak? Not necessarily universal just easy to use? Do BSD operating systems have something like .deb files?
I agree that every application needs a tar ball but, I still feel like they are a pain to use.
It's certainly not dead, as the maintainer (Leah Rowe) will just merge new revisions of Coreboot with her own patches.
Also, Libreboot is not hostile to BSD: https://notabug.org/vimuser/libreboot-website/commit/6d8ac69e0c252c4e0bdf019aee978d8a13de0e10
It appears jaimef is updating the benchmarks with more OS's, but they're still available and are linked at the bottom of the text file. Direct link here.
Your assumption about how the benchmarks operate is incorrect however. As you can see from reading one of the samples e.g. bm_fiber_ring.rb, they use a Bench class to do the iterations.
I would agree that some different metrics could be used though. Perhaps run each benchmark for x seconds, and then count how many iterations were performed for the duration. Might prove insightful.
The FreeBSD No Starch book just came out a year and a half ago and the Handbook is constantly updated so I don't know why you think they're outdated.
In addition, if you really want to get into the bowels of the FreeBSD operating system
No this one is for private usage.
I found this also, http://www.amazon.com/Super-Micro-X7SPA-H-Motherboard-Chipset/dp/B0038GVR82
UPDATE: Oh, didn't notice, Openbsd only supports Intel i82540, i82541, i82542, i82543, i82544, i82545, i82546, i82547, i82571, i82572 and i82573 based adapters.
So this is a no go - BUMMER!
Hello iio7, >It turns out that the X7SPA-H works perfectly. I think I am gonna go with that as it is cheaper than Soekris.
~~Can you link to that?~~
You did: http://www.amazon.com/Super-Micro-X7SPA-H-Motherboard-Chipset/dp/B0038GVR82
Also in it behind some isp router / modem?
The Soekris box their using takes one of these mini cards, they're just recommending one that is well supported.
EDIT: I would recommend just getting a cheap consumer router and setting it up just as an AP, let the router just do the ethernet.