I have recently started trying out BSDs as an alternative to Linux and found out that Spotify isn’t supported. Before you say try it in a browser this doesn’t work as spotify has DRM that doesn’t work on BSD OSes.
Now is there a way to stream music similar to Spotify? I know there is a downloader program available.
Furthermore do you know what self-hosted options are available? I already have a basic *arr stack and am always up for convoluted server and Linux hijinks.
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.
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.
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.
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.
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.
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.
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !piracy@lemmy.dbzer0.com
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
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.
Install on ZFS root, snapshot a known good, then you can rollback as you wish.
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.
That almost certainly untrue. Do not run CURRENT, it has
INVARIANTSandWITNESSenabled that will make it painfully slow.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.
Again, it is because you are using CURRENT. Don’t use it.
Never used current, I went with stable. What’s the solution?
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.
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.
ubt0: ubt_bulk_read_callback:1131: bulk-in transfer failed: USB_ERR stalled.
Also ctrl+L isn’t clearing the screen.
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.
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 need to read the handbook before you start spouting judgments about the releng process.
STABLE is cut from CURRENT. RELEASE is cut from STABLE.
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.