You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I propose to use symbolic links for the cloned files instead of copy them to /usr/local/sbin
Ex.
sudo ln -s $(pwd)/rpi-clone /usr/local/sbin/rpi-clone
sudo ln -s $(pwd)/rpi-clone-setup /usr/local/sbin/rpi-clone-setup
If/when updates are made to rpi-clone or rpi-clone-setup the links in /usr/local/sbin are then pointing to the new updated files.
Eg. no need to copy the files..
Best regards,
Anders Fromell
The text was updated successfully, but these errors were encountered:
I propose to use symbolic links for the cloned files instead of copy them to /usr/local/sbin
Ex.
sudo ln -s $(pwd)/rpi-clone /usr/local/sbin/rpi-clone
sudo ln -s $(pwd)/rpi-clone-setup /usr/local/sbin/rpi-clone-setup
The major advantage is:
if you update to the latest release by:
sudo git fetch https://github.com/billw2/rpi-clone.git
If/when updates are made to rpi-clone or rpi-clone-setup the links in /usr/local/sbin are then pointing to the new updated files.
Eg. no need to copy the files..
Best regards,
Anders Fromell
The text was updated successfully, but these errors were encountered: