This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Postinstall failure
- From: Igor Pechtchanski <pechtcha at cs dot nyu dot edu>
- To: Nebob <nbozovic1 at rogers dot com>
- Cc: cygwin at cygwin dot com
- Date: Wed, 27 Aug 2003 17:46:50 -0400 (EDT)
- Subject: Re: Postinstall failure
- References: <004d01c36ce0$734a0210$0201a8c0@seti>
- Reply-to: cygwin at cygwin dot com
On Wed, 27 Aug 2003, Nebob wrote:
> I searched don't hit me!
>
> The problem is that the postinstall scripts fail to execute properly and
> leave me with a non-functional cygwin installation. ie: clicking the cygwin
> shortcut leads to a "bash-2.05b$" prompt from which no commands work. System
> is XP SP1. setup.exe is 2.340.2.5.
>
> [snip]
>
> Linked is a 97.9KB rar archive containing setup.log, setup.log.full,
> cygcheck -svr and env.
>
> http://members.rogers.com/nbozovic1/diag.rar
>
> Here's some more information:
>
> bash-2.05b$ /bin/ls -ld /bin
> d--------- 3 Nebob ???????? 0 Aug 27 15:14 /bin
^^^^^^^^^^ ^^^^^^^^
These should ring a bell. See
<http://cygwin.com/cygwin-ug-net/ntsec.html#NTSEC-RELEASE1.3.20> for
details. There also seems to be some issue with mapping ACLs to
permissions -- please post the output of "/bin/getfacl /bin".
> bash-2.05b$ /bin/mount
> C:\cygwin\bin on /usr/bin type system (textmode)
> C:\cygwin\lib on /usr/lib type system (textmode)
> C:\cygwin on / type system (textmode)
> c: on /cygdrive/c type user (textmode,noumount)
> d: on /cygdrive/d type user (textmode,noumount)
No problems here.
> bash-2.05b$ type -a /bin/id
> /bin/id is /bin/id
>
> bash-2.05b$ /bin/ls -l /bin/id
> ---------- 1 Nebob ???????? 26112 Jan 7 2003 /bin/id
>
> Everything in /etc/postinstall has a .done extension.
>
> /home, /etc/passwd and /etc/group were not generated.
>
> I'd appreciate any and all assistance.
Apparently none of your executables have the execute permission -- most
likely because of some inherited permissions on a Windows directory. For
a short-term solution, try adding "nontsec" to your CYGWIN environment
variable and exiting all Cygwin processes. New processes started after
that should work, more or less. For a long-term solution, you might have
to do a recursive "chmod", once you figure out which permissions you need,
or fix up inherited ACLs on the c:\cygwin directory and reinstall Cygwin.
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha@cs.nyu.edu
ZZZzz /,`.-'`' -. ;-;;,_ igor@watson.ibm.com
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster." -- Patrick Naughton
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/