After discussion with Colin Watson and others on #ubuntu-devel the decision was made that spufs could be handled as a special case in domount(). My proposed patch is attached.
NOTE this must be applied in conjunction with the patch on LP: #274858 [0] It isn't a good idea to let any or all calls to domount run through to the mount command without validation as it returns the same error code (32) for almost any type of mount failure so we couldn't provide a neat and specific boot log message. Also domount is only used to mount special filesystems like procfs/tmpfs/sysfs etc which will be built into the kernel. spufs is the only filesystem type compiled as a kernel module which domount is likely to be called for. Therefore no need to generalise domount to handle any filesystem type specified as a possible kernel module. [0] https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/274858 ** Attachment added: "domount_try_to_modprobe_spufs_if_not_loaded.diff" http://launchpadlibrarian.net/18194435/domount_try_to_modprobe_spufs_if_not_loaded.diff ** Changed in: sysvinit (Ubuntu) Status: In Progress => Fix Committed ** Changed in: ubuntu-ps3-port Status: In Progress => Fix Committed -- spufs filesystem not mounted on boot https://bugs.launchpad.net/bugs/274854 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
