Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Dan Vasaru" To: Subject: RE: [Proposal] Moving user mount information to HKLM Date: Fri, 27 Sep 2002 16:19:49 +0200 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal In-Reply-To: <1033133576.22922.269.camel@lifelesswks> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Importance: Normal > 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 Dan. -- 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/