My PC has two instances of cygwin. My production is 1,7,1-1 while I'm
trying to get my 1.5 working again. For my 1.5, I have populated the
/c/_cygwinCD/etc/fstab with the following contents:
/c/_cygwinCD/etc.$ cat fstab
C:/_cygwinCD/bin on /usr/bin type ntfs (binary,auto)
C:/_cygwinCD/lib on /usr/lib type ntfs (binary,auto)
C:/_cygwinCD on / type ntfs (binary,auto)
A: on /a type unknown (binary)
C: on /c type ntfs (binary)
D: on /d type unknown (binary)
E: on /e type ntfs (binary)
F: on /f type ntfs (binary)
G: on /g type ntfs (binary)
H: on /h type ntfs (binary)
I: on /i type ntfs (binary)
J: on /j type ntfs (binary)
K: on /k type ntfs (binary)
However when I startup the 1.5 system, the root (/) is set inproperly.
A "cd /" fails. Some other particulars are:
PATH=\_cygwinCD\bin;C:\Program Files;... OK(DOS)
HOME=/home/Paul
cd /
ksh: cd: / - No such file or directory
ENV=/home/Paul/.bash_login
After reading the section on the "mount-point", I thought that shed some
light on the subject but apparently not. I also linked etc/fstab to
etc/fstab.d/Paul but that didn't help. Can someone identify anything I
missed in the mount-point section?
Another thought I'm uncertain about. When you use "mount -m" as part of
fstab construction, the mount command does not output the mounted
filesystems on drive C:
When I re-read the mount-point section again, I discovered that words
like "on" and "type" are not mentioned and should be omitted. Thus my
fstab looks like:
C:/_cygwinCD/bin /usr/bin ntfs (binary,auto)
C:/_cygwinCD/lib /usr/lib ntfs (binary,auto)
C:/_cygwinCD / ntfs (binary,auto,override)
A: /a unknown (binary)
C: /c ntfs (binary)
D: /d unknown (binary)
E: /e ntfs (binary)
F: /f ntfs (binary)
G: /g ntfs (binary)
H: /h ntfs (binary)
I: /i ntfs (binary)
J: /j ntfs (binary)
K: /k ntfs (binary)
Note: I know that 1.5 & 1.7 are mutually exclussive.
--
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
