On Wed, 28 Nov 2018 22:34:27 +0100 (CET), k...@aspodata.se wrote in
message <20181128213427.2e51f862a...@turkos.aspodata.se>:
> Rich Moen:
> > Quoting KatolaZ (kato...@freaknet.org):
> ...
> > > # ldd /bin/ps | grep "/usr"
> > > liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1
> > > (0x00007fd7f6ebc000)
> >
> > Yeah, those two are really annoying. FWIW, my server system has
> > older versions of those two utilities that do _not_ have that (IMO)
> > build error. Local packages will be an immediate resort, when/if I
> > hit that.
> ...
>
> Attached is a program to find possible /-/usr link breakage.
> It could possible be changed into an un-usrmerge-program if we want.
..yup, and packaged too. Put it in /sbin ? A shell or busybox
or binary version might be handy to debug those boot-oopses.
> Example output on a smallish system:
> # usr.pl
> /bin/nano
> /usr/lib64/libmagic.so.1
> /bin/ping
> /usr/lib64/libcrypto.so.1.0.0
..the output from my "life boat" install of
devuan_ascii_2.0.0_amd64_desktop-live.iso
is quite telling:
sda3:~# usr.pl
/bin/efibootmgr
/usr/lib/x86_64-linux-gnu/libefivar.so.1
/usr/lib/x86_64-linux-gnu/libefiboot.so.1
/bin/efibootdump
/usr/lib/x86_64-linux-gnu/libefivar.so.1
/usr/lib/x86_64-linux-gnu/libefiboot.so.1
/bin/ping
/usr/lib/x86_64-linux-gnu/libnettle.so.6
/sbin/mount.nfs
/usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2
/usr/lib/x86_64-linux-gnu/libkrb5.so.3
/usr/lib/x86_64-linux-gnu/libk5crypto.so.3
/usr/lib/x86_64-linux-gnu/libkrb5support.so.0
/sbin/dhclient
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.2
/sbin/rpcbind
/usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2
/usr/lib/x86_64-linux-gnu/libkrb5.so.3
/usr/lib/x86_64-linux-gnu/libk5crypto.so.3
/usr/lib/x86_64-linux-gnu/liblz4.so.1
/usr/lib/x86_64-linux-gnu/libkrb5support.so.0
/sbin/crda
/usr/lib/x86_64-linux-gnu/libssl.so.1.1
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1
/sbin/tc
/usr/lib/x86_64-linux-gnu/libelf.so.1
/sbin/umount.udisks2
/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
/usr/lib/x86_64-linux-gnu/libudisks2.so.0
/usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0
/usr/lib/x86_64-linux-gnu/libffi.so.6
/sbin/wpa_supplicant
/usr/lib/x86_64-linux-gnu/libpcsclite.so.1
/usr/lib/x86_64-linux-gnu/libssl.so.1.0.2
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.2
/sbin/rpc.statd
/usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2
/usr/lib/x86_64-linux-gnu/libkrb5.so.3
/usr/lib/x86_64-linux-gnu/libk5crypto.so.3
/usr/lib/x86_64-linux-gnu/libkrb5support.so.0
/sbin/regdbdump
/usr/lib/x86_64-linux-gnu/libssl.so.1.1
/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1
/sbin/discover
/usr/lib/libdiscover.so.2
/sbin/sgdisk
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
/sbin/gdisk
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
/sbin/cgdisk
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
/sbin/sm-notify
/usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2
/usr/lib/x86_64-linux-gnu/libkrb5.so.3
/usr/lib/x86_64-linux-gnu/libk5crypto.so.3
/usr/lib/x86_64-linux-gnu/libkrb5support.so.0
/sbin/fixparts
/usr/lib/x86_64-linux-gnu/libstdc++.so.6
/sbin/showmount
/usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2
/usr/lib/x86_64-linux-gnu/libkrb5.so.3
/usr/lib/x86_64-linux-gnu/libk5crypto.so.3
/usr/lib/x86_64-linux-gnu/libkrb5support.so.0
/sbin/xtables-multi
/usr/lib/x86_64-linux-gnu/libip4tc.so.0
/usr/lib/x86_64-linux-gnu/libip6tc.so.0
/usr/lib/x86_64-linux-gnu/libxtables.so.12
sda3:~#
..note that I did toss out Xfce for LXQt to ease my workload fixing
vdev or eudev, both are too polite to help build me a bootable initrd.
--
..med vennlig hilsen = with Kind Regards from Arnt Karlsen
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
