From: Andrey Repin <anrdaemon@yandex.ru>
To: Alejandro Benitez <BenitezAlejandroeepo@outlook.com>, cygwin@cygwin.com
Subject: Re: Windows upgrade
Date: Wed, 13 Jun 2018 08:35:00 -0000 [thread overview]
Message-ID: <1992844183.20180613060823@yandex.ru> (raw)
In-Reply-To: <CP2P152MB1793C5EA6179682AFEA781F8DC7F0@CP2P152MB1793.LAMP152.PROD.OUTLOOK.COM>
Greetings, Alejandro Benitez!
> I just don't know what I'll need to tweak /
> migrate so that the new Windows installation installed on top of the same
> drive that currently holds the 32 bit cygwin knows it's there. I'm betting
> some registry entries and environment variables. Does anyone know these
> tweaks for certain? I need cygwin to be fully functional, I mean setup.exe
> needs to be able to install packages, otherwise it won't be of much use.
> I might also be wrong and need to install cygwin64 as I upgrade Windows. Fingers are crossed.
All you'd need to do (to be on safest possible side) is to issue
rebase-trigger full
then run a normal setup session to the end at least once, specifying your
existing Cygwin installation directory as the target.
If any issues would arise after that, please check
> FAQ: http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
and if all else fails, follow the
> Problem reports: http://cygwin.com/problems.html
--
With best regards,
Andrey Repin
Wednesday, June 13, 2018 6:05:20
Sorry for my terrible english...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-06-13 3:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 3:20 Alejandro Benitez
2018-06-13 6:12 ` Sam Habiel
2018-06-13 13:49 ` Andrey Repin
2018-06-13 14:39 ` Sam Habiel
2018-06-13 8:35 ` Andrey Repin [this message]
2018-06-13 18:37 ` Achim Gratz
2018-06-15 11:17 ` Andrey Repin
2018-06-14 1:29 ` Hans-Bernhard Bröker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1992844183.20180613060823@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=BenitezAlejandroeepo@outlook.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).