X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Torfinn Ottesen Subject: Re: "fork problem" debugging Date: Mon, 29 May 2006 06:52:12 +0000 (UTC) Lines: 21 Message-ID: References: <20060518023929 DOT 65449 DOT qmail AT web31310 DOT mail DOT mud DOT yahoo DOT com> <447A2C61 DOT 3060702 AT cygwin DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes 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 Larry Hall (Cygwin cygwin.com> writes: > The key words here are "If you use Registry Editor incorrectly". In other > words, if you modify something other than what's recommended, you might > cause yourself other problems. This is standard boiler-plate legalese that's > spewed whenever mention of changing the registry is uttered by MS (and > others). While you are free to interpret it as you wish and you are, of > course, under no obligation to make these or any other changes in the > registry via the registry editor, you should not feel like the above means > that you should not edit your registry. For those occassions where you do > edit the registry yourself, just do so with care. I know, but my emplyer provides this PC for me - I am neither prepared to nor supposed to act as "root" doing major surgery on the Windows system registry and break it. Cygwin is in this context what makes MS OS a mostly acceptable working environment, thanks. Torfinn -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/