From: linas@austin.ibm.com (Linas Vepstas)
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org, nfonteno@us.ibm.com
Subject: [PATCH] ppc64_defconfig to use AUTOFS_V4 not V3
Date: Wed, 29 Nov 2006 12:05:22 -0600 [thread overview]
Message-ID: <20061129180522.GM10879@austin.ibm.com> (raw)
Paul,
Please apply. Although I have a general question: who is served
by the ppc64_defconfig these days? Any reason why its not more
like powerpc_defcofig? "make defconfig" uses uname -m to pick up
the defconfig, and my cell, rhel5 and sles10 boxes report ppc64
not pseries for uname -m.
--linas
Defconfig ppc64 kernels running under late-model distros
may hang in the automounter rc.d script, which seems to be
expecting autofs version 4. This patch uses the newer autofs.
Signed-off-by: Linas Vepstas <linas@austin.ibm.com>
----
arch/powerpc/configs/ppc64_defconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Index: linux-2.6.19-rc4-git3/arch/powerpc/configs/ppc64_defconfig
===================================================================
--- linux-2.6.19-rc4-git3.orig/arch/powerpc/configs/ppc64_defconfig 2006-11-01 16:15:06.000000000 -0600
+++ linux-2.6.19-rc4-git3/arch/powerpc/configs/ppc64_defconfig 2006-11-29 11:53:48.000000000 -0600
@@ -1386,8 +1386,8 @@ CONFIG_INOTIFY=y
CONFIG_INOTIFY_USER=y
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
-CONFIG_AUTOFS_FS=y
-# CONFIG_AUTOFS4_FS is not set
+# CONFIG_AUTOFS_FS is not set
+CONFIG_AUTOFS4_FS=m
# CONFIG_FUSE_FS is not set
#
next reply other threads:[~2006-11-29 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 18:05 Linas Vepstas [this message]
2006-11-29 18:45 ` [PATCH] ppc64_defconfig to use AUTOFS_V4 not V3 Olof Johansson
2006-11-29 19:32 ` Linas Vepstas
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=20061129180522.GM10879@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=nfonteno@us.ibm.com \
--cc=paulus@samba.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).