public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Shaddy Baddah <helium@shaddybaddah.name>
To: cygwin@cygwin.com
Subject: case-sensitivity in cygwin problems and their patches
Date: Sun, 11 Apr 2010 14:52:00 -0000	[thread overview]
Message-ID: <4BC1E212.9020207@shaddybaddah.name> (raw)

[-- Attachment #1: Type: text/plain, Size: 1093 bytes --]

Hi,

As some may recall from a previous thread of mine, i turned on 
case-sensitivity in Windows + cygwin, as per:

http://cygwin.com/cygwin-ug-net/using-specialnames.html#pathnames-casesensitive

I encountered two issues, for which i have provided the attached patches:

1. I found that there were no links to hosts, network, etc.. in /etc. 
Looking through the log files and the base-files-mketc.sh script that is 
meant to create them, I found that the reason that these were not 
created was related to case-sensitivity against the system32 directory. 
In Windows 7 and Vista at least, this directory name is capitalised to 
System32. This means that the directory existence test fails on case 
sensitivity. The attached patch corrects this.

2. I also found that the ssh-host-config script will have a non-fatal 
error when it tries to create a temporary mount to the drivers/etc 
subdirectory under System32 because of the same case-sensitivity issues. 
The attached patch also corrects this using the same utilisation of 
cygpath -S to get the System32 path.

Hope that helps,
Shaddy



[-- Attachment #2: base-files-3.9-3-sys32dir-patch.diff --]
[-- Type: text/plain, Size: 532 bytes --]

diff -x '*~' -urN ./base-files-3.9-3.orig/base-files-mketc.sh ./base-files-3.9-3/base-files-mketc.sh
--- ./base-files-3.9-3.orig/base-files-mketc.sh	2010-04-11 14:09:42.044274900 +0000
+++ ./base-files-3.9-3/base-files-mketc.sh	2010-04-11 14:38:08.617885400 +0000
@@ -9,8 +9,8 @@
 FILES="hosts protocols services networks"
 
 OSNAME="`/bin/uname -s`"
-WINHOME="`/bin/cygpath -w -W`"
-WINETC="$WINHOME\\system32\\drivers\\etc"
+WINSYS32HOME="`/bin/cygpath -S -w`"
+WINETC="$WINSYS32HOME\\drivers\\etc"
 
 if [ ! -d "$WINETC" ]
 then

[-- Attachment #3: openssh-5.4p1-1-sys32dir-patch.diff --]
[-- Type: text/plain, Size: 530 bytes --]

diff -x '*~' -urN ./openssh-5.4p1-1.orig/ssh-host-config ./openssh-5.4p1-1/ssh-host-config
--- ./openssh-5.4p1-1.orig/ssh-host-config	2010-04-11 13:47:56.576606400 +0000
+++ ./openssh-5.4p1-1/ssh-host-config	2010-04-11 13:51:10.300686800 +0000
@@ -78,7 +78,7 @@
 
   if csih_is_nt
   then
-    _win_etcdir="${SYSTEMROOT}\\system32\\drivers\\etc"
+    _win_etcdir="$(cygpath -S -w)\\drivers\\etc"
     _services="${_my_etcdir}/services"
     # On NT, 27 spaces, no space after the hash
     _spaces="                           #"


[-- Attachment #4: Type: text/plain, Size: 218 bytes --]

--
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:[~2010-04-11 14:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-11 14:52 Shaddy Baddah [this message]
2010-04-11 15:05 ` Corinna Vinschen

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=4BC1E212.9020207@shaddybaddah.name \
    --to=helium@shaddybaddah.name \
    --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).