In my user login, I created a new folder in Dolphin, and gave it ‘A-install-logs’ as a directory name.
I moved all of my install logs into it.
Now when I open Dolphin, that directory is no longer there. As in gone, disappeared.
It is not under hidden files.
Any way to find it and do it right?? So it doesn’t get lost.
I’d really like those install logs back.
They are probably out in the ‘system’ logs somewhere, but I don’t want to dig through that load for 6 or 7 files.
How I do such things:
Do you remember one of the file names or a part of the name? Then you may query the machine: find / -name ‘NAME’.
I’m a big fan of the “locate” tool.
Unlike default tools on your system like Find, its lightning fast on any system even those with minimal CPU and RAM.
You can install it by running the following command
zypper in mlocate
After installed, the database of your entire system’s directory tree will be updated every 24 hrs
But you don’t want to wait up to 24 hrs after a new install or a recent change, right?
So, whenever you want to update the database immediately, run
updatedb
After that, you can search for any string (sequence of characters) that is exactly what you’re looking for…
You can search for simply a filename like
locate resolv.conf
Or a name fragment
locate resol
You can specify a location by including the directory path
locate /etc/reso
And Regular Expressions including wildcards are supported.
Also,
I don’t know what you mean by “moved” your logs…
Did you actually copy and not move?
If you moved your files, did you also re-configure your system to write logs to the new location?
If you’re on BTRFS, IIRC log file locations are not excluded from snapshots, so you can recover either individual files or do a complete partition rollback if needed.
TSU
I know how to use Midnight Commander(have for years, even in Windows). But why ??? would I want to F7 ‘mkdir’ when I had already made it, and moved files to it, then verified the move. Then starting Dolphin again later, the directory I made (with files moved to to it) was GONE.
Either you missed what I was asking, or you are imparting another Linux lesson.
Thanks, and yes, I tried that. All the files that were lost when the directory went poof( for what ever reason) were named ‘install-log-for-<file name>’, and searching on the first two words still couldn’t find them.
I created the directory in Dolphin, highlighted the files to put in it in another instance of Dolphin, dragged them to the Dolphin empty directory I created, and selected ‘move here’ from the context menu.
I do not user BTRFS.
But I will add the ‘locate’ tool you suggested. It won’t help me find what has been lost, but in the future may stop it happening.
In summary, I guess those files and the directory I created are wasting away in the system 0’s an 1’s somewhere, never to be seen again. <sigh>.
In addition to my response above;
I most always create a copy of the install log after YaST finishes and shows me what was installed. They are not ‘system’ logs.
Just a copy, and paste into Kate and saved in my home directory. I do this simply because the system logs are confusing to me, and I want MY own record of what I installed so I know what to take out later if I don’t like it. Someplace I can find it easily without having to do a bunch of terminal work.
So, no, I didn’t re-configure the system to write logs to a new location.
Eh, locate is nice. but it doesn’t search everything… F.e. not Trash. Since nobody suggested so, did you check the Trash. Just asking since I’ve found back files in there that I thought were missing myself. Most likely my own doing with dragging, dropping, moving files in a couple of dolphin windows.
Yes, I did check trash, the graphic version in Dolphin and Krusader and mc, and in a terminal as root. Sadly, nothing there.
I guess I should have ask this above.
Can I install ‘locate’ now and still try to find that directory and it’s files with it now?
I had assumed I needed it before things went upside down with that directory.
The machine has been restarted several times since things went missing if that makes a difference.
‘mlocate’ can be installed at any time. It can be configured in many ways, but the default on openSUSE is to scan the filesystems mounted at boot. Even though the package name has changed, the command is still ‘locate STRING_HERE’ , example:
knurpht@Knurpht-HP:~> locate .config | head
/etc/manpath.config
/etc/apparmor.d/usr.lib.dovecot.config
/etc/apparmor.d/local/usr.lib.dovecot.config
/etc/libssh/libssh_client.config
/etc/libssh/libssh_server.config
/etc/skel/.config
/home/beheerder/.config
/home/beheerder/.config/Trolltech.conf
/home/beheerder/.config/akregatorrc
/home/beheerder/.config/autostart
knurpht@Knurpht-HP:~>
AFAIK activating it on Leap 15.1 requires running
sudo updatedb
Depending on disk types, partition sizes etc etc, the initial build of the database may take a while. But, once that is done… it’s much faster than ‘find STRING_HERE’.
F7 was an inexplicable brain lapse. I meant F9 and find file (ESC ?).
I’m facing the same problem and finally it solved!!! Thank you so much… tsu2;
Regards
Shery