Раздел смонтирован вот так
Код: Выделить всё
gentoo ~ # mount |grep usr
/dev/mapper/vg0-usr on /usr type ext4 (rw,noatime)
Теперь нормально не работает:
Код: Выделить всё
gentoo ~ # emerge iftop
Calculating dependencies... done!
>>> Verifying ebuild manifests
>>> Emerging (1 of 2) net-libs/libpcap-1.3.0-r1
* libpcap-1.3.0.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ]
sandbox:main could not open the sandbox rc file: /usr/share/sandbox/sandbox.bashrc: Permission denied
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
>>> Failed to emerge net-libs/libpcap-1.3.0-r1, Log file:
>>> '/var/tmp/portage/net-libs/libpcap-1.3.0-r1/temp/build.log'
* Messages for package net-libs/libpcap-1.3.0-r1:
* The ebuild phase 'unpack' has exited unexpectedly. This type of behavior
* is known to be triggered by things such as failed variable assignments
* (bug #190128) or bad substitution errors (bug #200313). Normally, before
* exiting, bash should have displayed an error message above. If bash did
* not produce an error message above, it's possible that the ebuild has
* called `exit` when it should have called `die` instead. This behavior
* may also be triggered by a corrupt bash binary or a hardware problem
* such as memory or cpu malfunction. If the problem is not reproducible or
* it appears to occur randomly, then it is likely to be triggered by a
* hardware problem. If you suspect a hardware problem then you should try
* some basic hardware diagnostics such as memtest. Please do not report
* this as a bug unless it is consistently reproducible and you are sure
* that your bash binary and hardware are functioning properly.
Пробовал
Код: Выделить всё
FEATURES="-sandbox -usersandbox" emerge -av sandbox
sandbox пересетапился, но после я также не могу ничего установить. Появляется таже ошибка что и выше.
Также пробовал выдать 777 на /usr/share/sandbox/sandbox.bashrc
Пробовал загрузить архив портежей, Пробовал вернуть назад usr на /
Вообщем ничего как-то не помогло.
Подскажите как вернуть к жизни портежи.