+config RCFS_FS
+ tristate "Resource Class File System (User API)"
+ depends on CKRM
+ help
+ RCFS is the filesystem API for CKRM. This separate configuration + option is provided only for debugging and will eventually disappear + since rcfs will be automounted whenever CKRM is configured. +
+ Say N if unsure, Y if you've enabled CKRM, M to debug rcfs + initialization.
+
So is this option going to stay around, or should it always be enabled if CKRM is enabled? Why not just do that for the user?
It may be a module, but yes, this should be auto-set in the future when CKRM is enabled.
Then fix it? :)
greg k-h
Sounds like a case is being made to make CONFIG_RCFS a "y" and eliminate
the possibility of it being a loadable module ? If so, I don't think its a good idea. While a kernel may have CKRM enabled, the user may choose not to use it. In such a case, he should have the option of not loading the rcfs module.
How does one restrict the choices of a tristate variable to exclude just the N selection ? It wasn't clear from the kconfig-language.txt...any pointers appreciated.
-- Shailabh
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
