From: Tim Hockin <thockin@sun.com>
To: autofs@linux.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: autofs and namespaces
Date: Wed, 20 Aug 2003 15:20:50 -0700 [thread overview]
Message-ID: <3F43F442.20404@sun.com> (raw)
For lack of clear insight into this, I thought I might put this out for
opinions.
We're examining autofs and issues customers are having with it. One of
the issues that came up during discussions of things we can do is
namespaces.
Does anyone have any ideas how namespaces and autofs ought to play
together? There are some obvious answers, but it seems to me that they
might not be correct.
Anyone out there want to throw some ideas out? We can just ignore it,
but that isn't exactly nice. What we really need is some guidance on
what kind of sematics are "correct".
Tim
--
Tim Hockin
Systems Software Engineer
Sun Microsystems, Linux Kernel Engineering
thockin@sun.com
next reply other threads:[~2003-08-20 22:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-20 22:20 Tim Hockin [this message]
2003-08-22 11:18 ` [autofs] autofs and namespaces 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=3F43F442.20404@sun.com \
--to=thockin@sun.com \
--cc=autofs@linux.kernel.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox