Mail Archives: cygwin/2002/09/27/10:55:55
Robert,
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: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]On Behalf
Of Robert Collins
Sent: Friday, September 27, 2002 4:28 PM
To: Dan Vasaru
Cc: cygwin AT cygwin DOT com
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
> > mount $USERPROFILE$CYGHOME /home/$USER
>
> You mean creating permanent system mounts while running as administrator.
We
> tried that, and hit some upper mount limit in cygwin1.dll. Try it
yourself:
>
> ~>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
25
> 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,
Rob
--
---
GPG key available at: http://users.bigpond.net.au/robertc/keys.txt.
---
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -