После того, как я переместил и скопировал обратно всё содержимое корневой папки с помощью команды cp -pr у меня не работают права доступа. Я делал это на запущенной с флешки tails, может это имеет значение. Разрешения на файлах в порядке, но оба профиля, что root, что user имеют только привилегии «остальных», т. е. как бы не входят в те группы, в которые добавлены.
Вывод groups для пользователя:
wheel audio users tuiroot bin daemon sys adm disk wheel floppy tape videoПримеры: 1) Обычный пользователь:
tui@tux ~ $ sudo
sudo: unable to stat /etc/sudoers: Permission denied
sudo: no valid sudoers sources found, quitting
sudo: не удаётся инициализировать модуль политикиtux /home/tui # emerge sudo
Calculating dependencies... done!
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) app-admin/sudo-1.8.27-r1::gentoo
* sudo-1.8.27.tar.gz BLAKE2B SHA512 size ;-) ... [ ok ]
Traceback (most recent call last):
File "/usr/lib/portage/python3.6/pid-ns-init", line 127, in <module>
sys.exit(main(sys.argv))
File "/usr/lib/portage/python3.6/pid-ns-init", line 91, in main
proc = subprocess.Popen(args, executable=binary, **popen_kwargs)
File "/usr/lib64/python3.6/subprocess.py", line 709, in __init__
restore_signals, start_new_session)
File "/usr/lib64/python3.6/subprocess.py", line 1344, in _execute_child
raise child_exception_type(errno_num, err_msg, err_filename)
PermissionError: [Errno 13] Permission denied: '/usr/bin/sandbox'
* 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 app-admin/sudo-1.8.27-r1, Log file:
>>> '/var/tmp/portage/app-admin/sudo-1.8.27-r1/temp/build.log'
