From: Andrey Repin <anrdaemon@yandex.ru>
To: Ulli Horlacher <framstag@rus.uni-stuttgart.de>, cygwin@cygwin.com
Subject: Re: Is there a way to clone-install Cygwin?
Date: Sat, 01 Feb 2020 10:05:00 -0000 [thread overview]
Message-ID: <1764577188.20200201125607@yandex.ru> (raw)
In-Reply-To: <20200131140622.GB6676@tik.uni-stuttgart.de>
Greetings, Ulli Horlacher!
> I tried to write an installer.bat which uses the Windows bsdtar, but it
> fails with:
> C:\>dir
> Volume in drive C has no label.
> Volume Serial Number is EC42-8D26
> Directory of C:\
> 31 Jan 2020 12:45 84.340.162 cygwin64.tgz
> 31 Jan 2020 14:38 91.960.715 cygwin64.zip
> 31 Jan 2020 12:45 45 cygwin64_addons.tgz
> 19 Mar 2019 05:52 <DIR> PerfLogs
> 13 Jan 2020 13:12 <DIR> Program Files
> 15 Jan 2020 17:32 <DIR> Program Files (x86)
> 13 Jan 2020 13:12 <DIR> Users
> 13 Jan 2020 14:46 <DIR> Windows
> 31 Jan 2020 13:59 <DIR> xx
> 31 Jan 2020 14:43 91.960.889 xxx_20200131_144048.zip
> 4 File(s) 268.261.811 bytes
> 6 Dir(s) 45.442.043.904 bytes free
> C:\>tar -xf cygwin64.zip
> cygwin64/bin/apropos: Can't create '\\\\?\\C:\\\\cygwin64\\bin\\apropos'
> cygwin64/bin/awk: Can't create '\\\\?\\C:\\\\cygwin64\\bin\\awk'
> cygwin64/bin/bzcmp: Can't create '\\\\?\\C:\\\\cygwin64\\bin\\bzcmp'
> cygwin64/bin/bzegrep: Can't create '\\\\?\\C:\\\\cygwin64\\bin\\bzegrep'
> cygwin64/bin/bzfgrep: Can't create '\\\\?\\C:\\\\cygwin64\\bin\\bzfgrep'
> cygwin64/bin/bzless: Can't create '\\\\?\\C:\\\\cygwin64\\bin\\bzless'
> cygwin64/bin/captoinfo: Can't create '\\\\?\\C:\\\\cygwin64\\bin\\captoinfo'
> ^C
> C:\>
> (I run it as administrator).
> Any idea what went wrong
Wrong is precisely the way you are trying to "install" it.
> and how I can fix it?
Use supported ways to install Cygwin.
Even if you would successfully unpack your clone, on a different system, you
would still need to run full rebase. It's way easier to just script setup.exe
to install what you need.
--
With best regards,
Andrey Repin
Saturday, February 1, 2020 12:53: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:[~2020-02-01 10:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
2020-01-21 19:17 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
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
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=1764577188.20200201125607@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=framstag@rus.uni-stuttgart.de \
/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).