This section describes the prerequisite procedures that must be completed before a HiRDB file system area can be created.
The superuser must initialize the hard disk (if the hard disk has already been initialized, this step may be skipped). For details about how to initialize the hard disk, see the applicable OS documentation.
The superuser must set partitions on the initialized hard disk (if partitions have already been set, this step may be skipped). For details about how to set partitions, see the applicable OS documentation.
If the HiRDB file system areas are to be used as regular file areas, the superuser must initialize the set partitions as a UNIX file system (if this initialization has already been completed, this step may be skipped). For details about how to initialize a UNIX file system, see the applicable OS documentation.
Perform the following if there is a file system area provided by the OS:
For the name of the HiRDB file system area, the superuser should use a name that is symbolically linked (with the ln OS command) to the entity name of the character special file or regular file instead of using the entity name itself. This simplifies the following operations:
For details about the ln command, see the applicable OS documentation.
The superuser must change the owner and access privileges of the HiRDB file system so that it can be protected from access by unauthorized users.
Table 2-6 lists the owners and access privileges to be specified for the HiRDB file system area.
Table 2-6 Owners and access privileges to be specified for HiRDB file system area
Owner, access privilege | Information to be specified | Command to be executed* | |
---|---|---|---|
Owner | User ID | HiRDB administrator | Chown command |
Group ID | HiRDB group | Chgrp command | |
Access privilege | Owner | rw- (both read and write permitted) | Chmod command |
Group | rw- (both read and write permitted) | ![]() | |
Other | ![]() | ![]() |