Eh - YT music (premium) offers 256kB-ish Opus now. That’s on par with 320kBps MP3.
Eh - YT music (premium) offers 256kB-ish Opus now. That’s on par with 320kBps MP3.
YT Music Premium delivers 256kBit/s Opus now, Deezer delivers FLAC.
That sentence does not make any sense whatsoever. SATA and SAS are hot pluggable as well.
I’ve got some vservers and some block storage at hosters in a different country and I terminate a VPN tunnel there from yet another country. Storage is LUKS encrypted and VMs are configured to halt hard automatically in case of certain triggers that hint towards hypervisor side fuckery.
It’s not bullet proof, but it’s fire and forget, basically seed boxes where I’ve split knowledge further.
I used this as an exercise in provider agnostic deployment and I’m mainly hosting archive.org torrents that can use some seeding there.
Please use Opus instead of Vorbis. Vorbis is old and had been superseded by Opus.
Yes, backups need monitoring. Preferably automated test restored, but at least monitoring of their archives.
except for System Shock 2.
No, at some point I’d make a very unmanly noise and Alt-F4 the fuck outta there.
Eaton. Supported by Nut, works with 50Hz as well as the 52Hz my emergency power puts out.
Subpoenaed for all reddit user data if those users. Didn’t go anywhere, iirc, but they do try.
That’s how my GPU instances for reencoding connect to my self deployed seed box instances. Works just fine.
Reddit was subpoenaed for that shit.
There’s something in there that causes the reply button to hang indefinitely.
side remark: That’ll be the behaviour when the Lemmy GUI tries a post that is rejected by the server for mybe being too long. You should see details about that in the network monitor of the browser debugging thingie you get to with F12.
Anyway:
The first red line on the left is where the logs start to divert. Everything else is a follow up error. It tells us, that your config was loaded and something failed during applying it. We now know that we don’t have to hunt anything regarding the “config stick”.
We will now have to find out, what actually happens to your network config in full automatic mode and why it can’t access the network.
Please remove the manual network from your config stick and instead, add an authorized_keys
file with your ssh key as described here: https://developers.home-assistant.io/docs/operating-system/debugging/
As long as you can resolve and access the GUI via homeassistant.local
, you should be able to ssh in to port 22222 on the same hostname as well.
After doing so, please run ha network info
and post the output. Should look something like this. I hope that this is possible during the stage at which the installer hangs for you.
Ah, so you have network connectivity on the RPi. That’s good. Could you download the raw logs, scrub them of any identifying data, aka, name, mac-adresses and the like and post them here?
Yep, that looks right then.
From the installation log, I get the follow message:
How did you get that information with network access - I assume, you have a screen connected? Is it possible to temporarily use the keyboard from your desktop?
Let’s cover the basics: you took care of this part?
Yes. Now, if we could implement an irl place without all those people as well, I think I’d like that. Everything contains idiots but I find the overall company around here at least somewhat filtered of them.
Yeah, those are awesome - but even with an ATX mainboard, a CPU and a few spinning disks it’s become easier to stay on this side of 40W.
Yeah - that has changed since then. Power usage in the 30 to 40W range is easily attainable of you take some care selecting the components.
Yes, but, no.
Yep. I dabble in recruiting related stuff at conferences and expos for our company occasionally and I usually meet one or two young people that get the “get in contact!” remark on the protocol sheet. They’re out there, they’re just rare.