On Fri, 13 Apr 2018 11:01:40 +0100
Mick <[email protected]> wrote:
[…]
Yes, the broken symlinks are from the sysinit runlevel. I checked another
system of mine and it *also* has these broken symlinks ... :-/
So, whatever mistake I made, I must have made it at least twice! LOL!
I think this is nothing special and not your fault. I vaguely remember
having broken symlinks in runlevels too – was it also tmpfiles.dev or
udev-mount? I cannot recall it but I’m sure about those in folder
/etc/ssl/certs or regarded to the packages media-libs/mesa and
x11-libs/libXvMC for example.
Shouldn't the openrc or udev ebuild remove the symlinks, back when they became
depracated?
In a perfect world …
But I can well believe how hard it is to keep track of probably
externally changed symlinks or similar. Most of the time it works and
while at it, I like to say “thanks!”. Sporadically and being in
housekeeping mode, I run something like:
# find /{etc,lib,usr,var} -path /etc/config-archive -prune -o \
-type l -xtype l -print
to obtain exceptional cases but ignoring prior sanitised stuff.
[…]
Thank you for these symlinks Floyd,
I posted those s/symlinks/links/ ;-) only for conveniently mouse
clicking, maybe you can find more relevant things by a recursive grep
search in:
"$(portageq get_repo_path / gentoo)/metadata/news/"
I am using '/dev/sda1' notation for partitions in /etc/fstab, rather
than any of the /dev/disk/by-* symlinks.
…and probably also in:
/lib/udev/rules.d/
because rules using “*/by-*” syntax for their ‘SYMLINK+="..."’ foo for
your re-plugged devices – as you can see with:
$ udevadm monitor -u -p
udev-settle is not in my sysinit runlevel.
As it is supposed to be:
“udev and udev-trigger will be added to your sysinit runlevel, but not
udev-settle. udev-settle should not be added to a runlevel. Instead, if
a service needs this, it should add "need udev-settle" to its
dependencies.”
by the 2015-06-08-udev-init-scripts-changes.en.txt news.
--
Regards,
floyd
