Always use /dev/disk/* (I use by-id) for RAID, as those links will stay constant even if a disk is renamed (for example, from sdb to sdd).
redditor since 2008, hoping kbin/the Fediverse can entirely replace it.
Always use /dev/disk/* (I use by-id) for RAID, as those links will stay constant even if a disk is renamed (for example, from sdb to sdd).
How I felt 10 minutes ago when I fixed a bug just after zipping it for release.
Ubuntu is just getting worse and worse. I was pretty happy running Ubuntu server for years after moving from Gentoo; I jag lost interest in spending time taking care for that server and wanted something easy.
I went to Debian half a year ago and it’s been great. Should’ve done it earlier.
ZFS is really nice. I started experimenting with it when it was being introduced to FreeBSD, around 2007-2008, but only truly started using it last year, for two NASes (on Linux).
It’s complex for a filesystem, but considering all it can do, that’s not surprising.
Helpful yes, but far from enough. It only helps in some scenarios (like accidental deletes, malware), but not in many others (filesystem corruption, multiple disks dying at once due to e.g. lightning, a bad PSU or a fire).
Offsite backup is a must for data you want to keep.
That’s in bytes. A modern NVMe drive can do about 7 GB/s (more than 10 for PCIe 5.0 drives). Even SATA could handle 5 Gbit/s, though barely.
Sorry for the nitpick, but you probably mean GB/s (or GiB/s, but I won’t go there). Gbps is gigabits per second, not gigabytes per second.
Since both are used in different contexts yet they differ by about a factor of 8, not confusing the two is useful.
I’m all for open source services, but realistically, what potential issues are there with using GitHub?
Every contributor has a copy of the Git repo, so isn’t the worst case basically losing access to issues and similar data? And even that is very unlikely.
Oh! That’s awesome. I’m that case I’ll either try it when the release containing that commit is out, it maybe even earlier.
I’m aware, but I don’t think that code will affect the webOS version unfortunately. And even if it does, the app needs to be updated first.
Honestly it’s been a year since I tried it now so I don’t remember everything. One thing I really feel is crucial is turning down subtitle brightness in HDR. Plex allows for grey subtitles, which in HDR look white, except not at 700+ nits. They literally light up the room in dark scenes, and it’s extremely jarring in dark scenes (with APL of 1 nit or less).
I’d love to use Jellyfin instead of Plex, but the LG webOS client has literally never been updated. The first public version from July 2022 is still the latest version, and it’s not really there yet.
Why would they plug the phone to a PC via USB AND set it to webcam mode AND record or broadcast in a program on the PC if they didn’t want people to see?
z is for gz files only though, there are plenty of others. xf autodetects and works with all of them (with GNU tar att least).
94 Mbps is basically exactly what you can get from a 100 Mbps connection after overhead. 93-95% or so of the theoretical maximum. Something’s wrong and you’re getting a 100 Mbit/s connection.
Do most editors do that by default? If so, that’s great – if not, it’s just a downside for tabs, if you need to hit enter, backspace out the automatic indents and then press space 30 times rather than just hit enter and have it aligned automatically.
vim seems to auto-insert tabs when you hit enter mid-function definition, at least with standard settings.
How does that work, and with which editor settings? If you simply set the tab width (tabstop) in vim, things go south.
Say you have a function definition one indent level in, then 22 characters of text. You more want to align the next line to that. How does that work in practice with tabs?
The obvious way with tabs and ts=4 would be 6 tabs and two spaces(one tab for the initial indent, the rest to match 22 characters). But then someone with ts=2 comes along and barely gets half way there, or someone with ts=8 who overshoots by a lot.
The consistent appearance thing is probably more about how mixing tabs (for indentation) and spaces (for alignment, eg in multi-line function definitions of calls) looks like complete crap if you change the tab width.
I don’t think I’ve ever made a “clean upgrade” on Linux. I’ve done the opposite though, that is, bring an old install over to a new computer.