From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: best way to re-install and keep cygwin configuration
Date: Thu, 12 Jul 2012 20:39:00 -0000 [thread overview]
Message-ID: <4FFF35DC.2060403@cygwin.com> (raw)
In-Reply-To: <CA+sc5mkk3T6Opz77gcjWVwcGqzVStfPa9ri_+OPPgVS=UoH=Rw@mail.gmail.com>
On 7/12/2012 4:31 PM, Earnie Boyd wrote:
> On Thu, Jul 12, 2012 at 4:27 PM, Larry Hall (Cygwin) wrote:
>> While I would also tend to just copy off my current Cygwin install and then
>> plop it back in when I finished the O/S reinstall, there will be things
>> like local user and group accounts in '/etc/passwd' and '/etc/group' that
>> will need updating. A reinstall of Cygwin avoids some of these little
>> clean-up tasks that come from just copying over a previous installation.
>
> Would one be able to re-execute the post install scripts to manage it?
Well, in the case of the '/etc/passwd' and '/etc/group' files, not entirely.
000-cygwin-post-install.sh will create these files but only if they don't
exist already.
--
Larry
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
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:[~2012-07-12 20:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-12 18:08 LMH
2012-07-12 20:10 ` Earnie Boyd
2012-07-12 20:28 ` Larry Hall (Cygwin)
2012-07-12 20:31 ` Earnie Boyd
2012-07-12 20:39 ` Larry Hall (Cygwin) [this message]
2012-07-12 20:44 ` K Stahl
2012-07-12 21:04 ` LMH
2012-07-12 21:42 ` Larry Hall (Cygwin)
2012-07-13 1:20 ` Andrey Repin
2012-07-13 2:14 ` LMH
2012-07-13 5:53 ` Mark Geisert
2012-07-13 15:59 ` James Johnston
2012-07-13 15:32 ` ping
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=4FFF35DC.2060403@cygwin.com \
--to=reply-to-list-only-lh@cygwin.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).