Re: [autofs] "simultaneous" mounts causing weird behavior

Re: [autofs] "simultaneous" mounts causing weird behavior

[Ian Kent]

On Tue, 2003-11-11 at 00:57, Matthew Mitchell wrote:

> > You should be using the latest autofs4 kernel module with this. It is
> > available form the same place you got the beta autofs-4.
> 
> OK.  Looks like a big change to the kernel setup (from a quick browse of
> the patch).  In the interest of isolating the change to userspace, can
> you point me to a version of autofs4 that works with the stock 2.4.20
> kernel module?  I'd be happy to forward-port anything that works and
> test it again with the newer code.  (I can test the new stuff pretty
> easily on one machine but I don't want to undertake the week-long
> process of updating the kernel on the whole cluster just for this
> problem.)
> 

What is the question here. autofs is a kernel automounter. The autofs4
kernel module is as much a part of the package as the daemon. There is
no userspace version of the kernel module. I can't see how there can be.

Using the module distributed with 2.4 kernels is fine if you don't want
browsable mount points and that's it.

<rant>

I must also add that you don't need to change the kernel source tree at
all to use my updated kernel module. This was one of the reasons I
constructed the module build kit (available on kernel.org in the same
directory as the autofs v4 package). Further more, the changes I have
made are exclusively to the autofs4 module, as should be the case for
any filesystem module.

The other reason I put the kit together was that when I took over
maintenance of autofs v4, the previous maintainer, although happy to
hand over the maintenance of the daemon, was less than happy for me to
maintain the kernel module. So I will, as time passes, try to get my
changes into the kernel although I haven't made any progress there yet.

</rant>

You need to read the doco in the kit to use it. Briefly, you need the
kernel source tree corresponding to the running kernel and matching
kernel config file. In Makefile.conf set the macro variables as
instructed and 'make' then 'make install' (install must be done as
root). This will build the module, make a copy of the kernels' module
and place the updated module in the right place. Subsequent 'make
install' will not overwrite the backup if it already exists. 'make
uninstall' will reinstate the original kernel module.

I have tried to cater for people who are reluctant to patch and build
kernels with the kit.  

What else can I do?

-- 

   ,-._|\    Ian Kent
  /      \   Perth, Western Australia
  *_.--._/   E-mail: raven@themaw.net
        v    Web: http://themaw.net/