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).
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.
What does this have to do with systemd? Aren’t they safer in this situation because they aren’t using the beta xz release?
My systems running Debian stable with systemd also aren’t affected…
This is about the website.
10x more?
Here’s a 3 meter UHS certified HDMI cable for $9.99. I doubt you can find one for much less that handles 4K 120 Hz w/ HDR properly.
My computer names don’t really have a pattern.
Desktop is Neutron, NAS hyperion, old server exscape.
Disks have names from astronomy. Cassiopeia, Andromeda, Pegasus, Orion.
I just recently named my large NAS RAIDZ2 array Laniakea.
It’s mind-boggling to me that this hasn’t been fixed (in Windows, I assume?), people have been complaining for years.
It’s not inherent to DisplayPort though. Some monitors that suffer from this issue can disable “deep sleep” and have the issue gone even with DisplayPort, but not all monitors allow turning it off.
(And others yet, like my old Acer XB271HU, doesn’t have the issue to begin with.)
Yes, that shouldn’t be an issue. I believe SFTP would be supported basically out-of-the-box if you install OpenSSH during the install, but you might want to create a group and configure access if you’re not the only user.
The version thing is what I’m doing with ZFS (also works with BtrFS, but it doesn’t feel as reliable yet). Basically I take snapshots every hour, and the entire state of the filesystem at that point becomes frozen in time, and can be accessed as long as the snapshots exists.
sanoid automates the process and cleans up so that there’s a reasonable amount of snapshots, not hundreds or thousands.
Of course, this means that you can’t really regain any space when you delete things, until the oldest snapshot containing the data is deleted.
It depends on what your goals are of course, but I use ZFS for the file system, sanoid to take snapshots on a schedule (hourly saved for a few days, daily saved for 1-2 weeks and so on up to monthly saved a year or two), Samba to actually share the files to Windows computers, Plex to share media to my TV.
Also rsync to a second (offsite) computer for replication/backups of the most important stuff. That computer also takes ZFS snapshots to get easy versioning of the files.
I wouldn’t recommend it for most people, but it’s nice if you’re comfortable working with Linux to begin with.
Plenty of FOSS ways to set up a NAS. I’m going for Debian with ZFS myself, I prefer custom solutions as they are almost always more flexible than “NAS OS:es”.
You can still block it easily with the command prompt (Shift+F10 during the install) as mentioned. But don’t let that stop you from switching to Linux if you feel like it.