public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: anyone interested in loading a portable drive?
Date: Mon, 27 Jan 2020 21:25:00 -0000	[thread overview]
Message-ID: <1683b370-c96c-5253-5256-bd64fe4e0e20@SystematicSw.ab.ca> (raw)
In-Reply-To: <CANV9t=Sjhifp9mjy9HUwX_h0zM-gbiQ=B1f98JJQaK8YwOp=Xg@mail.gmail.com>

On 2020-01-27 09:17, Bill Stewart wrote:
> On Sun, Jan 26, 2020 at 9:33 PM aimedtech wrote:
> 
>> Okay, this is a complaint.  I've spent the past few days trying to
>> download the Cygwin system and gotten nowhere.  I've tried several
>> download environments, using different protocols, nothing works.
> 
> Remember that we can't see your screen.
> 
> When you say that something didn't work, you have to say how it didn't
> work. https://devblogs.microsoft.com/oldnewthing/20100421-00/?p=14283
> 
> First, try reading the error message.
> https://devblogs.microsoft.com/oldnewthing/20090625-00/?p=17753

You said your install is a decade old: rename any old /etc/passwd or /etc/group
files as those could cause problems nowadays if not regenerated, and you no
longer really need them, and should consult the User Guide for those uses.

Don't use user names, home, root, or package directory names with spaces, or C:\
as root directory: you should have full control over those directories, and run
setup with an admin id so it can run elevated.

Select only the packages you need to install, as all packages take 148GB, which
will take a while to download, as long to install, and a lot of virtual memory
to run (assuming you're installing a 64 bit system, and have a lot of paging
space; if not, it won't install and won't run, as installing a lot of packages
using a lot of DLLs may require more than 3-4GB address space).

You should stop and exit all Cygwin processes so none are running while you run
setup.

See https://cygwin.com/faq/faq.html#faq.setup.setup-fails

Most problems with setup are network problems: in case it's not network, attach
setup.log.full (possibly in /var/log/ or the directory from which you ran setup)
as a plain text attachment for diagnosis.

-- 
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

      reply	other threads:[~2020-01-27 21:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-27  4:33 aimedtech
2020-01-27  4:47 ` Marco Atzeri
2020-01-27  6:38 ` Brian Inglis
2020-01-27  6:46   ` john doe
2020-01-27 14:18     ` Brian Inglis
2020-01-27 16:17 ` Bill Stewart
2020-01-27 21:25   ` Brian Inglis [this message]

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=1683b370-c96c-5253-5256-bd64fe4e0e20@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).