[OpenAFS] Windows AFS Client implemented as a Kernel mode or
User mode driver?
Tue, 29 Nov 2011 18:13:23 -0500
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
Content-Type: text/html; charset=UTF-8
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<meta content=3D"text/html; charset=3DUTF-8" http-equiv=3D"Content-Ty=
<body bgcolor=3D"#ffffff" text=3D"#000000">
My point is that regardless of whether it is implemented entirely in
userland or kernel you can't virtualize a file system.=C2=A0=C2=A0=C2=
=A0 Prior to
1.7, OpenAFS was implemented as a userland only service and a
network provider module that is loaded into all applications that
piggybacked upon loopback network adapter driver and the Microsoft
SMB redirector file system driver.=C2=A0 In 1.7 OpenAFS replaces the
loopback adapter driver and the SMB redirector file system driver
with its own redirector file system driver.=C2=A0=C2=A0 You can't vir=
parts of a file system and not do the entire thing.<br>
What would be an interesting direction would be executing ThinApp
packages out of AFS on student desktop images so you don't have to
deploy the packages everywhere.<br>
On 11/29/2011 5:58 PM, Valentine, Nick wrote:
I only ask because if AFS Client 1.7 is implemented as a Kernel based dri=
ver, I cannot virtualize it.
Then I can cross it off my NJIT List of Applications to Virtualize which=
was created by OpenAFS users/admins at NJIT.
If it is implemented as a user based driver, I can probably virtualize pa=
rts of it so that it can access AFS.
Does it make sense to do so? Most probably not.
Do I use the product? No, but I have to support deployment onto student d=
esktop images so my customers can access their files on AFS Repositories.=
Thank you for the fast response.
Telecommunications & Networks
New Jersey Institute of Technology
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:firstname.lastname@example.org=
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
-----END PGP SIGNATURE-----