We check if a given device should be included in the post-install
kickstart by comparing their
parent class to a map of supported parent classes. Turns out the ancestry of the tmpfs
device
is a bit different so it was not being included. Adding tmpfs to the map of supported
classes
fixed it.
Also another small change was needed - providing format to ksdata - so that the
resulting
kickstart line dost not include the (in this context incorrect) --noformat option.
With these changes, tmpfs mounts created during installation are now correctly
included in the post-installation kickstart file.
Looks fine to me.
- Chris