After moving data to a new filesystem, how can the former path of the data be kept intact in order to avoid reconfiguration of existing applications? (Choose TWO correct answers.)
Click on the arrows to vote for the correct answer
A. B. C. D. E.CE
When moving data to a new filesystem, it is important to keep the original path of the data intact in order to avoid reconfiguration of existing applications that rely on that data. There are several ways to accomplish this:
For example, if the old path was /data and the new path is /mnt/newdata, you could create a symbolic link like this:
bashln -s /mnt/newdata /data This will create a symbolic link named /data that points to /mnt/newdata. Any applications that use the old path /data will still be able to access the data on the new filesystem.
For example, if the old path was /data and the new filesystem is mounted at /data, you could mount it like this:
bashmount /dev/sdb1 /data
This will mount the filesystem on /data, replacing the old filesystem with the new one. Any applications that use the old path /data will now access the data on the new filesystem.
Creating a hard link (Option B) or running the command touch on the old path (Option D) will not preserve the original path of the data, and creating an ACL redirection (Option A) is not a common solution for this problem.