It's filesystem corruption. I've had that happen to many files before. If its bad enough then fsck can't fix it and you'll have to re-format. The wierd file permissions, uid, gid, and major/minors are a result of random numbers being written into the bytes for the files's i-node. Try fsck, but my guess is you'll have to re-format because you cant even delete files messed up like this. They could also spread like a virus to the rest of the partition (figuratively, not like an actual virus) further corrupting other fs entries. Jason On Tue, 5 Dec 2000 andy at theasis.com wrote: > > I have a "file" /usr/include/linux which is misbehaving: > > $ ls -l /usr/include/linux > c--sr-sr-t 1 26736 25601 46, 111 May 11 1999 /usr/include/linux > > I can't remove it or change permissions, either using sudo or a direct > login as root. Get "permission denied" and "can't unlink". > > It's *supposed* to be either a directory, or a symlink to one. This isn't > either a directory or a symlink. > > Any ideas about how I can axe the thing, given that root can't seem to > chmod or delet it? > > This is a redhat 7.0 system, upgraded from 6.2 via the 7.0 beta (6.9). I > suspect that the file was put there as part of the kernel-headers-2.4.?? > by that beta install. > > Thanks, > > Andy > > _______________________________________________ > tclug-list mailing list > tclug-list at lists.real-time.com > https://mailman.real-time.com/mailman/listinfo/tclug-list >