Quote:
Originally Posted by Ruskie_it
Yeah, and please note that update.bin.tmp.partial method does not work anymore with 5.6; I had that ***file*** at 5.6.1 and got updated to 5.6.1.0.2 nonetheless
|
hmm...
Do you actually mean
**FILE**?
If so, then that was a user error, it should have been a
directory of that name.
OR
Lab126 has discovered the difference between file unlink and directory delete. . . . .
Its on FAT32 so we can't confuse them with the "immutable" attribute. . . . .
How about making that name an active mount point?
Let us see how long it takes them to discover an in-use (active) mount point with that name and deal with it.