From: amak79 <amak79@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: hfsprogs-540.1.linux3_6: bash: /bin/fsck.hfs: No such file or directory
Date: Thu, 05 Nov 2020 00:57:47 +0100 [thread overview]
Message-ID: <20201104235747.3C2OCT5aD9K5xAyhPOXYEnBgjB2z_DxjbUNJPpktRbY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26125@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]
New comment by amak79 on void-packages repository
https://github.com/void-linux/void-packages/issues/26125#issuecomment-722037739
Comment:
@Duncaen
```
# xbps-pkgdb -a
ERROR: base-files: broken symlink /lib32 (target: /usr/lib32)
ERROR: base-files: broken symlink /lib64 (target: /usr/lib)
ERROR: base-files: broken symlink /usr/lib64 (target: /usr/lib)
```
That dosn't look good. This is a new install (20201103) using the chroot method from the docs, and a x86_64 rootfs I created with mkrootfs. I examined the tarball I used and it doesn't have the `/lib32`, `/lib64` and `/usr/lib64` symlinks. It only has `/lib -> usr/lib`. After creating the `/lib64` synlink, both `fsck.hfs` and `mkfs.hfsplus` work.
@Chocimier
```
# df -hT
Filesystem Type Size Used Avail Use% Mounted on
devtmpfs devtmpfs 3.9G 0 3.9G 0% /dev
tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs tmpfs 3.9G 888K 3.9G 1% /run
/dev/sda5 ext4 52G 2.4G 49G 5% /
cgroup tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
tmpfs tmpfs 3.9G 12K 3.9G 1% /tmp
tmpfs tmpfs 787M 4.0K 787M 1% /run/user/1000
# echo $PATH
/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin
# PATH=/usr/bin fsck.hfs
bash: /usr/bin/fsck.hfs: No such file or directory
```
next prev parent reply other threads:[~2020-11-04 23:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 10:06 [ISSUE] " amak79
2020-11-04 11:12 ` sgn
2020-11-04 11:24 ` amak79
2020-11-04 15:05 ` sgn
2020-11-04 15:06 ` sgn
2020-11-04 15:16 ` amak79
2020-11-04 15:27 ` ericonr
2020-11-04 15:33 ` amak79
2020-11-04 15:38 ` amak79
2020-11-04 17:13 ` Duncaen
2020-11-04 17:23 ` Chocimier
2020-11-04 23:45 ` amak79
2020-11-04 23:54 ` amak79
2020-11-04 23:57 ` amak79 [this message]
2020-11-05 0:15 ` amak79
2020-11-05 14:13 ` [ISSUE] [CLOSED] " ahesford
2020-11-05 14:13 ` ahesford
2020-11-05 14:46 ` amak79
2020-11-05 14:46 ` amak79
2020-11-05 14:51 ` ericonr
2020-11-05 14:59 ` amak79
2020-11-05 15:04 ` ericonr
2020-11-05 15:07 ` amak79
2020-11-05 15:09 ` Duncaen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201104235747.3C2OCT5aD9K5xAyhPOXYEnBgjB2z_DxjbUNJPpktRbY@z \
--to=amak79@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).