As was explained earlier during the overview of the FSSTND, Linux should        always go through a proper shutdown. Sometimes your system might crash        or a power failure might take the machine down. Either way, at the next        boot, a lengthy filesystem check (the speed of this check is dependent on        the type of filesystem that you actually use. ie. ext3 is faster than ext2        because it is a journalled filesystem) using fsck will be done. Fsck will        go through the system and try to recover any corrupt files that it finds.        The result of this recovery operation will be placed in this directory.        The files recovered are not likely to be complete or make much sense but        there always is a chance that something worthwhile is recovered. Each        partition has its own lost+found directory. If you find files in there,        try to move them back to their original location. If you find something        like a broken symbolic link to 'file', you have to reinstall the file/s        from the corresponding RPM, since your file system got damaged so badly        that the files were mutilated beyond recognition. Below is an example of        a /lost+found directory. As you can see, the vast majority of files        contained here are in actual fact sockets. As for the rest of the other        files they were found to be damaged system files and personal files.       These files were not able to be recovered.
source: http://tldp.org/LDP/Linux-Filesystem-Hierarchy/html/lostfound.html
5 Money Scams on Craigslist Boise
                      -
                    
Craigslist Boise is a great site for finding deals on used items, but it 
can also be a place where scammers attempt to take advantage of people. 
Recently...
2 years ago
 
 
![[FSF Associate Member]](http://static.fsf.org/nosvn/associate/fsf-12534.png)
 
 
 
 

 
 Posts
Posts
 
