From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Portable CygWin version for Windows?
Date: Sun, 14 Nov 2021 17:36:50 +0100 [thread overview]
Message-ID: <87czn28zj1.fsf@Rainer.invalid> (raw)
In-Reply-To: <2810021269.20211114191016@yandex.ru> (Andrey Repin via Cygwin's message of "Sun, 14 Nov 2021 19:10:16 +0300")
Andrey Repin via Cygwin writes:
> You will have to format the stick to NTFS, and run rebaseall for each time you
> insert your stick into a new system, which defeats the very idea of having a
> "portable Cygwin" - it will always be tied to a specific system.
It all depends on what you want to do with it and wahtr limitations you
are able and willing to accept, but those dependencies are what makes it
hard to have that "portable Cygwin".
And no, you don't need to run rebaseall each time you use the stick on a
new system, but it may well not work at all for entirely different
reasons if you chose NTFS (and a host of other problems if you don't and
go with FAT32).
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
next prev parent reply other threads:[~2021-11-14 16:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1ab88470-74c9-49d7-3c42-281927dee218.ref@yahoo.ca>
2021-11-14 7:37 ` Peter Steiner
2021-11-14 10:32 ` Marco Atzeri
2021-11-14 11:15 ` Thomas Wolff
2021-11-14 11:40 ` Larry W. Virden
2021-11-14 16:10 ` Andrey Repin
2021-11-14 16:36 ` Achim Gratz [this message]
2021-11-14 22:29 ` Shaddy Baddah
2021-11-14 16:39 ` Christian Franke
2021-11-14 11:38 Fergus Daly
2021-11-14 12:40 ` Marco Atzeri
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=87czn28zj1.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).