Re: [Bug-tar] Regarding untaring tar files containing symlinks

[Linda A. Walsh]

How are you setting your cygwin variable?  It needs to be set before
any cygwin processes start.

I.e. in controlpanel->system->, advanced, environment variables.

Best to set in System variables so all users will be sure to have it set.

If that is where you are setting it, then I'm more stumped, but at this
point you might ask on the cygwin list, since it works with the same
software on my system. 

It sounds like cygwin is using the old-link creation for some reason...
the Env var not being set early enough would be one reason (as well
as wrong cygwin version, or windows version lower than Vista, or
too old cygwin version, but your cygwin looks recent enough), so if
you are setting the env var in your Window's system variables, then
I'm sorta stumped, other than to direct you to a better forum (cygwin)
for this ... am 90+% sure it's nothing to do with tar at this point.

Amit Kapila wrote:
> On Sat, Jul 5, 2014 at 1:14 PM, Linda A. Walsh <address@hidden 
> <mailto:address@hidden>> wrote:
> > Amit Kapila wrote
> >
> >>
> >> Please extract in order as mentioned to ensure that symlink folder
> >> gets extracted first.
> >> Please check contents of C:\Data\pg_tblspc, ideally it should contain
> >> symlink to C:\tbs.
> >
> > ---
> > It appears to work as you are wanting it to (console output below).
>
> Thats great.
>
> > But I also note that if they are created in the wrong order (something
> > that would work on linux).  -- then I get the behavior you mention:
> >
> > instead of a symlink, I get a file containing text:
> >
> > C:\data\pg_tblspc>hexdump -C 16386
> > 00000000  21 3c 73 79 6d 6c 69 6e  6b 3e ff fe 63 00 3a 00 
>  |!<symlink>..c.:.|
> > 00000010  5c 00 74 00 62 00 73 00  00 00                    |\.t.b.s...|
> > 0000001a
>
> I am always getting file having contents as above.
>
> >
> > This might have to do with the version of cygwin you have.
> >
> > You might make sure your cygwin is up to date -- as I vaguely remember
> > somewhat older versions of 'cygwin' didn't create actual windows
> > symlinks and hardlinks but created dummy files with the information
> > in them (like you are seeing).  But that changed... maybe 2-4 years ago?
> >
> > If you are running on a 64-bit windows, there is also a 64-bit
> > cygwin that runs in native mode that gives some advantages over
> > 32-bit  cygwin on a 64-bit machine (like 32-bit processes can't
> > see the real C:\windows\system32, but are redirected to 
> C:\windows\syswow64
> > syswow64 = windows[32] on windows64)
> >
> > you can tell which version you are running by running uname -a:
> > CYGWIN_NT-6.1 Athenae 1.7.30(0.272/5/3) 2014-05-23 10:36 x86_64 Cygwin
> >
> > 32-bit cygwin would say:
> > CYGWIN_NT-6.1-WOW64 Athenae 1.7.28(0.271/5/3) 2014-02-09 21:06 i686 
> Cygwin
> >
>
> I am working Windows 64-bit and uname -a gives below info
> on my m/c.
>
> CYGWIN_NT-6.2 WIN-J9UR5I3UTSM 1.7.30(0.272/5/3) 2014-05-23 10:36 
> x86_64 Cygwin
>
> I have downloaded cygwin for windows64-bit from below link:
> https://www.cygwin.com/install.html
>
> Do I need to update my cygwin installation, any recommendation
> for same?
>
> With Regards,
> Amit Kapila.