R
- RAID (Redundant Array of Independent Disks)
A disk subsystem that is used to increase performance and/or provide fault tolerance. RAID is a classification of different ways to back up and store data on multiple disk drives. There are seven levels of RAID:
Level 0: Nonredundant disk array (striping) Level 1: Mirrored disk array Level 2: Memory-style Error Code Correction (ECC) Level 3: Bit-interleaved parity Level 4: Block-interleaved parity Level 5: Block-interleaved distributed parity Level 6: P + Q redundancy
SVM implements RAID levels 0, 1, and 5.
- RARP (Reverse ARP)
A method by which a client is assigned an IP address based on a lookup of its Ethernet address.
- Reconfiguration boot
A method of booting a system so that the system recognizes newly added peripheral devices and creates an entry in the /etc/path_to_inst file, and the /dev and /devices directories.
- Reconfiguration startup
See Reconfiguration boot.
- Redundancy
Duplication for the purpose of achieving fault tolerance. This refers to duplication or addition of components, data, and functions within the array.
- Replica
One or more additional copies of the state database.
- Restricted shell
Restricted versions of the Korn shell (rksh) and the Bourne shell (rsh) to limit the operations allowed for a particular user account. Restricted shells are especially useful for ensuring that time-sharing users, or users' guests on a system, have restricted permissions during login sessions.
- Rights profile
Also referred to as right or profile. A collection of overrides used in RBAC that can be assigned to a role or user. A rights profile can consist of authorizations, commands with set UIDs or GIDs, which are referred to as security attributes, and other rights profiles.
- Router
A machine that forwards Ethernet packets from one network to another.
- RPC (Remote Procedure Call)
A protocol that one program can use to request services from another system on the network.
- Rules file
A text file that contains a rule for each group of systems (or single system) that you want to install automatically using JumpStart. Each rule distinguishes a group of systems, based on one or more system attributes. The rules file links each group to a profile, which is a text file that defines how the Solaris 9 software is to be installed on each system in the group. See also profile.
- rules.ok file
A system generated version of the rules file. The rules.ok file is required by the custom JumpStart installation software to match a system to a profile. You must use the check script to create the rules.ok file.
- Run control script
Each init state has a corresponding series of run control scripts, referred to as rc scripts and located in the /sbin directory, to control each init state.
- Run state
When a system begins initialization, it enters one of eight run statesalso called init states. Because run state 4 is currently not used, only seven usable run states exist. A run state is also referred to as a run level.
|
