On Thu, 2011-02-24 at 14:42 +0800, Ian Kent wrote:
> On Wed, 2011-02-23 at 23:35 -0500, Vincent Liggio wrote:
> > On Thu, 24 Feb 2011, Ian Kent wrote:
> > 
> > >> I reported on both kernel.org and on am-utils.org that autofs and amd do
> > >> not work with F12's kernel in March/April of 2010 (kernel.org bug 15878
> > >> and am-utils bug 639). No one has acknowledged or worked on the bug, as
> > >> far as I can tell on the respective bugzillas.
> > >
> > > I don't remember seeing any mail on that bug even though I'm on the cc
> > > list for it.
> > >
> > > In any case, it's asking for the autofs module to be built as default
> > > which isn't likely to happen since, even at that time, the autofs module
> > > was going to be removed from the kernel.
> > 
> > It (autofs3) still exists as an option in F14 (if we build our own 
> > kernel), but doesn't seem to work either as a module or compiled into the 
> > kernel (it did work in F12). If there were a way for amd to work with 
> > autofs4, that'd be great, but it doesn't.
> > 
> > > But the autofs4 module should be able to be used for autofs kernel
> > > protocol version 3. It may require some changes in user space and, since
> > > the v3 protocol in autofs4 hasn't been tested for so long, there may be
> > > some other bugs that need fixing.
> > 
> > Problem is that amd I believe specifically looks for autofs3 (even though 
> > the code says minimum autofs version 3, it fails to work with autofs4). 
> > And since no one is responding to the bug I put in about that, and the 
> > last time code was released for amd was in 2005, amd using autofs on the 
> > current F14 kernel seems to dead.
> 
> I'll grab the amd source and have a quick look.
> Where is the right place to get it?

It looks like amd should work with autofs protocol version v4.
You should also try "modprobe autofs4" before starting amd and see what
happens.

Ian


_______________________________________________
autofs mailing list
autofs@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/autofs

Reply via email to