Re:Devops Horror Stories
by InclinedPlane on Friday November 01, 2013 @04:18AM
(#6652451)
Long ago I was trying to solve some thorny problem that I now forget and I thought it might be a good idea to uninstall and reinstall glibc. I knew it was a bad idea but I was at the point where I was past caring and figured why not see what happens. Turns out, in order to uninstall glibc there's a confirmation prompt, and instead of just 'y' or 'n' you have to type a whole sentence that's something like "yes, I understand this is a really bad idea". Well, I did that, and it was a really bad idea, the system was, unsurprisingly, basically unusable after that.
Would have used /media but was thinking, if, say I forgot to unmount it or someone looked at a disk free or whatever, that it would be obvious that it was there temporarily.
Obviously that was incorrect, but the reasoning was, I think, sound.
I like /mnt/scratch/ for that. If I was using systems with lots of others, I'd make it clearer with /mnt/tmp/.
You can't delete /proc, it is a pseudo filesystem the kernel creates. They aren't really files. Deleting /dev is a real pita however
Re:Devops Horror Stories
by vincentkriek on Friday November 01, 2013 @06:47AM
(#6652892)
With udev deleting /dev shouldn't be a problem I thought?
Why no, I've NEVER accidentally deleted whole file systems, I have completely earned superiority here.
Delete /proc and /dev on a running server. Thankfully not really disastrous but damn if people don't notice right away.
Thanks for the tmpwatch info btw.