This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Shadowcopy volume block devices
- From: Andrey Repin <anrdaemon at freemail dot ru>
- To: Corinna Vinschen <cygwin at cygwin dot com>
- Date: Wed, 29 May 2013 16:20:07 +0400
- Subject: Re: Shadowcopy volume block devices
- References: <CAKAA-nncyH+D0RXDQ1KF6xkxSKGPrhodp7tDJTBJLC2-k3L1Jg at mail dot gmail dot com> <20130528133514 dot GJ5264 at calimero dot vinschen dot de> <CAKAA-nkaDnV30NCDVnbZ_J4fr2D-PRkb7qixxfursi0dHKxDfw at mail dot gmail dot com> <20130528153302 dot GL5264 at calimero dot vinschen dot de> <CAKAA-nk4Z-4L3Xa9JVx=t9CQsZi7qbo6nuQDXk7tsLVM8eLVpg at mail dot gmail dot com> <20130529084703 dot GE31309 at calimero dot vinschen dot de>
- Reply-to: Andrey Repin <cygwin at cygwin dot com>
Greetings, Corinna Vinschen!
> Btw., as a sidenote, are you aware that you can access the filesystem
> underneath the volume shadow copy as well?
> Try this (note the trailing backslash!):
> $ cd /proc/sys/Device/HarddiskVolumeShadowCopy1/
> $ ls
> The only downside is that you can't cd into the root dir of the
> shadowcopy by using a ".." expression:
> $ cd /proc/sys/Device/HarddiskVolumeShadowCopy1/Users
> $ cd ..
> /proc/sys/Device/HarddiskVolumeShadowCopy1: Not a directory.
> $ cd ../
> /proc/sys/Device/HarddiskVolumeShadowCopy1: Not a directory.
> Here the path handling strips off the trailing backslash and what's
> left is a block device called /proc/sys/Device/HarddiskVolumeShadowCopy1.
> With that in mind, it's quite usable, though.
Can this be worked around by a symlink or junction point? (I don't have access
to SVC-enabled box yet, sorry.)
--
WBR,
Andrey Repin (anrdaemon@freemail.ru) 29.05.2013, <16:19>
Sorry for my terrible english...
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple