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
Reply-To: Cygwin List <cygwin AT cygwin DOT com>
Message-Id: <6.1.0.6.0.20040622121026.0322e748@pop.prospeed.net>
X-Sender: 
Date: Tue, 22 Jun 2004 12:11:00 -0400
To: Jerry Whitaker <jerry DOT whitaker AT mail DOT publix DOT com>,
   "'cygwin AT cygwin DOT com'" <cygwin AT cygwin DOT com>
From: Larry Hall <cygwin-lh AT cygwin DOT com>
Subject: Re: Windows 2003 Compatibility
In-Reply-To: <3DCD5E22BC2DD511BED100D0B7E3AD1712317278@L47XDTO1.publix.c om>
References: <3DCD5E22BC2DD511BED100D0B7E3AD1712317278 AT L47XDTO1 DOT publix DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 11:41 AM 6/22/2004, you wrote:
>Hello.  We are using Cygwin here at Publix Super Markets and are in the
>process of upgrading our servers to Windows 2003 Server. 
>
>Which version of the product is certified for Windows 2003 Server? Which
>version is supported under Windows 2003 Server? Are there any issues with
>doing an in-place upgrade using this version of the product? If so, what are
>they?
>
>Thank you for your assistance.


Cygwin has not been "certified" on any Windows platform.  As to the version
of Windows supported, the main Cygwin page states:


  The Cygwin DLL works with all non-beta, non "release candidate", ix86 32 
  bit versions of Windows since Windows 95, with the exception of Windows CE.


Issues using some Cygwin packages with W2K3 generally are related to 
security changes in W2K3 (i.e. the SYSTEM user has less permissions).
This is typically only a problem for packages that run as services and 
need to switch user contexts (from SYSTEM to some user).  Packages "caught"
by this change include ssh and cron, among others.  Solutions exist in 
the package READMEs.  

I'd expect that an in-place upgrade of Windows wouldn't adversely affect
Cygwin and the majority of it's packages at all.  But I've never done
such an upgrade and I haven't seen any reports of anyone trying this (not
that it hasn't been done, just that no one has reported doing it IIRC). 


--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


--
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/