Gentoo i błędy przy aktualizacji

[HaPe 242]

Witam,

mógłby jakiś znawca Gentoo oświecić mnie jakie kroki należy podjąć, aby uporać się z tym problemem?

virt1 ~ # uname -a
Linux virt1 2.6.32-042stab078.26 #1 SMP Wed Jun 19 11:05:34 MSK 2013 x86_64 Intel(R) Xeon(R) CPU E5520 @ 2.27GHz GenuineIntel GNU/Linux
virt1 ~ # emerge --update --deep --newuse world

 * IMPORTANT: 9 news items need reading for repository 'gentoo'.
 * Use eselect news to read news items.


 * IMPORTANT: config file '/etc/portage/repos.conf/gentoo.conf' needs updating.
 * See the CONFIGURATION FILES section of the emerge
 * man page to learn how to update config files.
Calculating dependencies... done!

>>> Verifying ebuild manifests
>>> Running pre-merge checks for sys-libs/pam-1.1.6-r4

>>> Emerging (1 of 142) sys-kernel/linux-headers-3.9
 * gentoo-headers-base-3.9.tar.xz SHA256 SHA512 WHIRLPOOL size ;-) ...   [ ok ]
 * gentoo-headers-3.9-1.tar.xz SHA256 SHA512 WHIRLPOOL size ;-) ...      [ ok ]
/usr/lib64/portage/bin/phase-functions.sh: line 742: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 742: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 742: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 775: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 778: /dev/null: Permission denied
/usr/portage/profiles/base/profile.bashrc: line 5: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 198: /dev/null: Permission denied
>>> Unpacking source...
/usr/lib64/portage/bin/phase-functions.sh: line 198: /dev/null: Permission denied
>>> Source unpacked in /var/tmp/portage/sys-kernel/linux-headers-3.9/work
/usr/lib64/portage/bin/phase-functions.sh: line 198: /dev/null: Permission denied
sh: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 742: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 742: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 742: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 775: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 778: /dev/null: Permission denied
/usr/portage/profiles/base/profile.bashrc: line 5: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 198: /dev/null: Permission denied
>>> Preparing source in /var/tmp/portage/sys-kernel/linux-headers-3.9/work ...
/usr/lib64/portage/bin/phase-functions.sh: line 198: /dev/null: Permission denied
>>> Source prepared.
/usr/lib64/portage/bin/phase-functions.sh: line 198: /dev/null: Permission denied
sh: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 742: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 742: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 742: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 775: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 778: /dev/null: Permission denied
/usr/portage/profiles/base/profile.bashrc: line 5: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 198: /dev/null: Permission denied
>>> Configuring source in /var/tmp/portage/sys-kernel/linux-headers-3.9/work ...
/usr/lib64/portage/bin/phase-functions.sh: line 198: /dev/null: Permission denied
>>> Source configured.
/usr/lib64/portage/bin/phase-functions.sh: line 198: /dev/null: Permission denied
sh: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 742: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 742: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 742: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 775: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 778: /dev/null: Permission denied
/usr/portage/profiles/base/profile.bashrc: line 5: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 198: /dev/null: Permission denied
>>> Compiling source in /var/tmp/portage/sys-kernel/linux-headers-3.9/work ...
/usr/lib64/portage/bin/phase-functions.sh: line 198: /dev/null: Permission denied
>>> Source compiled.
/usr/lib64/portage/bin/phase-functions.sh: line 198: /dev/null: Permission denied
sh: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 742: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 742: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 742: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 775: /dev/null: Permission denied
/usr/lib64/portage/bin/phase-functions.sh: line 778: /dev/null: Permission denied
/usr/portage/profiles/base/profile.bashrc: line 5: /dev/null: Permission denied
>>> Test phase [not enabled]: sys-kernel/linux-headers-3.9
sh: /dev/null: Permission denied

