49
Package up and transport a linux?
(sh.itjust.works)
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 19 Nov 2023
49 points (96.2% liked)
Linux
48740 readers
1222 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
/home yes., but ideally only files and dirs starting with a dot (so called "dotfiles" under your home dir.
tar cvfa homedots.tar.gz /home/username/.??*should take care of it.Please note it will include some large stuff that's probably not needed, like .cache, or some individual caches for other apps that don't use .cache, like the browsers.
Don't copy /etc, it's usually machine-specific.
Hostname no (if you don't bring etc). Username technically yes, you may want to rename the home dir. The user id and group id are important too but usually off it's the first user on the same distro it will receive the same ids (typically 1000 nowadays). If not, you can change that manually and recursively
chown 1000:1000 -r /home/username.I'd love to upvote you multiple times, you cleared it up for me. Thank you.
You're welcome.
To clarify, /etc can have things that are relevant for the machine so you may want to back it up, but it's not usually transferrable directly to another machine because it probably doesn't play the exact same role. It has things like service configs, network configs etc.
Even if you're trying to migrate a machine to new hardware and the machine will play the same role it's best to pick and choose files from /etc/ on a case by case basis. What I do is grab a tarball of /etc and set it aside, then if I need to redo something the same way it was on the old machine I can dig through the tarball and only use the relevant files.
Like I said it's extremely specific. For example if I want to reconfigure the SSH daemon that's usually a couple of lines which I know by heart (turn root login and password logins off) which I can do by hand; if I want to reconfigure CUPS printing it's best to use the CUPS admin interface to autodetect the printer, you don't usually want to mess with its config files; for some things like /etc/fstab or NFS or RAID I may want to copy some stuff but edit the disk UUIDs; for some things like Samba I could in theory copy the config straight over. It varies.
The list of installed packages may also be relevant when you migrate to a new machine. Different distros have different commands for obtaining a list of installed packages, and different ways of using that on the new machine to restore the same package selection. This is useful and typically can get you started much faster on the new machine.