reverse command












1















I have written this command:
sudo mv /* /usr/lib/I'm not sure about this folder name/



for install flash player and many files copied to this directory /usr/lib/I'm not sure about this folder name/ and my Ubuntu doesn't work now



I'm able to use live Ubuntu. Can I use reverse command and undoing movement and repair my Ubuntu? If yes, what is the reverse command?



Update
I did. now ubuntu waiting in booting page(page with ubuntu logoo and 5 dot changing color from red to white) for half an hour.



this is fstab content



#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=1d24ddd9-b5ed-45f7-9770-9a599cecf4a3 / ext4 errors=remount-ro 0 1
/swapfile none swap sw 0 0```









share|improve this question

























  • Is this a command that moves the whole disk storage to an interior directory?

    – xt1zer
    Jan 23 at 9:15






  • 2





    There are no direct revers comment. From live media you will have to mount your old / (root) dirirectory, and then move the relevant directories from /usr/lib/pepperflashplugin-nonfree/ to / . What are the output of ls -la /usr/lib/pepperflashplugin-nonfree/

    – Soren A
    Jan 23 at 9:17













  • Possible duplicate of Accidentally moved directories under root

    – Olorin
    Jan 23 at 9:19











  • @Olorin agreed but I do believe this warrants a personal approach ;-)

    – Rinzwind
    Jan 23 at 9:20











  • @Rinzwind but ... the only thing that would change is the path to be moved from? You'd still need to use busybox because the libraries would be moved around? Ah I see, live system is available. Never mind.

    – Olorin
    Jan 23 at 9:22


















1















I have written this command:
sudo mv /* /usr/lib/I'm not sure about this folder name/



for install flash player and many files copied to this directory /usr/lib/I'm not sure about this folder name/ and my Ubuntu doesn't work now



I'm able to use live Ubuntu. Can I use reverse command and undoing movement and repair my Ubuntu? If yes, what is the reverse command?



Update
I did. now ubuntu waiting in booting page(page with ubuntu logoo and 5 dot changing color from red to white) for half an hour.



this is fstab content



#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=1d24ddd9-b5ed-45f7-9770-9a599cecf4a3 / ext4 errors=remount-ro 0 1
/swapfile none swap sw 0 0```









share|improve this question

























  • Is this a command that moves the whole disk storage to an interior directory?

    – xt1zer
    Jan 23 at 9:15






  • 2





    There are no direct revers comment. From live media you will have to mount your old / (root) dirirectory, and then move the relevant directories from /usr/lib/pepperflashplugin-nonfree/ to / . What are the output of ls -la /usr/lib/pepperflashplugin-nonfree/

    – Soren A
    Jan 23 at 9:17













  • Possible duplicate of Accidentally moved directories under root

    – Olorin
    Jan 23 at 9:19











  • @Olorin agreed but I do believe this warrants a personal approach ;-)

    – Rinzwind
    Jan 23 at 9:20











  • @Rinzwind but ... the only thing that would change is the path to be moved from? You'd still need to use busybox because the libraries would be moved around? Ah I see, live system is available. Never mind.

    – Olorin
    Jan 23 at 9:22
















1












1








1








I have written this command:
sudo mv /* /usr/lib/I'm not sure about this folder name/



for install flash player and many files copied to this directory /usr/lib/I'm not sure about this folder name/ and my Ubuntu doesn't work now



I'm able to use live Ubuntu. Can I use reverse command and undoing movement and repair my Ubuntu? If yes, what is the reverse command?



Update
I did. now ubuntu waiting in booting page(page with ubuntu logoo and 5 dot changing color from red to white) for half an hour.



this is fstab content



#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=1d24ddd9-b5ed-45f7-9770-9a599cecf4a3 / ext4 errors=remount-ro 0 1
/swapfile none swap sw 0 0```









share|improve this question
















I have written this command:
sudo mv /* /usr/lib/I'm not sure about this folder name/



for install flash player and many files copied to this directory /usr/lib/I'm not sure about this folder name/ and my Ubuntu doesn't work now



I'm able to use live Ubuntu. Can I use reverse command and undoing movement and repair my Ubuntu? If yes, what is the reverse command?



Update
I did. now ubuntu waiting in booting page(page with ubuntu logoo and 5 dot changing color from red to white) for half an hour.



this is fstab content



#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=1d24ddd9-b5ed-45f7-9770-9a599cecf4a3 / ext4 errors=remount-ro 0 1
/swapfile none swap sw 0 0```






command-line fstab boot-repair 18.10






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 23 at 11:31







B linux

















asked Jan 23 at 9:11









B linuxB linux

62




62













  • Is this a command that moves the whole disk storage to an interior directory?

    – xt1zer
    Jan 23 at 9:15






  • 2





    There are no direct revers comment. From live media you will have to mount your old / (root) dirirectory, and then move the relevant directories from /usr/lib/pepperflashplugin-nonfree/ to / . What are the output of ls -la /usr/lib/pepperflashplugin-nonfree/

    – Soren A
    Jan 23 at 9:17













  • Possible duplicate of Accidentally moved directories under root

    – Olorin
    Jan 23 at 9:19











  • @Olorin agreed but I do believe this warrants a personal approach ;-)

    – Rinzwind
    Jan 23 at 9:20











  • @Rinzwind but ... the only thing that would change is the path to be moved from? You'd still need to use busybox because the libraries would be moved around? Ah I see, live system is available. Never mind.

    – Olorin
    Jan 23 at 9:22





















  • Is this a command that moves the whole disk storage to an interior directory?

    – xt1zer
    Jan 23 at 9:15






  • 2





    There are no direct revers comment. From live media you will have to mount your old / (root) dirirectory, and then move the relevant directories from /usr/lib/pepperflashplugin-nonfree/ to / . What are the output of ls -la /usr/lib/pepperflashplugin-nonfree/

    – Soren A
    Jan 23 at 9:17













  • Possible duplicate of Accidentally moved directories under root

    – Olorin
    Jan 23 at 9:19











  • @Olorin agreed but I do believe this warrants a personal approach ;-)

    – Rinzwind
    Jan 23 at 9:20











  • @Rinzwind but ... the only thing that would change is the path to be moved from? You'd still need to use busybox because the libraries would be moved around? Ah I see, live system is available. Never mind.

    – Olorin
    Jan 23 at 9:22



















Is this a command that moves the whole disk storage to an interior directory?

– xt1zer
Jan 23 at 9:15





Is this a command that moves the whole disk storage to an interior directory?

– xt1zer
Jan 23 at 9:15




2




2





There are no direct revers comment. From live media you will have to mount your old / (root) dirirectory, and then move the relevant directories from /usr/lib/pepperflashplugin-nonfree/ to / . What are the output of ls -la /usr/lib/pepperflashplugin-nonfree/

– Soren A
Jan 23 at 9:17







There are no direct revers comment. From live media you will have to mount your old / (root) dirirectory, and then move the relevant directories from /usr/lib/pepperflashplugin-nonfree/ to / . What are the output of ls -la /usr/lib/pepperflashplugin-nonfree/

– Soren A
Jan 23 at 9:17















Possible duplicate of Accidentally moved directories under root

– Olorin
Jan 23 at 9:19





Possible duplicate of Accidentally moved directories under root

– Olorin
Jan 23 at 9:19













@Olorin agreed but I do believe this warrants a personal approach ;-)

– Rinzwind
Jan 23 at 9:20





@Olorin agreed but I do believe this warrants a personal approach ;-)

– Rinzwind
Jan 23 at 9:20













@Rinzwind but ... the only thing that would change is the path to be moved from? You'd still need to use busybox because the libraries would be moved around? Ah I see, live system is available. Never mind.

– Olorin
Jan 23 at 9:22







@Rinzwind but ... the only thing that would change is the path to be moved from? You'd still need to use busybox because the libraries would be moved around? Ah I see, live system is available. Never mind.

– Olorin
Jan 23 at 9:22












2 Answers
2






active

oldest

votes


















2














The reverse would be



sudo mv /usr/lib/pepperflashplugin-nonfree/* /


but that is from your actual system.



From a live session you need to mount the partition. After mounting the disk cd to it using command line and then issue is from THAT directory. That would make it:



cd /media/{device}/
sudo mv usr/lib/pepperflashplugin-nonfree/* .


In between you can check with ls usr/lib/pepperflashplugin-nonfree/ if you are in the correct directory.



All commands here should be executed after verifying they are correct and valid. So use a lot of ls commands to see what the results are. After the cd for instance ls usr/lib/pepperflashplugin-nonfree/ should list your file system files that belong in /.



Good luck with this :) Anyone can make a mistake but the experts then make sure there is no mistake in repairing the problem.





From Soren A:




if you move everything from /usr/lib/pepperflashplugin-nonfree/ to / you will get the old content of /usr/lib/pepperflashplugin-nonfree/ moved to / too. It is better to move the few relevant directories one by one.




My method works but you will also move the files that should be in /usr/lib/pepperflashplugin-nonfree/ so it makes a bit of a mess of /. To clean that up you need to remove these files or do a little bit extra to start with:



So the new approach would be ...



cd /media/{device}/
ls usr/lib/pepperflashplugin-nonfree/


Investigate the results. Anything that looks like it belongs in the root of the device can then be mv'd to /media/{device}/. Some observations: the files in / will all belong to user "root" and group "root" and will all be directories (1st char of the result of ls will be a d) or symlinks (l)






share|improve this answer


























  • If you move everything from /usr/lib/pepperflashplugin-nonfree/ to / you will get the old content of /usr/lib/pepperflashplugin-nonfree/ moved to / too. It is better to move the few relevant directories one by one.

    – Soren A
    Jan 23 at 9:20











  • @SorenA good call :X

    – Rinzwind
    Jan 23 at 9:21











  • Valid point, but I'd give rescuing the OS priority over salvaging the Pepper Flash plugin any time.

    – Jos
    Jan 23 at 10:10











  • Thank you. Any solution for my fstab file?

    – B linux
    Jan 23 at 11:47



















0














Once you are in the live system mount the disk where Ubuntu were installed and perform a command to move back in place all files you have move.



For example, on the live system suppose the computer disk are automatically mounted on /media/disk-name enter in it with a terminal:



cd /media/disk-name


from that path execute the following command which should put every thing in place



mv ./usr/lib/pepperflashplugin-nonfree/* ./


NOTE: the ./ is not an error it is important to determinate that is the current path you are working



to be more safe use the absolute path:



mv /media/disk-name/usr/lib/pepperflashplugin-nonfree/* /media/disk-name/


An annotation: when you use wildcard character and recursive command it is recommended to think twice before run the command, for example if you execute a rm -rf ./ and you are in the root directory, you delete your entire system, moving is also dangerous! Prefer to use always the full path and a filter with the wildcard character, this to avoid distraction error could be potentially destructive.






share|improve this answer


























  • I did. now ubuntu waiting in booting page(page with ubuntu logoo and 5 dot changing color from red to white) for half an hour.

    – B linux
    Jan 23 at 10:28











  • ok, may all answer you (me included) we do not think the boot directory are a mount point, please run again in to live system and add in the question fstab content, the path after mounting should be /media/disk-name/etc/fstab

    – AtomiX84
    Jan 23 at 10:31











  • this is fstab content: # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sda1 during installation UUID=1d24ddd9-b5ed-45f7-9770-9a599cecf4a3 / ext4 errors=remount-ro 0 1 /swapfile none swap sw 0 0

    – B linux
    Jan 23 at 11:08











  • Also I read other solution I use busybox ls and press ctrl+D after that on live system, but it doesn't work.(that was before I post the fstab content)

    – B linux
    Jan 23 at 11:15













Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1112196%2freverse-command%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









2














The reverse would be



sudo mv /usr/lib/pepperflashplugin-nonfree/* /


but that is from your actual system.



From a live session you need to mount the partition. After mounting the disk cd to it using command line and then issue is from THAT directory. That would make it:



cd /media/{device}/
sudo mv usr/lib/pepperflashplugin-nonfree/* .


In between you can check with ls usr/lib/pepperflashplugin-nonfree/ if you are in the correct directory.



All commands here should be executed after verifying they are correct and valid. So use a lot of ls commands to see what the results are. After the cd for instance ls usr/lib/pepperflashplugin-nonfree/ should list your file system files that belong in /.



Good luck with this :) Anyone can make a mistake but the experts then make sure there is no mistake in repairing the problem.





From Soren A:




if you move everything from /usr/lib/pepperflashplugin-nonfree/ to / you will get the old content of /usr/lib/pepperflashplugin-nonfree/ moved to / too. It is better to move the few relevant directories one by one.




My method works but you will also move the files that should be in /usr/lib/pepperflashplugin-nonfree/ so it makes a bit of a mess of /. To clean that up you need to remove these files or do a little bit extra to start with:



So the new approach would be ...



cd /media/{device}/
ls usr/lib/pepperflashplugin-nonfree/


Investigate the results. Anything that looks like it belongs in the root of the device can then be mv'd to /media/{device}/. Some observations: the files in / will all belong to user "root" and group "root" and will all be directories (1st char of the result of ls will be a d) or symlinks (l)






share|improve this answer


























  • If you move everything from /usr/lib/pepperflashplugin-nonfree/ to / you will get the old content of /usr/lib/pepperflashplugin-nonfree/ moved to / too. It is better to move the few relevant directories one by one.

    – Soren A
    Jan 23 at 9:20











  • @SorenA good call :X

    – Rinzwind
    Jan 23 at 9:21











  • Valid point, but I'd give rescuing the OS priority over salvaging the Pepper Flash plugin any time.

    – Jos
    Jan 23 at 10:10











  • Thank you. Any solution for my fstab file?

    – B linux
    Jan 23 at 11:47
















2














The reverse would be



sudo mv /usr/lib/pepperflashplugin-nonfree/* /


but that is from your actual system.



From a live session you need to mount the partition. After mounting the disk cd to it using command line and then issue is from THAT directory. That would make it:



cd /media/{device}/
sudo mv usr/lib/pepperflashplugin-nonfree/* .


In between you can check with ls usr/lib/pepperflashplugin-nonfree/ if you are in the correct directory.



All commands here should be executed after verifying they are correct and valid. So use a lot of ls commands to see what the results are. After the cd for instance ls usr/lib/pepperflashplugin-nonfree/ should list your file system files that belong in /.



Good luck with this :) Anyone can make a mistake but the experts then make sure there is no mistake in repairing the problem.





From Soren A:




if you move everything from /usr/lib/pepperflashplugin-nonfree/ to / you will get the old content of /usr/lib/pepperflashplugin-nonfree/ moved to / too. It is better to move the few relevant directories one by one.




My method works but you will also move the files that should be in /usr/lib/pepperflashplugin-nonfree/ so it makes a bit of a mess of /. To clean that up you need to remove these files or do a little bit extra to start with:



So the new approach would be ...



cd /media/{device}/
ls usr/lib/pepperflashplugin-nonfree/


Investigate the results. Anything that looks like it belongs in the root of the device can then be mv'd to /media/{device}/. Some observations: the files in / will all belong to user "root" and group "root" and will all be directories (1st char of the result of ls will be a d) or symlinks (l)






share|improve this answer


























  • If you move everything from /usr/lib/pepperflashplugin-nonfree/ to / you will get the old content of /usr/lib/pepperflashplugin-nonfree/ moved to / too. It is better to move the few relevant directories one by one.

    – Soren A
    Jan 23 at 9:20











  • @SorenA good call :X

    – Rinzwind
    Jan 23 at 9:21











  • Valid point, but I'd give rescuing the OS priority over salvaging the Pepper Flash plugin any time.

    – Jos
    Jan 23 at 10:10











  • Thank you. Any solution for my fstab file?

    – B linux
    Jan 23 at 11:47














2












2








2







The reverse would be



sudo mv /usr/lib/pepperflashplugin-nonfree/* /


but that is from your actual system.



From a live session you need to mount the partition. After mounting the disk cd to it using command line and then issue is from THAT directory. That would make it:



cd /media/{device}/
sudo mv usr/lib/pepperflashplugin-nonfree/* .


In between you can check with ls usr/lib/pepperflashplugin-nonfree/ if you are in the correct directory.



All commands here should be executed after verifying they are correct and valid. So use a lot of ls commands to see what the results are. After the cd for instance ls usr/lib/pepperflashplugin-nonfree/ should list your file system files that belong in /.



Good luck with this :) Anyone can make a mistake but the experts then make sure there is no mistake in repairing the problem.





From Soren A:




if you move everything from /usr/lib/pepperflashplugin-nonfree/ to / you will get the old content of /usr/lib/pepperflashplugin-nonfree/ moved to / too. It is better to move the few relevant directories one by one.




My method works but you will also move the files that should be in /usr/lib/pepperflashplugin-nonfree/ so it makes a bit of a mess of /. To clean that up you need to remove these files or do a little bit extra to start with:



So the new approach would be ...



cd /media/{device}/
ls usr/lib/pepperflashplugin-nonfree/


Investigate the results. Anything that looks like it belongs in the root of the device can then be mv'd to /media/{device}/. Some observations: the files in / will all belong to user "root" and group "root" and will all be directories (1st char of the result of ls will be a d) or symlinks (l)






share|improve this answer















The reverse would be



sudo mv /usr/lib/pepperflashplugin-nonfree/* /


but that is from your actual system.



From a live session you need to mount the partition. After mounting the disk cd to it using command line and then issue is from THAT directory. That would make it:



cd /media/{device}/
sudo mv usr/lib/pepperflashplugin-nonfree/* .


In between you can check with ls usr/lib/pepperflashplugin-nonfree/ if you are in the correct directory.



All commands here should be executed after verifying they are correct and valid. So use a lot of ls commands to see what the results are. After the cd for instance ls usr/lib/pepperflashplugin-nonfree/ should list your file system files that belong in /.



Good luck with this :) Anyone can make a mistake but the experts then make sure there is no mistake in repairing the problem.





From Soren A:




if you move everything from /usr/lib/pepperflashplugin-nonfree/ to / you will get the old content of /usr/lib/pepperflashplugin-nonfree/ moved to / too. It is better to move the few relevant directories one by one.




My method works but you will also move the files that should be in /usr/lib/pepperflashplugin-nonfree/ so it makes a bit of a mess of /. To clean that up you need to remove these files or do a little bit extra to start with:



So the new approach would be ...



cd /media/{device}/
ls usr/lib/pepperflashplugin-nonfree/


Investigate the results. Anything that looks like it belongs in the root of the device can then be mv'd to /media/{device}/. Some observations: the files in / will all belong to user "root" and group "root" and will all be directories (1st char of the result of ls will be a d) or symlinks (l)







share|improve this answer














share|improve this answer



share|improve this answer








edited Jan 23 at 9:41

























answered Jan 23 at 9:19









RinzwindRinzwind

206k28397528




206k28397528













  • If you move everything from /usr/lib/pepperflashplugin-nonfree/ to / you will get the old content of /usr/lib/pepperflashplugin-nonfree/ moved to / too. It is better to move the few relevant directories one by one.

    – Soren A
    Jan 23 at 9:20











  • @SorenA good call :X

    – Rinzwind
    Jan 23 at 9:21











  • Valid point, but I'd give rescuing the OS priority over salvaging the Pepper Flash plugin any time.

    – Jos
    Jan 23 at 10:10











  • Thank you. Any solution for my fstab file?

    – B linux
    Jan 23 at 11:47



















  • If you move everything from /usr/lib/pepperflashplugin-nonfree/ to / you will get the old content of /usr/lib/pepperflashplugin-nonfree/ moved to / too. It is better to move the few relevant directories one by one.

    – Soren A
    Jan 23 at 9:20











  • @SorenA good call :X

    – Rinzwind
    Jan 23 at 9:21











  • Valid point, but I'd give rescuing the OS priority over salvaging the Pepper Flash plugin any time.

    – Jos
    Jan 23 at 10:10











  • Thank you. Any solution for my fstab file?

    – B linux
    Jan 23 at 11:47

















If you move everything from /usr/lib/pepperflashplugin-nonfree/ to / you will get the old content of /usr/lib/pepperflashplugin-nonfree/ moved to / too. It is better to move the few relevant directories one by one.

– Soren A
Jan 23 at 9:20





If you move everything from /usr/lib/pepperflashplugin-nonfree/ to / you will get the old content of /usr/lib/pepperflashplugin-nonfree/ moved to / too. It is better to move the few relevant directories one by one.

– Soren A
Jan 23 at 9:20













@SorenA good call :X

– Rinzwind
Jan 23 at 9:21





@SorenA good call :X

– Rinzwind
Jan 23 at 9:21













Valid point, but I'd give rescuing the OS priority over salvaging the Pepper Flash plugin any time.

– Jos
Jan 23 at 10:10





Valid point, but I'd give rescuing the OS priority over salvaging the Pepper Flash plugin any time.

– Jos
Jan 23 at 10:10













Thank you. Any solution for my fstab file?

– B linux
Jan 23 at 11:47





Thank you. Any solution for my fstab file?

– B linux
Jan 23 at 11:47













0














Once you are in the live system mount the disk where Ubuntu were installed and perform a command to move back in place all files you have move.



For example, on the live system suppose the computer disk are automatically mounted on /media/disk-name enter in it with a terminal:



cd /media/disk-name


from that path execute the following command which should put every thing in place



mv ./usr/lib/pepperflashplugin-nonfree/* ./


NOTE: the ./ is not an error it is important to determinate that is the current path you are working



to be more safe use the absolute path:



mv /media/disk-name/usr/lib/pepperflashplugin-nonfree/* /media/disk-name/


An annotation: when you use wildcard character and recursive command it is recommended to think twice before run the command, for example if you execute a rm -rf ./ and you are in the root directory, you delete your entire system, moving is also dangerous! Prefer to use always the full path and a filter with the wildcard character, this to avoid distraction error could be potentially destructive.






share|improve this answer


























  • I did. now ubuntu waiting in booting page(page with ubuntu logoo and 5 dot changing color from red to white) for half an hour.

    – B linux
    Jan 23 at 10:28











  • ok, may all answer you (me included) we do not think the boot directory are a mount point, please run again in to live system and add in the question fstab content, the path after mounting should be /media/disk-name/etc/fstab

    – AtomiX84
    Jan 23 at 10:31











  • this is fstab content: # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sda1 during installation UUID=1d24ddd9-b5ed-45f7-9770-9a599cecf4a3 / ext4 errors=remount-ro 0 1 /swapfile none swap sw 0 0

    – B linux
    Jan 23 at 11:08











  • Also I read other solution I use busybox ls and press ctrl+D after that on live system, but it doesn't work.(that was before I post the fstab content)

    – B linux
    Jan 23 at 11:15


















0














Once you are in the live system mount the disk where Ubuntu were installed and perform a command to move back in place all files you have move.



For example, on the live system suppose the computer disk are automatically mounted on /media/disk-name enter in it with a terminal:



cd /media/disk-name


from that path execute the following command which should put every thing in place



mv ./usr/lib/pepperflashplugin-nonfree/* ./


NOTE: the ./ is not an error it is important to determinate that is the current path you are working



to be more safe use the absolute path:



mv /media/disk-name/usr/lib/pepperflashplugin-nonfree/* /media/disk-name/


An annotation: when you use wildcard character and recursive command it is recommended to think twice before run the command, for example if you execute a rm -rf ./ and you are in the root directory, you delete your entire system, moving is also dangerous! Prefer to use always the full path and a filter with the wildcard character, this to avoid distraction error could be potentially destructive.






share|improve this answer


























  • I did. now ubuntu waiting in booting page(page with ubuntu logoo and 5 dot changing color from red to white) for half an hour.

    – B linux
    Jan 23 at 10:28











  • ok, may all answer you (me included) we do not think the boot directory are a mount point, please run again in to live system and add in the question fstab content, the path after mounting should be /media/disk-name/etc/fstab

    – AtomiX84
    Jan 23 at 10:31











  • this is fstab content: # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sda1 during installation UUID=1d24ddd9-b5ed-45f7-9770-9a599cecf4a3 / ext4 errors=remount-ro 0 1 /swapfile none swap sw 0 0

    – B linux
    Jan 23 at 11:08











  • Also I read other solution I use busybox ls and press ctrl+D after that on live system, but it doesn't work.(that was before I post the fstab content)

    – B linux
    Jan 23 at 11:15
















0












0








0







Once you are in the live system mount the disk where Ubuntu were installed and perform a command to move back in place all files you have move.



For example, on the live system suppose the computer disk are automatically mounted on /media/disk-name enter in it with a terminal:



cd /media/disk-name


from that path execute the following command which should put every thing in place



mv ./usr/lib/pepperflashplugin-nonfree/* ./


NOTE: the ./ is not an error it is important to determinate that is the current path you are working



to be more safe use the absolute path:



mv /media/disk-name/usr/lib/pepperflashplugin-nonfree/* /media/disk-name/


An annotation: when you use wildcard character and recursive command it is recommended to think twice before run the command, for example if you execute a rm -rf ./ and you are in the root directory, you delete your entire system, moving is also dangerous! Prefer to use always the full path and a filter with the wildcard character, this to avoid distraction error could be potentially destructive.






share|improve this answer















Once you are in the live system mount the disk where Ubuntu were installed and perform a command to move back in place all files you have move.



For example, on the live system suppose the computer disk are automatically mounted on /media/disk-name enter in it with a terminal:



cd /media/disk-name


from that path execute the following command which should put every thing in place



mv ./usr/lib/pepperflashplugin-nonfree/* ./


NOTE: the ./ is not an error it is important to determinate that is the current path you are working



to be more safe use the absolute path:



mv /media/disk-name/usr/lib/pepperflashplugin-nonfree/* /media/disk-name/


An annotation: when you use wildcard character and recursive command it is recommended to think twice before run the command, for example if you execute a rm -rf ./ and you are in the root directory, you delete your entire system, moving is also dangerous! Prefer to use always the full path and a filter with the wildcard character, this to avoid distraction error could be potentially destructive.







share|improve this answer














share|improve this answer



share|improve this answer








edited Jan 23 at 9:31

























answered Jan 23 at 9:22









AtomiX84AtomiX84

845111




845111













  • I did. now ubuntu waiting in booting page(page with ubuntu logoo and 5 dot changing color from red to white) for half an hour.

    – B linux
    Jan 23 at 10:28











  • ok, may all answer you (me included) we do not think the boot directory are a mount point, please run again in to live system and add in the question fstab content, the path after mounting should be /media/disk-name/etc/fstab

    – AtomiX84
    Jan 23 at 10:31











  • this is fstab content: # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sda1 during installation UUID=1d24ddd9-b5ed-45f7-9770-9a599cecf4a3 / ext4 errors=remount-ro 0 1 /swapfile none swap sw 0 0

    – B linux
    Jan 23 at 11:08











  • Also I read other solution I use busybox ls and press ctrl+D after that on live system, but it doesn't work.(that was before I post the fstab content)

    – B linux
    Jan 23 at 11:15





















  • I did. now ubuntu waiting in booting page(page with ubuntu logoo and 5 dot changing color from red to white) for half an hour.

    – B linux
    Jan 23 at 10:28











  • ok, may all answer you (me included) we do not think the boot directory are a mount point, please run again in to live system and add in the question fstab content, the path after mounting should be /media/disk-name/etc/fstab

    – AtomiX84
    Jan 23 at 10:31











  • this is fstab content: # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sda1 during installation UUID=1d24ddd9-b5ed-45f7-9770-9a599cecf4a3 / ext4 errors=remount-ro 0 1 /swapfile none swap sw 0 0

    – B linux
    Jan 23 at 11:08











  • Also I read other solution I use busybox ls and press ctrl+D after that on live system, but it doesn't work.(that was before I post the fstab content)

    – B linux
    Jan 23 at 11:15



















I did. now ubuntu waiting in booting page(page with ubuntu logoo and 5 dot changing color from red to white) for half an hour.

– B linux
Jan 23 at 10:28





I did. now ubuntu waiting in booting page(page with ubuntu logoo and 5 dot changing color from red to white) for half an hour.

– B linux
Jan 23 at 10:28













ok, may all answer you (me included) we do not think the boot directory are a mount point, please run again in to live system and add in the question fstab content, the path after mounting should be /media/disk-name/etc/fstab

– AtomiX84
Jan 23 at 10:31





ok, may all answer you (me included) we do not think the boot directory are a mount point, please run again in to live system and add in the question fstab content, the path after mounting should be /media/disk-name/etc/fstab

– AtomiX84
Jan 23 at 10:31













this is fstab content: # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sda1 during installation UUID=1d24ddd9-b5ed-45f7-9770-9a599cecf4a3 / ext4 errors=remount-ro 0 1 /swapfile none swap sw 0 0

– B linux
Jan 23 at 11:08





this is fstab content: # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sda1 during installation UUID=1d24ddd9-b5ed-45f7-9770-9a599cecf4a3 / ext4 errors=remount-ro 0 1 /swapfile none swap sw 0 0

– B linux
Jan 23 at 11:08













Also I read other solution I use busybox ls and press ctrl+D after that on live system, but it doesn't work.(that was before I post the fstab content)

– B linux
Jan 23 at 11:15







Also I read other solution I use busybox ls and press ctrl+D after that on live system, but it doesn't work.(that was before I post the fstab content)

– B linux
Jan 23 at 11:15




















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1112196%2freverse-command%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

Mangá

Eduardo VII do Reino Unido