From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Is there a way to clone-install Cygwin?
Date: Fri, 31 Jan 2020 20:25:00 -0000 [thread overview]
Message-ID: <bc6e7097-a2db-6357-6374-e9a2ab8cf789@SystematicSw.ab.ca> (raw)
In-Reply-To: <87r1zfqvo2.fsf@Rainer.invalid>
On 2020-01-31 12:21, Achim Gratz wrote:
> Ulli Horlacher writes:
>>> To a new naked Windows box, if you can "mount" it over the network
>>
>> No, I cannot do that. My destination Windows hosts are behind firewalls.
>> They cannot mount anything. I have to transfer a container file.
>
> Try a vhdx maybe?
Works only on some editions, flavours, features.
Format a USB drive as NTFS, copy the Cygwin directory tree verbatim onto that,
then copy the Cygwin directory tree verbatim onto the destination system.
You should use a common (admin?) owner, and a common (guest?) user if you want
to preset a home dir.
You could set everything up in a single tree including packages and setup so
that you could do reinstalls if required.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
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:[~2020-01-31 20:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 14:06 KARL BOTTS
2020-01-31 14:13 ` Ulli Horlacher
2020-01-31 19:21 ` Achim Gratz
2020-01-31 20:25 ` Brian Inglis [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-21 19:17 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2020-01-21 0:58 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2020-01-21 1:27 ` Brent Epp
2020-01-31 10:25 ` Ulli Horlacher
2020-01-31 11:29 ` Ulli Horlacher
2020-01-31 12:05 ` Ulli Horlacher
2020-01-31 12:54 ` Thomas Wolff
2020-01-31 14:06 ` Ulli Horlacher
2020-02-01 10:05 ` Andrey Repin
2020-02-01 11:21 ` BGINFO4X
2020-02-03 16:40 ` Ulli Horlacher
2020-02-03 17:01 ` BGINFO4X
2020-02-04 17:16 ` Ulli Horlacher
[not found] ` <16fc5b08e80.2780.a1382e26d1292f71ec6ef0cd03d49346@pdc.ca>
2020-01-21 2:33 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2020-01-21 2:55 ` Brent Epp
2020-01-21 4:46 ` Marco Atzeri
2020-01-21 20:33 ` Achim Gratz
2020-01-28 21:35 ` Andrey Repin
2020-01-28 22:00 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
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=bc6e7097-a2db-6357-6374-e9a2ab8cf789@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).