On Fri, Nov 14, 2008 at 8:50 PM, rhubbell <rhubbell at ihubbell.com> wrote: > Well the problem is a little more complicated now. > > The kernel has FUSE code in it now and that code is not the > same code that's in the latest FUSE. > > If similar transitions in the past can be used as a guide, the linux > kernel takes precedence as the defacto repository. > > I think glusterfs should decide how it wants to handle this. > If you look at recent history glusterfs would future-proof > itself by selecting the FUSE kernel source as the target to be > compatible with. Since the separate FUSE will likely become deprecated. > Exactly! I'd imagine sticking with the kernel FUSE would also provide better stability. But it'd also mean there must be a known stable kernel, and any subsequent FUSE patches made by the GlusterFS community. But it'd also create (slight) complications for VServer users, like me. :) KwangErn -------------- next part -------------- An HTML attachment was scrubbed... URL: http://zresearch.com/pipermail/gluster-users/attachments/20081114/178de896/attachment.htm
