Application of Solaris 8 patch 112438-01 without reboot

[Andrew J Caines]

Now that Sun has finally seen the light and given us /dev/[u]random for
Solaris 8 in the form of patch 112438-01, I note that the patch
instructions take the MSish easy way out and require a reboot, as if the
average admin doesn't load and unload kernel modules, make nodes, etc. on
a daily basis.

For the record, what is the correct process for enabling the new random
device on a running Solaris 8 box?

In what way is the following incorrect and/or insufficient?

# patchadd 112438-01
# mknod /devices/pseudo/random at 0:random c 82 0
# mknod /devices/pseudo/random at 0:urandom c 82 1
# chgrp sys /devices/pseudo/random*
# cd /dev
# ln -s ../devices/pseudo/random at 0:random /dev/random 
# ln -s ../devices/pseudo/random at 0:urandom /dev/urandom
# modload /kernel/drv/random

Major 82 comes from /etc/name_to_major, owner and perms from
/etc/minor_perm. Minors are presumed, as are pathnames under /devices. Are
they correct?

FWIW, "dd if=/dev/urandom of=file count=1" results in a file filled with
some randomlike data.

For the record, should the prescribed reboot be a reconfig, or will the
new device be created automagically? The modload alone did not create
them. I haven't had a chance to verify yet.


-Andrew-
-- 
 ________________________________________________________________
|  -Andrew J. Caines-   703-886-2689    Andrew.J.Caines at wcom.com |
| Unix Systems Engineer, WorldCom  Andrew.J.Caines+page at wcom.com |