>> Can you be more specific about what you are doing? rumprun/rumpconfig >> already automatically mounts specified file systems.
I might be misguided or off track here so please feel free to set me straight. I’ll describe what I’m trying to achieve and would value feedback. I don’t know exactly how rump works, so it might actually do some or all of this now. The core idea I’m working to is that it should be possible to take a kernel and run it on a cloud provider (EC2 in the first case as it is the primary player in the field at the moment). kernels are naturally one of three types: type 1: kernel has no need for a file system. No block device required. type 2: kernel has need of a small number of read only files, total size < total RAM. No block device required. type 3: kernel has need of access to an abitrary set of files. Block device required. In some cases read only, in some cases read/write access is required. From a deployment perspective the most easy to deploy is kernel types 1 and 2 because no block device needs to be configured, attached and managed. For kernel type 3, things become more complex because we need to attach one or more block devices/file systems which need to be pre-formatted. Ideally somehow if a kernel is started up with 1 or more block devices attached, the kernel would detect the block device, detect the file system format and mount the file systems without needing to receive commands instructing it to do so. So my goal is to successfully launch all three types of kernel requirements on EC2. Does this make sense or am I off track? as
