This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Is 1.7 ready?/Installation Issues


Hi Folks,

I got the latest libstdc and have 1.7 now running on my work system thanks to your advice - it was invaluable. Thanks guys.

I'd like to bring the conversation back to why base-files-mketc.sh / base-files-profile.sh had the wrong permissions to start with. Are they being installed with the wrong permissions or is something running bash -c to execute the post install procedure when it should be omitting the -c as Ken suggested in the manual procedure?

Just want to check in case there is a lingering problem under the covers since I did do the install numerous times and got the same behaviour...

Cheers
Dave





Dave & Diane wrote:

Thanks for the speedy reply Chuck - I'm game!

I did as you suggest and it sped along to some degree but of course a lot of tools weren't in the path, so I had to add /usr/bin in to the path before running the for loop....

Interestingly when I did, I got:

/bin/bash: /etc/postinstall/base-files-mketc.sh: Permission denied
/bin/bash: /etc/postinstall/ : Permission denied

Looking at these I see the exe bit isn't set:

$ ls -l base-files-mketc.sh
-rw-r--r-- 1 Dave Trollope 4294967295 665 2009-12-06 04:33 base-files-mketc.sh
$ ls -l base-files-profile.sh
-rw-r--r-- 1 Dave Trollope 4294967295 530 2009-12-06 04:33 base-files-profile.sh


Other .sh files have the exe bit set... Is there a problem with the permissions on the packages being downloaded?

$ ls -l
total 33
-rwxr-xr-x 1 Dave Trollope 4294967295 6154 2009-05-14 05:28 000-cygwin-post-inst
all.sh.done
-rw-r--r-- 1 Dave Trollope 4294967295 665 2009-12-06 04:33 base-files-mketc.sh
-rw-r--r-- 1 Dave Trollope 4294967295 530 2009-12-06 04:33 base-files-profile.sh
-rwxr-xr-x 1 Dave Trollope 4294967295 1063 2009-07-01 20:20 bash.sh.done
-rwxr-xr-x 1 Dave Trollope 4294967295 518 2008-12-17 16:16 coreutils.sh.done
-rwxr-xr-x 1 Dave Trollope 4294967295 406 2009-10-14 18:19 font-adobe-dpi75.sh.done
-rwxr-xr-x 1 Dave Trollope 4294967295 1645 2009-10-14 18:22 font-alias.sh.done
-rwxr-xr-x 1 Dave Trollope 4294967295 399 2009-10-14 19:06 font-misc-misc.sh.done
-rwxr-xr-x 1 Dave Trollope 4294967295 52 2009-09-24 21:30 fontconfig.sh.done
-rwxr-xr-x 1 Dave Trollope 4294967295 461 2007-04-06 07:13 man.sh.done
-rwxr-xr-x 1 Dave Trollope 4294967295 805 2009-05-11 06:24 passwd-grp.sh.done
-rwxr-xr-x 1 Dave Trollope 4294967295 527 2009-11-30 21:48 terminfo.sh.done
-rwxr-xr-x 1 Dave Trollope 4294967295 236 2009-11-26 10:04 terminfo0.sh.done
-rwxr-xr-x 1 Dave Trollope 4294967295 415 2008-08-10 10:34 update-info-dir.sh.done


After fixing those permissions and rerunning them things look good. I started a cygwin command shell with bash and it detected it was the first install and copied the users default settings/profile etc as I would expect. I'm still suspicous that packages already marked "done" didn't really complete cleanly so I'll check that out tomorrow but I suspect there is something in the bash package with the wrong permissions or the mketc/profile.sh post install scripts don't for some reason get their permissions changed.

Thanks for the help - and I hope this helps you ( or Corinna ;-) ) find something that needs before going live with 1.7. I'll let you know if I find anything else odd tomorrow as I proceed further with getting it set up to take over from 1.5

Cheers
Dave


Charles Wilson wrote:


Dave & Diane wrote:



I appreciate that I'm not giving you a lot to go on here, but my gut
tells me there are some serious gremlins in the guts and in the
installation still, it certainly prevents me from moving my 1.5 system
to 1.7 at work and I'm worried that if 1.7 is released you'll be
overwhelmed with support requests that are eerily similar. This is why I
ask if 1.7 is ready for prime time. Perhaps I'm just being unlucky, and
thats ok.


I'm assuming you've checked for BLODAs, and that you have no known or
suspected BLODAs running.  In that case...

My gut says that the postinstall scripts are encountering the dreaded
"*** unable to remap" error, which (a) takes a few seconds before cygwin
gives up and reports it (to setup; you won't see the error message), and
(b) leaves a zombie process running around. If this occurs every time
setup tries to run a postinstall script, and there are 40-50 such
scripts in a typical 'virgin' installation, then...pain.

My suggestion is: if everything has actually been downloaded and
installed, and only the postinstall scripts are causing problems, then
kill setup, and manually:

launch cmd
cd C:\cygwin-1.7\bin
ash
rebaseall -v
for f in /etc/postinstall/*.sh ; do
 /bin/bash -c $f && mv $f $f.done
done

But...take all that with a grain of salt.  It's just my gut feeling with
very little evidence to back it up.

--
Chuck

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








--

Diane & Dave
http://www.velvetstarbears.com/  http://www.kringlecottage.com/
Fortune: The difference between America and England is that the
English think 100 miles is a long distance and the Americans
think 100 years is a long time.



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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]