Re: [patch] cygport-0.2.7 bugfix for apply_patch

2007-01-07 Thread Yaakov (Cygwin Ports)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Charles Wilson wrote:
> The recent change in apply_patch has a small bug, fixed by the attached.
> 
> 2006-01-05  Charles Wilson  <...>
> 
> * bin/cygport.in (apply_patch): use correct variable name

Thanks.  Fixed in CVS.


Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFoKn3piWmPGlmQSMRCNRsAJ9w/73LSSb6Sq1nDNlvqYxc2KaHigCfd056
ektw4TT0yG6gImVL7nVwl0s=
=TCe5
-END PGP SIGNATURE-

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



Re: [patch] cygport-0.2.7 autoconf-2.61/automake-1.10 support

2007-01-07 Thread Yaakov (Cygwin Ports)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Charles Wilson wrote:
> * bin/cygport.in: use --datarootdir in preference
> to --datadir/--infodir/--mandir when using
> autoconf-2.60 and later.

Thanks.  Fixed in CVS.

> * autogen.sh: Ensure that autoconf will not complain
> when it is newer than the one previously used (needed
> because automake-1.10's aclocal now inserts more stringent
> checking into aclocal.m4)

Investigating further, I got this error while running autogen.sh in the
CVS tree but not with autoreconf in the -src tarball.  The former after
'aclocal --force' still showed dep on ac-2.60, where the latter showed
ac-2.61.

I finally figured out that the difference was caused solely by
autom4te.cache; removing that allowed autogen.sh to proceed.  Therefore
I have added a 'rm -fr autom4te.cache' to autogen.sh in CVS, and no more.


Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFoLVvpiWmPGlmQSMRCP/JAJ9WWw/rVT+vaul9x6I+iW+nkBSgwwCfSO/v
puSpuYw/9G54ABMgw730KNc=
=Bd2+
-END PGP SIGNATURE-

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



Re: cygport patch: Add PATCHOPTS

2007-01-07 Thread Yaakov (Cygwin Ports)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Christian Franke wrote:
> The attached patch adds the ability to pass patch options to cygport
> prep command.
> 
> Example: Set original timestamps from patch file (like g-b-s does):
> 
> PATCHOPTS+="-Z"

The original purpose of the -Z was to allow patching the autotool files
directly with the g-b-s, see
http://cygwin.com/ml/cygwin-apps/2004-02/msg00286.html and thread for
details.

This is not necessary with cygport because the autotools are always
regenerated, and not changes in the generated files are not included in
the patch.

Did you find this particularly necessary somehow, and why?


Yaakov
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.5 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFoLsHpiWmPGlmQSMRCHJUAJ4y22wnyibUEXDC23KEXr7IaDSP6wCg6wfm
BH40doNfOf/g7vw6lMuedZo=
=MM1w
-END PGP SIGNATURE-

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



Re: 1.7.0 CVS mmap failure

2007-01-07 Thread Corinna Vinschen
On Jan  5 15:15, Brian Ford wrote:
> On Fri, 5 Jan 2007, Corinna Vinschen wrote:
> 
> > "overmap"?  -v please?
> 
> Posix symantics: mmap fixed region x, mmap fixed region y which is a
> subregion of x where y replaces x's mapping.

