AutoFS5 for 2.6.27.x?

AutoFS5 for 2.6.27.x?

[Carsten Aulbert]

Hi all,

I'm reading/skimming this list for quite a bit of time, but somehow I
lost track. In the mainline kernel 2.6.27.4 there seems to be only
autofs4 not autofs5, right?  At least I'm only seeing CONFIG_AUTOFS_FS
and CONFIG_AUTOFS4_FS.

On the ftp server of kernel.org I found 5.0.3 patches from January, but
that seems quite old to me. The golden question: Is this the correct
tarball to use or is there some git repo were I should pull the patches
- and how?

Sorry if this question is dump :(

Cheers

Carsten

Re: AutoFS5 for 2.6.27.x?

[Jeff Moyer]

Carsten Aulbert <carsten.aulbert@aei.mpg.de> writes:

> Hi all,
>
> I'm reading/skimming this list for quite a bit of time, but somehow I
> lost track. In the mainline kernel 2.6.27.4 there seems to be only
> autofs4 not autofs5, right?  At least I'm only seeing CONFIG_AUTOFS_FS
> and CONFIG_AUTOFS4_FS.
>
> On the ftp server of kernel.org I found 5.0.3 patches from January, but
> that seems quite old to me. The golden question: Is this the correct
> tarball to use or is there some git repo were I should pull the patches
> - and how?

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.

Cheers,

Jeff

Re: AutoFS5 for 2.6.27.x?

[Carsten Aulbert]

Hi Jeff,

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.

Ah thanks, I should pay closer attention to the list as this distinction
slipped by.

Thanks!

Carsten

Re: AutoFS5 for 2.6.27.x?

[Carsten Aulbert]

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

and when starting autofs it complains about wrong kernel protocol version:

/etc/init.d/autofs restart
Stopping automount: done.
Starting automount: /usr/sbin/automount: kernel protocol version 5.00 or
above required.
no valid automount entries defined.

auto.master only has a single line:
/atlas/data          yp:auto.data      --timeout=5

and ypcat yields:
$ ypcat auto.data
-fstype=nfs,nfsvers=3,hard,rsize=32768,wsize=32768,tcp,rw       &:/data/

Something's wrong here but I can't spot it.

Cheers

Carsten

Re: AutoFS5 for 2.6.27.x?

[Jeff Moyer]

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.

You want:

CONFIG_AUOTFS_FS=n
CONFIG_AUTOFS4_FS=m

Cheers,

Jeff

Re: AutoFS5 for 2.6.27.x?

[Ian Kent]

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

Re: AutoFS5 for 2.6.27.x?

[Ian Kent]

On Mon, 2008-11-03 at 14:24 +0100, Carsten Aulbert wrote:
> Hi all,
> 
> I'm reading/skimming this list for quite a bit of time, but somehow I
> lost track. In the mainline kernel 2.6.27.4 there seems to be only
> autofs4 not autofs5, right?  At least I'm only seeing CONFIG_AUTOFS_FS
> and CONFIG_AUTOFS4_FS.

Like Jeff says, you need autofs4.

You should make sure that the autofs4 module is being loaded, not the
autofs module. If your using a later init script it will explicitly load
the module, but only if one isn't already present (so rmmod autofs
before startup should make things work). Another way to prevent being
caught is to "alias autofs autofs4" in your modules configuration (at
least I think that's the order, it's been a while since we've had this
problem reported).

> 
> On the ftp server of kernel.org I found 5.0.3 patches from January, but
> that seems quite old to me. The golden question: Is this the correct
> tarball to use or is there some git repo were I should pull the patches
> - and how?

The version 5 patch series is located at:
http://www.kernel.org/pub/linux/daemons/autofs/v5.

See patch_order-5.0.3 also. The patch list is quite large.

The git repo is at:
git clone git://git.kernel.org/pub/scm/linux/storage/autofs/autofs.git

The kernel patches in the repo are usually not up to date but, as I'm
wanting to release 5.0.4, they are at the moment.

Ian