Mail Archives: cygwin/2009/02/26/00:17:49
Greg Freemyer wrote:
> 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. How stable is the
>>>>> actual dll(s). Especially 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. What is clear, however, is if
>>>> there is a problem using this functionality in 1.7, now would be the time
>>>> to find out. Since the 1.7 DLL is near its final form for release, any
>>>> hope of fixing problems before the release requires that they be found
>>>> first.
>>> Okay, (trouble report, see the end of the email. Successes first :)
>>>
>>> I've got the latest 1.7 release. I'm testing right now on Vista Home.
>>>
>>> Just as an FYI, this machine has 32 snapshots in place. Going back to
>>> Thanksgiving. All of these were created automatically by Vista. I
>>> 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=<global-device-path> | od -cv | less
>>>
>>> is showing what looks like good data.
>>>
>>> I tried the same with snapshot instance 33. As 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. Per task manager all are actively
>>> reading data. Very cool. They 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:. Apparently that is a XP only trick. Or 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. I 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. I can't get the 'cd' or 'dir' to work from the Vista command
>> prompt. For me, 'dir foo' (I named the link 'foo') gives me 'File Not
>> Found'. So 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?
Sorry. Fresh out of Vista machines (sniff ;-))
--
Larry Hall http://www.rfk.com
RFK Partners, Inc. (508) 893-9779 - RFK Office
216 Dalton Rd. (508) 893-9889 - FAX
Holliston, MA 01746
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
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 -