On Thu, 2 Mar 2000 kmself@ix.netcom.com wrote: > On Thu, Mar 02, 2000 at 10:19:40AM -0500, Allan M. Wind wrote: > > On 2000-03-01 23:42:37, kmself@ix.netcom.com wrote: > > > On Wed, Mar 01, 2000 at 07:05:04PM -0500, Allan M. Wind wrote: > > > > On 2000-03-01 23:42:21, Mary Honeycutt wrote: > > > > > tar cf - source | ( cd /target; tar xpf - ) > > > > Yes, that would be more like it. > > Thought so. I'd hate for someone to find out the hard way.... > > > > There's a utility to recreate the lost+found directory if you do manage > > > to overwrite it -- it needs to sit on a specific inode for the filesystem > > > to be able to recover lost clusters properly. RTFM, it's there somewhere. > > > > Isn't lost+found created by mkfs? > > Yes, it is (or mke2fs, or whatever). My understanding of this is > somewhat limited, but here goes. > > Files and directories are identified under most Linux-like fileystems > (e2fs, minix fs, UFS, etc., but *not* msdos, vfat), by inodes. An inode > is essentially a database entry in a table giving storage location, > name, and values of several attributes (read/write/execute/suid), etc. ^^^^^^
name? Files are nameless in UNIX. Read about hard links for example And from inode you should get storage, attirbutes, times (creation, access) and reference counter. regards OK
