r**********g
发帖数: 22734 | | d********g
发帖数: 10550 | 2 显然不应该用。storage存一下就没有symbolic信息了，整个结构完全不同。如果建一
个指向父目录或者root的symbolic link，岂不是进入了死循环，设计不好的cloud马上
就歇菜
【在 r**********g 的大作中提到】
: 不管支不支持，为了不让自己crew up，我认为都不应该使用。
: http://blog.kyloo.net/2012/04/24/why-symbolic-link-is-evil-for-
| r**********g
发帖数: 22734 | 3 Right, 这是针对那位想用symbolic link的童鞋的。Cloud storage 只是store 数据，
结构信息应该放在本地。
Twist service没有好处
【在 d********g 的大作中提到】
: 显然不应该用。storage存一下就没有symbolic信息了，整个结构完全不同。如果建一
: 个指向父目录或者root的symbolic link，岂不是进入了死循环，设计不好的cloud马上
: 就歇菜
| t*******d
发帖数: 1530 | 4 这个博主就是个半吊子，怎么被你引来当论据呢。
Dropbox does not care if it is a symbolic link or not. it will loyally think
it is a real file and happily sync it.
If you point current folder to its parent/root, you will make your OS think
you will have a unlimited sub folders, and dropbox will think the same way
and keep syncing it until it runs out of space. that is expected behavior.
[发表自未名空间手机版 - m.mitbbs.com]
【在 r**********g 的大作中提到】
: 不管支不支持，为了不让自己crew up，我认为都不应该使用。
: http://blog.kyloo.net/2012/04/24/why-symbolic-link-is-evil-for-
| r**********g
发帖数: 22734 | 5 That's why you don't use symbolic link, unless you want to screw up yourself.
Just an advice, you want to keep twisting the service, that's your choice.
The concept is simple, cloud storage is for data not links.
Read again, the problem the blog is talking about is cause by
"Dropbox does not care if it is a symbolic link or not. it will loyally
think it is a real file and happily sync it."
think
think
【在 t*******d 的大作中提到】
: 这个博主就是个半吊子，怎么被你引来当论据呢。
: Dropbox does not care if it is a symbolic link or not. it will loyally think
: it is a real file and happily sync it.
: If you point current folder to its parent/root, you will make your OS think
: you will have a unlimited sub folders, and dropbox will think the same way
: and keep syncing it until it runs out of space. that is expected behavior.
:
: [发表自未名空间手机版 - m.mitbbs.com]
| p****e
发帖数: 3548 | 6 大家的网速都多少阿。。。
sync这个功能，如果大点的文件和频繁编辑，没有光纤都玩不转吧 | l***h
发帖数: 9308 | 7 只同步变化的部分，这方面有谁比dropbox做得更好？
【在 p****e 的大作中提到】
: 大家的网速都多少阿。。。
: sync这个功能，如果大点的文件和频繁编辑，没有光纤都玩不转吧
| t*******d
发帖数: 1530 | 8 你要读几遍才能弄懂这个博主是个半吊子啊。
yourself.
[发表自未名空间手机版 - m.mitbbs.com]
【在 r**********g 的大作中提到】
: That's why you don't use symbolic link, unless you want to screw up yourself.
: Just an advice, you want to keep twisting the service, that's your choice.
: The concept is simple, cloud storage is for data not links.
: Read again, the problem the blog is talking about is cause by
: "Dropbox does not care if it is a symbolic link or not. it will loyally
: think it is a real file and happily sync it."
:
: think
: think
| b********7
发帖数: 12906 | 9 huh? can you elaborate more? this is something new to me. how do they only
sync the changed portion in a bigger file?
【在 l***h 的大作中提到】
: 只同步变化的部分，这方面有谁比dropbox做得更好？
| r**********g
发帖数: 22734 | 10 呵呵，as you like, 我就是博主。跟你说了这只是个善意的suggestion，你不愿意听
我也没办法。
如果你觉得你的办法好，也可以分享一下，我的博文如果能给让大家减少一些麻烦，就
算好了。
你觉得怎么用symbolic link更好，欢迎到我的博客讨论
【在 t*******d 的大作中提到】
: 你要读几遍才能弄懂这个博主是个半吊子啊。
:
: yourself.
: [发表自未名空间手机版 - m.mitbbs.com]
| | | r**********g
发帖数: 22734 | 11 text file may be possible, binary file is hard, as far as I know, when use
truecrypt disk image in dropbox, syncing take very long time
【在 b********7 的大作中提到】
: huh? can you elaborate more? this is something new to me. how do they only
: sync the changed portion in a bigger file?
| d********g
发帖数: 10550 | 12 git啊
其实对binary来说都是浮云，基于diff的只有文本才给力，bin不行
【在 l***h 的大作中提到】
: 只同步变化的部分，这方面有谁比dropbox做得更好？
| p****e
发帖数: 3548 | 13 只同步变化部分很容易造成文件损坏
【在 d********g 的大作中提到】
: git啊
: 其实对binary来说都是浮云，基于diff的只有文本才给力，bin不行
| t*******d
发帖数: 1530 | 14 哦sorry，不是有意冒犯啊。不过这个文章还是在纠结link confusing dropbox，or
storage needs to maintain relationship. it doesn't have to. that's OS's job.
it is all files to dropbox.
[发表自未名空间手机版 - m.mitbbs.com]
【在 r**********g 的大作中提到】
: 呵呵，as you like, 我就是博主。跟你说了这只是个善意的suggestion，你不愿意听
: 我也没办法。
: 如果你觉得你的办法好，也可以分享一下，我的博文如果能给让大家减少一些麻烦，就
: 算好了。
: 你觉得怎么用symbolic link更好，欢迎到我的博客讨论
| d********g
发帖数: 10550 | 15 这倒不会，VCS已经很成熟了，不过也基本只限于文本
【在 p****e 的大作中提到】
: 只同步变化部分很容易造成文件损坏
| r**********g
发帖数: 22734 | 16 No problem, my point is using symbolic link inside the storage is dangerous
and can cause problem.What I mean is whether or not storage can maintain
relationships is not important, but user need to realize you can't depend on
the provider to maintain it correctly for ALL the devices. Always use
symbolic link from outside the storage. E.g. in your case, you can just put
all the (non-symbolic link) files onto dropbox/skydrive, then write a script
to reconstruct the directory structure outside the storage.
That's what I did for my projects, so far so good.
job.
【在 t*******d 的大作中提到】
: 哦sorry，不是有意冒犯啊。不过这个文章还是在纠结link confusing dropbox，or
: storage needs to maintain relationship. it doesn't have to. that's OS's job.
: it is all files to dropbox.
:
: [发表自未名空间手机版 - m.mitbbs.com]
| t*******d
发帖数: 1530 | 17 "you can't depend on the provider to maintain it correctly for ALL the
devices"
Provider has nothing to maintain, and user never expect any relationship
being maintained, why worry for nothing?
If I follow your strategy and put everything under dropbox/skydrive, it is a
pain to rearrange working project folder, and it means I will never be able
to use symbolic link in my project any more, because if I use it once, it
render all the folder rearrangement trouble useless.
I have been working across os x and linux using dropbox and symbolic links
all the time and enjoy the convenience it offers deeply, never run into any
problem.
it is a pity that skydrive and google drive are not feature rich as dropbox
and offer no replacement for dropbox.
dangerous
on
put
script
[发表自未名空间手机版 - m.mitbbs.com]
【在 r**********g 的大作中提到】
: No problem, my point is using symbolic link inside the storage is dangerous
: and can cause problem.What I mean is whether or not storage can maintain
: relationships is not important, but user need to realize you can't depend on
: the provider to maintain it correctly for ALL the devices. Always use
: symbolic link from outside the storage. E.g. in your case, you can just put
: all the (non-symbolic link) files onto dropbox/skydrive, then write a script
: to reconstruct the directory structure outside the storage.
: That's what I did for my projects, so far so good.
:
: job.
| b********7
发帖数: 12906 | 18 that's why there are difference choices and everybody has the freedom to
choose whatever he/she needs. If you think sym link is really important to
you, use dropbox. that's the best choice for u. for most people out there,
they don't use sym links. they can choose to use skydrive or anything else.
a
able
any
【在 t*******d 的大作中提到】
: "you can't depend on the provider to maintain it correctly for ALL the
: devices"
: Provider has nothing to maintain, and user never expect any relationship
: being maintained, why worry for nothing?
: If I follow your strategy and put everything under dropbox/skydrive, it is a
: pain to rearrange working project folder, and it means I will never be able
: to use symbolic link in my project any more, because if I use it once, it
: render all the folder rearrangement trouble useless.
: I have been working across os x and linux using dropbox and symbolic links
: all the time and enjoy the convenience it offers deeply, never run into any
| r**********g
发帖数: 22734 | 19 Actually I don't understand how you are now running into problem.
If you put file A in dropbox directory, and create a symbolic link B to A,
also in dropbox directory, dropbox doesn't know they are the same file and
sync to copies. In another computer, you edit A, and think that B will also
be updated, but dropbox won't do that, now even in the original computer, A
and B are different and unrelated. If you are working in a team, other
members working on A wont be aware of the change you made on B. Anyway, that
's not what you expected.
Or, if you modified A and B in different computers, then it will bring more
troubles.
Why not keep only A in dropbox, map the directory structure with symlink
outside your dropbox directory, and link B to A only outside?
Believe me, when your team grows large enough, you can't rely on dropbox to
keep your file & links, one copy for one file is the guideline.
PS, don't build your project directly in dropbox, build it outside.
a
able
any
【在 t*******d 的大作中提到】
: "you can't depend on the provider to maintain it correctly for ALL the
: devices"
: Provider has nothing to maintain, and user never expect any relationship
: being maintained, why worry for nothing?
: If I follow your strategy and put everything under dropbox/skydrive, it is a
: pain to rearrange working project folder, and it means I will never be able
: to use symbolic link in my project any more, because if I use it once, it
: render all the folder rearrangement trouble useless.
: I have been working across os x and linux using dropbox and symbolic links
: all the time and enjoy the convenience it offers deeply, never run into any
| c****e
发帖数: 1453 | 20 Partition into blocks and each block has it own signature. You only sync the
changed blocks. It's standard techniques. I don't think Dropbox owns any
advantage here.
【在 b********7 的大作中提到】
: huh? can you elaborate more? this is something new to me. how do they only
: sync the changed portion in a bigger file?
| t*******d
发帖数: 1530 | 21 OK， I see your point. Dropbox will break your local link if you are
actually editing the link itself, i.e., editing a file content if the
linked is a file, or editing the folder name if the linked if a folder (
editing folder content is safe). That is indeed unexpected behaviour and
never occurred to me before. Lucky me I guess.
However, if you following the two examples on your blog literally, you will
realize they are bad examples.
In the 1st Pictures example, the later Win C:\Users\YOU\Picures will win,
and Mac ~/Pictures will be modified. Becuase only folder content are
involved here, not Folder name.
In the 2nd example, if you "edit A", both A and B will be updated in both
places, because A is not the symlink. B is. Your case will be true if you "
edit B".
Thanks.
also
A
that
more
[发表自未名空间手机版 - m.mitbbs.com]
【在 r**********g 的大作中提到】
: Actually I don't understand how you are now running into problem.
: If you put file A in dropbox directory, and create a symbolic link B to A,
: also in dropbox directory, dropbox doesn't know they are the same file and
: sync to copies. In another computer, you edit A, and think that B will also
: be updated, but dropbox won't do that, now even in the original computer, A
: and B are different and unrelated. If you are working in a team, other
: members working on A wont be aware of the change you made on B. Anyway, that
: 's not what you expected.
: Or, if you modified A and B in different computers, then it will bring more
: troubles.
| r**********g
发帖数: 22734 | 22 Good that you understand the problem and yes the pictures are not well
designed. Anyway you get my idea, believe me when you team grow larger, this
will happen and can be catastrophic.
To avoid problems, I still suggest, never use symbolic link in cloud storage
. This hurt me, I don't want other ppl to get hurt again. |
|
