All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Techie <techchavez@gmail.com>
Cc: autofs@linux.kernel.org
Subject: Re: Executable maps
Date: Mon, 14 Jun 2010 12:44:51 +0800	[thread overview]
Message-ID: <1276490691.9943.68.camel@localhost> (raw)
In-Reply-To: <AANLkTin8PTdQLShcrAk_cT21pFfwcuatXvMNMQSgYmO3@mail.gmail.com>

On Mon, 2010-06-07 at 16:33 -0700, Techie wrote:
> Hi Ian, List,
> 
> 2 questions..
> 
> 1) Has a fix been released for the Admin or "$" shares in regards to
> cifs yet? The automounter fails to mount them even though the path
> looks ok. It mounts the non admin shares fine. I can mount them fine
> from the CLI.

Not sure, since there was no feedback from the thread:
http://www.mail-archive.com/autofs@linux.kernel.org/msg07896.html

but the patch posted there has been committed and is available on
kernel.org. There may well be other patches in the series that it
depends on so beware.

> 
> 2) I have modified the auto.smb script to create a direct map since
> the indirect fails to mount admin shares. Can a direct map be used as
> an executable map? My feeling from my reading of the manpage is no but
> maybe there is a way.

Don't think that could work.
There's no way for a program map to enumerate the entire map at initial
startup and I don't want to add something that allows that because
program maps are dynamic and that introduces all sorts of difficulties
for the handling of direct mounts. And there is no way to use a program
map for a direct mount that has not been mounted (at startup).

Ian

  reply	other threads:[~2010-06-14  4:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-07 23:33 Executable maps Techie
2010-06-14  4:44 ` Ian Kent [this message]
2010-07-02 22:02   ` H. Peter Anvin
2010-07-06  1:19     ` 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=1276490691.9943.68.camel@localhost \
    --to=raven@themaw.net \
    --cc=autofs@linux.kernel.org \
    --cc=techchavez@gmail.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.