VanLUG Email Archive
Richard Pitt (richard@fireplug.net)
Sun, 10 Jan 1999 04:31:04 -0800
Lost+found is somewhat similar to the "file0000.chk" that Micro$oft leaves
when it finishes a check of a somewhat screwed up file system.
The L+F directory is pre-created at disk initialization time with some
"empty" inodes (directory entries) which the "fsck" command can use to
re-attach files it finds incorrectly represented in the rest of the file
system.
Somehow (reaching back into memory, not bookshelf) your "strict" command
"Perl pragma to restrict unsafe constructs " has become an orphan in its
normal spot on the disk hierarchy, so fsck put it into lost+found so you
wouldn't "really" lose it by simply freeing up the affected inodes completely.
You can move it back to where it belongs - if you can figure out where that
is - my system doesn't have the file, just the man page.
richard
At 03:51 AM 10/01/99 -0800, Ya`akov N. Miles wrote:
>This is the first time I have EVER seen anything in the /lost+found
>directory. Strict is a BINARY file, could someone tell me the
>philosophy behind lost+found, and possibly what "strict" is?
>
>--
>Linux - it isn't just for breakfast anymore... mailto:ynmiles@ibm.net
>Note http://www.cheapbytes.com for (almost) free Linux & freeBSD CD-ROMs
>and http://www.mit.edu/afs/sipb/user/xiphmont/cdparanoia for CD ripper
>also http://www.happyhacker.org/hwgstart.html - Enjoy...
-
Richard C. Pitt President/C.E.O.
FirePlug Computers Inc. WWW.FIREPLUG.NET
Voice: 604-644-9265 E-Mail: richard@fireplug.net
Fax: 604-465-2666 Consulting to ISPs since 1986
Plug and Play Firewalls Internet Facilities and Management
This archive was generated by hypermail 2.0b3 on Sun 10 Jan 1999 - 05:02:18 PST