mv /home/bobg/Public/nfs4exports / will put it back. mv will "move" the directory and all subdirectories.
Usually to fix something like this (down too many levels) assuming you want that, then go into the directory were the data now is and do mv * ../ and that will relocate it up one directory, that will happen fast as long as . and ../ are on the same mount point, in the same mount point case it will just move the pointers to the data.
On Tue, Sep 15, 2020 at 3:10 PM Bob Goodwin bobgoodwin@fastmail.us wrote:
On 2020-09-15 06:58, Bob Goodwin wrote:
I will do as you suggest
° Well, never trusting the "mv" command, I decided to do some experimenting and did:
[root@nfs bobg]# mv /nfs4exports /home/bobg/Public
expecting to move my stored data into "Public" and it did that but the result is not quite what I thought it would be now this is where it is:
/home/bobg/Public/nfs4exports/home
Which I assume is what I would or could export with /etc/ecxports
I think the best ting I might do now is to move thins back to where they were, return the data back to /nfs4exports But it takes a while to run this and I would like to get it right.
Will this restore what I had originally,
mv /home/bobg/Public/nfs4exports/home /nfs4exports
or will it create an even longer file name?
Help, my confidence is shrinking, Bob
-- Bob Goodwin - Zuni, Virginia, USA FEDORA-32/64bit LINUX XFCE Fastmail POP3 _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org