Jump to content

Hardlink vs Move Deployment


Goffender

Recommended Posts

I assume questions on how to go here not in feedback?

 

So it sounds like Hardlink method of deployment is trying to be like MO. And Move Deployment ( experimental ) is the old way. Does that mean that with hardlink (default method ) Vortex will be required to be running in the back ground?

 

 

 

 

Link to comment
Share on other sites

  On 6/30/2018 at 3:48 PM, Goffender said:

I assume questions on how to go here not in feedback?

 

So it sounds like Hardlink method of deployment is trying to be like MO. And Move Deployment ( experimental ) is the old way. Does that mean that with hardlink (default method ) Vortex will be required to be running in the back ground?

 

 

 

 

 

Vortex is never required to be running in the background. And Hard Links are nothing like MO.

Link to comment
Share on other sites

move deployment tries to replicate the behaviour of hard links on filesystems that don't support hard links.

It's generally going to be a more complicated and fragile system so I would strongly advise against using it unless hard links are not an option. Apart from compatibility there is absolutely no advantage to move deployment.

Link to comment
Share on other sites

What's the difference between a hard link and an "actual file"? I can almost guarantee that you have a misconception about what hard links are.

 

It's true that with move deployment the "original" file gets placed in the data directory and a custom "link" is instead placed in the mod directory so we can reverse the move, but from the user perspective there is no practical difference to hard linking. Any difference would be for the worse.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...