=== Napsterbater is now known as Guest4716
=== Napsterbater_ is now known as Napsterbater
=== Napsterbater_ is now known as Napsterbater
=== Napsterbater is now known as Guest27573
=== Napsterbater_ is now known as Napsterbater
=== Napsterbater_ is now known as Napsterbater
=== Rotnevlat is now known as Tornevall
[12:10] <foo> Running jdupes on data (currently in os x, but my question is a bit more generic). This is the specific jdupes command: jdupes -r -L ~/Desktop/Folders/ | tee ~/Desktop/Folders/jdupes.txt -> jdupes is finding dupes, and linking multiple copies to the original first source that is found that matches. The issue I just realized is if I have 5 text files that are the same, and they all get relinked to the
[12:10] <foo> same source now, but if I change one of those text files... that change is reflecfted across all previously found "copies" since they're hard linked to the same source. I can possibly seeing this being an issue with code backups I have or code, or maybe git data, or database data. Can anyone here speak to this concern? Is it valid?
[12:12] <lotuspsychje> foo: a dupes question on OsX in #ubuntu-server?
[12:13] <foo> lotuspsychje: sigh. I run this same command on my ubuntu servers, if that helps. It's not an OS X specific concept...
[12:14] <foo> I'm trying to understand the implications of this, I didn't realize this nuance
[12:14] <foo> I generally rune jdupes with intent to free up space
[12:18]  * foo reads https://github.com/jbruchon/jdupes
=== Napsterbater is now known as Guest24912
=== Napsterbater_ is now known as Napsterbater