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: setup.exe to have Install button
Date: Thu, 08 Sep 2016 16:38:00 -0000	[thread overview]
Message-ID: <aa8c60fa-d125-c982-fdfb-55d7568946b4@SystematicSw.ab.ca> (raw)
In-Reply-To: <a8224511-f084-7838-d8ba-a9528c1136f1@SystematicSw.ab.ca>

On 2016-09-08 08:47, Brian Inglis wrote:
> On 2016-09-08 06:59, Nellis, Kenneth wrote:
>> Just in case anyone's collecting change requests
>> against Setup.exe, here's a simple one that I'd
>> like to see:
>>
>> All screens until the final screen display a "Next>"
>> button. Typically, after launching, I just click
>> this button until I get to the list of packages to
>> review, but this screen also has a "Next>" button.
>> Clicking it installs the packages.
>>
>> My request is for the button on this screen to be
>> changed to "Install", to better convey to the user
>> that we are have completed the question-answer
>> screens and are at the final screen before the
>> actual installation.
>
> I would request just a little more for the Install view:
> after making selections and clicking Next button,
> change to Pending view with all selected packages displayed.
>
> Could this also show required new or upgraded dependent packages?

Also just checking setup.log, I noticed it had ballooned to 55MB:
I found that recent setup_x86_64 releases appear to be spinning
on file replacement, trying thousands of times a minute to replace
a file before giving up!

Could this be replaced by exponential backoff sleeps of say 1, 2,
4, 8, 16, 32s, before either: asking the user whether to continue,
or setting up reboot replacement of the file, and warning the user.

If the Search Indexer is examining a file, or it is in use in a
Scheduled Task, giving the other task quiet time to finish seems
more likely to eliminate contention than loading the system with
failed accesses.

Having removed the hundreds of thousands of repeated lines:
"io_stream_cygfile: fopen(/usr/bin/...) failed 13 Permission denied
Failed to open cygfile:///usr/bin/... for writing.
Not replacing in-use file cygfile:///usr/bin/..."
setup.log is back to a reasonable 1.5MB since I first installed
cygwin643 years ago.

Checking cygwin32 setup.log I am glad to see it has only reached
a meagre .5MB since its last reinstall 4 years ago, with annual
updates or a bit more frequent when building or checking cygports.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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:[~2016-09-08 16:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-08 12:59 Nellis, Kenneth
2016-09-08 14:47 ` Brian Inglis
2016-09-08 16:38   ` Brian Inglis [this message]
2016-09-09  0:44 ` Shaddy Baddah

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=aa8c60fa-d125-c982-fdfb-55d7568946b4@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).