Re: Small patch for the FAQ
At 10:37 PM 11/13/2003 +, David Starks-Browning wrote:
It will be *quite* some time before I am able to wade through the
main
cygwin list and discover things for the FAQ on my own. But I
should
be able to apply patches on a fairly regular and timely basis,
at
least for a while.
Thanks David.
I attach a patch to install.texinfo that covers
http://www.cygwin.com/ml/cygwin/2003-03/msg00447.html and
http://cygwin.com/ml/cygwin-patches/2003-q1/msg00315.html
but not (among others)
http://www.cygwin.com/ml/cygwin/2003-04/msg01416.html
Pierre
Index: install.texinfo
===
RCS file: /cvs/src/src/winsup/doc/install.texinfo,v
retrieving revision 1.45
diff -u -p -r1.45 install.texinfo
--- install.texinfo 10 Apr 2003 20:09:35 - 1.45
+++ install.texinfo 18 Nov 2003 03:35:33 -
@@ -40,6 +40,31 @@ from the rest of your Windows system dis
(In the past, there had been genuine bugs that would cause problems
for people who installed in C:\, but we believe those are gone now.)
[EMAIL PROTECTED] How are file permissions determined
+
+The directories and files created by setup inherit the default ACL of their
+parent directory. Thus in a fresh installation all permissions are initially
+determined by the ACL of the top directory (e.g. @samp{C:\} for an
+installation in @samp{C:\cygwin}).
+
+After running setup it is a good idea to verify the permissions with the
+Windows program ``cacls'', which shows the true ACL,
+or with ``ls -l /bin'', which shows the mapping of the ACL to Posix permissions.
+If you are not happy with what you see, set the permissions as you
+wish by using commands such as:
[EMAIL PROTECTED]
[EMAIL PROTECTED] ``cd /''
+
[EMAIL PROTECTED] ``chmod -R a+r .''
+
[EMAIL PROTECTED] ``chmod -R a+x bin usr/sbin usr/local/bin lib/gcc-lib usr/X11R6/bin''
[EMAIL PROTECTED] enumerate
+You can also change the group and the owner with ``chgrp -R'' and/or ``chown -R''.
+
+Note that programs executed by services (such as inetd or cron) must be executable
+by SYSTEM, which is in the ``Administrators'' and ``Everyone'' groups but not
+e.g. in ``Users'' nor in ``Authenticated Users''.
+
@subsection Can I use Cygwin Setup to update a B18, B19, B20, B20.1 or CD-ROM (1.0)
installation of Cygwin?
No, you must start from scratch with the new Cygwin Setup. The
@@ -198,14 +223,49 @@ character as a word delimiter. Under ce
possible to get around this with various shell quoting mechanisms, but
you are much better off if you can avoid the problem entirely.
-In particular, the environment variables @samp{USER} and @samp{HOME} are
-set for you in /etc/profile. By default these derive from your Windows
-logon name. You may edit this file and set them explicitly to something
-without spaces.
-
-(If you use the @samp{login} package or anything else that reads
-/etc/passwd, you may need to make corresponding changes there. See the
-README file for that package.)
+On Windows NT/2000/XP you have two choices:
[EMAIL PROTECTED]
+
[EMAIL PROTECTED] You can rename the user in the Windows User Manager GUI and then
+run mkpasswd.
+
[EMAIL PROTECTED] You can simply edit the /etc/passwd file and change the Cygwin user
name
+(first field). It's also a good idea to avoid spaces in the home directory.
+
[EMAIL PROTECTED] enumerate
+
+On Windows 95/98/ME you can create a new user and run mkpasswd,
+or you can delete the offending entry from /etc/passwd.
+Cygwin will then use the name in the default entry with uid 500.
+
[EMAIL PROTECTED] My @samp{HOME} environment variable is not what I want.
+
+When starting Cygwin from Windows, @samp{HOME} is determined as follows
+in order of decreasing priority:
+
[EMAIL PROTECTED]
+
[EMAIL PROTECTED] @samp{HOME} from the Windows environment, translated to POSIX form.
+
[EMAIL PROTECTED] The entry in /etc/passwd
+
[EMAIL PROTECTED] @samp{HOMEDRIVE} and @samp{HOMEPATH} from the Windows environment
+
[EMAIL PROTECTED] /
+
[EMAIL PROTECTED] enumerate
+
+When using Cygwin from the network (telnet, ssh,...), @samp{HOME} is set
+from /etc/passwd.
+
+If your @samp{HOME} is set to a value such as /cygdrive/c, it is likely
+that it was set in Windows. Start a DOS Command Window and type
+set HOME to verify if this is the case.
+
+Access to shared drives is often restricted when starting from the network,
+thus Domain users may wish to have a different @samp{HOME} in the
+Windows environment (on shared drive) than in /etc/passwd (on local drive).
+Note that ssh only considers /etc/passwd, disregarding @samp{HOME}.
@subsection How do I uninstall individual packages?
Small patch for the FAQ
On Friday 29 Aug 03, Elfyn McBratney writes: Index: how-programming.texinfo ... Index: how-resources.texinfo ... Index: what.texinfo ... Thank you for these Elfyn. Applied with just a few minor changes. Sorry for being so far behind. I'm trying to catch up now. If anyone has patches against winsup/doc/*.texinfo files for me, send them here (cygwin-patches) and I'll try to get to them at least once a week. It will be *quite* some time before I am able to wade through the main cygwin list and discover things for the FAQ on my own. But I should be able to apply patches on a fairly regular and timely basis, at least for a while. Thanks for your patience and understanding. Regards, David
Re: Small patch for the FAQ
When I started over as FAQ maintainer (sheesh -- *years* ago?) I was told that Changelog entries were not necessary for documentation, as long as the cvs commit messages were informative. (Perhaps this was only intended for the FAQ, and not the other documentation, I don't know.) Occasionally, someone will add a Changelog entry anyway. Hopefully this is out of habit, rather than to suggest a change in policy. I hope the policy hasn't changed, because I'm happy not maintaining a Changelog for the FAQ texinfo source, and I agree with the original opinion that it isn't necessary. Best wishes, David On Monday 1 Sep 03, Corinna Vinschen writes: Dig, dig, dig... hmm, I don't find the ChangeLog entry here... Corinna On Fri, Aug 29, 2003 at 01:18:14PM +0100, Elfyn McBratney wrote: Index: how-programming.texinfo ...
Re: Small patch for the FAQ
On Thu, Nov 13, 2003 at 10:46:51PM +, David Starks-Browning wrote: When I started over as FAQ maintainer (sheesh -- *years* ago?) I was told that Changelog entries were not necessary for documentation, as long as the cvs commit messages were informative. (Perhaps this was only intended for the FAQ, and not the other documentation, I don't know.) Occasionally, someone will add a Changelog entry anyway. Hopefully this is out of habit, rather than to suggest a change in policy. I hope the policy hasn't changed, because I'm happy not maintaining a Changelog for the FAQ texinfo source, and I agree with the original opinion that it isn't necessary. GNU policy changed at some point and now, apparently, it is common to include ChangeLog entries for documentation. However, I don't really care either way. If you don't want to add ChangeLog entries, that's fine with me. I'm just happy, as always, that you are performing this service for the cygwin community. cgf
Re: Small patch for the FAQ
Dig, dig, dig... hmm, I don't find the ChangeLog entry here...
Corinna
On Fri, Aug 29, 2003 at 01:18:14PM +0100, Elfyn McBratney wrote:
Index: how-programming.texinfo
===
RCS file: /cvs/src/src/winsup/doc/how-programming.texinfo,v
retrieving revision 1.25
diff -u -u -p -r1.25 how-programming.texinfo
--- how-programming.texinfo 13 Feb 2003 14:20:32 - 1.25
+++ how-programming.texinfo 29 Aug 2003 12:11:04 -
@@ -6,12 +6,15 @@ If you are willing to be a package maint
volunteers to prepare and maintain packages, because the priority of the
Cygwin Team is Cygwin itself.
-There will be a separate web page where all the details are documented,
-but this is not prepared yet. Meanwhile, pore through the cygwin-apps
-mailing archives (start at @file{http://cygwin.com/lists.html}), and
-subscribe. Charles Wilson posted a short recipe of what's involved,
-using texinfo as an example,
-at @file{http://cygwin.com/ml/cygwin-apps/2000-11/msg00055.html}. This
+There's a Cygwin Contributor's Guide on the project web page available
+here @file{http://cygwin.com/setup.html}, which details everything you'll
+need to know about being a package maintainer. If you need any extra
+help you can ask on cygwin-apps @emph{at} cygwin @emph{dot} com mailing
+list, or alternatively you can search the cygwin-apps archives
+(start at @file{http://http://cygwin.com/lists.html}), as your question
+may well have been asked before. Charles Wilson posted a short recipe
+of what's involved, using texinfo as an example, available at
[EMAIL PROTECTED]://cygwin.com/ml/cygwin-apps/2000-11/msg00055.html}. This
should give you an idea of what is required.
You should announce your intentions to the general cygwin list, in case
Index: how-resources.texinfo
===
RCS file: /cvs/src/src/winsup/doc/how-resources.texinfo,v
retrieving revision 1.7
diff -u -u -p -r1.7 how-resources.texinfo
--- how-resources.texinfo 21 Feb 2003 20:13:55 - 1.7
+++ how-resources.texinfo 29 Aug 2003 12:11:05 -
@@ -18,10 +18,6 @@ There is a comprehensive Cygwin User's G
and an API Reference at
@file{http://cygwin.com/cygwin-api/cygwin-api.html}.
-There is an interesting paper about Cygwin from the 1998 USENIX Windows
-NT Workshop Proceedings at
[EMAIL PROTECTED]://cygwin.com/usenix-98/cygwin.html}.
-
You can find documentation for the individual GNU tools at
@file{http://www.fsf.org/manual/}. (You should read GNU manuals from a
local mirror, check @file{http://www.fsf.org/server/list-mirrors.html}
Index: what.texinfo
===
RCS file: /cvs/src/src/winsup/doc/what.texinfo,v
retrieving revision 1.21
diff -u -u -p -r1.21 what.texinfo
--- what.texinfo 27 Jul 2002 23:05:45 - 1.21
+++ what.texinfo 29 Aug 2003 12:11:06 -
@@ -32,17 +32,16 @@ exhibit different limitations, on the va
@section Where can I get it?
-The main location for the Cygwin project is
[EMAIL PROTECTED]://cygwin.com/}. There you should find
-everything you need for Cygwin, including links for download and setup,
-a current list of ftp mirror sites, a User's Guide, an API Reference,
-mailing lists and archives, and additional ported software.
+The home page for the Cygwin project is @file{http://cygwin.com/}.
+There you should find everything you need for Cygwin, including links
+for download and setup, a current list of ftp mirror sites,
+a User's Guide, an API Reference, mailing lists and archives, and
+additional ported software.
You can find documentation for the individual GNU tools at
@file{http://www.fsf.org/manual/}. (You should read GNU manuals from a
local mirror. Check @file{http://www.fsf.org/server/list-mirrors.html}
for a list of them.)
-
@section Is it free software?
-- Elfyn
Index: how-programming.texinfo
===
RCS file: /cvs/src/src/winsup/doc/how-programming.texinfo,v
retrieving revision 1.25
diff -u -u -p -r1.25 how-programming.texinfo
--- how-programming.texinfo 13 Feb 2003 14:20:32 - 1.25
+++ how-programming.texinfo 29 Aug 2003 12:11:04 -
@@ -6,12 +6,15 @@ If you are willing to be a package maint
volunteers to prepare and maintain packages, because the priority of the
Cygwin Team is Cygwin itself.
-There will be a separate web page where all the details are documented,
-but this is not prepared yet. Meanwhile, pore through the cygwin-apps
-mailing archives (start at @file{http://cygwin.com/lists.html}), and
-subscribe. Charles Wilson posted a short recipe of what's involved,
-using texinfo as an example,
-at @file{http://cygwin.com/ml/cygwin-apps/2000-11/msg00055.html}. This
+There's a Cygwin Contributor's Guide on the project web page
