lego12239

You can't avoid systemd simply by installing openrc. Many binaries of systemd package can still be in a system. In funtoo you can easily do: epro mix-ins no-systemd In gentoo(when i tried it) this can't be done so easy. I didn't say that in gentoo net conf is complex, i said that funtoo do it better ;-).

Gentoo doesn't allow easily eliminate systemd. Networking configuration in funtoo is better. The one thing annoying - i can't find in-system documentation for net stuff (man pages); and every time i configure nic, i need to go to /etc/netif.d/ to remember how parameters are written.

I can, but i wan't :-). And funtoo give me this possibility to live as i want.

Except other significant things, funtoo allow you to live without systemd. In our days this is very important.

Bad colons. I've removed colons from mduuid and grub now boot the system without problems.

Hi, all. May be anybody know an answer and i can save some time :-). If i do an external redirect in exim, what MAIL FROM is used exim in smtp connection to an external server? example /etc/aliases: me: me@gmail.com example email: MAIL FROM <somebody@his.server> RCPT TO <me@my.server> my.server redirect it to gmail according to aliases: MAIL FROM <?????> RCPT TO <me@gmail.com>

Hi, all! My grub doesn't see mdraid (raid1) by mduuid. /boot/grub/grub.cfg: set timeout=2 menuentry 'Funtoo, 4.14.97' { insmod gzio insmod mdraid1x insmod part_msdos insmod ext2 set root='(mduuid/232d2317:1469bc36:e85fd34c:9136eb63,msdos1)' echo 'Loading kernel...' linux /boot/vmlinuz-4.14.97-nat root=LABEL=rootfs ro domdadm echo 'Loading initial ramdisk...' initrd /boot/initramfs-genkernel-x86_64-4.14.97-nat } If i replace "set root='(mduuid/232d2317:1469bc36:e85fd34c:9136eb63,msdos1)'" with "set root='(md/0,msdos1)'", then grub boot the system. Grub was installed with the next command(sda and sdb are raid component devices): grub-install --boot-directory=/boot/ --modules='part_msdos mdraid1x' /dev/sda grub-install --boot-directory=/boot/ --modules='part_msdos mdraid1x' /dev/sdb mdraid UUID: mdadm --detail /dev/md127 | grep UUID UUID : 232d2317:1469bc36:e85fd34c:9136eb63 How can i fix this?

May be it's a time to go to plan9 and make it more usable for everyday use ;-).

This is not linux, this is lindows :-). I can't understand why Poettering still haven't added to systemd registry and bsod...

Hi, all! Why do we have both loopback and net.lo initscripts?

Fixed by adding rm before ln in the ebuild.

Some strange error when boost installing: >>> Install boost-1.65.0 into /var/tmp/portage/dev-libs/boost-1.65.0/image/ category dev-libs * abi_x86_64.amd64: running multilib-minimal_abi_src_install * python2_7: running installation * ACCESS DENIED: symlinkat: /var/tmp/portage/dev-libs/boost-1.65.0/temp/libpython2.7.so ln: failed to create symbolic link '/var/tmp/portage/dev-libs/boost-1.65.0/temp/libpython2.7.so': Permission denied * ERROR: dev-libs/boost-1.65.0::core-kit failed (install phase): * (no error message) * * Call stack: * ebuild.sh, line 92: Called src_install * environment, line 4402: Called multilib-minimal_src_install * environment, line 2544: Called multilib_foreach_abi 'multilib-minimal_abi_src_install' * environment, line 2738: Called multibuild_foreach_variant '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_install' * environment, line 2443: Called _multibuild_run '_multilib_multibuild_wrapper' 'multilib-minimal_abi_src_install' * environment, line 2441: Called _multilib_multibuild_wrapper 'multilib-minimal_abi_src_install' * environment, line 436: Called multilib-minimal_abi_src_install * environment, line 2534: Called multilib_src_install * environment, line 3049: Called python_foreach_impl 'installation' * environment, line 3817: Called multibuild_foreach_variant '_python_multibuild_wrapper' 'installation' * environment, line 2443: Called _multibuild_run '_python_multibuild_wrapper' 'installation' * environment, line 2441: Called _python_multibuild_wrapper 'installation' * environment, line 565: Called installation * environment, line 3007: Called create_user-config.jam * environment, line 917: Called die * The specific snippet of code: * ln -f -s "$(python_get_library_path)" "${T}/lib${EPYTHON}$(get_libname)" || die; * * If you need support, post the output of `emerge --info '=dev-libs/boost-1.65.0::core-kit'`, * the complete build log and the output of `emerge -pqv '=dev-libs/boost-1.65.0::core-kit'`. * The complete build log is located at '/var/tmp/portage/dev-libs/boost-1.65.0/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/dev-libs/boost-1.65.0/temp/environment'. * Working directory: '/var/tmp/portage/dev-libs/boost-1.65.0/work/boost_1_65_0-abi_x86_64.amd64' * S: '/var/tmp/portage/dev-libs/boost-1.65.0/work/boost_1_65_0' * --------------------------- ACCESS VIOLATION SUMMARY --------------------------- * LOG FILE: "/var/log/sandbox/sandbox-30018.log" * VERSION 1.0 FORMAT: F - Function called FORMAT: S - Access Status FORMAT: P - Path as passed to function FORMAT: A - Absolute Path (not canonical) FORMAT: R - Canonical Path FORMAT: C - Command Line F: symlinkat S: deny P: /var/tmp/portage/dev-libs/boost-1.65.0/temp/libpython2.7.so A: /var/tmp/portage/dev-libs/boost-1.65.0/temp/libpython2.7.so R: /usr/lib64/libpython2.7.so.1.0 C: ln -f -s /usr/lib64/libpython2.7.so /var/tmp/portage/dev-libs/boost-1.65.0/temp/libpython2.7.so How can i fix it?

It seems this isn't work as needed :-). But i try to play with settings again. Can we mirror the forum to mailing list like nginx do (post on the forum appear in the mailing list and vise versa)?

Wow! This helped! Now emerge is working. Thank you!

# ./ego profile === Enabled Profiles: === arch: x86-64bit build: stable subarch: generic_64 flavor: core mix-ins: no-systemd === Python kit: === branch: 3.6-prime === All inherited flavor from core flavor: === minimal (from core flavor)