All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Taylor, ForrestX" <forrestx.taylor@intel.com>
To: "Myers, Parrish" <PMyers@sikorsky.com>
Cc: autofs@linux.kernel.org
Subject: Re: auto.net
Date: Thu, 22 Jan 2004 09:35:31 -0800	[thread overview]
Message-ID: <401009E3.2090709@intel.com> (raw)
In-Reply-To: B94D9EFEABBFD745A8BCFC0F658E3D740390C427@sussfe01.sikorsky.com

Myers, Parrish wrote:
> Hello,
> 
> I was wondering if I could get some help?  I am kinda new to the autofs
> thing... I think this is a simple question: Is there a simple way to tell if
> I have autofs4 built into my linux kernel?  And, if it isn't, does this
> still affect the use of auto.net (which is a replacement for the '-host'
> flag in the sgi verison)? I am having problems with getting auto.net to
> work. Everything in the setup seems to say it sould work: it does everyting
> but actually mound the directories.


You must use autofs4 for auto.net to work.  Try `/sbin/lsmod | grep autofs`.

If you see autofs, then you are using the old autofs3 module.  Stop 
autofs and remove the module (/etc/init.d/autofs stop ; modprobe -r 
autofs).  Edit /etc/modules.conf and add this line:
alias autofs autofs4
Restart autofs and see if it works.

If you see autofs4, then you are using the autofs4 module, and something 
else is wrong.  Check /var/log/message on the client machine and the 
machine that you are trying to connect to.

If you don't see autofs, then you may have autofs built into the kernel. 
  You'll have to look at the kernel configuration to see whether or not 
you included it.

Forrest

  reply	other threads:[~2004-01-22 17:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-22 16:19 auto.net Myers, Parrish
2004-01-22 17:35 ` Taylor, ForrestX [this message]
2004-01-23  0:36 ` auto.net Ian Kent

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=401009E3.2090709@intel.com \
    --to=forrestx.taylor@intel.com \
    --cc=PMyers@sikorsky.com \
    --cc=autofs@linux.kernel.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 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.