This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: [Proposal] Moving user mount information to HKLM


Your solution only works if the users are local administrators, as a domain
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 solution,
but we're still left with a maximum of 25-30 simultaneous users. But we'll
go with it while waiting for a better mount.

Thanks, Dan.

-----Original Message-----
From: []On Behalf
Of Robert Collins
Sent: Friday, September 27, 2002 4:28 PM
To: Dan Vasaru
Subject: RE: [Proposal] Moving user mount information to HKLM

On Sat, 2002-09-28 at 00:19, Dan Vasaru wrote:
> > On the user mount in HKLM idea, it's a no-goer. Normal users don't
> >  have write access to most of HKLM, on any partly-secure install
> > of NT (which is where the original posters issue arose).
> I may be wrong, but couldn't setup, or whoever creates the original
> HKLM/../cygwin key, set up the security attributes such that any
> authenticated user may write there ?
> > Secondly, there is a much more straightforward solution
> > for the poster:
> > use something like
> You mean creating permanent system mounts while running as administrator.
> tried that, and hit some upper mount limit in cygwin1.dll. Try it
> ~>for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
> 26; do mount h: /home/user$i; done

Yes, it's limited to 30. See shared_info.h in the source.

This affects BOTH user and system mounts.

As a workaround you can hook the exiting of the login shell to unmount
the path when you're finished.

Hope that helps,
GPG key available at:

Unsubscribe info:
Bug reporting:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]