FWIW, I ended up going with PuTTYcyg
http://code.google.com/p/puttycyg/
It was super easy to set up (and I needed something fast).
Thanks for the other suggestions, and I will test those out when I get
some more time!
--
Problem reports: http://cygwin.com/problems.html
FAQ:
irectory, I get the
> following error. (Everything works fine from Cygwin's interface, of
> course)
>
>
> Error: Current working directory is a virtual Cygwin directory.
> Can't start native Windows applic
interface, of
course)
Error: Current working directory is a virtual Cygwin directory.
Can't start native Windows application from here.
bash: /cygdrive/c/WINDOWS/system32/ls: File name too long
bash-3.2$ ls -al
Error: Current working dire
t.masked.goodSeq_HGblast/S1172_Spanish_Protin_Total_Nucleic_Acid.fa.cdhit_out.masked.goodSeq_file7.HGblast.out:
>> Cannot open: File name too long
>>
>> This name is only 201 chars long; I thought Windows max file length
>> was 255.
>
> I have a vague memory that the limit includes the current directory
> path. Anyone else kno
On Tue, 24 Feb 2009, Paul Cantalupo wrote:
tar:
S1172_Spanish_Protin_Total_Nucleic_Acid/S1172_Spanish_Protin_Total_Nucleic_Acid.fa.cdhit_out.masked.goodSeq_HGblast/S1172_Spanish_Protin_Total_Nucleic_Acid.fa.cdhit_out.masked.goodSeq_file7.HGblast.out:
Cannot open: File name too long
This name
Paul Cantalupo wrote:
Hello,
I updated my cygwin installation to 1.5.25-15 but I'm still getting
'file name too long' errors when trying to extract a .tgz archive that
contains some really long pathnames.
Here is an example of one of the errors:
tar:
S1172_Spanish_Protin_Tot
Hello,
I updated my cygwin installation to 1.5.25-15 but I'm still getting
'file name too long' errors when trying to extract a .tgz archive that
contains some really long pathnames.
Here is an example of one of the errors:
tar:
S1172_Spanish_Protin_Tot
On Feb 11 10:01, Jason Pyeron wrote:
> > http://cygwin.com/ml/cygwin/2009-02/msg00222.html
>
> Great.
>
> I have just installed it over 1.5 letting the setup choose the packages.
>
> I am no longer getting the file name too long error.
>
> I may be immagining, but
> -Original Message-
> From: cygwin-ow...@cygwin.com
> [mailto:cygwin-ow...@cygwin.com] On Behalf Of Corinna Vinschen
> Sent: Wednesday, February 11, 2009 9:46
> To: cygwin@cygwin.com
> Subject: Re: File name too long issues while using snv (subversion)
>
> On Fe
On Feb 11 09:32, Jason Pyeron wrote:
>
> > -Original Message-
> > From: cygwin-ow...@cygwin.com
> > [mailto:cygwin-ow...@cygwin.com] On Behalf Of Christopher Faylor
> > Sent: Wednesday, February 11, 2009 1:03
> > To: cygwin@cygwin.com
> > Subje
> -Original Message-
> From: cygwin-ow...@cygwin.com
> [mailto:cygwin-ow...@cygwin.com] On Behalf Of Christopher Faylor
> Sent: Wednesday, February 11, 2009 1:03
> To: cygwin@cygwin.com
> Subject: Re: File name too long issues while using snv (subversion)
>
> On
On Wed, Feb 11, 2009 at 12:49:10AM -0500, Jason Pyeron wrote:
>How can I make use of
>http://www.cygwin.com/ml/cygwin-developers/2008-03/msg0.html?
You obviously haven't been paying attention to Corinna's Cygwin
1.7 announcements.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscri
> -Original Message-
> From: cygwin-ow...@cygwin.com
> [mailto:cygwin-ow...@cygwin.com] On Behalf Of Jason Pyeron
> Sent: Wednesday, February 11, 2009 0:30
> To: cygwin@cygwin.com
> Subject: RE: File name too long issues while using snv (subversion)
>
>
&
> -Original Message-
> From: cygwin-ow...@cygwin.com
> [mailto:cygwin-ow...@cygwin.com] On Behalf Of Jason Pyeron
> Sent: Tuesday, February 10, 2009 23:34
> To: cygwin@cygwin.com
> Subject: File name too long issues while using snv (subversion)
>
> Is there a wo
Is there a workaround?
$ (pwd && echo
/hibernate-distribution-3.3.1.GA/project/testsuite/src/test/java/org/hibernate/t
est/event/collection/association/bidirectional/on
etomany/.svn/text-base/BidirectionalOneToManyBagSubclassCollectionEventTest.java
.svn-base) | wc
2 2 262
-jason
Klaus Tiedemann wrote:
> Hello cygwin,
>
> is there any progress on the "file name too long" problem ?
> I think a lot of people would like to use rsync under cygwin for backup
> or replication, but as long as cygwin can't handle long path names this
> is not a se
Hello cygwin,
is there any progress on the "file name too long" problem ?
I think a lot of people would like to use rsync under cygwin for backup or replication,
but as long as cygwin can't handle long path names this is not a serious option ...
Is there at least a wor
pplication
Data/Application Data/Application Data/Application
Data/Anwendungsdaten/Application Data/Start Menu/Programme" (in C)) failed:
File name too long (91)
In the server logfile I see:
full backup started for directory C (baseline backup #8)
Connected to Loredana.mybackup:10025, re
On Dec 18 21:06, Eric Blake wrote:
> According to Linda Walsh on 12/18/2007 3:30 PM:
> > Is it possible the update quoted at the bottom will address or fix
> > the path-len problem, mentioned below, in cygwin?
>
> Why not try out the snapshots, and see for yourself? But yes, it looks
> like Corin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Linda Walsh on 12/18/2007 3:30 PM:
> Is it possible the update quoted at the bottom will address or fix
> the path-len problem, mentioned below, in cygwin?
Why not try out the snapshots, and see for yourself? But yes, it looks
like Corin
Is it possible the update quoted at the bottom will address or fix
the path-len problem, mentioned below, in cygwin?
Corinna Vinschen wrote:
On Dec 1 15:43, Marty Leisner wrote:
So for now I did a mount onto a shorter path and things worked fine:
C:\Documents and Settings\leisner on /mnt type
On Dec 1 15:43, Marty Leisner wrote:
> So for now I did a mount onto a shorter path and things worked fine:
> C:\Documents and Settings\leisner on /mnt type system (binmode)
> when I queried in /mnt...
>
> Whats the current status of this problem?
Work in progress.
Corinna
--
Corinna Vins
=X1MDOTc1NDYxNjgEX3IDMgRmcmNvZGUDY3NjX3ltYWlsY2wEaXQDc2hvcnRjdXRzOi91cy9pbnN0YW5jZS9pZGVudGlmaWVyL1VSTARuX3R5cAMxBHNjbGFiZWwDaHR0cDovL290dGF3YS5raW[2].adNoOp&fr=csc_ymailcl':
File name too long
du: cannot access `Temporary Internet
Files/Content.IE5/WLCFOZCR/Type=click&FlightID=30975&AdID=43842&TargetID=8870&Segments=1,9,3875,4301,4719,5878,6125,[1].11%2CZIPCODE%2C14601%2CA
JPL wrote:
Hi,
We are having the same problem then the one you already answers last
year in:
http://www.cygwin.com/ml/cygwin/2005-04/msg00395.html
Since the cygwin-1.5.21-1 specified that future release might not
support win_9x
Do you have any plan for supporting longer path/filename than t
Hi,
We are having the same problem then the one you already answers last year in:
http://www.cygwin.com/ml/cygwin/2005-04/msg00395.html
Since the cygwin-1.5.21-1 specified that future release might not support win_9x
Do you have any plan for supporting longer path/filename than the
actual 260 by
On 10 May 2006 18:22, Capaci, Christopher wrote:
> Hi,
>
> I have two machines which, as far as I know, have the same setup. Using
> the same PATH string, one fails when trying to convert it with cygpath
> and one doesn't. The error is saying that the file name is too long. Can
> anyone suggest s
Hi,
I have two machines which, as far as I know, have the same setup. Using
the same PATH string, one fails when trying to convert it with cygpath
and one doesn't. The error is saying that the file name is too long. Can
anyone suggest some windows or cygwin setting that might be slightly
different
g and we just don't see it because the path restrictions
are more liberal.
FWIW,
Rob
Rob Hatcherson wrote:
Dave Korn wrote:
Original Message
From: Rob Hatcherson
Sent: 17 August 2005 20:49
All,
This issue involves a "File name too long" error being
Dave Korn wrote:
Original Message
From: Rob Hatcherson
Sent: 17 August 2005 20:49
All,
This issue involves a "File name too long" error being generated by the
C preprocessor that came along with 1.5.18-1. The compiler reports
version 3.4.4, the distro file sa
Original Message
>From: Rob Hatcherson
>Sent: 17 August 2005 20:49
> All,
>
> This issue involves a "File name too long" error being generated by the
> C preprocessor that came along with 1.5.18-1. The compiler reports
> version 3.4.4, the distro file
All,
This issue involves a "File name too long" error being generated by the
C preprocessor that came along with 1.5.18-1. The compiler reports
version 3.4.4, the distro file says 3.4.4-1.
I have a header file whose total path length is 190 characters counting
drive letters (ye
On Apr 10 02:07, Xu?n Baldauf wrote:
> Hello,
>
> I'm hitting "File name too long (91)" errors when using "rsync" or even
> "ls" within cygwin. I tracked down this problem to the constant
> "CYG_MAX_PATH", which seems to be define
Hello,
I'm hitting "File name too long (91)" errors when using "rsync" or even
"ls" within cygwin. I tracked down this problem to the constant
"CYG_MAX_PATH", which seems to be defined in "cygtls.h". Would it be a
problem to rise this
33 matches
Mail list logo
