Skip to main content
Tweaked formatting and punctuation; deleted fluffy apology.
Source Link

My objective is to have my files in any of the machines that I logon in my network.

My objective is to have my files in any of the machines that I logon in my network.

This ancient question may be answered in a more simple manner:

  • Designate one machine as a "server" and set up NFS upon it.
  • Or use SyncThing, so there is no centralised server.

With SyncThing, the directories and files you define are automatically synchronised to ALL OTHER machines. It can be as real-time as you define.

The first option is certainly easy. If one is a noobie, use WebMin on the "server" and it has a helpful browser-based GUI to set it up.

NFS is a nice, simple protocol to set up remote shares locally. They can be mapped anywhere and look just as if they exist on the machine you are using.

SyncThing offers the resilience of having a pseudo-replication solution. If one  If one machine should catch fire, itsit's not such a trauma. It also  It also offers "versions" so if another machine should change a file file, the old the old file is kept kept. There are  There are options to restrict this (n-versions, n-days/months, etc)

.....

Apologies to resurrect this from the grave. It is beginning to be asked more on places like Reddit as more people adopt Linux :) :)

My objective is to have my files in any of the machines that I logon in my network.

This ancient question may be answered in a more simple manner:

  • Designate one machine as a "server" and set up NFS upon it.
  • Or use SyncThing, so there is no centralised server.

With SyncThing, the directories and files you define are automatically synchronised to ALL OTHER machines. It can be as real-time as you define.

The first option is certainly easy. If one is a noobie, use WebMin on the "server" and it has a helpful browser-based GUI to set it up.

NFS is a nice, simple protocol to set up remote shares locally. They can be mapped anywhere and look just as if they exist on the machine you are using.

SyncThing offers the resilience of having a pseudo-replication solution. If one machine should catch fire, its not such a trauma. It also offers "versions" so if another machine should change a file, the old file is kept. There are options to restrict this (n-versions, n-days/months, etc)

.....

Apologies to resurrect this from the grave. It is beginning to be asked more on places like Reddit as more people adopt Linux :) :)

My objective is to have my files in any of the machines that I logon in my network.

This ancient question may be answered in a more simple manner:

  • Designate one machine as a "server" and set up NFS upon it.
  • Or use SyncThing, so there is no centralised server.

With SyncThing, the directories and files you define are automatically synchronised to ALL OTHER machines. It can be as real-time as you define.

The first option is certainly easy. If one is a noobie, use WebMin on the "server" and it has a helpful browser-based GUI to set it up.

NFS is a nice, simple protocol to set up remote shares locally. They can be mapped anywhere and look just as if they exist on the machine you are using.

SyncThing offers the resilience of having a pseudo-replication solution.  If one machine should catch fire, it's not such a trauma.  It also offers "versions" so if another machine should change a file, the old file is kept.  There are options to restrict this (n-versions, n-days/months, etc.)

Source Link

My objective is to have my files in any of the machines that I logon in my network.

This ancient question may be answered in a more simple manner:

  • Designate one machine as a "server" and set up NFS upon it.
  • Or use SyncThing, so there is no centralised server.

With SyncThing, the directories and files you define are automatically synchronised to ALL OTHER machines. It can be as real-time as you define.

The first option is certainly easy. If one is a noobie, use WebMin on the "server" and it has a helpful browser-based GUI to set it up.

NFS is a nice, simple protocol to set up remote shares locally. They can be mapped anywhere and look just as if they exist on the machine you are using.

SyncThing offers the resilience of having a pseudo-replication solution. If one machine should catch fire, its not such a trauma. It also offers "versions" so if another machine should change a file, the old file is kept. There are options to restrict this (n-versions, n-days/months, etc)

.....

Apologies to resurrect this from the grave. It is beginning to be asked more on places like Reddit as more people adopt Linux :) :)