Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Subject:	RE: [Proposal] Moving user mount information to HKLM
From:	Robert Collins <rbcollins AT cygwin DOT com>
To:	Dan Vasaru <dvasaru AT broadpark DOT no>
Cc:	cygwin AT cygwin DOT com
In-Reply-To:	<CHEDKHJJDLOCCOFLMGEAEEMICMAA.dvasaru@broadpark.no>
References:	<CHEDKHJJDLOCCOFLMGEAEEMICMAA DOT dvasaru AT broadpark DOT no>
Date:	28 Sep 2002 00:57:35 +1000
Message-Id:	<1033138655.22922.312.camel@lifelesswks>
Mime-Version:	1.0

--=-FtrfIjc81mvsqSCncuhC
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sat, 2002-09-28 at 00:57, Dan Vasaru wrote:
>=20
> Robert,
>=20
> Your solution only works if the users are local administrators, as a doma=
in
> user has no rights to HKLM  (and hence to create a system mount). In our
> case, giving all users local administrator rights is an acceptable soluti=
on,
> but we're still left with a maximum of 25-30 simultaneous users. But we'l=
l
> go with it while waiting for a better mount.
>=20
> Thanks, Dan.

Excellent, I'm glad you have a workaround.

FWIW the HKLM user mounts would have the same security ramification
(which is why it's not a generically viable solution).

Rob

--=-FtrfIjc81mvsqSCncuhC
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQA9lHHeI5+kQ8LJcoIRAqWkAJ4okyCc7CigqwXyzTswPJQ+/SwP/gCcD5+G
0ONlHjDZLZHoJCi+sZ0DjfU=
=P+7t
-----END PGP SIGNATURE-----

--=-FtrfIjc81mvsqSCncuhC--

- Raw text -