AFAIK that doesn't work on Windows.  But, somebody has to test it(tm).
This would be exactly the situation in which we could utilize the
AT_EXTENDABLE_FILE flag, if it only would work with MAP_PRIVATE :(
http://www.cygwin.com/ml/cygwin-developers/2004-03/msg00033.html


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

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



Re: 1.7.0 CVS mmap failure

2007-01-07 Thread Corinna Vinschen
On Jan  6 07:45, Christopher Layne wrote:
> (warning a bunch of strace, scroll wide).
> 
> So I haven't been able to totally nail anything down on this issue due
> to the incredible complexity of Cygwin's mmap interface.

Lots of comments throughout the file...

> This is 2 simple mmap()s in succession, 1st is 46121 bytes, 2nd is 111 bytes.
> Both opened read/write. The second mmap always fails. This is the current
> snapshot code.
> 
> In the 2nd strace, I changed the mmap logic to stop trying to align the 1st
> map on a 4k granularity boundary and just allocate a single map w/ 64k of
> left over dead space (what I would typically expect in posix land). I also
> added more debug info at various stages to try and figure things out. When
> changing it to use 64k period, the mmaps are both successful - which is good,
> but VirtualProtect always fails, no matter what, on unmap.

The strace is rather useless without the (hopefully very short) source
code of the (hopefully very small) testcase.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

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



Re: `setfacl -m u:jdoe:rwx foo` returns 0, but file not writable by jdoe??

2007-01-07 Thread Corinna Vinschen
On Jan  5 13:34, Tom Rodman wrote:
> Admittedly, this may be going "outside the cygwin perms model" a bit:
> 
> In the below test case file 'foo' has it's RO file attribute set, then has
> it's owner changed to someone other than the current user, has the posix
> group set to None, the DACL protected, and all aces removed from the DACL.
> 
> Next step is to run this (assumes we are user 'jdoe' [an administrator]):
> 
>   setfacl -m u:jdoe:rwx foo
> 
> Above command returns 0 but jdoe can not write.  The cause appears to
> be that the windows RO file attribute is not unset by setfacl.

I see the point.  That old DOS R/O attribute is SO crappy on a file
system which supports real permissions.  Oh well...


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

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



[Packaging Bug ?] Re: [ANNOUNCEMENT] Updated: git-1.4.4.3-1

2007-01-07 Thread Dr. Volker Zell
> Eric Blake writes:

> A new release of git, 1.4.4.3-1, has been uploaded, replacing 1.4.4.1-3 as
> the current version.

This is the contents of 
/usr/lib/perl5/vendor_perl/5.8/cygwin/auto/Git/.packlist:

/usr/lib/perl5/vendor_perl/5.8/Git.pm
/usr/lib/perl5/vendor_perl/5.8/Error.pm
/usr/lib/perl5/vendor_perl/5.8/Git.pm

but the /usr/lib/perl5/vendor_perl/5.8/Error.pm is missing.
It used to be there in the previous version. Is this a packaging bug ?

Ciao
  Volker


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



Re: can't start sshd

2007-01-07 Thread Thorsten Kampe
* Charles D. Russell (Sat, 06 Jan 2007 13:08:21 -0600)
> After a clean reinstall of cygwin from the web and copying my old HOME 
> directory to the new installation, I can no longer start sshd.  Messages 
> are as follows:
> 
> $ net start sshd
> The CYGWIN sshd service is starting.
> The CYGWIN sshd service could not be started.
> 
> The service did not report an error.
> 
> More help is available by typing NET HELPMSG 3534.
> 
> $ cygrunsrv -S sshd
> cygrunsrv: Error starting a service: QueryServiceStatus:  Win32 error 1062:
> The service has not been started.

Check the event log and /var/log/ssh*


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



Complete Vi documentation?

2007-01-07 Thread Steven Buroff
Where can I find the complete vi(m) documentation? The man page
has practically nothing. It doesn't describe the editing commands 
or the ":set" options, only the command line options. Doing a 
"set all?" lists the options but I really need a description of 
each one. Thanks.

Steve


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



Re: Complete Vi documentation?

2007-01-07 Thread zzapper
Steven Buroff <[EMAIL PROTECTED]> wrote in news:003b01c73276$6f116850
[EMAIL PROTECTED]:

> Where can I find the complete vi(m) documentation? The man page
> has practically nothing. It doesn't describe the editing commands 
> or the ":set" options, only the command line options. Doing a 
> "set all?" lists the options but I really need a description of 
> each one. Thanks.
> 
> Steve
> 

http://vimdoc.sourceforge.net

or from within vim

:help set



-- 
zzapper
http://successtheory.com/tips/ Vim, Zsh, MySQL Tips


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



Re: Complete Vi documentation?

2007-01-07 Thread zzapper
zzapper <[EMAIL PROTECTED]> wrote in news:Xns98B1B75E41678zzappergmailcom@
80.91.229.5:

> Steven Buroff <[EMAIL PROTECTED]> wrote in news:003b01c73276$6f116850
> [EMAIL PROTECTED]:
> 
>> Where can I find the complete vi(m) documentation? The man page
>> has practically nothing. It doesn't describe the editing commands 
>> or the ":set" options, only the command line options. Doing a 
>> "set all?" lists the options but I really need a description of 
>> each one. Thanks.
>> 
>> Steve
>> 
> 
> http://vimdoc.sourceforge.net
> 
> or from within vim
> 
>:help set
or better
:help option-list

find a specific option
:helpgrep ignorecase
:helpgrep set.*ignorecase





-- 
zzapper
http://successtheory.com/tips/ Vim, Zsh, MySQL Tips


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



Exclude cygwin folder from malware scans?

2007-01-07 Thread Fred Ma

After some surfing, I haven't found any evidence of malware targetting
cygwin.  I'm considering excluding the massive file tree from scans
(AV, SpyBot, AdAware).  I'd be interested in more experienced opinions
about this.  Thanks.

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



Re: having problems with getting Up and Runnign

2007-01-07 Thread Morgan Gangwere

Thanks! i deleted all registry entrys and the cygwin dir. i suspect that
how cygwin handles all the locations of things (such as where the
binaries live) and how all that runs
i also found that bash and such have an issue with mulit-word usernames
windows allows these but Pine and Mutt fail because they are made for
/home/username/mail/ but i used /home/user name/mail (username was Sys
Admin)
bash would show "[Sys [EMAIL PROTECTED]" but GNUStep would try to
write to /home/sys/GNUStep/ not /home/Sys Admin/GNUStep/
should we fix this in a future version? make the username all one word
(or use "_" in place - this makes it simpler)?

thanks,
Morgan Gangwere

On 1/6/07, Larry Hall (Cygwin) <[EMAIL PROTECTED]> wrote:

Morgan Gangwere wrote:
> all:
> i have been using cygwin for some time now and found a problem.
> i installed irssi with cygwin static and have now decided to run real
> cygwin.
> here is hte proccess i went through:
> 1. install irssi
> 2. use irssi
> 3. decide I want real cygwin
> 4. download and Install cygwin (setting the install path to C:\cygwin\
> and the temp to C:\cygtemp\ )
> 4. uninstall irssi
> 5. attempt to use cygwin
>
> FAILIURE MODE:
> when I run Cygwin.bat i get the following:
> "Bash: Bash - command not found"
> aparrently, from what i have seen is that bash runs itself in order to
> check variables and to run ~/.bashrc
> this is a problem apparently related to the process that i used
> how do i fix this?

You're best bet?  

A WAG is that you should re-run "setup.exe" and choose "Reinstall" for all.
If you choose to try my WAG before consulting
, please consult it if my WAG doesn't work
out for you.

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

_

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

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





--
Morgan gangwere

"Space does not reflect society, it expresses it." -- Castells, M.,
Space of Flows, Space of Places: Materials for a Theory of Urbanism in
the Information Age, in The Cybercities Reader, S. Graham, Editor.
2004, Routledge: London. p. 82-93.

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



Re: Complete Vi documentation?

2007-01-07 Thread Tim Prince

[EMAIL PROTECTED] wrote:

Where can I find the complete vi(m) documentation? The man page
has practically nothing. It doesn't describe the editing commands 
or the ":set" options, only the command line options. Doing a 
"set all?" lists the options but I really need a description of 
each one. Thanks.



If :help isn't sufficient, why not check www.vim.org ?

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



Re: `setfacl -m u:jdoe:rwx foo` returns 0, but file not writable by jdoe??

2007-01-07 Thread Tom Rodman
On Sun 1/7/07 12:23 +0100 cygwin@cygwin.com wrote:
> On Jan  5 13:34, Tom Rodman wrote:
> > Admittedly, this may be going "outside the cygwin perms model" a bit:
> > 
> > In the below test case file 'foo' has it's RO file attribute set, then has
> > it's owner changed to someone other than the current user, has the posix
> > group set to None, the DACL protected, and all aces removed from the DACL.
> > 
> > Next step is to run this (assumes we are user 'jdoe' [an administrator]):
> > 
> >   setfacl -m u:jdoe:rwx foo
> > 
> > Above command returns 0 but jdoe can not write.  The cause appears to
> > be that the windows RO file attribute is not unset by setfacl.
> 
> I see the point.  That old DOS R/O attribute is SO crappy on a file
> system which supports real permissions.  Oh well...

theory - these 2 steps will make *any* windows NTFS file,
no matter what it's owner, group,  perms, or file attributes are,
writable by user "jdoe" (assuming it's not "in use"):

  setfacl -m u:jdoe:rwx foo 
# running as administrator "jdoe"
  cmd /c attrib -R foo 
# setacl step above allows the 'attrib' to work for user "jdoe"

I appreciate the power in setfacl. :->

--
Tom

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



Re: Two short scripts for Cygwin-Windows interoperation

2007-01-07 Thread Christian Franke

Corinna Vinschen wrote:

On Jan  4 23:39, Christian Franke wrote:
  

...
Thanks for any comment



http://cygwin.com/acronyms/#PTC
http://cygwin.com/acronyms/#SHTDI

Come on, what did you expect? ;)

  


Hmm...at least some info whether such a patch would be accepted.
(I don't want to do patches which need many iterations or end up in 
/dev/null ;-)


See attached patch.
I missed that -M is already used and replaced it with -O (dOcuments).

2007-01-07Christian Franke <[EMAIL PROTECTED]>

   * cygpath.cc (usage): Add -O and -F, remove tabs.
   (get_special_folder): New function.
   (get_user_folder): New function.
   (dowin): Add -O and -F, better -D, -P error handling.
   (main): Add -O and -F.
   * utils.sgml (cygpath): Document -O and -F.

Christian

diff -urp cygwin-1.5.23-2.orig/winsup/utils/cygpath.cc 
cygwin-1.5.23-2/winsup/utils/cygpath.cc
--- cygwin-1.5.23-2.orig/winsup/utils/cygpath.cc2006-02-17 
13:17:47.00100 +0100
+++ cygwin-1.5.23-2/winsup/utils/cygpath.cc 2007-01-07 20:27:10.890625000 
+0100
@@ -25,7 +25,7 @@ details. */
 static const char version[] = "$Revision: 1.42 $";
 
 static char *prog_name;
-static char *file_arg;
+static char *file_arg, *output_arg;
 static int path_flag, unix_flag, windows_flag, absolute_flag;
 static int shortname_flag, longname_flag;
 static int ignore_flag, allusers_flag, output_flag;
@@ -52,13 +52,15 @@ static struct option long_options[] = {
   {(char *) "allusers", no_argument, NULL, 'A'},
   {(char *) "desktop", no_argument, NULL, 'D'},
   {(char *) "homeroot", no_argument, NULL, 'H'},
+  {(char *) "mydocs", no_argument, NULL, 'O'},
   {(char *) "smprograms", no_argument, NULL, 'P'},
   {(char *) "sysdir", no_argument, NULL, 'S'},
   {(char *) "windir", no_argument, NULL, 'W'},
+  {(char *) "folder", required_argument, NULL, 'F'},
   {0, no_argument, 0, 0}
 };
 
-static char options[] = "ac:df:hilmMopst:uvwADHPSW";
+static char options[] = "ac:df:hilmMopst:uvwADHOPSWF:";
 
 static void
 usage (FILE * stream, int status)
@@ -67,29 +69,32 @@ usage (FILE * stream, int status)
 fprintf (stream, "\
 Usage: %s (-d|-m|-u|-w|-t TYPE) [-f FILE] [OPTION]... NAME...\n\
%s [-c HANDLE] \n\
-   %s [-ADHPSW] \n\
+   %s [-ADHOPSW] \n\
+   %s [-F ID] \n\
 Convert Unix and Windows format paths, or output system path information\n\
 \n\
 Output type options:\n\
-  -d, --dosprint DOS (short) form of NAMEs (C:\\PROGRA~1\\)\n\
+  -d, --dos print DOS (short) form of NAMEs (C:\\PROGRA~1\\)\n\
   -m, --mixed   like --windows, but with regular slashes (C:/WINNT)\n\
-  -M, --mode   report on mode of file (binmode or textmode)\n\
-  -u, --unix   (default) print Unix form of NAMEs 
(/cygdrive/c/winnt)\n\
+  -M, --modereport on mode of file (binmode or textmode)\n\
+  -u, --unix(default) print Unix form of NAMEs 
(/cygdrive/c/winnt)\n\
   -w, --windows print Windows form of NAMEs (C:\\WINNT)\n\
   -t, --type TYPE   print TYPE form: 'dos', 'mixed', 'unix', or 
'windows'\n\
 Path conversion options:\n\
   -a, --absoluteoutput absolute path\n\
-  -l, --long-name  print Windows long form of NAMEs (with -w, -m only)\n\
-  -p, --path   NAME is a PATH list (i.e., '/bin:/usr/bin')\n\
-  -s, --short-name print DOS (short) form of NAMEs (with -w, -m only)\n\
+  -l, --long-name   print Windows long form of NAMEs (with -w, -m only)\n\
+  -p, --pathNAME is a PATH list (i.e., '/bin:/usr/bin')\n\
+  -s, --short-name  print DOS (short) form of NAMEs (with -w, -m only)\n\
 System information:\n\
-  -A, --allusersuse `All Users' instead of current user for -D, -P\n\
-  -D, --desktopoutput `Desktop' directory and exit\n\
+  -A, --allusersuse `All Users' instead of current user for -D, -O, 
-P\n\
+  -D, --desktop output `Desktop' directory and exit\n\
   -H, --homerootoutput `Profiles' directory (home root) and exit\n\
-  -P, --smprograms output Start Menu `Programs' directory and exit\n\
-  -S, --sysdir output system directory and exit\n\
-  -W, --windir output `Windows' directory and exit\n\
-", prog_name, prog_name, prog_name);
+  -O, --mydocs  output `My Documents' directory and exit\n\
+  -P, --smprograms  output Start Menu `Programs' directory and exit\n\
+  -S, --sysdir  output system directory and exit\n\
+  -W, --windir  output `Windows' directory and exit\n\
+  -F, --folder ID   output special folder with numeric ID and exit\n\
+", prog_name, prog_name, prog_name, prog_name);
   if (ignore_flag)
 /* nothing to do */;
   else if (stream != stdout)
@@ -101,9 +106,9 @@ Other options:\n\
   -f, --file FILE   read FILE for input; use - to read from STDIN\n\
   -o, --option  read options from FILE as well (for use with --file)\n\
   -c, --close HANDLEclose HANDLE (for use in captured process)\n\
-  -i, --ignore

Re: Exclude cygwin folder from malware scans?

2007-01-07 Thread Larry Hall (Cygwin)

Fred Ma wrote:

After some surfing, I haven't found any evidence of malware targetting
cygwin.  I'm considering excluding the massive file tree from scans
(AV, SpyBot, AdAware).  I'd be interested in more experienced opinions
about this.  Thanks.


Any such reports on this list in the past have later been shown to be
problems with the software that claims to have found a fault in Cygwin.
Such is the reasoning behind the following FAQ:



There has actually been more evidence to support that virus scanners,
firewalls, and spyware detection programs *cause* Cygwin problems by
interfering with its proper operation.  You can see such reports and
the subsequent resolutions (un-install faulty security software) in
the email archives.


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

_

A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?

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



Re: cygport patch: Add PATCHOPTS

2007-01-07 Thread Christian Franke

Yaakov (Cygwin Ports) wrote:

...
This is not necessary with cygport because the autotools are always
regenerated, and not changes in the generated files are not included in
the patch.

Did you find this particularly necessary somehow, and why?

  


I prefer to have the original timestamps of the files preserved by 
"cygport ... prep".

This should not rely on the source of the file (.tar or .patch).

Not really necessary, it is more a "nice to have" feature ;-)

BTW: Is the -N patch option always appropriate?

Christian


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



Re: having problems with getting Up and Runnign

2007-01-07 Thread Larry Hall (Cygwin)

Morgan Gangwere wrote:

Thanks! i deleted all registry entrys and the cygwin dir. i suspect that
how cygwin handles all the locations of things (such as where the
binaries live) and how all that runs
i also found that bash and such have an issue with mulit-word usernames
windows allows these but Pine and Mutt fail because they are made for
/home/username/mail/ but i used /home/user name/mail (username was Sys
Admin)
bash would show "[Sys [EMAIL PROTECTED]" but GNUStep would try to
write to /home/sys/GNUStep/ not /home/Sys Admin/GNUStep/
should we fix this in a future version? make the username all one word
(or use "_" in place - this makes it simpler)?



Paths with spaces with them are annoying but are legal path names, even
outside of Windows.  There are, unfortunately, still a number of packages
and scripts out in the wild that don't properly account for this though.
If you see specific issues, it's best to report them and even provide
patches to correct them.  Translating them into something else is buggy
at best though.  Better to just make sure the paths are quoted properly
so that the underlying code sees them properly.


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

_

A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?

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



Re: Two short scripts for Cygwin-Windows interoperation

2007-01-07 Thread Larry Hall (Cygwin)

On 01/07/2007, Christian Franke wrote:

Corinna Vinschen wrote:
> On Jan  4 23:39, Christian Franke wrote:
>  
>> ...

>> Thanks for any comment
>> 
>

> http://cygwin.com/acronyms/#PTC
> http://cygwin.com/acronyms/#SHTDI
>
> Come on, what did you expect? ;)
>
>   


Hmm...at least some info whether such a patch would be accepted.
(I don't want to do patches which need many iterations or end up in 
/dev/null ;-) 


I think it's fair to assume that  covers
this concern. :-)

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

_

A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?

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



Re: Exclude cygwin folder from malware scans?

2007-01-07 Thread Fred Ma

Fred Ma wrote:

After some surfing, I haven't found any evidence of malware targetting
cygwin.  I'm considering excluding the massive file tree from scans
(AV, SpyBot, AdAware).  I'd be interested in more experienced opinions
about this.  Thanks.


Larry Hall:

Any such reports on this list in the past have later been shown to
be problems with the software that claims to have found a fault in
Cygwin.  Such is the reasoning behind the following FAQ:



There has actually been more evidence to support that virus
scanners, firewalls, and spyware detection programs *cause* Cygwin
problems by interfering with its proper operation.  You can see such
reports and the subsequent resolutions (un-install faulty security
software) in the email archives.


I haven't had any problems in that regard (malware scanners
interfering with cygwin or having false positives), though I don't
doubt that it has happened before.  I was more wondering about the
wisdom of taking the plunge and excluding the cygwin directory tree
from future scans based on the past track record of not being
targeted.

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



Re: Exclude cygwin folder from malware scans?

2007-01-07 Thread Bobby McNulty

Fred Ma wrote:

Fred Ma wrote:

After some surfing, I haven't found any evidence of malware targetting
cygwin.  I'm considering excluding the massive file tree from scans
(AV, SpyBot, AdAware).  I'd be interested in more experienced opinions
about this.  Thanks.


Larry Hall:

Any such reports on this list in the past have later been shown to
be problems with the software that claims to have found a fault in
Cygwin.  Such is the reasoning behind the following FAQ:



There has actually been more evidence to support that virus
scanners, firewalls, and spyware detection programs *cause* Cygwin
problems by interfering with its proper operation.  You can see such
reports and the subsequent resolutions (un-install faulty security
software) in the email archives.


I haven't had any problems in that regard (malware scanners
interfering with cygwin or having false positives), though I don't
doubt that it has happened before.  I was more wondering about the
wisdom of taking the plunge and excluding the cygwin directory tree
from future scans based on the past track record of not being
targeted.

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



I would. In fact, with Norton Antivirus, AVG and some of the others, you 
can individually select

the directory.
I just got a new computer the week before last. Came with PC Cillian. 
Hate it cause it only lasts 2 monthes. I put  Norton on. Norton 
systemworks. and internet security.

Works like a charm.
Its a AMD 64 Athlon Duo Core.
Not bad. Beats the pants off of my old system.
Cygwin works like a charm.
ANd I have never encountered a problem with Cygwin and Norton because i 
close out Cygwin when I am done with it.

Cygwin works on Windows XP Media center edition 2005 just fine.
Waiting on Vista to try it there.



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



Re: Exclude cygwin folder from malware scans?

2007-01-07 Thread Larry Hall (Cygwin)

Fred Ma wrote:

Fred Ma wrote:

After some surfing, I haven't found any evidence of malware targetting
cygwin.  I'm considering excluding the massive file tree from scans
(AV, SpyBot, AdAware).  I'd be interested in more experienced opinions
about this.  Thanks.


Larry Hall:

Any such reports on this list in the past have later been shown to
be problems with the software that claims to have found a fault in
Cygwin.  Such is the reasoning behind the following FAQ:



There has actually been more evidence to support that virus
scanners, firewalls, and spyware detection programs *cause* Cygwin
problems by interfering with its proper operation.  You can see such
reports and the subsequent resolutions (un-install faulty security
software) in the email archives.


I haven't had any problems in that regard (malware scanners
interfering with cygwin or having false positives), though I don't
doubt that it has happened before.  I was more wondering about the
wisdom of taking the plunge and excluding the cygwin directory tree
from future scans based on the past track record of not being
targeted.



I doubt there are many out there that would think Cygwin is a good vector
to compromise machines with.  It's just not on enough machines to attract
that kind of attention.  The call is, of course, yours but I would say that
a Cygwin-based attack isn't likely to be your biggest concern.


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

_

A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?

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



Re: Where can I find the /usr/bin/tbl?

2007-01-07 Thread Yiran Guo
My groff package doesn't include tbl.exe, is there anything wrong?

Warren Young  etr-usa.com> writes:

 
 Yiran Guo wrote:
  I am using man in cygwin, but get this message:
  $ man man
  sh: /usr/bin/tbl: No such file or directory
  
  where can I get this tbl?
 
 The answer to that sort of question is always answered by the Cygwin 
 packages list page:
 
http://cygwin.com/cgi-bin2/package-grep.cgi?grep=bin%2Ftbl



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



RE: Where can I find the /usr/bin/tbl?

2007-01-07 Thread Dave Korn
On 08 January 2007 02:35, Yiran Guo wrote:

> My groff package doesn't include tbl.exe, is there anything wrong?

  Check it out by running " cygcheck -c groff".  It'll probably report that
it's incomplete; use setup.exe to reinstall it.


cheers,
  DaveK
-- 
Can't think of a witty .sigline today


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



Re: Where can I find the /usr/bin/tbl?

2007-01-07 Thread Yiran Guo

Dave Korn  artimi.com> writes:

> 
> On 08 January 2007 02:35, Yiran Guo wrote:
> 
> > My groff package doesn't include tbl.exe, is there anything wrong?
> 
>   Check it out by running " cygcheck -c groff".  It'll probably report that
> it's incomplete; use setup.exe to reinstall it.
> 
> cheers,
>   DaveK


Dear Dave,

It seems groff is ok:

$ cygcheck -c groff
Cygwin Package Information
Package  VersionStatus
groff1.18.1-2   OK

So odd.



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