Question.

        This is just a small one..

        What problems would there be in making the afs support
actually part of the kernel, and keeping the system mouning
utilities at transarc so our site contacts get them for us?  Is
there any proprietary code in the kernel module that can't
be placed in the standard kernel?

        If yes, I understand.

        If no, lets move it so we don't have to have 400 different
module versions, it's just part of the kernel, and we get
the userland stuff (afsd's etc) from our site contacts.

        - jared

Derek Atkins graced my mailbox with this long sought knowledge:
> Hi All!
> 
> I'm pleased to report that I have made two releases of Linux-AFS
> available to MIT and US-Domestic Transarc Customers.  For those of you
> International users, do not dispair -- these releases will be
> available to you in a couple days, as soon as Transarc personnel can
> copy my distributions over to the export directory.
> 
> The new releases are only for Linux/x86 (I'm still working on
> sparc-linux, and I dont have access to Linux/axp).  The two releases
> are:
> 
>       2.0.11-2 -- this fixes the general protection fault which
> happened during large data transfers.  It also hopefully fixes the
> "chmod g+s" bug, so you should now be able to make programs setgid!
> 
>       2.0.12 -- this is a port to Linux 2.0.12.  It has all the
> bugfixes that 2.0.11-2 has, except this works with the 2.0.12 Linux
> kernel.
> 
> To get Linux-AFS, you need to follow the appropriate instructions.  If
> you are at MIT, you can get it directly:
>       attach afsuser
>       cd /mit/afsuser/sipb-dist/linux
> 
> If you are not at MIT, you need to contact your AFS Site Contact.
> Your site contact should authenticate to transarc and grab Linux-AFS
> from the appropriate directory:
>       klog -c transarc.com
>       cd /afs/transarc.com/public/afs-contrib
>       cd bin/linux.client                     # domestic
>       cd bin.export/linux.client.export       #international
>       
>       <grab everything in sight>
> 
> If you are not already a subscriber, you should get added to the
> Linux-AFS mailing list, [EMAIL PROTECTED]  To get added, send mail to
> [EMAIL PROTECTED] and ask to be subscribed.  If you are at MIT
> you can add yourself:
>       blanche linux-afs -a $USER
> 
> If you find problems in Linux-AFS, such as a kernel oops, please do
> the following:
> 
>       * combine /usr/src/linux/System.map and /usr/tmp/zModule.map
> (you will need to hand-edit out the empty lines in zModule.map)
> 
>       * Use ksymoops (found in /usr/src/linux/scripts).. Feed it the
> combined system mapfile from above and the oops information.
> 
>       * Send both the original oops and the output of ksymoops to
> [EMAIL PROTECTED]
> 
>       * wait.
> 
> Thanks!  I hope you enjoy using Linux-AFS!
> 
> -derek
> 

Reply via email to