From: "Gordon Lack" <gml4410@ggr.co.uk>
To: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org
Subject: Re: autofsv5 enhancement - map names in /proc/mounts
Date: Tue, 14 Nov 2006 10:00:57 +0000 [thread overview]
Message-ID: <455993D9.4010003@ggr.co.uk> (raw)
In-Reply-To: <1163469607.3297.22.camel@localhost>
Ian Kent wrote:
>
> I'd like to find a simple way to accommodate this while retaining the
> multiple map functionality.
Fine by me. Bear in mind that the map-name (the bit I'm suggesting
should be added to /proc/mounts) will be different. eg: from your
original example:
/home /etc/auto.server1.home
/home /etc/auto.server2.home
So we'd end up with 2 lines in /proc/mounts:
/etc/auto.server1.home /home autofs ....
/etc/auto.server2.home /home autofs ....
(I think...although whether the patch I sent is sufficient to achieve
that I don't know)
next prev parent reply other threads:[~2006-11-14 10:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-07 15:02 -hosts and -null enabling for autofs v4.1.x Gordon Lack
2006-07-13 13:10 ` Ian Kent
2006-07-13 13:42 ` Jeff Moyer
2006-07-14 11:33 ` Gordon Lack
2006-07-14 13:31 ` Jeff Moyer
2006-07-14 15:58 ` Gordon Lack
2006-08-07 6:56 ` Ian Kent
2006-08-22 14:03 ` Bug (and patch) in autofs init.d script (v4.1.4) Gordon Lack
2006-08-22 14:18 ` Enhancement patch for autofs v4.1.4 init.d script Gordon Lack
2006-09-08 11:31 ` Bug in autofs v4.1.4 init.d script (and fix) Gordon Lack
2006-09-12 12:58 ` Bug in autofs v4.1.4 init.d script for reload " Gordon Lack
2006-09-13 9:42 ` Gordon Lack
2006-11-10 11:58 ` autofsv5 bug. Non-existent dirs get "mounted"! Gordon Lack
2006-11-10 12:05 ` autofsv5 enhancement - map names in /proc/mounts Gordon Lack
2006-11-10 17:33 ` autofsv5 - mouting files (not dirs) Gordon Lack
2006-11-11 2:58 ` Ian Kent
2006-11-11 2:53 ` autofsv5 enhancement - map names in /proc/mounts Ian Kent
2006-11-13 10:09 ` Gordon Lack
2006-11-13 15:44 ` Ian Kent
2006-11-13 16:58 ` Gordon Lack
2006-11-14 2:00 ` Ian Kent
2006-11-14 10:00 ` Gordon Lack [this message]
2006-11-14 11:42 ` 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=455993D9.4010003@ggr.co.uk \
--to=gml4410@ggr.co.uk \
--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.