public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Warren Young <wyml@etr-usa.com>
To: cygwin@cygwin.com, Rainer.Woitok@Gmail.Com
Subject: Re: How to correctly rebase?
Date: Mon, 19 Oct 2015 23:59:00 -0000	[thread overview]
Message-ID: <BBA147EC-B740-44BC-963C-DCFFDBC218A8@etr-usa.com> (raw)
In-Reply-To: <22051.32540.675000.621396@woitok.gmail.com>

On Oct 18, 2015, at 5:14 AM, Dr Rainer Woitok wrote:
> 
>>> Or switch to 64-bit Cygwin?
> 
> what does 64 bit Cygwin require?   Only any Windows on a 64 bit
> hardware or a 64 bit Windows on a 64  bit hardware?   I suspect it's the
> latter …

You are correct: 64-bit Cygwin requires 64-bit Windows.

(But 32-bit Cygwin will still run on 64-bit Windows, which is why we don’t ask if you’re running 64-bit Windows.)

As for your driver problems, have you checked whether newer versions of 64-bit Windows include the necessary drivers?

While it may be true that your hardware requires third-party 32-bit only drivers under Vista, it may also be the case that later version of Windows have native support for that hardware, so Microsoft has ported the driver to 64-bit.

Vista has been out of primary support for 3.5 years now.  It’s long past time to upgrade anyway.

If upgrading the OS simply is not an option, you might at least refresh your current Cygwin installation:

1. Stop all Cygwin processes

2. Rename c:\cygwin to something else

3. With an Explorer window showing the contents of c:\old-cygwin\bin, reinstall Cygwin to c:\cygwin, adding only the packages you know you need right now.

4. After starting the new Cygwin instance, copy over /cygdrive/c/cygwin/home/Chef and whatever else is unique about c:\old-cygwin.

If nothing else, this would have gotten you back into action a lot faster than the 7 days you’ve been fighting with your current installation.

> I've appended the output below

I’ll echo Ken: you were asked to *attach* the output to the message, not paste it in at the end.  In addition to not reducing the SNR of search results, attachments make it easier to read your message, since most readers won’t want to scroll past pages and pages of details about your system.

> Service             : cron                
> Display name        : Cron daemon
> Current State       : Running

Someone else caught this, but I’ll repeat it: Until the Cygwin cron service is stopped, Cygwin is still running, so a rebaseall will not be as effective as it should be.

> Service             : cygserver           
> Display name        : CYGWIN cygserver
> Current State       : Running

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

  parent reply	other threads:[~2015-10-19 23:59 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 14:26 Dr Rainer Woitok
2015-10-14 17:27 ` Warren Young
2015-10-14 19:27   ` Achim Gratz
2015-10-14 21:30     ` Warren Young
2015-10-14 22:08       ` Warren Young
2015-10-14 22:37         ` Warren Young
2015-10-15  7:53           ` Achim Gratz
2015-10-15  7:15       ` Achim Gratz
2015-10-15 13:16   ` Dr Rainer Woitok
2015-10-15 20:54     ` Warren Young
2015-10-15 21:10       ` Ken Brown
2015-10-16 12:57         ` Dr Rainer Woitok
2015-10-16 12:58           ` Ken Brown
2015-10-16 15:08             ` Ken Brown
2015-10-16 15:16               ` cyg Simple
2015-10-16 15:29                 ` Ken Brown
2015-10-16 15:50               ` Andrey Repin
2015-10-18 11:15               ` Dr Rainer Woitok
2015-10-18 11:59                 ` Achim Gratz
2015-10-18 12:45                 ` Ken Brown
2015-10-18 16:20                 ` Dr Rainer Woitok
2015-10-19 23:59                 ` Warren Young [this message]
2015-10-20 16:55                   ` Dr Rainer Woitok
2015-10-16  7:21       ` Achim Gratz
2015-10-16 20:11         ` Warren Young
2015-12-18 16:28           ` Achim Gratz
2015-10-14 19:58 ` Achim Gratz

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=BBA147EC-B740-44BC-963C-DCFFDBC218A8@etr-usa.com \
    --to=wyml@etr-usa.com \
    --cc=Rainer.Woitok@Gmail.Com \
    --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).