On Jun 12 08:06, Arthur Norman via Cygwin wrote:
> This running on Windows 10 1909 and cygwin has been updated to the latest
> version. The effect was also visible on a freshly installed minimal cygwin
> put on an almost fresh Windows 10 VM.
>
> Cygwin these days seems to have a behaviour that con
On Sat, Jun 13, 2020 at 1:50 PM Andrey Repin wrote:
> The cygdrive prefix is resolved, if no other mount points match.
> Since you have /mnt/C mount point, it is resolved first.
I wish it would have resolved it to the cygdrive prefix, because then
it would have worked (and would have been /cygdriv
Greetings, Wayne Davison!
> On Fri, Jun 12, 2020 at 4:05 AM Andrey Repin wrote:
>> And you've got exactly what you asked for.
> I think you missed the important part of the email. Distilled down,
> this is wrong:
> $ ln -s /cygdrive/C/Windows foo
> $ readlink foo
> /mnt/C/Windows
The cygdrive p
On Fri, Jun 12, 2020 at 4:05 AM Andrey Repin wrote:
> And you've got exactly what you asked for.
I think you missed the important part of the email. Distilled down,
this is wrong:
$ ln -s /cygdrive/C/Windows foo
$ readlink foo
/mnt/C/Windows
The symlink's value changed to a path that doesn't exi
Greetings, Arthur Norman!
> This running on Windows 10 1909 and cygwin has been updated to the latest
> version. The effect was also visible on a freshly installed minimal cygwin
> put on an almost fresh Windows 10 VM.
> Cygwin these days seems to have a behaviour that confuses me regarding the
Hi Corinnayou are right,I mixed it the symlink with the hard link
the symlink is sl (on file source)
E:\>type sl
source < just the filename as you say>
but the hard link does work (on file source)
E:\>type hl
hallo
erna
otto
hugo
E:\>echo rudi >> source
E:\>type hl
hallo
erna
otto
hugo
rudi
o
Please, do not top-post.
On Dec 17 18:50, Simon Liesenfeld via cygwin wrote:
> Hi Corinna,
> since you answered your own questionsI can better understand my own
> stupidity.I have created now a hard and a soft link with a native
> linux,then I booted Windows, started the paragon driver,then cyg
Hi Corinna,
since you answered your own questionsI can better understand my own stupidity.I
have created now a hard and a soft link with a native linux,then I booted
Windows, started the paragon driver,then cygwin programs as well as any dos
program perfectly
understood the links.
Even if cyg
Am 17.12.18 um 19:45 schrieb Stefan Baur:
>> Features implemented and bugfix:
>>
>> 1, FIXME: superblock corruption of EXT4 volumes with 64BIT mode enabled
>> 2, FIXME: possible corruption by race conditions in buffer-head reapering
>> 3, FIXME: possible deadlock issues (when flushing
Am 17.12.18 um 17:57 schrieb Corinna Vinschen:
> As a sidenote, the OSS project Ext2Fsd handles symlinks transparently
> via standard Windows functions. With "CYGWIN=winsymlinks:native" you
> can generate real ext4 symlinks transparently. Even the good old Cygwin
> symlink works on Cygwin without
On Dec 17 10:34, Corinna Vinschen wrote:
> On Dec 17 08:11, Simon Liesenfeld via cygwin wrote:
> > Hi all
> >
> > There is a commercial ext3-4 file system driver for windowsLinux File
> > Systems für Windows | Paragon Softwarewhich enable Windows to read an
> > write on native ext3-4 volumes.In Ge
Hi Corinna,I 've set in the Control Panel,and this reflects in bash.I still
does work.
$ set | grep -i nativeCYGWIN=winsymlinks:native
$ ln -s /cygdrive/e/source sl
$ cat sl
!▒▒/cygdrive/e/source
One can download a 10 days trial version at:
http://dl.paragon-software.com/demo/linuxwin_trial.m
On Dec 17 12:03, Simon Liesenfeld via cygwin wrote:
> Hi all,
> Thank you so much for the response,and nearby for the entire cygwin
> Project.(Best of both worlds)"The devil is in the detail"I admire
> cygwin so much, and I' am overwhelmed
> that it can do the named pipes on paragon systemalready.
Hi all,
Thank you so much for the response,and nearby for the entire cygwin
Project.(Best of both worlds)"The devil is in the detail"I admire cygwin so
much, and I' am overwhelmed
that it can do the named pipes on paragon systemalready.I do not expect cygwin
to master the symbolic links,it's to
Greetings, Simon Liesenfeld!
> Hi all
> There is a commercial ext3-4 file system driver for windowsLinux File
> Systems für Windows | Paragon Softwarewhich enable Windows to read an write
> on native ext3-4 volumes.In General cygwin works perfectly on such
> volumes,even named pipes work,
> but
On Dec 17 10:34, Corinna Vinschen wrote:
> On Dec 17 08:11, Simon Liesenfeld via cygwin wrote:
> > Hi all
> >
> > There is a commercial ext3-4 file system driver for windowsLinux File
> > Systems für Windows | Paragon Softwarewhich enable Windows to read an
> > write on native ext3-4 volumes.In Ge
On Dec 17 08:11, Simon Liesenfeld via cygwin wrote:
> Hi all
>
> There is a commercial ext3-4 file system driver for windowsLinux File
> Systems für Windows | Paragon Softwarewhich enable Windows to read an
> write on native ext3-4 volumes.In General cygwin works perfectly on
> such volumes,even n
On 01/01/2010 04:52 PM, Lee Rothstein wrote:
Will Windows junctions (for the path; plus the file name) work, here, Andy?
(http://technet.microsoft.com/en-us/sysinternals/bb896768.aspx)
NTFS junctions are for directories only.. For files and directories, one could
use "mklink" on Vista and newe
> You could create a Windows symbolic link using the Windows 'mklink'
> tool though, and it should work both in cmd.exe and in Cygwin.
Thanks for the info and Corinna's quote.
Probably I'll just create windows symlinks like from
c:\users\tuli\bin\gcc.exe to c:\cygwin\bin\gcc-3.exe
so that cygwin
Lee Rothstein:
>> Will Windows junctions (for the path; plus the file name) work, here?
Don't think so, afaik junction points (introduced in Win2000, and
different from Vista/7 symlinks) work correctly for directories only.
Hard links, however, should work just fine for the problem at hand.
tul
> Will Windows junctions (for the path; plus the file name) work, here, Andy?
> (http://technet.microsoft.com/en-us/sysinternals/bb896768.aspx)
>
> (Admittedly, a kludge, but this is Windows, after all. ;-))
>
> Lee
Actually, in Windows 7, Microsoft has implemented true symbolic links
(as far as I
Andy Koppe wrote:
2009/12/30 Larry Hall (Cygwin):
I've been using gcc and other tools in older versions of cygwin with
32-bit Windows XP and Vista from windows command prompt (cmd.exe)
without problems. But now I'm using 64-bit Windows 7, and some command
line tools like gcc.exe do not work anym
2009/12/30 Larry Hall (Cygwin):
>> I've been using gcc and other tools in older versions of cygwin with
>> 32-bit Windows XP and Vista from windows command prompt (cmd.exe)
>> without problems. But now I'm using 64-bit Windows 7, and some command
>> line tools like gcc.exe do not work anymore (from
> This is a known limitation of the symbolic links in Cygwin 1.7. The solution
> is ...
Thanks for the info. I'll try one of your workarounds.
Cheers,
Tuli
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwi
On 12/30/2009 08:30 AM, tuli tanssi wrote:
Hi,
I've been using gcc and other tools in older versions of cygwin with
32-bit Windows XP and Vista from windows command prompt (cmd.exe)
without problems. But now I'm using 64-bit Windows 7, and some command
line tools like gcc.exe do not work anymore
On Oct 29 02:40, Larry Hall (Cygwin) wrote:
> On 10/29/2009 01:26 AM, Neil Mowbray wrote:
> >Dear Folks,
> >
> >On NTFS systems that support real symbolic links (eg those with Vista)
> >the comand ln -s does *not* create a native symbolic link merely an old
> >style shortcut.
> >
> >Will ln -s be c
On 10/29/2009 01:26 AM, Neil Mowbray wrote:
Dear Folks,
On NTFS systems that support real symbolic links (eg those with Vista)
the comand ln -s does *not* create a native symbolic link merely an old
style shortcut.
Will ln -s be chansed to support native symbolic links?
No, not until, at leas
Scott Webster Wood wrote:
> I tried doing a if(-l $file) where $file was the name of a symbolically
> linked directory in the current working directory and it returned a false.
> Doing a (-d $file) returned true.
I can't reproduce this:
$ mkdir foo; ln -s foo bar
$ perl -e 'print "yes\n" if
Ugh, top-posting... Reformatted.
On Fri, 2 Dec 2005, Akshay Dua wrote:
> > From: Igor Pechtchanski [mailto:[EMAIL PROTECTED]
> > Sent: Friday, December 02, 2005 6:43 PM
> > To: Akshay Dua
> > Cc: [EMAIL PROTECTED]
<http://cygwin.com/acronyms/#PCYMTNQREAIYR>. Than
; To: Akshay Dua
> Subject: Re: Symbolic links with cvs
>
> Akshay Dua wrote:
> > Thanks so much for your reply.
> >
> > Is there a way to tell Cygwin to stop converting (or treating) .lnk
> > files as symlinks? The thing is my colleagues with the same version
of
avior back?
Thanks
Akshay
> -Original Message-
> From: Igor Pechtchanski [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 02, 2005 6:43 PM
> To: Akshay Dua
> Cc: cygwin@cygwin.com
> Subject: Re: Symbolic links with cvs
>
> On Fri, 2 Dec 2005, Akshay Dua wrote:
>
On Fri, 2 Dec 2005, Akshay Dua wrote:
> Hello,
>
> Unfortunately, we have .lnk files in our source control so I cannot
> avoid the following problem. When I try to checkout a symbolic link
> file, something happens to it and cvs is unable to stat it to set
> necessary file information. Its almost
> -Original Message-
> From: cygwin-owner On Behalf Of Steve Kelem
> Sent: 23 December 2004 18:32
> I'm running the latest Cygwin on WinXP SP2. I have coreutils-5.2.1-3
> installed.
>
> I have a Linux directory mounted via Samba.
http://cygwin.com/faq/faq_3.html#SEC66 help any?
ch
On Dec 15 21:58, Elliott Wilcoxon wrote:
> NTFS also supports hard links, and there's a program that comes with
> Windows that lets you make them (searching WinXP Pro's Help and Support
> Center for 'hardlink' gives the relevant entries). The result would
> then be that it would work in both Cy
NTFS also supports hard links, and there's a program that comes with
Windows that lets you make them (searching WinXP Pro's Help and Support
Center for 'hardlink' gives the relevant entries). The result would
then be that it would work in both Cygwin and Windows (all programs),
although it can
Dan Adams wrote:
>
> My question was, is there any way to use the cygwin links, not the windows
> ones, to also be able to work in the open dialog box in MS Office products
> like excel for example. As I said, it is working in windows explorer. The
> only reason why I was mentioning about the wind
My question was, is there any way to use the cygwin links, not the windows
ones, to also be able to work in the open dialog box in MS Office products
like excel for example. As I said, it is working in windows explorer. The
only reason why I was mentioning about the windows links is because they
we
On Mon, Dec 15, 2003 at 01:16:16PM -0700, Dan Adams wrote:
>When I try to use a windows shortcut file in cygwin it doesn't seem to work.
Correct. It is not supposed to work. Cygwin understands cygwin shortcuts.
Windows understand windows and cygwin shortcuts.
--
Please use the resources at cygwi
al Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of Dan Adams
> > Sent: Monday, December 15, 2003 2:39 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Symbolic Links
> >
> >
> > Part of the reason I am interested in this, I
CTED]
> Subject: Re: Symbolic Links
>
>
> Part of the reason I am interested in this, I guess I forgot
> to say is to be able to have both Windows and Cygwin
> recognize the links. If I use the windows shortcut creation,
> cygwin doesn't recognize it. If I use the cygwi
Part of the reason I am interested in this, I guess I forgot to say is to be
able to have both Windows and Cygwin recognize the links. If I use the
windows shortcut creation, cygwin doesn't recognize it. If I use the cygwin
thing below, excel doesn't recognize it, but windows does.
Dan
"Dan Adams
41 matches
Mail list logo
