Review remaining fileops vectors for UUID support

[rwatson]

The dtrace_uuid branch introduced UUID support for vnodes, pipes, and sockets -- but left other fileops types unmodified. They will also require UUID support -- especially devices (covered in issue #23), but also kevent, PTYs, etc. This issue is to review the remaining types for situations where improvements are needed.

[rwatson]

Defined fileops vectors in the kernel tree appear to be (roughly):

opencrypto/cryptodev.c, line 304
kern/sys_pipe.c, line 158
kern/uipc_shm.c, line 129
kern/uipc_mqueue.c, line 221,2583
kern/tty_pts.c, line 599
kern/kern_event.c, line 122
kern/vfs_vnops.c, line 104
kern/uipc_sem.c, line 137
kern/kern_descrip.c, line 3974
kern/sys_socket.c, line 101
kern/sys_procdesc.c, line 97
compat/linuxkpi/common/src/linux_compat.c, line 743
compat/linux/linux_event.c, line 133
fs/devfs/devfs_vnops.c, line 69,1840
dev/streams/streams.c, line 90

This suggests that UUID support is required in the following:

• Cryptographic offload devices
• Pipes
• POSIX shared memory
• POSIX message queues
• Pseudoterminals
• KQueues
• Vnodes
• POSIX semaphores
• Sockets
• Process descriptors
• Linux device nodes
• Linux event FDs
• Device nodes
• System V streams

Of these, sorting out device nodes, process descriptors, and pseudo terminals seem most urgent for the first adversarial engagement.