All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Liggio <vince@blueskystudios.com>
To: Ion Badulescu <ionut@badula.org>
Cc: autofs@linux.kernel.org, Lee Damon <nomad@ee.washington.edu>,
	am-utils@fsl.cs.sunysb.edu, Ian Kent <raven@themaw.net>
Subject: Re: Before I start carving wheels....
Date: Sat, 26 Feb 2011 15:24:39 -0500	[thread overview]
Message-ID: <4D696187.4050004@blueskystudios.com> (raw)
In-Reply-To: <alpine.LRH.2.00.1102251234570.14837@ionlinux.tower-research.com>

Ok, that works. I will put a bug report into redhat so they hopefully 
will integrate that into the latest code. Why they are releasing a -18 
for F15 I don't get, when it doesn't even have any code changes.

So to sum up, amd 6.1.5 patched as below works fine on F14 kernel's with 
autofs4.

The amd redhat supplies does NOT work, in fact, it doesn't even load 
properly with autofs enabled.

Vince

On 02/25/2011 12:39 PM, Ion Badulescu wrote:
> On Thu, 24 Feb 2011, Ian Kent wrote:
>
>>>>> 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.
>
> No, amd will happily work with either autofs3 or autofs4.
>
> The problem is that it (optimistically) tries to use the highest version
> that the kernel supports, which is autofs5 these days. But it itself
> doesn't have support for autofs5, so it fails miserably.
>
> The patch (copy/pasted so it might not apply cleanly) fixes autofs:
>
> commit 5cefcd3e1c7cb4943697e48996b8b1cbc7a9e7de
> Author: Ion Badulescu <ionut@buggy.badula.org>
> Date: Tue Nov 30 07:14:23 2010 -0500
>
> max supported autofs version is 4
>
> diff --git a/conf/autofs/autofs_linux.c b/conf/autofs/autofs_linux.c
> index af61804..e901da7 100644
> --- a/conf/autofs/autofs_linux.c
> +++ b/conf/autofs/autofs_linux.c
> @@ -59,7 +59,7 @@
> */
>
> #define AUTOFS_MIN_VERSION 3
> -#define AUTOFS_MAX_VERSION AUTOFS_MAX_PROTO_VERSION
> +#define AUTOFS_MAX_VERSION 4
>
>
> /*
>
>
> -Ion

  parent reply	other threads:[~2011-02-26 20:24 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mj849qulir49bmajiif61sp3.1298416168018@email.android.com>
     [not found] ` <alpine.LFD.1.10.1102222203150.7886@gardencity.blueskystudios.com>
2011-02-23 14:19   ` Before I start carving wheels Jeff Moyer
2011-02-23 15:03     ` Vincent Liggio
2011-02-24  3:16       ` Ian Kent
2011-02-24  4:35         ` Vincent Liggio
2011-02-24  6:42           ` Ian Kent
2011-02-24 10:42             ` Ian Kent
2011-02-24 20:11               ` Vincent Liggio
2011-02-25  3:19                 ` Ian Kent
2011-02-25 17:39               ` Ion Badulescu
2011-02-26  2:28                 ` Ian Kent
2011-02-26 20:35                   ` Vincent Liggio
2011-02-26 20:24                 ` Vincent Liggio [this message]
2011-02-26 22:23                   ` Ion Badulescu
2011-02-27  4:28                   ` Ian Kent
2011-02-27  5:01                     ` Vincent Liggio
2011-02-27  6:13                       ` Ian Kent
2011-02-26 20:25                 ` Vincent Liggio

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=4D696187.4050004@blueskystudios.com \
    --to=vince@blueskystudios.com \
    --cc=am-utils@fsl.cs.sunysb.edu \
    --cc=autofs@linux.kernel.org \
    --cc=ionut@badula.org \
    --cc=nomad@ee.washington.edu \
    --cc=raven@themaw.net \
    /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.