3 ms·
Yeah I'd call the behavior unexpected rather than wrong. As a design decision it makes a lot of sense, especially given the ideas that went into UNIX filesyste
by marginalia_nu 3y ago
Yeah I'd call the behavior unexpected rather than wrong.
As a design decision it makes a lot of sense, especially given the ideas that went into UNIX filesystems that didn't quite pan out (hard links are a very neat idea in theory, but I'm not sure when I'd ever actually use them).
- somat 3y agoHard links are tags. A file is just a big lump of data with an address(the inode) A name is then linked to the data(If you wanted you could call it a tag, it is almost exactly the same thing). If the data needs more metadata go ahead and link additional names to it. Note that no name is the "real name" with hard links they are all equal. I built a whole music database once where all the metadata and playlists were hardlinks... The main problem encountered was you had to be very careful archiving the structure, it tended to explode into a million duplicate files(this is probably why people don't use hardlinks)