Excerpts from internet.computing.netbsd.port-i386: 12-Aug-97 Re: AFS for
1.2G? by Bill Studenmund@macro.st 
> The change worked well, except that vi added a CR on the end of the file.
> I haven't tried that, but the other person said that'd be bad.
>  
> Sould I just try it as is? Or is there a better way?

    I used emacs and the hexl-mode (M-x hexl-mode), and searched for
1.2E and changed the E to a G.  It didn't touch the rest of the file,
and worked perfectly.  I'd been doing this from 1.2A on down, with the
already noted exception of whenever the vfs code changed and an actual
new build was needed.

    BTW, why are things done this way?  Are kernel modules always
hard-wired to a specific version like this?  Given how rarely the
modules seem to break, I guess I don't see the point of having it
disable itself if the version doesn't match.  Could this be changed to
simply issuing a *warning* that the version doesn't match, but still
letting you run it?  Seems to me that so long as the module will link
it'll probably work.

                                                          Will Ferry

--------------------------------------------------------------------------
William O Ferry <woferry@CMU.EDU> | finger:  woferry@WarpDrive.RES.CMU.EDU
talk:  finger for online status   | http://warpdrive.res.cmu.edu/~woferry/
--------------------------------------------------------------------------