False. A filesystem is simply one way to organize and secure data held on disk. Many applications have their own built-in way of retrieving data from raw volumes . A filesystem is a convenient mechanism to organize data on disk, but not the only way.
A2:
False. Users do not use (or care, or know) what an inode is. There are no user -level utilities that utilize inode numbers as a means of referencing files (administration commands like clri . fsdb , etc., are not user-level commands).
A3:
False. A hard link must point to a valid inode number within the same filesystem. A soft/symbolic link can link to a non-existent file.
A4:
False. All alternate superblocks are equivalent; they contain the static information relating to the filesystem, which was calculated at the time the filesystem was created. From this, the dynamic information can subsequently be calculated with the invocation of subsequent fsck commands.
A5:
False. The C2 (Orange Book) security classification specifies only that individuals can be identified and given their own permissions. This is what HFS/VxFS ACLs offer; an administrator can assign permissions to individual users or individual groups. The permissions that the administrator can apply are still only read, write. and execute.
