← All posts tagged Gentoo

Linux Gentoo security ? Mac Какой mandatory access control позволит разграничить мне права для скриптоговнища, которое живёт в виде кучи симлинков с разными именами на один говноскрипт, который по имени понимает что именно запускать, без дополнительных обёрток на каждый симлинк?
musl Gentoo portage ? qemu >> Emerging (1 of 32) sys-libs/ncurses-6.0-r1::gentoo * ncurses-6.0.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ]
/usr/lib/portage/python2.7/phase-functions.sh: line 234: 29396 Segmentation fault install -m${PORTAGE_WORKDIR_MODE:-0700} -d "${WORKDIR}"
* ERROR: sys-libs/ncurses-6.0-r1::gentoo failed (unpack phase):
* Failed to create dir '/var/tmp/portage/sys-libs/ncurses-6.0-r1/work'

# ulimit -c

И хули он мне не высрал core dump?
mutt Gentoo # Post-release hot-fixes grabbed from HG, this is what all following
# patches are based on in my Mercurial patchqueue (mq).

# must have fixes to compile or behave correctly, upstream
# ignores, disagrees or simply doesn't respond/apply

# the big feature patches that upstream doesn't want to include, but
# nearly every distro has due to their usefulness
Gentoo systemrescuecd system-rescue-cd.org
СЯУ можно обновлять установленный sysresccd, не трогая доустановленный в него хлам, используя присутствующую в нём искаропки с незапамятных времён прогрессивную технологию aufs + loopback block device.
будующее Gentoo If a bug report pertains to a specific package, then you enter the package's directory in your copy of the gentoo git repository (or perhaps the online version which should always be more or less up to date) and read the metadata.xml file you find there. When metadata.xml lists a single maintainer, then you assign the bug to that maintainer. When the file lists multiple entries, then you assign the bug to the first <maintainer>, and CC the other <maintainer>(s). If you find that metadata.xml lists inappropriate and/or confusing contact information, then make a note of that in a comment on the bug report and assign/CC the bug report as well as you can.
Gentoo paludis Кривой костыль для eapply_user в paludis:

--- /usr/libexec/paludis/6/build_functions.bash 2016-02-27 23:33:13.028855100 +0300
+++ /tmp/p 2016-02-27 23:33:09.132142253 +0300
@@ -75,9 +75,35 @@
ebuild_need_extglob eapply

+# Ported epatch_user
— return 0
+ : ${EPATCH_USER_SOURCE:=${PORTAGE_CONFIGROOT%/}/etc/portage/patches}
+ [[ $# -ne 0 ]] && die "epatch_user takes no options"
+ # Allow multiple calls to this function; ignore all but the first
+ local applied="${T}/epatch_user.log"
+ [[ -e ${applied} ]] && return 2
+ # don't clobber any EPATCH vars that the parent might want
+ local EPATCH_SOURCE check
+ for check in ${CATEGORY}/{${P}-${PR},${P},${PN}}{,:${SLOT%/*}}; do
+ if [[ -d ${EPATCH_SOURCE} ]] ; then
+ EPATCH_SUFFIX="patch" \
+ EPATCH_FORCE="yes" \
+ EPATCH_MULTI_MSG="Applying user patches from ${EPATCH_SOURCE} ..." \
+ epatch
+ echo "${EPATCH_SOURCE}" > "${applied}"
+ return 0
+ fi
+ done
+ echo "none" > "${applied}"
+ return 1

Gentoo paludis говно 22:51:32]<L29Ah> /usr/libexec/paludis/6/build_functions.bash:eapply_user()
/usr/libexec/paludis/6/build_functions.bash- return 0
22:51:33]<L29Ah> T_T
22:52:50]<ciaranm> compliant implementation
22:52:57]<ciaranm> feel free to implement something else if you want it
22:53:01]<ciaranm> but only if you do it properly