Of course I haven't. The massive majority of desktop installs will never need it.
What I've tried to do is challenge the argument for excluding it. It isn't loaded by default. It is simply a small file that sits idle in the /lib/modules folder. And for the <.01% of users who want to try it out without installing a server kernel (me, at least), it makes their lives much easier. I have no need for anything else in the server kernel. No need for weird processor types, memory systems. All I really want to do is try OCFS2 locally on a desktop to get a feel for it. I believe there is a pretty clear separation between these types of things. There are things which can cause negative effects for one machine type: processor types, memory stuff, preempt, etc. And there are things which can't: file system kernel modules. If I'm wrong about the last point, at least in the OCFS2 case, please correct me. I suppose my one concern would be if the introduction of OCFS2 introduces some new exploit vector for desktop systems, such as maybe being auto-loaded in some fashion. -- Include OCFS2/CLUSTER/GFS in non-server kernels https://launchpad.net/bugs/71997 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
