On 2 May 2021 at 17:12, Qiyu Yan wrote:
Subject: Re: Question about broken link files?
From: Qiyu Yan <yanqiyu(a)fedoraproject.org>
To: Community support for Fedora users <users(a)lists.fedoraproject.org>
Date sent: Sun, 02 May 2021 17:12:41 +0800
Send reply to: Community support for Fedora users <users(a)lists.fedoraproject.org>
在 2021-05-02星期日的 18:05 +1000,Michael D. Setzer II via users写道:
> Just upgraded my notebook to sdd drive and then did dnf
> update to Fedora 33.
>
> Ran the following command in / to see what it finds.
> find . -xtype l >/badlinks
>
> Summary of results of broken links by top directory
> /etc 15
> /home 17
> /proc 170
> /root 2
> /run 145
> /usr 325
> 674
>
> Not an awful lot, but wonder if they should be fixed or
> just left alone?
> One was projectM have a link to some fonts, but the fonts
> and the directory they are suppose to be in don't exist.
Maybe those fonts will can be installed in another package, or moved
due to licensing problems.
> The there are a number K50netconsole files in /etc
I did not see such file in my system.
> /proc and /run not sure of??
Thanks assumed there was probable something more to
those in the /proc and /run. But about half are in /usr and
K50netconsole are in all the rc.d directories.
The projectM ones
ls -l /usr/share/projectM/fonts/*.ttf
lrwxrwxrwx. 1 root root 33 Feb 22 08:30
/usr/share/projectM/fonts/VeraMono.ttf -> /usr/share/fonts/TTF/VeraMono.ttf
lrwxrwxrwx. 1 root root 29 Feb 22 08:30 /usr/share/projectM/fonts/Vera.ttf ->
/usr/share/fonts/TTF/Vera.ttf
Not only the two fonts don't exist, but neither does the
TTF directory. Assume at some time the fonts and
directory did exist, but a dnf whatprovides finds no
reference.
Thanks for the quick responses, guess not worth really
working at. Had also noticed that some links in /lib64
have ../../lib64?? Assume that is because original files
were in different directories, but now directors are sym
links to others.
I started on a 1963 IBM 1130 with 4K ram and punched
cards and 5M disk.. So, had to be very clean on what you
had.
If its not causing problems, I think those dangling links should not
be
a problem.
For example, podman-docker is supposed to set up a symlink:
/run/docker.sock -> /run/podman/podman.sock
to let programs hardcoded to talk to docker socket to communicate with
podman daemon. While when podman is not running, the symlink becomes
dangling.
Or symlink is used for other reasons, for example systemd creates
/run/systemd/units/invocation:<unit name> which points to its
invocation id.
> /home seem to be mostly files in .wine
>
> Thanks..
>
>
> +------------------------------------------------------------+
> Michael D. Setzer II - Computer Science Instructor
> (Retired)
> mailto:mikes@guam.net
> mailto:msetzerii@gmail.com
> Guam - Where America's Day Begins
> G4L Disk Imaging Project maintainer
> http://sourceforge.net/projects/g4l/
> +------------------------------------------------------------+
--
Qiyu Yan
GPG keyid: 0x4FC914F065F2DF12
About:
https://fedoraproject.org/wiki/User:Yanqiyu