delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2009/02/25/23:55:32

X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.5 required=5.0 tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <49A5F3E4.1090905@cygwin.com>
References: <87f94c370902241242q78d0d068o4416b4ae2aa9be62 AT mail DOT gmail DOT com> <49A59485 DOT 8090401 AT t-online DOT de> <87f94c370902251121s12579193q3032a5ce7cdef685 AT mail DOT gmail DOT com> <49A5CDDE DOT 4040703 AT cygwin DOT com> <87f94c370902251620h746060f8j4137fa5c3747e6e4 AT mail DOT gmail DOT com> <49A5F3E4 DOT 1090905 AT cygwin DOT com>
Date: Wed, 25 Feb 2009 23:55:18 -0500
Message-ID: <87f94c370902252055i29aaaad9ped23fae6ed9ea685@mail.gmail.com>
Subject: Re: special name for vss shadow copy device?
From: Greg Freemyer <greg DOT freemyer AT gmail DOT com>
To: cygwin AT cygwin DOT com
X-IsSubscribed: yes
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

On Wed, Feb 25, 2009 at 8:44 PM, Larry Hall (Cygwin)
<reply-to-list-only-lh AT cygwin DOT com> wrote:
> Greg Freemyer wrote:
>>
>> On Wed, Feb 25, 2009 at 6:01 PM, Larry Hall (Cygwin)
>> <reply-to-list-only-lh AT cygwin DOT com> wrote:
>>>
>>> Greg Freemyer wrote:
>>> <snip>
>>>
>>>> Time to experiment with Cygwin 1.7
>>>>
>>>> I know the whole package is still considered test. =A0How stable is the
>>>> actual dll(s). =A0Especially as relates to this type of functionality.
>>>
>>> Difficult to say since this functionality isn't on a typical use path
>>> and no specific efforts have been made to 'integrate' it into Cygwin,
>>> whatever form that integration might take. =A0What is clear, however, i=
s if
>>> there is a problem using this functionality in 1.7, now would be the ti=
me
>>> to find out. =A0Since the 1.7 DLL is near its final form for release, a=
ny
>>> hope of fixing problems before the release requires that they be found
>>> first.
>>
>> Okay, =A0(trouble report, see the end of the email. =A0Successes first :)
>>
>> I've got the latest 1.7 release. =A0I'm testing right now on Vista Home.
>>
>> Just as an FYI, this machine has 32 snapshots in place. =A0Going back to
>> Thanksgiving. =A0All of these were created automatically by Vista. =A0I
>> don't think I did any config work etc. to make it happen.
>>
>> I can see these from the Vista Command Prompt by running "vssadmin
>> list shadows".
>>
>> Very cool.
>>
>> dd seems to be working great, but I've only done a couple quick tests.
>>
>> dd if=3D<global-device-path> | od -cv | less
>>
>> is showing what looks like good data.
>>
>> I tried the same with snapshot instance 33. =A0As hoped dd came back
>> with an error message since that snapshot does not exist.
>>
>> I currently have 5 dd's running against 5 different snapshots and the
>> output going to /dev/null. =A0 =A0Per task manager all are actively
>> reading data. =A0Very cool. =A0They are reading very slowly, but then
>> again I'm beating the heck out of the drive.
>>
>> I tried the "dosdev" trick from one of the links to mount the snapshot
>> as V:. =A0Apparently that is a XP only trick. =A0Or at least Vista does
>> not have it.
>>
>> From the Vista command prompt I can do:
>> mklink /d C:\shadow_copy21
>> \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy21\
>>
>> and then cd into that directory and see my old snapshot data. =A0I can
>> also see it from the Vista file explorer.
>>
>> From cygwin's shell if I try to do so I get:
>> $ cd /cygdrive/c/shadow_copy21
>> bash: cd: /cygdrive/c/shadow_copy21: No such file or directory
>>
>> I assume that should work?
>
> Dunno. =A0I can't get the 'cd' or 'dir' to work from the Vista command
> prompt. =A0For me, 'dir foo' (I named the link 'foo') gives me 'File Not
> Found'. =A0So in my case, what you see from Cygwin makes sense since it's
> consistent with what Windows tells me.

Very strange mklink created usable directories for me on both Vista
Home and Win 2008.  Can you or someone else test it on another
machine?

ie. Cygwin need not be installed to test this Windows feature.

Greg
--=20
Greg Freemyer
Litigation Triage Solutions Specialist
http://www.linkedin.com/in/gregfreemyer
First 99 Days Litigation White Paper -
http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf

The Norcross Group
The Intersection of Evidence & Technology
http://www.norcrossgroup.com

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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019