Why Was: US Military Dead during Iraq War 1828
Ok. That leaves redundancy.
Heh. That's why those bit gods earned their money.
But how do you edit the disk if it is the inode that gets corrupt? Every thing depends on one count (which means one bit) staying uncorrupted. I don't see how anybody can edit that count and recover the disk enough such that the real data can be retrieved.
But only if the inode remains intact. ISTM the weak point in this design is the inode inuse count.
Why Was: US Military Dead during Iraq War 1829
uses. I used it all the time by invoking the File Daemon. Nobody logged in under 1,2 could write; I allowed them to read. No. There was no...
sure. emoticon handwaves This is the operation of the file system and is a variable that gets snapshot every so often to freeze the state of the file system. Even here ISTM that it would be difficult for any user to know when to restart to recover from the last system fault. See my response to Lynn about the user needing a datetime stamp for computing recovery.
Of course. Who recovers when it's the inode itself that is messed up? Is an inode redundant.
Yea, I think that's a normal maturity pattern. I wonder if anybody has done a study about what any OS has to go through from conception thru its teenage years into adulthood?
Subtract a hundred and four for e-mail.