>>> Install linux-headers-3.9 into /var/tmp/portage/sys-kernel/linux-headers-3.9/image/ category sys-kernel
chmod: cannot access `*': No such file or directory
make headers_install INSTALL_HDR_PATH=/var/tmp/portage/sys-kernel/linux-headers-3.9/image///usr/include/.. ARCH=x86 CROSS_COMPILE=x86_64-pc-linux-gnu-
make: *** No rule to make target `headers_install'.  Stop.
emake failed
 * ERROR: sys-kernel/linux-headers-3.9::gentoo failed (install phase):
 *   (no error message)
 *
 * Call stack:
 *     ebuild.sh, line   93:  Called src_install
 *   environment, line 2839:  Called kernel-2_src_install
 *   environment, line 2013:  Called install_headers
 *   environment, line 1894:  Called die
 * The specific snippet of code:
 *           emake headers_install INSTALL_HDR_PATH="${D}"/${ddir}/.. ${xmakeopts} || die;
 *
 * If you need support, post the output of `emerge --info '=sys-kernel/linux-headers-3.9::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-kernel/linux-headers-3.9::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-kernel/linux-headers-3.9/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-kernel/linux-headers-3.9/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-kernel/linux-headers-3.9/work'
 * S: '/var/tmp/portage/sys-kernel/linux-headers-3.9/work/gentoo-headers-base-3.9'

>>> Failed to emerge sys-kernel/linux-headers-3.9, Log file:

>>>  '/var/tmp/portage/sys-kernel/linux-headers-3.9/temp/build.log'

 * Messages for package sys-kernel/linux-headers-3.9:

 * ERROR: sys-kernel/linux-headers-3.9::gentoo failed (install phase):
 *   (no error message)
 *
 * Call stack:
 *     ebuild.sh, line   93:  Called src_install
 *   environment, line 2839:  Called kernel-2_src_install
 *   environment, line 2013:  Called install_headers
 *   environment, line 1894:  Called die
 * The specific snippet of code:
 *           emake headers_install INSTALL_HDR_PATH="${D}"/${ddir}/.. ${xmakeopts} || die;
 *
 * If you need support, post the output of `emerge --info '=sys-kernel/linux-headers-3.9::gentoo'`,
 * the complete build log and the output of `emerge -pqv '=sys-kernel/linux-headers-3.9::gentoo'`.
 * The complete build log is located at '/var/tmp/portage/sys-kernel/linux-headers-3.9/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-kernel/linux-headers-3.9/temp/environment'.
 * Working directory: '/var/tmp/portage/sys-kernel/linux-headers-3.9/work'
 * S: '/var/tmp/portage/sys-kernel/linux-headers-3.9/work/gentoo-headers-base-3.9'
virt1 ~ #

Plik w /etc/make.profile jest zlinkowany do wersji 13.0.

Edytowano Sierpień 6, 2013 przez Aimer (zobacz historię edycji)

[tym 205]

chmod 666 /dev/null

[Pan Kot 1535]

Ew. 777 jakby nie pomogło.

[blackfire 185]

666. Jaki sens ma +x dla /dev/null? @Aimer, Sprawdź przy okazji (ls -l /dev/null), czy /dev/null jest urządzeniem, bo może coś je podmieniło zwykłym plikiem. Pierwsza kolumna wyniku ls ma wyglądać tak: crw-rw-rw- (i ew. kropka jak używasz SELinuxa)

Edytowano Sierpień 7, 2013 przez blackfire (zobacz historię edycji)

[Gość patrys]

Po sprawdzeniu utwórz je, w sumie to można wywalić odrazu odejdzie jedna komenda:

rm /dev/null && mknod -m 666 /dev/null c 1 3

@Archi: nawet nie mów, że wszędzie gdzie widzisz "Permission denied" dajesz 777?

[Pan Kot 1535]

@blackfire @patrys

99.9% programów/skryptów/aplikacji powinna wyłącznie czytać i pisać do /dev/null, ale spotkałem się z jednym, który bez +x nie ruszał, nie powiem Ci niestety jak ta apka się nazywała bo już nie pamiętam, ale nie wykluczam że była prawdopodobnie słabo napisana.

[HaPe 242]

Dzięki Panowie. Nie pomyślałem, że chmody mogą być nie tak. Niby był kłopot z dostępem do tego pliku, ale nie wpadło mi na myśl, że coś może być nie tak, bo z roota zwyczajnie update był robiony.

 

Zapytam jeszcze czy testował ktoś grsecurity na openvz?