From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Perry Hutchison" <perryh@pluto.rain.com>
Cc: <cygwin@cygwin.com>
Subject: RE: setup fails: "Can't open (null) for reading: No such file"
Date: Sat, 04 May 2002 01:24:00 -0000 [thread overview]
Message-ID: <FC169E059D1A0442A04C40F86D9BA7600C5FB8@itdomain003.itdomain.net.au> (raw)
Ok, to upgrade setup, download a new one from
http://www.cygwin.com/setup.exe.
> -----Original Message-----
> From: Perry Hutchison [mailto:perryh@pluto.rain.com]
> Sent: Saturday, May 04, 2002 6:00 PM
> > What options did you select when running setup?
>
> Install from Local Directory
> next screen unchanged (root C:\cygwin, all users, Unix files)
> next screen unchanged (local pkg dir C:\download\cygwin) Here
> it suggests upgrading setup, but doesn't provide a means to
> do so. Select to install the newly-downloaded packages. It
> started to install, then died.
>
> > Why did you run a two-step install?
>
> To have the install sets available for setting up other
> machines, or for reinstalling this one if (when!) Windoze gets hosed.
Are you aware that 'install from internet' also makes the install sets
available?
Rob
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2002-05-04 8:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-04 1:24 Robert Collins [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-07 0:51 Robert Collins
2002-05-04 23:35 Robert Collins
2002-05-04 22:14 Perry Hutchison
2002-05-04 15:27 Robert Collins
2002-05-04 14:37 Perry Hutchison
2002-05-04 18:33 ` Michael A Chase
2002-05-07 0:50 ` Matt Wilkie
2002-05-04 1:10 Perry Hutchison
2002-05-04 0:14 Robert Collins
2002-05-04 0:13 Perry Hutchison
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=FC169E059D1A0442A04C40F86D9BA7600C5FB8@itdomain003.itdomain.net.au \
--to=robert.collins@itdomain.com.au \
--cc=cygwin@cygwin.com \
--cc=perryh@pluto.rain.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).