Figure 18-4 shows the procedure for creating a HiRDB file system area for system files.
Figure 18-4 Procedure for creating a HiRDB file system area for system files
Initialize the hard disk.
Initialize the hard disk; for the procedure, see the OS manual.
Set partitions on the initialized hard disk.
Set partitions on the initialized hard disk; for the procedure, see the OS manual.
If regular files had been used in the HiRDB file system area, initialize the partitions as a UNIX file system; for the procedure, see the OS manual.
If the partitions are already initialized, skip this step.
Change the owner and access privileges of the HiRDB file system area, so it will be protected from unauthorized accesses. Table 18-20 shows the owner and access privileges to be set for the HiRDB file system area.
Table 18-20 Owner and access privileges to be set for HiRDB file system area (HiRDB file system area for system files)
Owner, access privileges | Information to be set | Command to be executed* | |
---|---|---|---|
Owner | User ID | HiRDB administrator | chown command |
Group ID | HiRDB group | chgrp command | |
Access privilege | Owner | rw- (read and write operations permitted) | chmod command |
Group | rw- (read and write operations permitted) | ||
Other | --- (access denied) |
* These are OS commands; for details, see the OS manual.
For a HiRDB file system area, a name linked symbolically to its entity by the ln OS command should be used instead of using the name of its character special file or regular file entity as is. When a symbolically linked name is used, the HiRDB file system area can be restored easily onto another hard disk in the event of a hard disk failure.
For details on the ln command, see the OS manual.
Use the pdfmkfs command to initialize the HiRDB file system area for system files:
pdfmkfs -n 40 -l 5 -k SYS /sysfile_c |