It is possible to mount afs on glue (via afs, not nfs ;-), but you do need OpenAFS even in Linux to do it.
I haven't done it in quite some time, and I don't currently have it set up on any of my machines, so I can't give you simple step-by-step instructions. You probably need to install the openafs-client, openafs-krb5, and openafs-modules-source packages, then compile and load the kernel module ... I don't remember what exactly, if anything, you need to do after that. Anyone else on the list have step-by-step instructions for this? On Sun, Nov 18, 2007 at 12:20:46AM -0500, Stephen Yang wrote: > Thanks so much! The instructions for vpnc worked brilliantly. However, I > was wondering if it would be possible to mount /afs on glue via nfs.. I > just tried "sudo mount -t glue.umd.edu:/afs ~/afs", to no avail. I know in > Windows I can do this via OpenAFS.. > > Thanks for all your help. > > Stephen > > Paul Donohue wrote: >> Some distros don't include a .config file in their linux kernel source >> packages, but do include a copy of the config in the linux kernel binary >> packages. This is because the same kernel source is used to build >> multiple binary kernels with different configurations, and it would be a >> waste to distribute multiple kernel source packages with only minor >> .config file changes. >> >> So, in Debian, for example, you have to do >> 'cp /boot/config-2.6.22-2-686 /usr/src/linux-source-2.6.22/.config' >> before compiling anything using the kernel sources. >> >> BTW ... if you're just trying to use the Campus VPN service, vpnc is >> sufficient (packaged in Debian as 'vpnc') ... you don't have to install >> the official Cisco client. >> >> Put the following lines in /etc/vpnc/umd.conf (make sure your email client >> hasn't broken the secret into several lines) >> IPSec gateway vpn.umd.edu >> IPSec ID UMD >> IPSec obfuscated secret >> B5C8B92963EBD895D71E62F1CAC60FA01C20A57E1B17CEBCEF3A67F88450E39D623489E86A40F63637552CD20AF32B50938C96923F0859FB17527991E1578DFF >> Xauth username <your UMD Directory username> >> >> Put the following lines in /etc/vpnc/umd-all.conf (make sure your email >> client hasn't broken the secret into several lines) >> IPSec gateway vpn.umd.edu >> IPSec ID UMD-TunnelAll >> IPSec obfuscated secret >> 84B813ADBA87E86EBD5743D604F98F9159F2AAAD47F0C4DA36F1EDDA5CA95030D915C772103D025D9966E622EFF629B4A822F1A48DE3A79A289AF759DD1359C3 >> Xauth username <your UMD Directory username> >> >> Then just run 'vpnc-connect umd' or 'vpnc-connect umd-all' ... run >> 'vpnc-disconnect' to disconnect. >> >> On Sat, Nov 17, 2007 at 02:16:34AM -0500, Stephen Yang wrote: >> >>> I think there is something wrong with my linux source. When I run the >>> install script, it has some grievances which I have reproduced below: >>> >>> * Binaries will be installed in "/usr/local/bin". >>> * Modules will be installed in "/lib/modules/2.6.20-16-386/CiscoVPN". >>> * The VPN service will be started AUTOMATICALLY at boot time. >>> * Kernel source from "/usr/src/linux-source-2.6.20" will be used to build >>> the module. >>> >>> Is the above correct [y] >>> >>> Making module >>> make -C >>> /usr/src/linux-source-2.6.20SUBDIRS=/home/stephen/downloads/vpnclient >>> modules >>> make[1]: Entering directory `/usr/src/linux-source-2.6.20' >>> >>> ERROR: Kernel configuration is invalid. >>> include/linux/autoconf.h or include/config/auto.conf are >>> missing. >>> Run 'make oldconfig && make prepare' on kernel src to fix it. >>> >>> >>> WARNING: Symbol version dump >>> /usr/src/linux-source-2.6.20/Module.symvers >>> is missing; modules will have no dependencies and modversions. >>> >>> Building modules, stage 2. >>> /usr/src/linux-source-2.6.20/scripts/Makefile.modpost:42: >>> include/config/auto.conf: No such file or directory >>> make[2]: *** No rule to make target `include/config/auto.conf'. Stop. >>> make[1]: *** [modules] Error 2 >>> make[1]: Leaving directory `/usr/src/linux-source-2.6.20' >>> make: *** [default] Error 2 >>> Failed to make module "cisco_ipsec.ko". >>> >>> >>> Does the vpn not work with my kernel? I'm not sure what to make of these >>> errors. Could anyone help me out? >>> >>> Thanks a million. >>> >>> Stephen >>> >
