All of lore.kernel.org
 help / color / mirror / Atom feed
From: Moshe Kaminsky <kaminsky@math.huji.ac.il>
To: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org
Subject: Re: [ANNOUNCE] autofs 5.0.0 beta1
Date: Thu, 4 May 2006 20:33:52 +0300	[thread overview]
Message-ID: <20060504173352.GB12272@kaminsky> (raw)
In-Reply-To: <Pine.LNX.4.64.0605040124240.31510@raven.themaw.net>


[-- Attachment #1.1: Type: text/plain, Size: 1270 bytes --]

* Ian Kent <raven@themaw.net> [03/05/06 20:45]:
> On Wed, 3 May 2006, Moshe Kaminsky wrote:
> 
> > * Ian Kent <raven@themaw.net> [03/05/06 18:00]:
> > > On Wed, 3 May 2006, Moshe Kaminsky wrote:
> > > > Another question I have: I once asked if it's possible to run the 
> > > > actual mount command as the user trying to read the directory, 
> > > > instead of root. I was told that this is impossible in version 4. 
> > > > Will it be possible now?
> > > 
> > > Do you have a mount that will work for a user?
> > > 
> > > You can use the $USER substitution variable now to mount with a 
> > > "user=${USER}" option or $UID and $GID with "uid=${UID}" and "gid=${GID}" 
> > > in your map. Will that help?
> > > 
> > 
> > I don't think so. What I have in mind is that a user will be able to 
> > automount his home directory on a remote machine using sshfs. For this, 
> > that user has to actually run the mount command, so that his ~/.ssh is 
> > used.
> 
> The problem here is that mount(8) will only allow the "user" option if 
> an entry is present in the fstab which defeats the purpose of using 
> autofs.

Funny. It appears that you're right. I'm sure it used to work, though 
(maybe something changed in the kernel?)

Thanks,
Moshe

[-- Attachment #1.2: Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

_______________________________________________
autofs mailing list
autofs@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/autofs

  reply	other threads:[~2006-05-04 17:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-02 15:35 [ANNOUNCE] autofs 5.0.0 beta1 Ian Kent
2006-05-02 17:33 ` Steinar H. Gunderson
2006-05-03  1:26   ` Ian Kent
2006-05-03 13:16 ` Moshe Kaminsky
2006-05-03 14:48   ` Ian Kent
2006-05-03 16:55     ` Moshe Kaminsky
2006-05-03 17:30       ` Ian Kent
2006-05-04 17:33         ` Moshe Kaminsky [this message]
2006-05-05  1:32           ` Ian Kent
2006-05-03 15:15   ` Ian Kent
2006-05-03 16:58     ` Moshe Kaminsky
2006-05-03 15:58   ` Ian Kent
2006-05-03 17:00     ` Moshe Kaminsky
2006-05-03 17:56       ` Ian Kent
2006-05-04 17:28         ` Moshe Kaminsky
  -- strict thread matches above, loose matches on Subject: below --
2006-05-04 11:16 Rigler, Stephen C.
2006-05-04 12:29 ` Ian Kent
2006-05-04 13:56   ` Jeff Moyer
2006-05-04 13:08 Rigler, Stephen C.
2006-05-04 13:57 ` Jeff Moyer
2006-05-04 17:29 Rigler, Stephen C.
2006-05-04 18:03 ` Jeff Moyer
2006-05-05  1:37 ` Ian Kent
2006-05-08 11:51 Rigler, Stephen C.
2006-05-09 10:51 ` 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=20060504173352.GB12272@kaminsky \
    --to=kaminsky@math.huji.ac.il \
    --cc=autofs@linux.kernel.org \
    --cc=raven@themaw.net \
    /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.