ldconfig breaks inode???
Posted on 1997-08-29
I've found that on my Slackware system with 2.0.30 kernel, every time ldconfig is run (originally it was in rc.S) it 'breaks' and inode, causing a fsck to give the following message when check is forced:
Deleted inode n has zero dtime
The inode number(n) seems to be the inode number of ld.so.cache. I am wondering how to stop it from doing this.
My system in a P100MHz with 32MB RAM, 32MB swap, 1GB (windoze) and 3.1GB(linux and extra windoze) drives.