Search Criteria
Package Details: di 6.0.0-2
Package Actions
Git Clone URL: | https://aur.archlinux.org/di.git (read-only, click to copy) |
---|---|
Package Base: | di |
Description: | A disk information utility, displaying everything (and more) that your df command does |
Upstream URL: | https://diskinfo-di.sourceforge.io/ |
Licenses: | zlib |
Submitter: | arojas |
Maintainer: | uffe |
Last Packager: | uffe |
Votes: | 6 |
Popularity: | 0.080074 |
First Submitted: | 2019-04-03 06:17 (UTC) |
Last Updated: | 2025-07-15 11:35 (UTC) |
Latest Comments
vgivanovic commented on 2025-07-14 21:07 (UTC) (edited on 2025-07-14 21:11 (UTC) by vgivanovic)
On my system (6.15.6-arch1-1, ZFS on root), the 6.0.0-1 package tries to install into /usr/lib64, and when it finds that /usr/lib already exists (as a link), it creates a directory of the same name. (The package 'filesystem' installs /lib64 as a symbolic link pointing to /lib.)
This prevents booting. A kernel panic reports "No working 'init' found".
Here is a snippet from 'yay -Sa di':
I went ahead and installed di-6.0.0-1 (using --overwrite=/usr/lib64) and put /usr/lib64/libdi.so* into /usr/lib and /usr/lib64/pkgconfig/di.pc into /usr/lib/pkgconfig. Then I forcibly re-created the symbolic link /usr/lib64 to point to lib.
All seems well.