delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
Date: | Wed, 2 Nov 2005 12:21:58 -0500 |
From: | Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com> |
To: | cygwin AT cygwin DOT com |
Subject: | cygcheck improvements |
Message-ID: | <20051102172158.GA6655@trixie.casa.cgf.cx> |
Reply-To: | cygwin AT cygwin DOT com |
Mime-Version: | 1.0 |
User-Agent: | Mutt/1.5.8i |
Seeing Igor's analysis of corrupt /etc/services symlinks reminded me that I wanted to start a discussion on cygcheck improvements. Ideally, cygcheck should report on things like /etc/services being wrong. What other kind of common things could cygcheck be testing for? cgf -- 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/
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |