public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Larry Hall <cygwin-lh@cygwin.com>
To: "Oskar Enoksson" <enok@lysator.liu.se>,
	"Cygwin List" <cygwin@cygwin.com>
Subject: Re: Q: cygwin setup problems
Date: Thu, 30 Oct 2003 17:11:00 -0000	[thread overview]
Message-ID: <6.0.0.22.0.20031030113234.03c32110@127.0.0.1> (raw)
In-Reply-To: <009301c39efa$f3ca7450$bb4f40d5@masonit>

At 10:31 AM 10/30/2003, Oskar Enoksson you wrote:
>> At 11:07 AM 10/29/2003, enok@lysator.liu.se you wrote:
>> 
>> >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 creates
>> >all directories and files as write protected (dr--r--r--) and then fails
>> >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=ntsec.
>> >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!
>> 
>> 
>> 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 
>> your previous attempts at "fiddling" with the install tree didn't fare 
>> very well so I wouldn't recommend you do more experimentation here (unless
>> you plan to live with the consequences and/or find the solutions to the 
>> problems you cause).  The two options that I think will work the best for 
>> you is to simply change the permissions globally to add write and execute 
>> permissions where appropriate or to simply remove your current 
>> installation and reinstall, making sure that the directory under which 
>> you're installing Cygwin has reasonably open permissions.
>
>Thanks for responding. My problem is that even if I deleted the root cygwin 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 manually (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 install everything with correct permissions and all.
>
>But I'm still not sure what was the problem. What file permission settings must be fulfilled for the parent directory of cygwin root? Is that mentioned in the documentation somewhere? Why can't setup.exe fix those permissions when creating the cygwin root directory? Could this be a bug in cygwin setup.exe?


Default permissions are generally fine, unless they've been changed to be
very restrictive or the user installing doesn't have the appropriate 
permissions or groups.  Adding "Everyone" to the parent directory permissions
is arguably the easiest way to make sure everything works.  This isn't a 
bug, though it is an annoyance in cases where the defaults aren't 
appropriate.  I'm sure a patch to setup to make these fringe cases work
more smoothly would be thoughtfully reviewed and considered.


--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


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

  reply	other threads:[~2003-10-30 16:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-29 17:02 enok
2003-10-29 18:22 ` Larry Hall
2003-10-30 16:34   ` Oskar Enoksson
2003-10-30 17:11     ` Larry Hall [this message]
2003-10-30 20:42       ` Oskar Enoksson

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=6.0.0.22.0.20031030113234.03c32110@127.0.0.1 \
    --to=cygwin-lh@cygwin.com \
    --cc=cygwin@cygwin.com \
    --cc=enok@lysator.liu.se \
    /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).