#bsds — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #bsds, aggregated by home.social.
-
We need alternatives that work:
1. #Technologists: #Smartphones need #customizable #alternatives like PCs with #Linux or #BSDs. NOW is the time to double down on it.
2. #Governments: If you really care about your #sovereignty, we need #regulations and strict #laws against this abuse, and the #corporate stranglehold of the #component_market.
3. #Consumers: Vote with your wallet! Prioritize your #freedom over short-term #savings. This is a time-tested strategy.
[6/6]
-
We need alternatives that work:
1. #Technologists: #Smartphones need #customizable #alternatives like PCs with #Linux or #BSDs. NOW is the time to double down on it.
2. #Governments: If you really care about your #sovereignty, we need #regulations and strict #laws against this abuse, and the #corporate stranglehold of the #component_market.
3. #Consumers: Vote with your wallet! Prioritize your #freedom over short-term #savings. This is a time-tested strategy.
[6/6]
-
We need alternatives that work:
1. #Technologists: #Smartphones need #customizable #alternatives like PCs with #Linux or #BSDs. NOW is the time to double down on it.
2. #Governments: If you really care about your #sovereignty, we need #regulations and strict #laws against this abuse, and the #corporate stranglehold of the #component_market.
3. #Consumers: Vote with your wallet! Prioritize your #freedom over short-term #savings. This is a time-tested strategy.
[6/6]
-
We need alternatives that work:
1. #Technologists: #Smartphones need #customizable #alternatives like PCs with #Linux or #BSDs. NOW is the time to double down on it.
2. #Governments: If you really care about your #sovereignty, we need #regulations and strict #laws against this abuse, and the #corporate stranglehold of the #component_market.
3. #Consumers: Vote with your wallet! Prioritize your #freedom over short-term #savings. This is a time-tested strategy.
[6/6]
-
We need alternatives that work:
1. #Technologists: #Smartphones need #customizable #alternatives like PCs with #Linux or #BSDs. NOW is the time to double down on it.
2. #Governments: If you really care about your #sovereignty, we need #regulations and strict #laws against this abuse, and the #corporate stranglehold of the #component_market.
3. #Consumers: Vote with your wallet! Prioritize your #freedom over short-term #savings. This is a time-tested strategy.
[6/6]
-
Thanks!
It's a great little OS! Only complaint is that it's a little slow to resume from S3 suspend (about 8 seconds), but it does so reliably.
Some intensive processes like opening bloated web pages incur a bit of a hiccup/delay, and I'm not sure why. I know the kernel scheduler is tunable, but I haven't found out how to go about doing that yet.
They're trying to target laptops more, so there's still some work to be done.
Of course, heavy Linux games don't run (haven't been able to get #KerbalSpaceProgram to work on #FreeBSD yet), but simpler linux executables can run (even GUI ones), and the
pkgrepos are quite exhaustive, about as many binary packages as Debian (around 150k), from my estimation.No flatpak, no Steam, so binary sources are limited, but there's tons of FOSS software that just runs without trouble.
The handbook (installable as a package or available on the web, both as html and pdf) is quite good, and fairly exhaustive, and to me, the biggest feature of the #BSDs is that they just make sense as an operating system, and aren't a haphazard and ever-changing collection of FOSS parts, like Linux distros are.
FreeBSD does take some manual configuration to get a GUI going, but it's honestly pretty easy, and the handbook tells you exactly what to do. They will have a GUI install screen in the installer soon, so that will become automatic.
I've got it running with #Wayland and the #Sway compositor, almost no issues. For some reason, neither i3status nor waybar have the ability to show Wifi link name and quality, so I developed my own little front-end script for i3status to restore that (I had to do the same thing for #OpenBSD for RAM usage).
I've had to come up with my own way to make sense of memory usage (a script that mimics Linux'
freeutility) and wifi link quality, but those were fun problems to solve.After a week or two of hacking around with it and getting all my own scripts and little utilities working with it, it has now become almost completely transparent and gloriously "boring." Basically the same as running Linux for most everything I do. XD
It has fewer pain points than #OpenBSD (which I honestly love as well, don't misinterpret me): a rock solid filesystem (ZFS), and full emoji support (lol priorities, amirite?).
It also has very good full-disk-encryption baked right in, which I'm missing from #NetBSD (but plan on playing with that OS later on as well, because I want to try ALL THE #BSDs! XD )
-
Thanks!
It's a great little OS! Only complaint is that it's a little slow to resume from S3 suspend (about 8 seconds), but it does so reliably.
Some intensive processes like opening bloated web pages incur a bit of a hiccup/delay, and I'm not sure why. I know the kernel scheduler is tunable, but I haven't found out how to go about doing that yet.
They're trying to target laptops more, so there's still some work to be done.
Of course, heavy Linux games don't run (haven't been able to get #KerbalSpaceProgram to work on #FreeBSD yet), but simpler linux executables can run (even GUI ones), and the
pkgrepos are quite exhaustive, about as many binary packages as Debian (around 150k), from my estimation.No flatpak, no Steam, so binary sources are limited, but there's tons of FOSS software that just runs without trouble.
The handbook (installable as a package or available on the web, both as html and pdf) is quite good, and fairly exhaustive, and to me, the biggest feature of the #BSDs is that they just make sense as an operating system, and aren't a haphazard and ever-changing collection of FOSS parts, like Linux distros are.
FreeBSD does take some manual configuration to get a GUI going, but it's honestly pretty easy, and the handbook tells you exactly what to do. They will have a GUI install screen in the installer soon, so that will become automatic.
I've got it running with #Wayland and the #Sway compositor, almost no issues. For some reason, neither i3status nor waybar have the ability to show Wifi link name and quality, so I developed my own little front-end script for i3status to restore that (I had to do the same thing for #OpenBSD for RAM usage).
I've had to come up with my own way to make sense of memory usage (a script that mimics Linux'
freeutility) and wifi link quality, but those were fun problems to solve.After a week or two of hacking around with it and getting all my own scripts and little utilities working with it, it has now become almost completely transparent and gloriously "boring." Basically the same as running Linux for most everything I do. XD
It has fewer pain points than #OpenBSD (which I honestly love as well, don't misinterpret me): a rock solid filesystem (ZFS), and full emoji support (lol priorities, amirite?).
It also has very good full-disk-encryption baked right in, which I'm missing from #NetBSD (but plan on playing with that OS later on as well, because I want to try ALL THE #BSDs! XD )
-
Thanks!
It's a great little OS! Only complaint is that it's a little slow to resume from S3 suspend (about 8 seconds), but it does so reliably.
Some intensive processes like opening bloated web pages incur a bit of a hiccup/delay, and I'm not sure why. I know the kernel scheduler is tunable, but I haven't found out how to go about doing that yet.
They're trying to target laptops more, so there's still some work to be done.
Of course, heavy Linux games don't run (haven't been able to get #KerbalSpaceProgram to work on #FreeBSD yet), but simpler linux executables can run (even GUI ones), and the
pkgrepos are quite exhaustive, about as many binary packages as Debian (around 150k), from my estimation.No flatpak, no Steam, so binary sources are limited, but there's tons of FOSS software that just runs without trouble.
The handbook (installable as a package or available on the web, both as html and pdf) is quite good, and fairly exhaustive, and to me, the biggest feature of the #BSDs is that they just make sense as an operating system, and aren't a haphazard and ever-changing collection of FOSS parts, like Linux distros are.
FreeBSD does take some manual configuration to get a GUI going, but it's honestly pretty easy, and the handbook tells you exactly what to do. They will have a GUI install screen in the installer soon, so that will become automatic.
I've got it running with #Wayland and the #Sway compositor, almost no issues. For some reason, neither i3status nor waybar have the ability to show Wifi link name and quality, so I developed my own little front-end script for i3status to restore that (I had to do the same thing for #OpenBSD for RAM usage).
I've had to come up with my own way to make sense of memory usage (a script that mimics Linux'
freeutility) and wifi link quality, but those were fun problems to solve.After a week or two of hacking around with it and getting all my own scripts and little utilities working with it, it has now become almost completely transparent and gloriously "boring." Basically the same as running Linux for most everything I do. XD
It has fewer pain points than #OpenBSD (which I honestly love as well, don't misinterpret me): a rock solid filesystem (ZFS), and full emoji support (lol priorities, amirite?).
It also has very good full-disk-encryption baked right in, which I'm missing from #NetBSD (but plan on playing with that OS later on as well, because I want to try ALL THE #BSDs! XD )
-
Thanks!
It's a great little OS! Only complaint is that it's a little slow to resume from S3 suspend (about 8 seconds), but it does so reliably.
Some intensive processes like opening bloated web pages incur a bit of a hiccup/delay, and I'm not sure why. I know the kernel scheduler is tunable, but I haven't found out how to go about doing that yet.
They're trying to target laptops more, so there's still some work to be done.
Of course, heavy Linux games don't run (haven't been able to get #KerbalSpaceProgram to work on #FreeBSD yet), but simpler linux executables can run (even GUI ones), and the
pkgrepos are quite exhaustive, about as many binary packages as Debian (around 150k), from my estimation.No flatpak, no Steam, so binary sources are limited, but there's tons of FOSS software that just runs without trouble.
The handbook (installable as a package or available on the web, both as html and pdf) is quite good, and fairly exhaustive, and to me, the biggest feature of the #BSDs is that they just make sense as an operating system, and aren't a haphazard and ever-changing collection of FOSS parts, like Linux distros are.
FreeBSD does take some manual configuration to get a GUI going, but it's honestly pretty easy, and the handbook tells you exactly what to do. They will have a GUI install screen in the installer soon, so that will become automatic.
I've got it running with #Wayland and the #Sway compositor, almost no issues. For some reason, neither i3status nor waybar have the ability to show Wifi link name and quality, so I developed my own little front-end script for i3status to restore that (I had to do the same thing for #OpenBSD for RAM usage).
I've had to come up with my own way to make sense of memory usage (a script that mimics Linux'
freeutility) and wifi link quality, but those were fun problems to solve.After a week or two of hacking around with it and getting all my own scripts and little utilities working with it, it has now become almost completely transparent and gloriously "boring." Basically the same as running Linux for most everything I do. XD
It has fewer pain points than #OpenBSD (which I honestly love as well, don't misinterpret me): a rock solid filesystem (ZFS), and full emoji support (lol priorities, amirite?).
It also has very good full-disk-encryption baked right in, which I'm missing from #NetBSD (but plan on playing with that OS later on as well, because I want to try ALL THE #BSDs! XD )
-
Thanks!
It's a great little OS! Only complaint is that it's a little slow to resume from S3 suspend (about 8 seconds), but it does so reliably.
Some intensive processes like opening bloated web pages incur a bit of a hiccup/delay, and I'm not sure why. I know the kernel scheduler is tunable, but I haven't found out how to go about doing that yet.
They're trying to target laptops more, so there's still some work to be done.
Of course, heavy Linux games don't run (haven't been able to get #KerbalSpaceProgram to work on #FreeBSD yet), but simpler linux executables can run (even GUI ones), and the
pkgrepos are quite exhaustive, about as many binary packages as Debian (around 150k), from my estimation.No flatpak, no Steam, so binary sources are limited, but there's tons of FOSS software that just runs without trouble.
The handbook (installable as a package or available on the web, both as html and pdf) is quite good, and fairly exhaustive, and to me, the biggest feature of the #BSDs is that they just make sense as an operating system, and aren't a haphazard and ever-changing collection of FOSS parts, like Linux distros are.
FreeBSD does take some manual configuration to get a GUI going, but it's honestly pretty easy, and the handbook tells you exactly what to do. They will have a GUI install screen in the installer soon, so that will become automatic.
I've got it running with #Wayland and the #Sway compositor, almost no issues. For some reason, neither i3status nor waybar have the ability to show Wifi link name and quality, so I developed my own little front-end script for i3status to restore that (I had to do the same thing for #OpenBSD for RAM usage).
I've had to come up with my own way to make sense of memory usage (a script that mimics Linux'
freeutility) and wifi link quality, but those were fun problems to solve.After a week or two of hacking around with it and getting all my own scripts and little utilities working with it, it has now become almost completely transparent and gloriously "boring." Basically the same as running Linux for most everything I do. XD
It has fewer pain points than #OpenBSD (which I honestly love as well, don't misinterpret me): a rock solid filesystem (ZFS), and full emoji support (lol priorities, amirite?).
It also has very good full-disk-encryption baked right in, which I'm missing from #NetBSD (but plan on playing with that OS later on as well, because I want to try ALL THE #BSDs! XD )
-
Thus Open Source versions of the #BSDs weren’t a big break from the original source, #FreeBSD & #NetBSD were already full complete operating systems while Linux remains an ever expanding kernel.
Not to mention the fact that it’s the #Linux community that usually borrows from innovations that the #BSD and #Solaris & #Illumos communities created, for decades, not the other way around.
-
I used to game on Arch too. Worked pretty well.
There's also the #BSDs in case you're not aware although not really for gaming. Just alternatives so you don't feel like you're in another walled garden like Apple and Microsoft.
-
I used to game on Arch too. Worked pretty well.
There's also the #BSDs in case you're not aware although not really for gaming. Just alternatives so you don't feel like you're in another walled garden like Apple and Microsoft.
-
I used to game on Arch too. Worked pretty well.
There's also the #BSDs in case you're not aware although not really for gaming. Just alternatives so you don't feel like you're in another walled garden like Apple and Microsoft.
-
I used to game on Arch too. Worked pretty well.
There's also the #BSDs in case you're not aware although not really for gaming. Just alternatives so you don't feel like you're in another walled garden like Apple and Microsoft.
-
I used to game on Arch too. Worked pretty well.
There's also the #BSDs in case you're not aware although not really for gaming. Just alternatives so you don't feel like you're in another walled garden like Apple and Microsoft.
-
@amin @daniel @sotolf @OpenComputeDesign @jp
Also, htop has braille graphs available, too. You just have to hunt through the options.
Not quite as purty as btop, but still extremely useful.
Most of the time, I just use this:
alias s='COLUMNS=999 top -bin 1 |head'Because how often do you just sit there and watch htop? I almost never do. I just want to know right then and there how the system is doing, and what's eating up the resources, and that alias is perfect for that:
~ $ s top - 12:07:57 up 4 days, 1:50, 7 users, load average: 3.71, 3.13, 3.12 Tasks: 449 total, 3 running, 446 sleeping, 0 stopped, 0 zombie %Cpu(s): 5.0 us, 15.0 sy, 0.0 ni, 75.0 id, 5.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 31811.8 total, 10477.4 free, 9630.5 used, 13957.3 buff/cache MiB Swap: 34991.0 total, 33129.0 free, 1862.0 used. 22181.3 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 15288 root 20 0 0 0 0 I 23.5 0.0 1:49.72 kworker/0:3-events 26378 root 20 0 0 0 0 R 23.5 0.0 0:37.77 kworker/u32:5+USBC000:00-con2 11140 root 20 0 0 0 0 I 11.8 0.0 0:20.64 kworker/6:2-eventsNote: if anyone's saying "why don't you just use
top -w999, the answer is that the alias is written to work on Linux and all of the major #BSDs. ;) -
@amin @daniel @sotolf @OpenComputeDesign @jp
Also, htop has braille graphs available, too. You just have to hunt through the options.
Not quite as purty as btop, but still extremely useful.
Most of the time, I just use this:
alias s='COLUMNS=999 top -bin 1 |head'Because how often do you just sit there and watch htop? I almost never do. I just want to know right then and there how the system is doing, and what's eating up the resources, and that alias is perfect for that:
~ $ s top - 12:07:57 up 4 days, 1:50, 7 users, load average: 3.71, 3.13, 3.12 Tasks: 449 total, 3 running, 446 sleeping, 0 stopped, 0 zombie %Cpu(s): 5.0 us, 15.0 sy, 0.0 ni, 75.0 id, 5.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 31811.8 total, 10477.4 free, 9630.5 used, 13957.3 buff/cache MiB Swap: 34991.0 total, 33129.0 free, 1862.0 used. 22181.3 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 15288 root 20 0 0 0 0 I 23.5 0.0 1:49.72 kworker/0:3-events 26378 root 20 0 0 0 0 R 23.5 0.0 0:37.77 kworker/u32:5+USBC000:00-con2 11140 root 20 0 0 0 0 I 11.8 0.0 0:20.64 kworker/6:2-eventsNote: if anyone's saying "why don't you just use
top -w999, the answer is that the alias is written to work on Linux and all of the major #BSDs. ;) -
@amin @daniel @sotolf @OpenComputeDesign @jp
Also, htop has braille graphs available, too. You just have to hunt through the options.
Not quite as purty as btop, but still extremely useful.
Most of the time, I just use this:
alias s='COLUMNS=999 top -bin 1 |head'Because how often do you just sit there and watch htop? I almost never do. I just want to know right then and there how the system is doing, and what's eating up the resources, and that alias is perfect for that:
~ $ s top - 12:07:57 up 4 days, 1:50, 7 users, load average: 3.71, 3.13, 3.12 Tasks: 449 total, 3 running, 446 sleeping, 0 stopped, 0 zombie %Cpu(s): 5.0 us, 15.0 sy, 0.0 ni, 75.0 id, 5.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 31811.8 total, 10477.4 free, 9630.5 used, 13957.3 buff/cache MiB Swap: 34991.0 total, 33129.0 free, 1862.0 used. 22181.3 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 15288 root 20 0 0 0 0 I 23.5 0.0 1:49.72 kworker/0:3-events 26378 root 20 0 0 0 0 R 23.5 0.0 0:37.77 kworker/u32:5+USBC000:00-con2 11140 root 20 0 0 0 0 I 11.8 0.0 0:20.64 kworker/6:2-eventsNote: if anyone's saying "why don't you just use
top -w999, the answer is that the alias is written to work on Linux and all of the major #BSDs. ;) -
@amin @daniel @sotolf @OpenComputeDesign @jp
Also, htop has braille graphs available, too. You just have to hunt through the options.
Not quite as purty as btop, but still extremely useful.
Most of the time, I just use this:
alias s='COLUMNS=999 top -bin 1 |head'Because how often do you just sit there and watch htop? I almost never do. I just want to know right then and there how the system is doing, and what's eating up the resources, and that alias is perfect for that:
~ $ s top - 12:07:57 up 4 days, 1:50, 7 users, load average: 3.71, 3.13, 3.12 Tasks: 449 total, 3 running, 446 sleeping, 0 stopped, 0 zombie %Cpu(s): 5.0 us, 15.0 sy, 0.0 ni, 75.0 id, 5.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 31811.8 total, 10477.4 free, 9630.5 used, 13957.3 buff/cache MiB Swap: 34991.0 total, 33129.0 free, 1862.0 used. 22181.3 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 15288 root 20 0 0 0 0 I 23.5 0.0 1:49.72 kworker/0:3-events 26378 root 20 0 0 0 0 R 23.5 0.0 0:37.77 kworker/u32:5+USBC000:00-con2 11140 root 20 0 0 0 0 I 11.8 0.0 0:20.64 kworker/6:2-eventsNote: if anyone's saying "why don't you just use
top -w999, the answer is that the alias is written to work on Linux and all of the major #BSDs. ;) -
@amin @daniel @sotolf @OpenComputeDesign @jp
Also, htop has braille graphs available, too. You just have to hunt through the options.
Not quite as purty as btop, but still extremely useful.
Most of the time, I just use this:
alias s='COLUMNS=999 top -bin 1 |head'Because how often do you just sit there and watch htop? I almost never do. I just want to know right then and there how the system is doing, and what's eating up the resources, and that alias is perfect for that:
~ $ s top - 12:07:57 up 4 days, 1:50, 7 users, load average: 3.71, 3.13, 3.12 Tasks: 449 total, 3 running, 446 sleeping, 0 stopped, 0 zombie %Cpu(s): 5.0 us, 15.0 sy, 0.0 ni, 75.0 id, 5.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 31811.8 total, 10477.4 free, 9630.5 used, 13957.3 buff/cache MiB Swap: 34991.0 total, 33129.0 free, 1862.0 used. 22181.3 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 15288 root 20 0 0 0 0 I 23.5 0.0 1:49.72 kworker/0:3-events 26378 root 20 0 0 0 0 R 23.5 0.0 0:37.77 kworker/u32:5+USBC000:00-con2 11140 root 20 0 0 0 0 I 11.8 0.0 0:20.64 kworker/6:2-eventsNote: if anyone's saying "why don't you just use
top -w999, the answer is that the alias is written to work on Linux and all of the major #BSDs. ;) -
Fortunately, it's all very linear and (hopefully) pretty easy to understand. I'd like to think that if you stuck a
set -xat the very top, the output would be pretty easy to mentally parse. It's mostly just if statements ;)All Debian-based and most rpm-based distros should work out of the box, in addition to homebrew, flatpak, snap (eww, lol), and even pipx, cargo, and rustup.
Also, the three major #BSDs, of course! ;)
-
Fortunately, it's all very linear and (hopefully) pretty easy to understand. I'd like to think that if you stuck a
set -xat the very top, the output would be pretty easy to mentally parse. It's mostly just if statements ;)All Debian-based and most rpm-based distros should work out of the box, in addition to homebrew, flatpak, snap (eww, lol), and even pipx, cargo, and rustup.
Also, the three major #BSDs, of course! ;)
-
Fortunately, it's all very linear and (hopefully) pretty easy to understand. I'd like to think that if you stuck a
set -xat the very top, the output would be pretty easy to mentally parse. It's mostly just if statements ;)All Debian-based and most rpm-based distros should work out of the box, in addition to homebrew, flatpak, snap (eww, lol), and even pipx, cargo, and rustup.
Also, the three major #BSDs, of course! ;)
-
Fortunately, it's all very linear and (hopefully) pretty easy to understand. I'd like to think that if you stuck a
set -xat the very top, the output would be pretty easy to mentally parse. It's mostly just if statements ;)All Debian-based and most rpm-based distros should work out of the box, in addition to homebrew, flatpak, snap (eww, lol), and even pipx, cargo, and rustup.
Also, the three major #BSDs, of course! ;)
-
Fortunately, it's all very linear and (hopefully) pretty easy to understand. I'd like to think that if you stuck a
set -xat the very top, the output would be pretty easy to mentally parse. It's mostly just if statements ;)All Debian-based and most rpm-based distros should work out of the box, in addition to homebrew, flatpak, snap (eww, lol), and even pipx, cargo, and rustup.
Also, the three major #BSDs, of course! ;)
-
@royal @fedora @SlashNevSlashDull
Wow, that's really #wholesome
Don't anyone forget @debian and #slackware, though! The grand-pappys of them all! ;)
And also, the other part of the #FreeSoftware OS family, the #BSDs! #OpenBSD, #FreeBSD, #NetBSD, #DragonflyBSD and derivatives, take a bow!
-
@royal @fedora @SlashNevSlashDull
Wow, that's really #wholesome
Don't anyone forget @debian and #slackware, though! The grand-pappys of them all! ;)
And also, the other part of the #FreeSoftware OS family, the #BSDs! #OpenBSD, #FreeBSD, #NetBSD, #DragonflyBSD and derivatives, take a bow!
-
Lots of responses already but I want to make a suggestion to look at other alternatives too.
The #BSDs are a decent option too. Maybe slightly more involved depending on your hardware. I'd recommend #GhostBSD (more traditional feel), #helloSystem (more like old Macs) or any Linux distro really.
Could also try WSL on Windows if you want to try something else.
-
Lots of responses already but I want to make a suggestion to look at other alternatives too.
The #BSDs are a decent option too. Maybe slightly more involved depending on your hardware. I'd recommend #GhostBSD (more traditional feel), #helloSystem (more like old Macs) or any Linux distro really.
Could also try WSL on Windows if you want to try something else.
-
Lots of responses already but I want to make a suggestion to look at other alternatives too.
The #BSDs are a decent option too. Maybe slightly more involved depending on your hardware. I'd recommend #GhostBSD (more traditional feel), #helloSystem (more like old Macs) or any Linux distro really.
Could also try WSL on Windows if you want to try something else.
-
Lots of responses already but I want to make a suggestion to look at other alternatives too.
The #BSDs are a decent option too. Maybe slightly more involved depending on your hardware. I'd recommend #GhostBSD (more traditional feel), #helloSystem (more like old Macs) or any Linux distro really.
Could also try WSL on Windows if you want to try something else.
-
Lots of responses already but I want to make a suggestion to look at other alternatives too.
The #BSDs are a decent option too. Maybe slightly more involved depending on your hardware. I'd recommend #GhostBSD (more traditional feel), #helloSystem (more like old Macs) or any Linux distro really.
Could also try WSL on Windows if you want to try something else.
-
@case2tv I chose #Enpass since it literally runs on everything* - espechally #Android and #Linux and doesn'r equire some subscription or charges people for the "privilegue" of self-hosting, like #BitWarden.
It's also #TechIlliterate-friendly.*Okay it doesn't run on #BSDs and #Unix except macOS & iOS, but then again:
People who daily drive #OpenBSD, #FreeBSD or #NetBSD are usually #TechLiterate enough to basically setup their own #password storage system from scratch & sync and backup stuff. -
@case2tv I chose #Enpass since it literally runs on everything* - espechally #Android and #Linux and doesn'r equire some subscription or charges people for the "privilegue" of self-hosting, like #BitWarden.
It's also #TechIlliterate-friendly.*Okay it doesn't run on #BSDs and #Unix except macOS & iOS, but then again:
People who daily drive #OpenBSD, #FreeBSD or #NetBSD are usually #TechLiterate enough to basically setup their own #password storage system from scratch & sync and backup stuff. -
@case2tv I chose #Enpass since it literally runs on everything* - espechally #Android and #Linux and doesn'r equire some subscription or charges people for the "privilegue" of self-hosting, like #BitWarden.
It's also #TechIlliterate-friendly.*Okay it doesn't run on #BSDs and #Unix except macOS & iOS, but then again:
People who daily drive #OpenBSD, #FreeBSD or #NetBSD are usually #TechLiterate enough to basically setup their own #password storage system from scratch & sync and backup stuff. -
That Old NetBSD Server, Running Since 2010
https://it-notes.dragas.net/2023/08/27/that-old-netbsd-server-running-since-2010/
#NetBSD #Xen #Virtualization #SysAdmin #Containers #BSD #BSDs #IT
-
That Old NetBSD Server, Running Since 2010
https://it-notes.dragas.net/2023/08/27/that-old-netbsd-server-running-since-2010/
#NetBSD #Xen #Virtualization #SysAdmin #Containers #BSD #BSDs #IT
-
That Old NetBSD Server, Running Since 2010
https://it-notes.dragas.net/2023/08/27/that-old-netbsd-server-running-since-2010/
#NetBSD #Xen #Virtualization #SysAdmin #Containers #BSD #BSDs #IT
-
That Old NetBSD Server, Running Since 2010
https://it-notes.dragas.net/2023/08/27/that-old-netbsd-server-running-since-2010/
#NetBSD #Xen #Virtualization #SysAdmin #Containers #BSD #BSDs #IT
-
That Old NetBSD Server, Running Since 2010
https://it-notes.dragas.net/2023/08/27/that-old-netbsd-server-running-since-2010/
#NetBSD #Xen #Virtualization #SysAdmin #Containers #BSD #BSDs #IT
-
...
With #BSD, there's no silly info pages or html help (at least as a primary source of documentation). There's just REALLY good manpages, especially on OpenBSD. FreeBSD comes with (or it might be an optional install) their excellent handbook as a PDF you can peruse at your leisure. Again, NetBSD I have the least knowledge of.
My experience with the big three #BSDs:
...
-
...
With #BSD, there's no silly info pages or html help (at least as a primary source of documentation). There's just REALLY good manpages, especially on OpenBSD. FreeBSD comes with (or it might be an optional install) their excellent handbook as a PDF you can peruse at your leisure. Again, NetBSD I have the least knowledge of.
My experience with the big three #BSDs:
...
-
...
With #BSD, there's no silly info pages or html help (at least as a primary source of documentation). There's just REALLY good manpages, especially on OpenBSD. FreeBSD comes with (or it might be an optional install) their excellent handbook as a PDF you can peruse at your leisure. Again, NetBSD I have the least knowledge of.
My experience with the big three #BSDs:
...
-
...
With #BSD, there's no silly info pages or html help (at least as a primary source of documentation). There's just REALLY good manpages, especially on OpenBSD. FreeBSD comes with (or it might be an optional install) their excellent handbook as a PDF you can peruse at your leisure. Again, NetBSD I have the least knowledge of.
My experience with the big three #BSDs:
...
-
...
With #BSD, there's no silly info pages or html help (at least as a primary source of documentation). There's just REALLY good manpages, especially on OpenBSD. FreeBSD comes with (or it might be an optional install) their excellent handbook as a PDF you can peruse at your leisure. Again, NetBSD I have the least knowledge of.
My experience with the big three #BSDs:
...
-
📢 Introducing the #FreeBSD Security Advisories and Errata Notices Bot! 🤖🔒
This bot, on an hourly basis, will monitor the rss feed from https://www.freebsd.org/security/feed.xml and share the headlines and links to the latest articles.
Happy reading! 📰💻
-
📢 Introducing the #FreeBSD Security Advisories and Errata Notices Bot! 🤖🔒
This bot, on an hourly basis, will monitor the rss feed from https://www.freebsd.org/security/feed.xml and share the headlines and links to the latest articles.
Happy reading! 📰💻
-
📢 Introducing the #FreeBSD Security Advisories and Errata Notices Bot! 🤖🔒
This bot, on an hourly basis, will monitor the rss feed from https://www.freebsd.org/security/feed.xml and share the headlines and links to the latest articles.
Happy reading! 📰💻
-
📢 Introducing the #FreeBSD Security Advisories and Errata Notices Bot! 🤖🔒
This bot, on an hourly basis, will monitor the rss feed from https://www.freebsd.org/security/feed.xml and share the headlines and links to the latest articles.
Happy reading! 📰💻