45
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 02 Oct 2023
45 points (97.9% liked)
Linux
47953 readers
1182 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
Why not encrypting the new SSD and rsync'ing the content from one drive to the other? Would be easier and safer.
I wasn't aware that
rsync
also copied system files. I'm curious to know why my method is unsafe. The only potential problem I see with what I did is mixing upif
andof
indd
.Your method is safer imo as long as you get the dd command right. Because afterwards you'll have two bootable copies of your system. If you mess up resizing the filesystem on the new drive, just dd again from the old one.
Glad you figured it out.
rsync also gives you two bootable copies of your system. Even better, it gives you a checksum based copy of your files including permissions.
Safe/unsafe might be the wrong word, but rsync is resumable and also copies permissions for example. dd is more like the brute force method of data transfer.
Pause and resume are nice but
dd
also gives you the permissions. It copies everything, byte for byte, hence why it's a "low-level copy"