All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: autofs@linux.kernel.org
Subject: Re: AutoFS5 for 2.6.27.x?
Date: Tue, 04 Nov 2008 09:39:51 +0900	[thread overview]
Message-ID: <1225759191.3003.15.camel@zeus.themaw.net> (raw)
In-Reply-To: <x49abcgkdup.fsf@segfault.boston.devel.redhat.com>

On Mon, 2008-11-03 at 10:50 -0500, Jeff Moyer wrote:
> Carsten Aulbert <carsten.aulbert@aei.mpg.de> writes:
> 
> > Hi all
> >
> > Jeff Moyer wrote:
> >> The kernel module is named autofs4 for reasons I won't get into.  The
> >> latest userspace package is autofs version 5.  The autofs4 kernel
> >> modules speaks the autofs version 5 protocol.
> >> 
> >> In short, you want the autofs version 5 userspace packages.
> >
> > Jumping up and down too early I guess:
> >
> > I've userland autofs5 version 5.0.3 installed, the kernel 2.6.27.2 has
> > AUTOFS4 set
> > $ zgrep AUTOFS /proc/config.gz
> > CONFIG_AUTOFS_FS=y
> > CONFIG_AUTOFS4_FS=y
> 
> Don't build them both into the kernel.  Ian, we should see if there's a
> way to disallow that.

Yeah, that does seem sensible these days.
Mmmm ... I've not really needed to do anything in the kernel build
system before, so I'm not sure either!

> 
> You want:
> 
> CONFIG_AUOTFS_FS=n
> CONFIG_AUTOFS4_FS=m
> 
> Cheers,
> 
> Jeff
> 
> _______________________________________________
> autofs mailing list
> autofs@linux.kernel.org
> http://linux.kernel.org/mailman/listinfo/autofs

  reply	other threads:[~2008-11-04  0:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-03 13:24 AutoFS5 for 2.6.27.x? Carsten Aulbert
2008-11-03 14:17 ` Jeff Moyer
2008-11-03 14:55   ` Carsten Aulbert
2008-11-03 15:07   ` Carsten Aulbert
2008-11-03 15:50     ` Jeff Moyer
2008-11-04  0:39       ` Ian Kent [this message]
2008-11-04  0:37 ` Ian Kent

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1225759191.3003.15.camel@zeus.themaw.net \
    --to=raven@themaw.net \
    --cc=autofs@linux.kernel.org \
    --cc=jmoyer@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.