Want a design that makes it easy to implement virtual files like /dev/random, /dev/null, /proc/

• Useful to look at how the kernel separates file systems and mirror their separation
• E.g. They might define callbacks for /proc that applies to everything under /proc, and similar for /dev/.

categorize files into two? general categories:

• files that are accessed through the host's filesystem, and
• in-memory files that shadow handles (ex: /proc)

we may want to have different file objects for different kernel filesystems (for example a shadow file type for /proc files, another shadow file type for /sys files, etc)

• we should look at the kernel code to see if these virtual filesystems behave differently or not (for example does seek() behave differently for /proc and /sys files)
• we should probably try to follow how Linux does this as much as possible

in shadow's File enum, we can have RegularFile for the host's filesystem and ShadowFile (naming?) for shadow's in-memory files

have a virtualized "file table" in the host where we can override how certain paths are opened

• would need to be some sort of tree that allows us to move directories containing virtualized files/directories, and keep this in sync
• NOTE: this is probably too complex for us atm, so we should not do this over the short term