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 Message-ID: <20030116223045.87892.qmail@web14601.mail.yahoo.com> Date: Thu, 16 Jan 2003 17:30:45 -0500 (EST) From: - Subject: editing automount points via registry question To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii i think there was an error when i saw key /usr/bin with the registry value of /bin, i guess i decided to post this here to mention about the automounting feature i don't see quite oftenly talked about...editing the registry is repelling since you'll have to search for two spots for cygwin-> (find 'cygwin' using this text string works good...) - one for root section, the other for X11 font paths, - I'm not sure if there's another way to tell cygwin where the root path is, anyone? (CYGWIN_ROOT ?) - Does cygwin always need at least these two points in the registry? - Also i noticed that issuing 'mount' after using my custom registry values for cygwin paths, tells me that any relative symbolinks or relative paths of the same pathnames that are on fat or ntfs records are irrelevant, the registry settings would override them, more appropriate 'mount' typed in cygwin after the registry settings would show that they're mounted automatically and I assume that the 'mount' features of cygwin ovverides them. a silly question, but is this safe, or should i resort more closely with cygwin scripts using mount..? jagg ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca -- 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/