You are not logged in.
Pages: 1
Examining my file system, I see that arch use a lot of hard links ("find / -mount -not -type d -links +1" to find file being hard linked). Is it really intentional? Why not use soft links instead? The problems with hard links is that it is not immediatly visible and you normally do not notice that two names refer to the same files. Also making backup of the whole filesystem; we should carefully check that the tools used manage hard links correctly.
Offline
I'm guessing most of these are man pages and that is just the way they are installed. It sometimes makes no sense which to choose as the primary file and which should be the link.
Why would you back up / anyway? If you have a package list, pacman will restore this for you. Just backup config files.
Offline
Why would you back up / anyway? If you have a package list, pacman will restore this for you. Just backup config files.
Yep. config files, ~ and some things in /var/lib maybe. That should be it.
< Daenyth> and he works prolifically
4 8 15 16 23 42
Offline
There are a lot of reason to backup. The hard disk can died, moreover I do some experiment outside of pacman. I remember having restored a backup after having installed realplayer that put tons of files outside the directory where it was supposed to install.
Also when I want to install arch on a new computer; I usually make a copy of all the files present in my current installation instead of installing it normally. Note that it is not a real problem if we know we must pay attention to it: I usually use rsync which as a --hard-links options (but it is not implied by the --archive option so we must be careful to use it).
Simply my reproach to hard links is that it is not sufficiently visible; we understand what is on the file system better with soft links, but that is my opinion.
Offline
Pages: 1