How did you set that path exactly?

Out of curiosity what do you use Linux for and what do you use FreeBSD for? Do you use FreeBSD as a desktop or only as a server?

I hardly use Bluetooth. But yes I don’t think FreeBSD will work on my laptop for example. It has issues with the keyboard on that machine.

I managed to fix it using some command from a forum luckily.

I now believe it’s Bluetooth related. Boads well for using Bluetooth devices.

ubt0: ubt_bulk_read_callback:1131: bulk-in transfer failed: USB_ERR stalled.

Also ctrl+L isn’t clearing the screen.

It’s USB related. Probably an unsupported device. If it’s really an issue I can address it later but first I need to get the thing installed. Also I had no idea you could do that with ncurses.

Yeah I got that thanks. It’s a very odd way to label things. It doesn’t follow industry standards which are normally: alpha, beta, release candidate, release.

Or even the debian method of: unstable, testing, stable, oldstable.

Never used current, I went with stable. What’s the solution?

Did I say CURRENT? I meant STABLE. Which is weird because shouldn’t something called stable be the version you release, but release is a separate one. It’s confusing.

You can run a Linux Jail/Container in FreeNAS, right?

I am aware jails exist, I had bastille installed before I bricked my system to play with.

That’s good to know. Is there also a way to suppress error messages in the installer? They fill the whole screen from one repeating message and I can’t actually install it because of that.

I tried that method. It’s seriously borked if you ever want transcoding to work. Jellyfin has a customized version of ffmpeg they used that just dosen’t exist on FreeBSD to the best of my knowledge. You can maybe make it work with the FreeBSD version but it would be an ugly hack.

Yeah this might be the way. I have created a FreeBSD current USB drive to install off of. I am thinking the newer slightly less stable version has less GPU issues as that seems to be the main factor.

Okay I will probably move to FreeBSD proper eventually. I am still new to this though and likely to break things. I don’t want to have to go through a whole process every time I mess up to get a usable working system until I actually know what I am doing.

I mean docker and especially lxc do a lot more than just chroot. They use cgroups, namespaces, and other stuff that’s beyond my paygrade. LXC remaps user IDs for example. That’s without getting into tech like gvisor and runsc that further isolates them by restricting system calls and re implementing some of them to increase security. Obviously there are things like privileged containers which have fewer restrictions, but those are the exception not the rule. From what I understand of chroot it only really restricts what files it can see; there is a reason why android supports chroots + termux but not a full docker install. Chroots to me are mainly used for bootstrapping systems and recovering systems. They aren’t meant for real virtualization or server work by themselves if you catch my drift.

Now you sound like an Arch kid. I say this as someone who used to be an Arch kid sort of.

Oh I am sure the kernel support is great. I am more having issues working with chroots directly. I am much more at home managing docker and lxc which are more isolated. I just broke something trying to remove a couple chroots while stuff was still mounted - I think I nuked /home. You don’t really have that issue with docker containers or lxc, it’s a simple command to remove.

Honestly I haven’t found them to do anything daft yet. From my understanding FreeBSD is a pain to configure for desktop usage as it’s designed more for servers. Tell me if I am wrong.

Yeah tbh I made a mess of the Linux environment. I am gonna reinstall and see what happens. There are other potentially GPU related things going on on this system though so IDK. Like I could disable it for that one application but that wouldn’t fix the other issues if that makes sense.

The Linuxulator is cool but I kind of don’t trust it. Maybe I will try Linux containers.

Those steps are outdated. I specifically had to lookup spotify’s directions for installing on Ubuntu as the public key has changed I think. It’s also just sort of freezes, it doesn’t close or anything. There is a message about the GPU drivers I don’t really understand and probably can’t fix as that’s a kernel issue.