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.
>
> chee
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
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 questi
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
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
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
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 w
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 P
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
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 la
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 pat
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 curr
[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. Tha
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 becaus
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
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
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 al
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
--
Unsubscrib
* 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 ss
> 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
/u
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 protect
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 succes
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(
-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
-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
> wh
-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
26 matches
Mail list logo
