Please Help... Accidentally renamed a file in /lib/ Raspbian Buster

[etherwar]

I really thought it wouldn't be that hard to figure this out..

I have 4 files in my /lib/ directory (Raspbian Buster)... 3 of them seem to be symlinks

1. cpp
2. ld-linux.so.3
3. ld-linux-armhf.so.3
and one file that, while trying to exit a black video played via omxplayer, I accidentally seemed to have renamed:
4. klibc-fAGGTaZfOmYXUytsXgfSuL5MT48.so

I have many directories in /lib/ as well that seem unharmed.

I've tried many different things at this point, could someone please look in their /lib/ folder and tell me what the filename is supposed to be?

Thanks,
E

[pfletch101]

Unless you have also been messing with my /lib folder , the strange name is correct. I have a file with precisely the same name. Why do you think that you renamed it?

[HawaiianPi]

You couldn't have renamed anything in /lib without using sudo (unless you were logged in as root, which is disabled by default in Raspbian).

[etherwar]

Lmao.

Thanks for the reassurance. I (probably stupidly) was running a file explorer in root mode as I am having to do a bunch of messing about as root as a process of installing OpenCV with gstreamer capabilities.

The reason I thought I renamed it is because I am creating a RPi that is a dedicated security feed viewing station/analysis console that can do things like count vehicles that can learn the vehicles that enter and leave on a daily basis and pop up alerts in various scenarios related to issues like that as well as within certain periods of time. I was experimenting with a black video feed placeholder, and ran omxplayer using the black video. At this point in time the black video went fullscreen and I was attempting to ctrl - c/ ctrl -d/ ctrl-x etc. when none of that worked, I dumbly started clicking and trying to figure out the keyboard controls. None of that worked, but when the video finally ended, /lib/ was open in the file explorer that was being run as root and that strange filename was selected. I assumed I had done that.

It's strange that I can't find any information about that file doing a google search, but oh well... I appreciate the help!

[trejan]

It's strange that I can't find any information about that file doing a google search, but oh well... I appreciate the help!

It is because the filename contains a hash of the symbols + addresses so the hash value changes if you compile it on something else or use a different version of the klibc library. The hash is there for versioning.

[etherwar]

It is because the filename contains a hash of the symbols + addresses so the hash value changes if you compile it on something else or use a different version of the klibc library. The hash is there for versioning.

That makes complete sense. I appreciate the clarification. That must be why it doesn't show up in the linked files related to klibc, which I was browsing trying to figure this out before I just burned another clean image and put into another rpi4 and saw it was the same name.

[moonstroller]

...... "...During the Linux startup process, klibc is loaded from within a temporary RAM file system, initramfs. It is incorporated by default into initial RAM file systems that are created by the mkinitramfs script in Debian[7] and Ubuntu. Furthermore, it has a set of small Unix utilities that are useful in early user space: cpio, dash, fstype, mkdir, mknod, mount, nfsmount, run-init, etc. all using the klibc library.[8] An alternate strategy is to include everything in one executable, like BusyBox, which determines the requested applet via arguments or a symlink..." ~Wikipedia.

Did you download a program made for Debian, Ubuntu, etc... something like a Ham Radio program? That can be used for scanning frequency bands, locating Airplanes, (skyspy)... etc?