On 8/23/2025 7:14 AM, Go Canes wrote:
On Fri, Aug 22, 2025 at 11:52 PM home user via users
<users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
On 8/22/2025 7:50 PM, Go Canes wrote:
[...]
My hope is that I can get a reader/writer that fits into a "bay" of the
desktop's case, just as on my old desktop the hard drive is mounted in a
case bays and connects to the motherboard via a cable (not via USB).
Connecting through USB, the USB will limit read/write speeds. I fear
you might be right about cost.
For an "in-tower" solution you are probably looking at either SATA or
SCSI. A current motherboard will typically have 4 SATA ports, so
unless you have a lot of disks, optical drives, etc., you will
probably have an available SATA port. If the solution is SCSI, you
will probably need an add-in SCSI card. Your power supply will also
need to be sufficient for providing power to the additions.
That's part of the reason for this advance planning, including this
thread, so I get something with enough power, bays, cooling, and so on.
"immutable": do you mean "chmod 111 [file]" and "chmod 555 [file]", or
do you mean something else?
I think it is "chattr +i file" - see "man chattr". It also might be
file-system specific?
I did not know about that command. Thank-you.
What are your requirements? Recovering deleted files? Protecting
against disk failure? Saving your data if your dwelling is destroyed
(fire/flood/earthquake/tornado/etc)?
* looking at old files; recovering older versions of files; recovering
deleted files
(I've very rarely needed these capabilities.)
* protecting personal data (not the OS and installed software) against
disk or desktop failure.
I don't currently have protection against fire and so on, but I
recognize I should.
My current focus is on the first 2.
If you have protection against fire and so on, you are protected
against deletion (for files that are actually backed-up) and disk
failure.
If you are protected against disk failure, you are protected against
deletion (for files that are actually backed-up).
There are trade-offs involved. Protecting against deletion is
relatively simple, fast, and inexpensive, but also may require more
discipline on your part (making sure you run a "backup" after creating
a file and before potentially deleting it). As an example, if you
want to protect source code for programs you write, you can use "git"
or pretty much any "revision control system".
You've been focused on speed, but speed = $$, and you also said "I've
very rarely needed these capabilities". You should consider how much
speed you actually *need*. As someone else mentioned backups are
typically scheduled to run overnight, or some other time when the
system is idle, and it doesn't really matter if the backup takes 5
minutes or an hour. This also assumes you leave the system
up-and-running overnight; if you need to conserve power the cost of
"speed" may be valuable.
I'm now thinking 3 kinds of back-up:
* incremental personal data back-ups, keep the 3 most recent, in-house.
already doing this, but needs improvement.
* larger semi-annual back-ups, all personal data, keep the 3 most
recent, in-house. already doing this, but needs improvement.
* off-site back-up (internet/cloud), important to critical personal
data. not yet doing this.
Yeah, there are cost/time/convenience/privacy/security/and-so-on trade-offs.
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
