amigan

100% agreed, but it is in the realm of possibility that they would do this. It’s somewhat smug of me, but honestly I have never been so happy as during the past few years not to be a gamer. Y’all have to deal with mountains of bullshit.

I wouldn’t take this for granted. Even if it is true today (I have no idea, I don’t own a switch, and wouldn’t be surprised if it requires even physical media to authenticate), Nintendo could alter the deal with an update.

Linux on laptops, and certain other servers (TV headend/DVR, APCO P25 SDRtrunk host), and video transfer workstation. FreeBSD on any other servers, routers, and workstations, including my home automation controller (I maintain a fork of Home Assistant for FreeBSD).

Running FreeBSD on a laptop newer than 5ish years old is asking for a bad time no matter what. Linux has Intel and AMD engineers implementing power management for their parts. FreeBSD has no such help. Your laptop will likely be idling at a much higher power consumption than it would under Linux.

An idea, maybe just stick to Linux if first class hardware and proprietary software support is what you’re chasing.

That is your bluetooth adapter. Just disable it, press 3 at the boot menu to break to loader prompt and set hint.ubt.0.disabled="1" and boot

Please quote me the relevant “industry standards.” It is all perspective, and FreeBSD releng certainly does not cater to what some rando online might think is an intuitive way to name release trains. This has been done this way for 30 years.

To what? Provide the error message and stop asking to be spoonfed? And you can hit ^L to make the install refresh the screen like with any curses program, fyi.

You need to read the handbook before you start spouting judgments about the releng process.

STABLE is cut from CURRENT. RELEASE is cut from STABLE.

The same as you can in regular FreeBSD, under a bhyve VM running Linux. You can also use the linux ABI in a jail.

Again, it is because you are using CURRENT. Don’t use it.

That almost certainly untrue. Do not run CURRENT, it has INVARIANTS and WITNESS enabled that will make it painfully slow.

Install on ZFS root, snapshot a known good, then you can rollback as you wish.

I know how docker and lxc work and the difference between them and chroots. But you’re talking about persistence of changes breaking things. You are right that chroot only operates on the VFS namespace. Jails are the kind of isolation you are after, and in fact were in FreeBSD before containerization was even a word.

Things like remapping user IDs start to pervert the line between userspace and what the kernel gives a shit about. Linux containerization technologies are many things, but elegant they are not.

I use Arch too. I’ve been using FreeBSD for 21 years, though. I run everything on it, even this Lemmy instance.

More isolated in which way? You should probably read up on how all this stuff is actually implemented, it will clarify your understanding of what is going on rather than just throwing commands at the wall and seeing what sticks.

Yes, you are wrong. FreeBSD is a general purpose operating system. You install what you need and configure what you need. GhostBSD and its ilk are for weenies.

My advice is to ditch GhostBSD, you are basically putting yourself further into the corner than you already are by trying to use FreeBSD on the desktop.

Linux binaries run just by a syscall shim. There’s not much to trust or distrust. If all the syscalls are implemented and mapped to native FreeBSD syscalls, the thing works. Otherwise, it doesn’t.

Spotify is just an electron app. You can disable any GPU access just like you can with chrome via a flag.

My point is, unless spotify is trying to call a heretofore unimplemented syscall, it can be made to run. The linuxulator is basically as good as native.

I am sure they have muddied the waters with some garbage “user-friendly” configuration.