<div dir="ltr">That would be nice for resolving the Kerberos thing as well (providing
users the option to use ssh keys). And I won't claim to love using FS
ACLs over POSIX permission bits, either (not that they're
non-functional--although file-level permissions are often nice--so much
as I like being able to stick with what I know). <br>
<br>Any idea what the timeline on this would be? Because of the above
issues, I've been planning to abandon hcoop as soon as I get around to
finding someplace new. But if this is really going to happen, I'd
probably stick it out and see how that goes. <br>
<br>Dan<br><br><div class="gmail_quote">On Tue, Sep 9, 2008 at 1:10 PM, Adam Chlipala <span dir="ltr"><<a href="mailto:adamc@hcoop.net">adamc@hcoop.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Daniel Margolis wrote:<br>
> Of course. But making people rearrange their home directories to<br>
> maintain any privacy is kind of silly.<br>
><br>
> It's not the end of the world, but saying "AFS provides users with the<br>
> most choice" is wrong. My choice would be to have my home directory be<br>
> private (ideally, from authenticed users as well).<br>
<br>
</div>The long-term plan that I've been advocating is to run a traditional<br>
UNIX machine, giving members the option to get accounts there. For now,<br>
AFS is so critical to enabling scaling to multiple machines that it will<br>
be the only option for a while.<br>
<div><div></div><div class="Wj3C7c"><br>
_______________________________________________<br>
HCoop-Discuss mailing list<br>
<a href="mailto:HCoop-Discuss@lists.hcoop.net">HCoop-Discuss@lists.hcoop.net</a><br>
<a href="https://lists.hcoop.net/listinfo/hcoop-discuss" target="_blank">https://lists.hcoop.net/listinfo/hcoop-discuss</a><br>
</div></div></blockquote></div><br></div>