From: Ian Kent <raven@themaw.net>
To: Vincent Liggio <vince@blueskystudios.com>
Cc: Ion Badulescu <ionut@badula.org>,
autofs@linux.kernel.org, Lee Damon <nomad@ee.washington.edu>,
am-utils@fsl.cs.sunysb.edu
Subject: Re: Before I start carving wheels....
Date: Sun, 27 Feb 2011 14:13:04 +0800 [thread overview]
Message-ID: <1298787184.3293.20.camel@perseus> (raw)
In-Reply-To: <alpine.LFD.1.10.1102262335210.21420@gardencity.blueskystudios.com>
On Sun, 2011-02-27 at 00:01 -0500, Vincent Liggio wrote:
> On Sun, 27 Feb 2011, Ian Kent wrote:
>
> > What are you saying?
> > If you add this patch to Fedora am-utils it then works?
>
> Yes. I downloaded the F14 SRPM for am-utils, changed that one line, did
> an rpmbuild, and it works with the default F14 kernel.
Great, then hopefully Karl will just add the patch and we'll be good.
>
> The F14 supplied amd from am-utils-6.1.5-17 does NOT work at all with
> autofs - we compiled a kernel with autofs3 enabled, amd would not load. We
> tried our F12 kernel (which we compiled with autofs3 enabled and which
> worked on our F12 machines), along with the amd from F14 and amd wouldn't
> load. We copied over the F12 amd binaries, and the F12 amd loaded fine
> with both of our F14 and F12 kernels that we modified for autofs3.
>
To be honest I don't think trying to work out what VFS change broke this
is worth while (if in fact it was a VFS change, there have been a few
prior to 2.6.38). The fact is that autofs has been removed from 2.6.38
and we need to spend our time making sure the autofs4 module works with
products that use autofs the kernel communication protocols.
The final change needed is for autofs4 to be renamed to autofs to
finally remove that fork in development. I'm looking forward to the
breakage that will cause, ;)
Ian
next prev parent reply other threads:[~2011-02-27 6:13 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
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 [this message]
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=1298787184.3293.20.camel@perseus \
--to=raven@themaw.net \
--cc=am-utils@fsl.cs.sunysb.edu \
--cc=autofs@linux.kernel.org \
--cc=ionut@badula.org \
--cc=nomad@ee.washington.edu \
--cc=vince@blueskystudios.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.