From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: how to access and display apps that I've launched
Date: Tue, 25 Jul 2017 18:16:00 -0000 [thread overview]
Message-ID: <00ecf4fe-157d-531c-1f6c-af38aaf3a477@cornell.edu> (raw)
In-Reply-To: <1438727230.474852.1500993486132@mail.yahoo.com>
On 7/25/2017 10:38 AM, Ian Lambert via cygwin wrote:
> > I'm using 64 bit
> cygwin already. This is a difference from the OP (It was in
> my earlier post).
>
> Sorry, I
> missed that. Have you looked at the output of 'rebase
> -is'?
> Conflicts are marked with
> '*'. What about BLODA?
>
> = = =
>
> I had not. It may be worth mentioning I have not found rebase
> in the fine manual, even under cygwin utilities. I only find
> it mentioned in forum posts, and with 4 rebase* programs
> under /usr/bin, it's playing too much monte carlo games with
> the install to just try those.
> Obviously something is not right; here is output from "rebase -is":
>
> rebase: failed to open rebase database "/etc/rebase.db.x86_64":
> No such file or directory
Normally you don't ever need to think about rebasing on x86_64. The
perpetual postinstall script /etc/postinstall/0p_000_autorebase.dash
should handle everything without any manual intervention. You might try
running that script (and the rebaselst script that it calls) line by
line (preferably in a dash shell started directly from Windows, with no
other Cygwin processes running) to see if you can figure out what's
going wrong.
> "locate rebase.db" gives:
> /cygdrive/e/cygwin64-3/etc/rebase.db.x86_64
> so it was apparently there when running locate database updates
> yesterday at ~1130-1330 (Eastern US), before doing the
> "rebase-trigger full", shutdown/restart, setup.
>
> BLODA is certainly a possibility; Symantec Protection is on the job...
> It was playing well together before, but things do change.
Ken
--
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:[~2017-07-25 15:06 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1438727230.474852.1500993486132.ref@mail.yahoo.com>
2017-07-25 18:12 ` Ian Lambert via cygwin
2017-07-25 18:16 ` Ken Brown [this message]
2017-07-25 19:57 ` Achim Gratz
[not found] <1128827672.1514648.1501092281786.ref@mail.yahoo.com>
2017-07-27 16:01 ` Ian Lambert via cygwin
[not found] <1534921570.1524318.1501093009415.ref@mail.yahoo.com>
2017-07-27 14:49 ` Ian Lambert via cygwin
[not found] <685307372.1339085.1501078785472.ref@mail.yahoo.com>
2017-07-26 17:09 ` Ian Lambert via cygwin
2017-07-26 17:13 ` Ken Brown
2017-07-26 18:27 ` Brian Inglis
2017-07-27 2:38 ` Achim Gratz
[not found] <1036849022.821922.1501019281615.ref@mail.yahoo.com>
2017-07-26 9:50 ` Ian Lambert via cygwin
2017-07-26 10:28 ` Brian Inglis
[not found] <799230527.525007.1500998733401.ref@mail.yahoo.com>
2017-07-25 18:21 ` Ian Lambert via cygwin
2017-07-25 21:52 ` Achim Gratz
2017-07-26 6:49 ` Ken Brown
[not found] <1783227004.4348461.1500934105434.ref@mail.yahoo.com>
2017-07-24 22:49 ` Ian Lambert via cygwin
2017-07-25 0:03 ` mike
2017-07-25 4:27 ` Ken Brown
2017-07-25 4:55 ` Ian Lambert via cygwin
2017-07-25 15:06 ` Ken Brown
2017-07-25 5:21 ` Brian Inglis
2017-07-25 10:17 ` Brian Inglis
2017-07-25 11:57 ` Brian Inglis
2017-07-25 13:03 ` Brian Inglis
2017-07-25 14:13 ` Brian Inglis
2017-07-25 19:19 ` Achim Gratz
2017-07-26 8:16 ` Brian Inglis
2017-07-25 19:01 ` Achim Gratz
[not found] <472748733.4076472.1500916852092.ref@mail.yahoo.com>
2017-07-24 19:46 ` Ian Lambert via cygwin
[not found] <949225432.4024000.1500912514455.ref@mail.yahoo.com>
2017-07-24 18:07 ` Ian Lambert via cygwin
2017-07-24 20:22 ` Ken Brown
2017-07-23 14:25 mike
2017-07-23 17:39 ` Jack
2017-07-23 18:14 ` mike
2017-07-23 19:18 ` Brian Inglis
2017-07-23 19:46 ` mike
2017-07-24 17:31 ` Brian Inglis
2017-07-25 2:16 ` mike
2017-07-23 22:46 ` Ken Brown
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=00ecf4fe-157d-531c-1f6c-af38aaf3a477@cornell.edu \
--to=kbrown@cornell.edu \
--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).