delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2005/11/02/17:57:45

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 17:57:34 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygcheck improvements
Message-ID: <20051102225734.GD17941@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <20051102172158 DOT GA6655 AT trixie DOT casa DOT cgf DOT cx> <43691F86 DOT 1B7BE77C AT dessent DOT net>
Mime-Version: 1.0
In-Reply-To: <43691F86.1B7BE77C@dessent.net>
User-Agent: Mutt/1.5.8i

On Wed, Nov 02, 2005 at 12:20:22PM -0800, Brian Dessent wrote:
>Christopher Faylor wrote:
>
>> What other kind of common things could cygcheck be testing for?
>
>I was thinking that instead of just reporting the current value of
>$PATH, it would be handy to also report on the Windows/Registry value of
>$PATH.  That way, you can tell if Cygwin is being added to the path in
>cygwin.bat or if the person actually added it to their Windows
>environment.  I forget exactly why this came up but I remember thinking
>it would have been useful more than once when trying to help someone.
>
>I guess it could also explicitly check /etc/passwd and /etc/group, even
>though at the moment you can sort of tell if this has been done by
>looking at the output of 'id'.
>
>The "pending file replacements" idea is a good one too, as is the
>"incomplete postinstall script" idea.  I'm not sure if the "SYSTEM user
>has mounts" issue would come up enough to warrant checking for it,
>because I can't really think of how that would come to happen.  It might
>be good to check if /usr/bin is a user mount and there are services,
>then print a warning.  This is something that you can determine by
>looking at the output already but having it as an explicit warning makes
>it more clear, especially for the user who isn't aware of the problem.

Given the message that follows this one on the list, should we
be issuing a helpful message if there are network shares and services
being used on the same system, too?

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/

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019