iirc British plugs do have a fuse built in to every plug, but they are also the only ones who do that
iirc British plugs do have a fuse built in to every plug, but they are also the only ones who do that
sorry, i shower twice a day and wear deodorant but i just sweat so damn much that i end up smelling within a few hours no matter what :(
idk what the official pronunciation is, but i say “gee lib cee” and “clang” (like the onomatopoeia)
I use a PowerEdge T620 as my daily driver, let me assure you the CPU fans at full speed can be heard clearly through 3 closed doors :P
they’re still pretty RISC, using fixed-width instructions and fairly simple encoding. certainly a hell of a lot simpler than the mess that is x86-64
That said, there are “active” USB extension cables which draw current from the power lines and use it to boost the signal along the data lines
Michelangelo’s David is a well-known marble statue which was carved using a chisel.
/r/homelabsales and /r/hardwareswap
Yeah, they were previously hosted by Curse until Fandom bought out all the Curse wikis and transferred them to their ad-ridden pile of shit
Yeah, although the neat part is that you can configure how much replication it uses on a per-file basis: for example, you can set your personal photos to be replicated three times, but have a tmp directory with no replication at all on the same filesystem.
You don’t want to unless you’re just planning on running a web browser or word processor or something, they’re significantly buggier and massively slower than the proprietary driver, and especially so on newer cards.
Looks like a graphics driver issue. Are you using the proprietary Nvidia drivers or Nouveau?
What exactly are you referring to? It seems to me to be pretty competitive with both ZFS and btrfs, in terms of supported features. It also has a lot of unique stuff, like being able to set drives/redundancy level/parity level/cache policy (among other things) per-directory or per-file, which I don’t think any of the other mainstream CoW filesystems can do.
The recommendation for ECC memory is simply because you can’t be totally sure stuff won’t go corrupt with only the safety measures of a checksummed CoW filesystem; if the data can silently go corrupt in memory the data could still go bad before getting written out to disk or while sitting in the read cache. I wouldn’t really say that’s a downside of those filesystems, rather it’s simply a requirement if you really care about preventing data corruption. Even without ECC memory they’re still far less susceptible to data loss than conventional filesystems.
I considered a KVM or something similar, but I still need access to the host machine in parallel (ideally side-by-side so I can step through the code running in the guest from a debugger in my dev environment on the host). I’ve already got a multi-monitor setup, so dedicating one of them to a VM while testing stuff isn’t too much of a big deal - I just have to keep track of whether or not my hands are on separate keyboard+mouse for the guest :)
Functionally it’s pretty solid (I use it everywhere, from portable drives to my NAS and have yet to have any breaking issues), but I’ve seen a number of complaints from devs over the years of how hopelessly convoluted and messy the code is.
I do this for testing graphics code on different OS/GPU combos - I have an AMD and Nvidia GPU (hoping to add an Intel one eventually) which can each be passed through to Windows or Linux VMs as needed. It works like a charm, with the only minor issue being that I have to use separate monitors for each because I can’t seem to figure out how to get the GPU output to be forwarded to the virt-manager virtual console window.
And Ctrl+shift+alt+win+L to open LinkedIn (seriously, try it!)
That is very slow, unless the drive is connected over USB or failing or something, a drive of that capacity should easily be able to handle sequential writes much faster than that. How is the drive connected, and is it SMR?
I don’t know about the others, but Arduino is literally just C++ with some macros/library functions.