This is the mail archive of the
mailing list for the Cygwin project.
Re: queries on Environment and Services before 1.5 -> 1.7 upgrade
- From: Jeremy Bopp <jeremy at bopp dot net>
- To: cygwin at cygwin dot com
- Date: Wed, 28 Apr 2010 14:16:48 -0500
- Subject: Re: queries on Environment and Services before 1.5 -> 1.7 upgrade
- References: <4BD8797E.firstname.lastname@example.org>
On 4/28/2010 1:07 PM, Lester Ingber wrote:
> I have some questions prior to upgrading from 1.5.25-15 to 1.7
> (currently 1.7.5-1) with respect to Environment and Services.
> I already am aware that after the upgrade I should run
> presumably in my first console shell.
I believe that step is only necessary if you have custom mount points
which you would like to preserve. If you don't have custom mount
points, you can skip this.
> Under My Computer -> Advanced -> Environment Variables -> System Variables
> should the variable server in
> Cygwin server
> be changed to no argument (unless there is a good reason to put in one?)
> before the upgrade? That is, is it OK to have nothing as the variable?
According to http://cygwin.com/cygwin-ug-net/using-cygwinenv.html,
"server" is now an obsolete option for the CYGWIN environment variable,
so you can remove it. Now if you don't need to set a value of the
CYGWIN environment variable, just remove it entirely. It probably won't
cause a problem if it's empty, but then you'll eventually wonder why you
have it at all.
> Under Administrative Services (Local) I now have cygrunsrv.exe used in:
> Cron daemon
> CYGWIN cygserver
> CYGWIN sshd
> Should these be changed or turned off during the upgrade? That is,
> should these be disabled and then after the upgrade run
> as if I were starting cygserver for the first time?
I never used cygserver or cron myself, but I know that you don't need to
delete the service for sshd in order to upgrade. All you should have to
do is follow the usual rules for performing any Cygwin update and make
sure that you stop all Cygwin processes for all users on the system,
including services. Failure to stop all Cygwin processes prior to
upgrade will force you to reboot before you have a functional Cygwin
> Are there any other common settings I should change before upgrading? I
> did look at the docs, but did not notice anything else.
I'm not aware of any other steps you need to perform, but if you're at
all concerned about losing what you currently have, it would be a great
idea to make a backup of your current Cygwin installation before you
upgrade. Simply copying the current installation directory to a new
location should be sufficient. If something goes wrong with your
upgrade, you should just be able to toss the current installation and
put the backup in its place before trying again.
If you have customized any files in /etc such as /etc/profile, be aware
that such files may not be upgraded. This another usual rule for any
Cygwin update, but it bears repeating.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple