Message-ID: <4D2AE66F.2050500@bonhard.uklinux.net>
Date: Mon, 10 Jan 2011 10:58:56 +0000
From: Fergus <fergus AT bonhard DOT uklinux DOT net>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
To: Cygwin ML <cygwin AT cygwin DOT com>
CC: Fergus <fergus AT bonhard DOT uklinux DOT net>
Subject: Brand new setup ends up not where intended (?but at default)
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

I know you're probably not much interested in legacy difficulties (or 
maybe you are) but as setup.exe = setup-legacy.exe I thought I'd mention 
it.

The following glitch has occurred several times, and I'm reminded of 
other posts written post-installation of the "cannot find /home" "cannot 
find /bin/bash" variety. I have always assumed that I must have suffered 
some kind of lapsed-concentration self-induced keypress malfunction. 
This time (like most times actually) I took good care.

Intention: to install legacy version 1.5 on drive I: (ie not default) 
from sources stored under F:\Cyg0\release-legacy (ie not web).

Command: F:\Cyg0\setup-legacy.exe

Prompts (3 of them): 1. choose location I:\ for installation; 2. say 
"YES I do mean that" in response to warning; and 3. state F:\Cyg0 for 
source.

The installation process appeared to run satisfactorily to completion 
(but surprisingly rapidly - I:\ is a usb stick and writes are pretty 
slow) but in the end all that's on I:\ is

/i/:
   \─bin/:
   \─etc/:
   │   \─setup/:
   │       \─timestamp
   \─home/:
   \─lib/:
   \─tmp/:
   \─usr/:
   │   \─bin/:
   │   \─lib/:
   │   \─local/:
   │   │   \─bin/:
   │   │   \─etc/:
   │   │   \─lib/:
   │   \─src/:
   │   \─tmp/:
   \─var/:
       \─log/:
       │   \─setup.log
       │   \─setup.log.full
       \─run/:
       │   \─utmp
       \─tmp/:

and what has actually happened is that the installation has been placed 
under C:\cygwin\. Not really what I wanted. The 4 files mentioned above 
(timestamp, setup.log.*, utmp) do NOT occur anywhere under c:\cygwin.

I'll do a transfer or something and attend to mounts; but this has 
definitely happened more than once. Something I'm doing, or failing to 
do? Something your end that under certain circumstances causes the 
default architecture to override user-stated preferences?

I did NOT clean the registry. Things were properly uninstalled (ie I had 
umount'ed everything) but without doubt the registry will have had 
trailing vestigial references to Cygwin and Cygnus Solutions, though 
essentially empty. Could this be the problem?

Fergus


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