To add some more : Done FreeBSD and OpenBSD installations here this month. Having FreeBSD on a Raspberry Pi was much easier than expected and boots from USB (yay!). Installing OpenBSD with disk encryption was also much easier than before because the installer has build in support. One day I’d like to have an OpenBSD server running with Honk on it for simple micro blogging, and maybe wireguard VPN.Perhaps with https://openbsd.amsterdam
I got a spare RPi3. Seems the hardware support is great, even with wifi. RTC seems to be unsupported tho. Such a shame since I got a DS3231 just for the Pi.
I got a spare RPi3. Seems the hardware support is great, even with wifi. RTC seems to be unsupported tho. Such a shame since I got a DS3231 just for the Pi.
What’s DS3231 ?
How’s your overall experience?
So far I’ve only been using ssh to log in to the FreeBSD stick on the pi4, and have been testing it with a GELI encrypted USB disk to explore that and learn some more, besides using LUKS with Linux. I have been thinking about making desktop backups to the Geli disk via rsync. I find it interesting to learn some more internals of BSD again (like years ago). For example in Linux the default command to check your own local IP address is ip. The command ifconfig has been deprecated on Linux. But on FreeBSD and iirc OpenBSD it is - tada! - ifconfig. I’m curious to have a look at Bastille given enough time.
DS3231 is an I2C based high accuracy RTC chip, usually comes in breakout modules. Mine was packaged in such a way you can plug in the header directly to the expansion pins of the Pi.
What you just described sounds wild to me. I’ll check it out!
Much depends on your use cases I figure. Here’s an example about my mixed feelings for Linux : I use Debian among others on the desktop. I noticed that when I log out from the GUI and return to the Display Manager a lot of processes keep running in the background all owned by my user. Maybe not a problem but I do not like it so much. I compared it with an OpenBSD installation I have. The same happens except for less processes and none of them is owned by my user.
If you’re trying to use it as a workstation or a laptop, you won’t find much compelling. It’s built with the intent to act as a server. In fact, as a web server or networking server it’s second to none.
Administrating BSD is lovely. It’s well documented and everything is very stable, understandable, and predictable.
I’m pretty much a Debian person at this point. I’ve been trying to have some love for the BSDs, but honestly it’s been hard. Any advice?
To add some more : Done FreeBSD and OpenBSD installations here this month. Having FreeBSD on a Raspberry Pi was much easier than expected and boots from USB (yay!). Installing OpenBSD with disk encryption was also much easier than before because the installer has build in support. One day I’d like to have an OpenBSD server running with Honk on it for simple micro blogging, and maybe wireguard VPN.Perhaps with https://openbsd.amsterdam
I got a spare RPi3. Seems the hardware support is great, even with wifi. RTC seems to be unsupported tho. Such a shame since I got a DS3231 just for the Pi.
How’s your overall experience?
What’s DS3231 ?
So far I’ve only been using ssh to log in to the FreeBSD stick on the pi4, and have been testing it with a GELI encrypted USB disk to explore that and learn some more, besides using LUKS with Linux. I have been thinking about making desktop backups to the Geli disk via rsync. I find it interesting to learn some more internals of BSD again (like years ago). For example in Linux the default command to check your own local IP address is
ip
. The commandifconfig
has been deprecated on Linux. But on FreeBSD and iirc OpenBSD it is - tada! -ifconfig
. I’m curious to have a look at Bastille given enough time.DS3231 is an I2C based high accuracy RTC chip, usually comes in breakout modules. Mine was packaged in such a way you can plug in the header directly to the expansion pins of the Pi.
What you just described sounds wild to me. I’ll check it out!
RTC chip, IIRC
Much depends on your use cases I figure. Here’s an example about my mixed feelings for Linux : I use Debian among others on the desktop. I noticed that when I log out from the GUI and return to the Display Manager a lot of processes keep running in the background all owned by my user. Maybe not a problem but I do not like it so much. I compared it with an OpenBSD installation I have. The same happens except for less processes and none of them is owned by my user.
loginctl user-status
If you’re trying to use it as a workstation or a laptop, you won’t find much compelling. It’s built with the intent to act as a server. In fact, as a web server or networking server it’s second to none.
Administrating BSD is lovely. It’s well documented and everything is very stable, understandable, and predictable.