From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9509 invoked by alias); 30 Oct 2003 19:04:59 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 9502 invoked from network); 30 Oct 2003 19:04:58 -0000 Received: from unknown (HELO smtp14.fre.skanova.net) (195.67.227.31) by sources.redhat.com with SMTP; 30 Oct 2003 19:04:58 -0000 Received: from masonit (h187n1fls22o974.bredband.comhem.se [213.64.79.187]) by smtp14.fre.skanova.net (8.12.10/8.12.10) with SMTP id h9UJ4tud018050 for ; Thu, 30 Oct 2003 20:04:55 +0100 (CET) Message-ID: <00a901c39f19$406fbf90$bb4f40d5@masonit> From: "Oskar Enoksson" To: "Cygwin List" References: <6.0.0.22.0.20031029112342.03c24480@127.0.0.1> <009301c39efa$f3ca7450$bb4f40d5@masonit> <6.0.0.22.0.20031030113234.03c32110@127.0.0.1> Subject: Re: Q: cygwin setup problems Date: Thu, 30 Oct 2003 20:42:00 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-SW-Source: 2003-10/txt/msg01792.txt.bz2 > At 10:31 AM 10/30/2003, Oskar Enoksson you wrote: > >> At 11:07 AM 10/29/2003, enok@lysator.liu.se you wrote: > >>=20 > >> >When I run setup.exe to install new packages the process hangs when > >> >copying the files into the file system. The reason is that setup crea= tes > >> >all directories and files as write protected (dr--r--r--) and then fa= ils > >> >to fill the newly created directory with files (because of the write > >> >protection). > >> > > >> >What is the problem? > >> > > >> >My platform is Windows 2000 with NTFS file system. I use CYGWIN=3Dnts= ec. > >> >After installing the initial cygwin packages I noticed that all files > >> >had protection rwxrwxrwx. I changed that of course and now all files = are > >> >instead created r--r--r--. Why? Please help! > >>=20 > >>=20 > >> It's a Windows thing. By default, children of a parent automatically > >> inherit the permissions of the parent. You can change that of course = but=20 > >> your previous attempts at "fiddling" with the install tree didn't fare= =20 > >> very well so I wouldn't recommend you do more experimentation here (un= less > >> you plan to live with the consequences and/or find the solutions to th= e=20 > >> problems you cause). The two options that I think will work the best = for=20 > >> you is to simply change the permissions globally to add write and exec= ute=20 > >> permissions where appropriate or to simply remove your current=20 > >> installation and reinstall, making sure that the directory under which= =20 > >> you're installing Cygwin has reasonably open permissions. > > > >Thanks for responding. My problem is that even if I deleted the root cyg= win directory and let setup.exe reinstall everything, the file permissions = were still completely wrong (as shown by ls -l). > > > >However, today I tried to first create the root cygwin directory manuall= y (E:\cygwin) and then change the permissions in windows for that directory= to include "Everyone". After that it seems that setup.exe is able to insta= ll everything with correct permissions and all. > > > >But I'm still not sure what was the problem. What file permission settin= gs must be fulfilled for the parent directory of cygwin root? Is that menti= oned in the documentation somewhere? Why can't setup.exe fix those permissi= ons when creating the cygwin root directory? Could this be a bug in cygwin = setup.exe? >=20 >=20 > Default permissions are generally fine, unless they've been changed to be > very restrictive or the user installing doesn't have the appropriate=20 > permissions or groups. Adding "Everyone" to the parent directory permiss= ions > is arguably the easiest way to make sure everything works. This isn't a= =20 > bug, though it is an annoyance in cases where the defaults aren't=20 > appropriate. I'm sure a patch to setup to make these fringe cases work > more smoothly would be thoughtfully reviewed and considered. Thanks again for response and hints.=20 Many windows security gurus recommend removing "everyone" group access righ= ts on NTFS root directory and replacing it by "verified users" group to imp= rove security (that's what I had done). This caused problems with cygwin se= tup. Mystery solved. /Oskar -- 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/