From: Ian Kent <raven@themaw.net>
To: Vincent Liggio <vince@blueskystudios.com>
Cc: autofs@linux.kernel.org, Lee Damon <nomad@ee.washington.edu>,
am-utils@fsl.cs.sunysb.edu
Subject: Re: Before I start carving wheels....
Date: Fri, 25 Feb 2011 11:19:34 +0800 [thread overview]
Message-ID: <1298603974.3439.48.camel@perseus> (raw)
In-Reply-To: <4D66BB5B.4040808@blueskystudios.com>
On Thu, 2011-02-24 at 15:11 -0500, Vincent Liggio wrote:
> On 02/24/2011 05:42 AM, Ian Kent wrote:
> >
> > It looks like amd should work with autofs protocol version v4.
> > You should also try "modprobe autofs4" before starting amd and see what
> > happens.
>
> We tried that before, and this is what happens:
>
> Feb 24 14:40:39 canton_64 amd[1504]: initializing amd.conf map amd.net
> of type nis
> Feb 24 14:40:39 canton_64 amd[1504]: amd.net mounted fstype toplvl on /net
> Feb 24 14:40:39 canton_64 amd[1504]: autofs: using protocol version 5
This is wrong, amd hasn't used the correct mount options or I'm not
parsing the options correctly. Not sure that I am parsing the options
incorrectly since autofs version 4 needs to use the version 4 protocol
and it seems to be able to request that OK.
> Feb 24 14:40:39 canton_64 amd[1504]: /net set to never timeout
>
> Then we change to a directory and we get:
>
> Feb 24 14:40:57 canton_64 amd[1504]: Unknown autofs packet type 3
>
> lsmod
> Module Size Used by
> autofs4 22687 13
> ipv6 278339 24
> ppdev 7925 0
> parport_pc 21081 0
> parport 31509 2 ppdev,parport_pc
> e1000 92062 0
> i2c_piix4 11998 0
> shpchp 29568 0
> i2c_core 26926 1 i2c_piix4
> mptspi 14609 3
> mptscsih 28444 1 mptspi
> mptbase 74728 2 mptspi,mptscsih
> scsi_transport_spi 22211 1 mptspi
>
next prev parent reply other threads:[~2011-02-25 3:19 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 [this message]
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
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=1298603974.3439.48.camel@perseus \
--to=raven@themaw.net \
--cc=am-utils@fsl.cs.sunysb.edu \
--cc=autofs@linux.kernel.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.