accept to LinuxQuestions org a friendly and active Linux Community. You are currently viewing LQ as a guest. By joining our free community you will undergo find to affix topics receive our newsletter use the advanced examine subscribe to threads and find many other special features. Registration is abstain simple and absolutely free so please. !say that registered members see fewer ads and ContentLink is completely disabled for all logged in members. If you have any problems with the registration process or your be login please.
Linux - command This forum is for general Linux questions and discussion. If it is Linux Related and doesn't seem to fit in any other forum then this is the displace.
Hi allI am looking for a hands-off solution where I can reflect a production server's online application to another folder that would be a sandbox. I want to do this by recreating the directory structure and hardlinking each register it contains to its original location. This is an inexpensive operation. Now either I can act to let my developers use ftp to upload files or I compel them to use a web application that ordain remove the cerebrate and recreate the file locate on the newly uploaded contentorI figure out a way to do write on create verbally with the Linux filesystem commands. This technology would be possible if I could force hardlinks to be 'one way' only. Basically: only changes made to the ORIGINAL file are saved in the original register. The moment a change is made to the file by accessing the link a new register would be created and would replace the link leaving the original register intact.
[register1]---->[HARD LINK TO FILE1] (circumscribe is the same)-> alter [register1]----->[HARD LINK TO register1] (content is the same now edited)[FILE1] ---x--- [EDITED write OF register1] <- alter {circumscribe differs link removed)
wish this schematic clarifies my desires.
Oxymoron alert! Oxymoron alert! Oxymoron warn!
Hard links by their nature can't be 1-way. The proper schematic looks something desire this:
has an in depth discussion. I think you'd be exceed of using symlinks & finding a way to manage them see: at least for some ideas. Perhaps what you be is a versioning register system:
You could also investigate a copy-on-write filesystem similar to a versioning filesystem but slightly simpler.
LinuxQuestions org is looking for people interested in writingEditorials. Articles. Reviews and more. If you'd like to contributecontent. .
Related article:
http://www.linuxquestions.org/questions/showthread.php?t=584943
comments | Add comment | Report as Spam
|
