Jason Lunz: > > - tmpfs + loopback ext2 fs-image + mount > > I'm not sure what you mean by this.
Basically it is the same thing to the ramdisk + mke2fs case. And I understand it useless for you. > For what? Is it just to avoid changing a multiply-hardlinked inode more > than once? If so it's just an optimization and noxino isn't a problem, > right? I don't know why they check inode number. All I know is the fact that they report an error when the inode number changed. > You mean when rmdir fails due to the directory being nonempty? If so, > rmdir can change the inode numbers (which you already warned about). But > rmdir doesn't care what the inode numbers *are*, right? Right. > If the xino code had a way to garbage-collect the unused mappings it > would be safe to use with tmpfs. I'll try, but I am not sure it will succeed. Junjiro Okajima ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
