|
![](/i/fill.gif) |
Warp wrote:
> Windows *does* support it. (And even if the support is extremely hard
> for a regular user to use, while the same feature in eg. linux is rather
> simple to use, you still manage to make it *sound* like it's a completely
> trivial thing to do in Windows as well, even if it really isn't.)
Actually, I think I've realized what's going on here.
I've used enough different systems that incidental awkwardness doesn't
bother me. Weird syntax and clunky that's annoying to work around isn't
a problem for me any more. Fundamental breakage that can't be avoided
is a problem for me, because I tend to run into this sort of thing a lot
in the kinds of stuff I do. The stuff I do needs to be correct when it's
working, even tho I don't always design things for 100% uptime.
So the fact that you need to use some OS-specific call to create a
volume shadow copy and what you wind up with is some weird string like
\\?\globalnamespace\vss\{12318-847-randomguid-381}
as the root directory (and you need more OS-specific calls to get to it)
doesn't bother me nearly as much as (say) the inability to make a
consistent backup of a running UNIX file system because it's changing
between the time you stat the file and the time you open it.
--
Darren New / San Diego, CA, USA (PST)
Post a reply to this message
|
![](/i/fill.gif) |