contains this command needs closer examination to

 

 

determine if the other logic is DRD-safe.

efi_ls

Yes

The efi_ls command itself is DRD-safe, however this

 

 

command is often used in conjunction with other logic

 

 

that is not DRD-safe. As such, any control script that

 

 

contains this command needs closer examination to

 

 

determine if the other logic is DRD-safe.

grep

Yes

--

ioscan

Varies

The ioscan –Mcommand is not DRD-safe.

 

 

Further, any use of ioscan to determine kernel

 

 

information is not DRD-safe. For example,

 

 

looking at the “CLAIMED” field or the name of

 

 

the driver that claims the device provides

 

 

information about the running kernel, NOT the

 

 

kernel that will be built on the inactive system

 

 

image.

 

 

Similarly, any use of the control_util

 

 

cu_hw_scan to determine kernel information is

 

 

not DRD-safe.

kill

Yes*

The kill command should only be used to modify

 

 

processes started within the runcmd environment. Using

 

 

kill on processes started outside of the runcmd

 

 

environment is not DRD-safe.

lifcp

Yes*

The lifcp command itself is DRD-safe, however this

 

 

command is often used in conjunction with other logic

 

 

that is not DRD-safe. As such, any control script that

 

 

contains this command needs closer examination to

 

 

determine if the other logic is DRD-safe.

lifls

Yes*

The lifls command itself is DRD-safe, however this

 

 

command is often used in conjunction with other logic

 

 

that is not DRD-safe. As such, any control script that

 

 

contains this command needs closer examination to

 

 

determine if the other logic is DRD-safe.

ln

Yes

--

ls

Yes

--

lvlnboot

Yes

--

mkboot

Yes*

The mkboot command itself is DRD-safe, however this

 

 

command is often used in conjunction with other logic

 

 

that is not DRD-safe. As such, any control script that

 

 

contains this command needs closer examination to

 

 

determine if the other logic is DRD-safe. A large concern

 

 

with the use of mkboot is the logic to determine the

 

 

device to be modified. In a runcmd environment, the

 

 

mkboot command should be operating on the boot disk

 

 

of the inactive system image and not the device from

 

 

which the system is currently booted.

mkdir

Yes

--

mknod

Yes

--

mount

Yes

Although mount is DRD-safe, it should not be used in SD

 

 

control scripts.

mv

Yes

--

nettlconf

Yes

--

ps

Yes*

The ps command itself is DRD-safe; however, the use of