Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU |
Ben Holland writes: > Just as a quick question and i'm not trying to be a dick about it, but if > you have a major file system corruption, why would the ability to know what > files are there be important. I really do ask this question in earnest, and > more to the point even, if the file system is hosed, and you can still > though the luck of the gods read the inode table how would the actual files > themselves not be corrupted. I mean, i'm kinda assuming that you picked this > info up because you had to, i'm just wondering about the circumstances. This seems the be the cannonical story that everybody alludes to: http://lug.wsu.edu/node/414 In my own career, I've had to use the "echo *" trick a couple of times. It is one of those tricks you hope you never have to use. Regards, --kevin -- GnuPG ID: B280F24E Meet me by the knuckles alumni.unh.edu!kdc of the skinny-bone tree. http://kdc-blog.blogspot.com/ -- Tom Waits -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. _______________________________________________ Discuss mailing list [hidden email] http://lists.blu.org/mailman/listinfo/discuss
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |