>Joseph Kowalski wrote: >> Garrett D'Amore wrote: >> >> 4.3.4 Unison does not understand hard links. >> > That's pretty unfortunate. I guess the necessary consequence of this >> > is that Unison my dramatically increase the bandwidth needs and >> > storage needs on the remote side. Imagine synchronizing a 4G ISO >> > image, which also has hardlinks to other names -- instead of >> > transferring and storing one 4G image, you are transferring and >> > storing n * 4G. >> >> Yea, but who actually does this? > >At least I do it - and many applications and users will do it, too. And >a look at usr/src/pkgdefs/ shows many many hardlinks being used in the >package system, too.
And I do it for /ws/tools which has a lot of duplication between versions (it saves about 80% of diskspace to hardlink identical files) >> The common use of hardlinks went away >> with AT&T supporting UNIX. > >Huh ? Could you please give further details on the relationship between >AT&T and hardlinks ? Symlinks didn't exist until SVR4 got them from BSD so I'm not sure what the point is (symlinks take a lot more diskspace) Casper
