[HN Gopher] The Importance of a Name
___________________________________________________________________
The Importance of a Name
Author : Sandeepg33k
Score : 13 points
Date : 2023-06-01 06:15 UTC (2 days ago)
(HTM) web link (joebordes.com)
(TXT) w3m dump (joebordes.com)
| compressedgas wrote:
| Sounds like lsof could have saved them.
| MongoTheMad wrote:
| or docker ps, where is shows volume mounts.
| arp242 wrote:
| I once deleted about 20 years worth of pictures from company
| outings and such. This was stored in "cms.original2/data/images"
| or some such. There was also "cms.original", "cms.old", and just
| "cms" (and the entire thing was unused and didn't even work in
| the first place).
|
| When I took over as maintainer of the intranet I set up
| subversion and cleaned up all of this "cp -r version control",
| which included checking in the latest version of everything and
| deleting everything else (there were dozens of projects with this
| kind of "version control", including "project.new",
| "project.new2", and it wasn't always obvious which one was the
| live version: could be anything).
|
| Wasn't discovered until a few months later when someone wanted to
| look up some pictures, by which time the backups had been
| overwritten. I got some pretty sour looks for that, but
| seriously, 1) this was a stupid location to store stuff, and 2)
| version control is not rocket science.
|
| Also: once had a customer who stored a lot of important documents
| in C:\Temp. I told him that was probably not a good idea.
| baking wrote:
| Can someone explain why this is a naming problem? I just feel
| like I'm missing something.
| JadeNB wrote:
| I think just in the sense that a directory called `/opt/redash`
| strongly hints by its name that it contains _only_ a Redash
| installation, so that either other crucial infrastructure
| should not have been placed there, or it should have been
| called something that better reflected its contents.
| fred_is_fred wrote:
| I agree. I cannot understand why they mounted the MySQL data
| directories where they did. It just doesn't make much sense. To
| me it's like mounting it onto /boot and then being surprised
| when it goes badly.
| Noumenon72 wrote:
| > Linux was intelligent enough to keep the i-node references even
| if the parent directory was different so the docker container
| kept working inside the deleteme_after_202202 directory.
|
| Who would have been launching a container inside the deleteme
| directory? They were very lucky if that's how they found it. How
| long did it take to discover that?
___________________________________________________________________
(page generated 2023-06-03 23:02 UTC)