On Fri, 13 Mar 2020 18:49:58 -0600 home user <mattisonw@xxxxxxxxxxx> wrote: > [liveuser@localhost-live ~]$ su - > [root@localhost-live ~]# mount /dev/sda6 /mnt/sysimage > mount: /mnt/sysimage: mount point does not exist. > [root@localhost-live ~]# > > I do not know how to determine what to use as the second argument. Samuel has already answered your question to your satisfaction, so this is just for future reference. At this point you could have used man mount to see how mount works. With your background you are fully capable of resolving simple errors like this. Mount doesn't create the mount point, so my memory was faulty and the mount point didn't already exist. Samuel got around this by using plain /mnt, as that always exists, but if there is anything else trying to use /mnt/[some directory], that will cause problems (unlikely from an ISO, though). > This might be easier if we make this more concrete. So let's suppose > I want to do > "journalctl" > or > "less /var/log/dnf" > After booting up the live image and doing the "su -", what do I do? Something that has worked for me in the past is to chroot to the installed system as you already are and then run dnf update to bring the system fully up to date. Often that will resolve a problem. But all this is irrelevant if the problem is hardware. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx
