What seems odd is that you 'rm' it, yet it's still there. There is nothing odd about a zero byte file - that's what you'd get from `touch filename`. The most parsimonious (not particularly parsimonious, but the most I can fathom) is that some process is continually recreating (and perhaps also removing) the file. Your very last point - that it's date and time keep progressing - is what I was noting through all the output. Most of these examples, I retried a few times to get them to work. home/ is a separate partition anyways, but it would be nice to have it out of the way until then.
If I need to copy everything except that file to a new partition (on the SSD when I switch), I can do that. I just want to get rid of it (and maybe figure out where it came from). It looks like a few people have had some weirdness with 0 byte files, but not anything like this. The reason I haven't posted anything yet is that I'm usually pretty good at searching stuff, but I can't find anything on this. I have no idea why it is named blinkingy. I was messing around with that when I was bored one day a few months ago. It might be a link to itself, but it doesn't show up as a link. This file has been here for a while, but since I'm switching to an SSD, I'm taking the opportunity to go through and clean up my system first.Īs to where it came from, probably me. It only shows up about 50% of the time (to anything, including bash tab completion). I hope this is the right place to put this.Īnyways, I have this weird file in my home directory.
#Linux delete zero byte files install#
I've been using Arch since some point last year (I've since installed it on 3 other computers, and then did a LFS install because I was bored), and am very comfortable with it (not really a newbie), but this is my first time posting on the forum. Before I get to the question, I want to say a few things.
0 kommentar(er)
