[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFz9ofF+Ey8VCDS8UEf2XSw36kj2RhkHfFScuzLXMeNrkA@mail.gmail.com>
Date: Mon, 23 Jan 2012 16:13:49 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Serge Hallyn <serge.hallyn@...onical.com>
Cc: Dave Hansen <haveblue@...ibm.com>, sukadev@...ux.vnet.ibm.com,
Andy Whitcroft <apw@...onical.com>,
Al Viro <viro@...iv.linux.org.uk>,
Matt Helsley <matthltc@...ibm.com>,
linux-kernel@...r.kernel.org, containers@...ts.linux-foundation.org
Subject: Re: [RFC] fix devpts mount behavior
On Mon, Jan 23, 2012 at 4:05 PM, Serge Hallyn
<serge.hallyn@...onical.com> wrote:
>
> I've been playing for the last week with ways to fix this, and in the
> end I can see two ways.
How about a third way:
- make "newinstance" mandatory (and "-o newinstance" is a no-op) and
forget about the whole issue.
- if you really want to remount the old global one, you have to use a
bind mount of that original mount instead.
There may be some subtle reason why the above is totally broken and
just fundamnetally wouldn't work, and breaks all existing setups, but
maybe it's worth at least discussing as an option?
Or did I entirely misunderstand the problem?
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists