On Fri, Nov 14, 2008 at 8:50 PM, rhubbell <span dir="ltr"><<a href="mailto:rhubbell@ihubbell.com">rhubbell@ihubbell.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Well the problem is a little more complicated now.<br>
<br>
The kernel has FUSE code in it now and that code is not the<br>
same code that's in the latest FUSE.<br>
<br>
If similar transitions in the past can be used as a guide, the linux<br>
kernel takes precedence as the defacto repository.<br>
<br>
I think glusterfs should decide how it wants to handle this.<br>
If you look at recent history glusterfs would future-proof<br>
itself by selecting the FUSE kernel source as the target to be<br>
compatible with. Since the separate FUSE will likely become deprecated.<br>
</blockquote></div><br>Exactly!<br><br>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.<br>
<br>But it'd also create (slight) complications for VServer users, like me. :)<br><br><br>KwangErn<br>