Access Domain model change

During the test phase it has been decided to ammend the fs access domain model and to add, in addtion to the default r-w access domain group 0, default r-o access domain group 1.

LinSec setuid code clears all access domain settings of the setuiding process as no privilege inheritance should take place on the change of ownership. On the other hand, to ease the configuration process, it is usually practice to create one access domain group with the neccessary library locations that most of the programs need to access and make a shell program a member of the group (thus all other programs executed by the shell have access to the library code). However, many Linux tools use setuid syscall for unexplicable purposes and if the tools are meant to further execute other programs those programs loose access permissions for the libraries. The creation of default r-o fs access domain group 1 solves the problem by forcing all its elements into r-o access domain of all processes on the system - analogue to the operation of the default r-w fs access domain group 0.