Jump to content
Read the Funtoo Newsletter: Summer 2023 ×

walterw

Members
 View Profile  See their activity

  • Posts

    39

  • Joined

  • Last visited

  • Days Won

    1

 Content Type 

Posts posted by walterw

  1. Linux Builder

    in General Discussion

    Posted

    Hi all,

    I built a java-based application that can build Gentoo / Funtoo / Ubuntu (and other Debian-based) systems from within any Linux distribution that has Java installed.  The source code is here:

    https://github.com/walterjwhite/linux-builder

     

    And, I have a corresponding "system" to build an image:

    https://github.com/walterjwhite/funtoo-linux

     

    Caveats:

    1. I will be updating the code on github as all of the dependencies for the linux-builder project are about a year old.  There is no documentation, this needs to be written for anyone to use.

    2. My own systems are much more complicated than the sample system there.  This is meant to showcase what you CAN do.  Furthermore, there is also no documentation as to what patches are available, this needs written.

        a. a "system" contains patches

        b. a "patch" contains all the changes necessary for that single patch unit.  This could be copying files, creating a user, group, adding a service to a runlevel, installing packages, etc.  Patches that are inter-related are linked through "dependencies".  This ensures the base patch is installed first so if those files or libraries, etc. are needed, they will be installed prior to installing this patch.  It is meant to be as generic as possible so if you want to prepare a configuration for Gentoo and want to translate that to Ubuntu, you can with ease (provided you know the package names and configuration directory).

        c. a "phase" can be setup, build, update, finalize and provides hooks at various stages of the build process.  Say for instance, you need to download a file before you attempt to unpack and install it, you would create a download item in the setup phase.

     

    I've been using this system for about 3 years now and my goals are / were to:

    1. make it easier to get started with Gentoo / Funtoo

    2. allow users to switch across distributions whilst having the same applications, configuration, etc.

           partially supported, each distribution tends to put files in different places and has different package names thus requiring the packages listed in add-packages to be updated as well as the configuration files to be in the right place

    3. share this utility with other linux users (Gentoo, Funtoo, etc.) and see what others' interests were and how this might help them to accomplish those goals

    4. allow users to backup their systems easily and restore them to a pristine state

    5. provide a means to capture all the patches applied to a system

        provided in an earlier release, and not currently implemented (relied on python and latex to generate PDF files describing the system)

     

     

     

    Thanks for your feedback,

     

    Walter

     

     

  2. genkernel-next - unable to install /usr/share/genkernel/src

    in General Help

    Posted

    Hi cardinal,

    My distfiles are downloaded to /var/cache/portage/distfiles as best as I can tell and it is installing genkernel-next-68.  I overwrote my logs, so I don't have the original message, but here is my /etc/make.conf (it is automatically generated, so I apologize for all the lines, they're organized by patches): 

    http_proxy="http://localhost:8118"

CHOST="x86_64-pc-linux-gnu"
CFLAGS="-march=x86-64 -O2 -pipe"
CXXFLAGS="-march=x86-64 -O2 -pipe"
CPU_FLAGS_X86="mmx mmxext sse sse2"
MAKEOPTS="-j5"
USE=""
VIDEO_CARDS=""
SANE_BACKENDS=""
LINGUAS=""


# kernel
USE="${USE} symlink -fortran -openmp acpi"

# funtoo-network
USE="${USE} -networkmanager"

# compression
USE="${USE} zlib minizip"

# lvm
USE="${USE} lvm device-mapper"

# permissions
USE="${USE} pam caps filecaps"

# cups
USE="${USE} cups"

# ext4
USE="${USE} ext4"

# luks
USE="${USE} cryptsetup"

# zsh
USE="${USE} zsh-completion"

# english
LINGUAS="${LINGUAS} en"

# compression
USE="${USE} lz4"

     

    I could remove the symlink and uninstall the kernel and try to reproduce it?

     

    Also, for genkernel, I do have a custom init + scripts, so that could be a potential concern, but I also grepped there and do not see anything that'd point to /usr/share/genkernel/src.  The error message was for genkernel-next only and it was after building the kernel and modules.  I think it was during the initramfs phase.

    EDIT:

    I am building a different system that uses ZFS and as such requires an earlier kernel, interestingly enough, that kernel built just fine along with the initramfs (no error messages about files not being in /usr/share/genkernel/src, and that directory does not exist).  The one that built is: 4.14.80 and the one that wasn't was 4.19.1.  Now, before I upgraded to 1.3-release, the last time I built the other system, it was actually using the 4.20 kernel, so the portage trees must have been different.  Furthermore, the last time I built this system, it was actually using the 4.14.90 kernel.  I'll have to investigate in more detail, maybe that will shed some light onto what is really going on.

  3. genkernel-next - unable to install /usr/share/genkernel/src

    in General Help

    Posted

    I am trying to build / install funtoo from a stage 3 tarball using the latest 1.3-release and hitting a snag with kernel compilation.  All other packages (from what I can tell) are being properly fetched to /var/cache/portage/distfiles and installed.  During the kernel compilation (specifically, when generating the initramfs), I'm getting an error:

    Could not find source tarball /usr/share/genkernel/src/open-iscsi-2.0-872.tar.gz. Please refetch.

     

    This is occurring for any files that are required for the init such as busybox and open-iscsi (which oddly enough should not be in my init), I manually copied a file there to see that it'd resolve it and it did just resolve that single one, but I don't want to do it piece meal.

    Now, the files are in distfiles (/var/cache/portage/distfiles) and I am thinking I can symlink /usr/share/genkernel/src/ to distfiles, but is that required or is there something else broken that is causing this?  I did check the install guide and don't see anything alluding to that.  I also grepped /etc for any such configuration also to no avail.

     

    EDIT:
    symlinking /usr/share/genkernel/src to /var/cache/portage/distfiles worked and I was able to install gentoo sources.

     

    Thanks,

    Walter

  4. why do we have such outdated packges?

    in General Discussion

    Posted

    Will funtoo be tracking upstream automatically or will there still be human intervention (even for current)?  Also, along the same lines, I noticed that sometimes I have packages I cannot install because my kits don't have that package version available.  Is there a utility that exists to perform that dependency check with the kit to ensure accuracy?

    I am on master so I would expect that to be manually revised / curated whereas 1.3 release would be automatic?

  8. emerge --newuse -uD world - mips-sources problem?

    in General Help

    Posted

    I am attempting to update my systems and for whatever reason, when running:

      

    emerge --newuse -uD world -vp

     

    mips-sources is complaining of eapi7-ver: EAPI=5 not supported.  I don't have mips-sources installed and I'm on an x86/64 system.


      

    Calculating dependencies / * ERROR: sys-kernel/mips-sources-4.13.16::nokit failed (depend phase):
 *   eapi7-ver: EAPI=5 not supported
 * 
 * Call stack:
 *                     ebuild.sh, line 603:  Called source '/var/git/meta-repo/kits/nokit/sys-kernel/mips-sources/mips-sources-4.13.16.ebuild'
 *   mips-sources-4.13.16.ebuild, line  27:  Called inherit 'eapi7-ver' 'eutils' 'kernel-2'
 *                     ebuild.sh, line 294:  Called __qa_source '/var/git/meta-repo/kits/core-kit/eclass/eapi7-ver.eclass'
 - *                     ebuild.sh, line  79:  Called source '/var/git/meta-repo/kits/core-kit/eclass/eapi7-ver.eclass'
 *              eapi7-ver.eclass, line  62:  Called die
 * The specific snippet of code:
 *           die "${ECLASS}: EAPI=${EAPI:-0} not supported";;
 * 
 * If you need support, post the output of `emerge --info '=sys-kernel/mips-sources-4.13.16::nokit'`,
 * the complete build log and the output of `emerge -pqv '=sys-kernel/mips-sources-4.13.16::nokit'`.
 * Working directory: '/usr/lib64/python2.7/site-packages'
 * S: '/var/tmp/portage/sys-kernel/mips-sources-4.13.16/work/linux--20171007'
 | * ERROR: sys-kernel/mips-sources-4.9.75::nokit failed (depend phase):
 *   eapi7-ver: EAPI=5 not supported
 * 
 * Call stack:
 *                    ebuild.sh, line 603:  Called source '/var/git/meta-repo/kits/nokit/sys-kernel/mips-sources/mips-sources-4.9.75.ebuild'
 *   mips-sources-4.9.75.ebuild, line  27:  Called inherit 'eapi7-ver' 'eutils' 'kernel-2'
 *                    ebuild.sh, line 294:  Called __qa_source '/var/git/meta-repo/kits/core-kit/eclass/eapi7-ver.eclass'
 *                    ebuild.sh, line  79:  Called source '/var/git/meta-repo/kits/core-kit/eclass/eapi7-ver.eclass'
 *             eapi7-ver.eclass, line  62:  Called die
 * The specific snippet of code:
 *           die "${ECLASS}: EAPI=${EAPI:-0} not supported";;
 * 
 * If you need support, post the output of `emerge --info '=sys-kernel/mips-sources-4.9.75::nokit'`,
 * the complete build log and the output of `emerge -pqv '=sys-kernel/mips-sources-4.9.75::nokit'`.
 - * Working directory: '/usr/lib64/python2.7/site-packages'
 * S: '/var/tmp/portage/sys-kernel/mips-sources-4.9.75/work/linux--20161216'
 \ * ERROR: sys-kernel/mips-sources-4.4.110::nokit failed (depend phase):
 *   eapi7-ver: EAPI=5 not supported
 * 
 * Call stack:
 *                     ebuild.sh, line 603:  Called source '/var/git/meta-repo/kits/nokit/sys-kernel/mips-sources/mips-sources-4.4.110.ebuild'
 *   mips-sources-4.4.110.ebuild, line  27:  Called inherit 'eapi7-ver' 'eutils' 'kernel-2'
 *                     ebuild.sh, line 294:  Called __qa_source '/var/git/meta-repo/kits/core-kit/eclass/eapi7-ver.eclass'
 *                     ebuild.sh, line  79:  Called source '/var/git/meta-repo/kits/core-kit/eclass/eapi7-ver.eclass'
 *              eapi7-ver.eclass, line  62:  Called die
 * The specific snippet of code:
 *           die "${ECLASS}: EAPI=${EAPI:-0} not supported";;
 * 
 * If you need support, post the output of `emerge --info '=sys-kernel/mips-sources-4.4.110::nokit'`,
 * the complete build log and the output of `emerge -pqv '=sys-kernel/mips-sources-4.4.110::nokit'`.
 * Working directory: '/usr/lib64/python2.7/site-packages'
 * S: '/var/tmp/portage/sys-kernel/mips-sources-4.4.110/work/linux--20160123'
... done!

Total: 0 packages, Size of downloads: 0 KiB

WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict:

dev-python/urllib3:0

  dev-python/urllib3-1.23:0/0::python-modules-kit, ebuild scheduled for merge conflicts with
    <dev-python/urllib3-1.23[python_targets_python2_7(-),python_targets_python3_4(-),-python_single_target_pypy(-),-python_single_target_python2_7(-),-python_single_target_python3_4(-),-python_single_target_python3_5(-),-python_single_target_python3_6(-)] required by dev-python/elasticsearch-py-6.3.0:0/0::python-modules-kit, installed

     

    Now, the interesting thing is, I only get this error when updating systems with ZFS, but those ebuilds don't appear to have changed recently.

    I'm running the default kits, but I also tried updating to 1.2 where possible, but that didn't seem to make any difference.

  9. sh: bad number

    in Installation Help

    Posted

    Hi cafaia,

    File received, I see it is compressed with gzip.

    1. I see that scandelay actually supports no args, it waits 3 seconds by default (when passed as an argument with no parameters)
    2. I didn't see anything that stood out, can you try editing /usr/share/genkernel/defaults/linuxrc and adding echo statements throughout to see where it might be occurring, followed by rebuilding the initramfs (and booting up with the modified init)?  Then, we can narrow down exactly.

    Don't forget to backup your original ... Also, share the updated initramfs just so I can see it was updated as expected.

  10. sh: bad number

    in Installation Help

    Posted

    Hi cafaia,

    If you don't mind, can you post your initramfs?  That is the only way I see to troubleshoot this.  The other alternative is to look at the source files in /usr/share/genkernel to try and backtrack what is going on there.

    BTW, I checked my linuxrc (/usr/share/genkernel/defaults/linuxrc), and I don't see an ro option, is that a kernel command-line option?  Just for giggles, can you remove that argument?

  12. sh: bad number

    in Installation Help

    Posted

    Hi cafaia,

    Hmm, this is an example of what I use, I have a modified initramfs ... 

    linux /kernel-genkernel-x86_64-4.8.7-hardened consoleblank=300 crypt_root=/dev/disk/by-uuid/87f271ea dolvm doluks root=/dev/250.1/root-1 real_root=/dev/250.1/root-1 rootfstype=squashfs scandelay=2 memory tmpfs_size=4G
initrd /initramfs-genkernel-x86_64-4.8.7-hardened

     

    If you modified your initramfs, please share.  If not, please also confirm.

    It is odd to be getting that message if you haven't modified the initramfs and before openrc starts.  In my case, I've gotten a variation before in shell scripts when I'm expecting a variable to be set, but it is not.

  14. ZFS fails to build [SOLVED]

    in Portage Help

    Posted

    I have previously installed ZFS with no issues, but am currently getting:

      

    sed: can't read /var/tmp/portage/sys-kernel/spl-9999/work/spl-9999/scripts/check.sh: No such file or directory
 * ERROR: sys-kernel/spl-9999::core-kit failed (prepare phase):
 *   Cannot patch check.sh

     

    I see in the upstream zfsonlinux/spl.git repository that there is indeed no check.sh script - it appears I should be using the spl-0.7.9999.ebuild.  However, that is not available in portage in any of the kits (1.0, 1.1, or 1.2).

  15. Building for another target architecture

    in Server Help

    Posted

    I am building funtoo root images for a different target architecture than the build system and wondering if that is causing some packages to fail to run.

     

    I am starting with a generic subarch: https://www.funtoo.org/Generic_64

    And, I modify /etc/make.conf to:

     

    CHOST="x86_64-pc-linux-gnu"
    CFLAGS="-march=x86-64 -O2 -pipe"
    CXXFLAGS="-march=x86-64 -O2 -pipe"
    CPU_FLAGS_X86="mmx mmxext sse sse2"
     

    I do that to hopefully ensure that gcc won't build for my system which is an i7 and the target systems are a 64-bit Intel Atom and a 64-bit AMD netbook processor.  However, I still am unable to run a select few applications as I get invalid opcode during execution (they do run just fine on the system on which I built them).

    Am I missing a step to build for a different target architecture?  I don't believe distcc is required here, but all I really want to do is tell gcc not to use march=native which it prefers to do by default.

  17. Unable to start lxd container

    in General Discussion

    Posted

    I am trying to launch a container with lxd and am not having any such luck.  These are the steps I followed:

    https://wiki.gentoo.org/wiki/LXD 

    1. install lxd (I did not install criu and will add that for a future build)

2. manually configure kernel for lxd (I didn't do ebuild lxc or ebuild criu)

3. lxd group / user didn't exist, so I created it

4. add myself to that group

5. started lxd

6. initialized lxd (the order on the gentoo website says otherwise, but I couldn't do it in that order)

7. lxd automatically setup the network interface via the lxd service, so I didn't have the net.lxbr0 to worry about

8. images repository already existed, I just chose alpine linux since it was tiny

      

    lxc launch images:alpine/3.4
    Creating the container
Container name is: peaceful-racer
Starting peaceful-racer
error: Failed to run: /usr/sbin/lxd forkstart peaceful-racer /var/lib/lxd/containers /var/log/lxd/peaceful-racer/lxc.conf: 
Try `lxc info --show-log local:peaceful-racer` for more info
    lxc info --show-log local:peaceful-racer
    Name: peaceful-racer
Remote: unix://
Architecture: x86_64
Created: 2018/03/13 10:24 UTC
Status: Stopped
Type: persistent
Profiles: default

Log:

            lxc 20180313102453.772 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
            lxc 20180313102453.772 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
            lxc 20180313102454.308 ERROR    lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18127 0 1000000 1000000000
            lxc 20180313102454.309 ERROR    lxc_start - start.c:lxc_spawn:1276 - Failed to set up id mapping.
            lxc 20180313102454.448 WARN     lxc_network - network.c:lxc_delete_network_priv:2557 - Failed to remove interface "vethPDC82W" from "lxdbr0": Invalid argument
            lxc 20180313102454.448 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
            lxc 20180313102454.448 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
            lxc 20180313102454.449 ERROR    lxc_container - lxccontainer.c:wait_on_daemonized_start:760 - Received container state "ABORTING" instead of "RUNNING"
            lxc 20180313102454.452 ERROR    lxc_start - start.c:__lxc_start:1459 - Failed to spawn container "peaceful-racer".
            lxc 20180313102454.452 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
            lxc 20180313102454.452 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
            lxc 20180313102454.610 ERROR    lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18143 0 1000000 1000000000 1000000000 0 1
            lxc 20180313102454.611 ERROR    lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18143"
            lxc 20180313102454.611 ERROR    lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/openrc//lxc/peaceful-racer
            lxc 20180313102454.645 ERROR    lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18145 0 1000000 1000000000 1000000000 0 1
            lxc 20180313102454.645 ERROR    lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18145"
            lxc 20180313102454.645 ERROR    lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/cpuset//lxc/peaceful-racer
            lxc 20180313102454.676 ERROR    lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18147 0 1000000 1000000000 1000000000 0 1
            lxc 20180313102454.677 ERROR    lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18147"
            lxc 20180313102454.677 ERROR    lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/cpu//lxc/peaceful-racer
            lxc 20180313102454.708 ERROR    lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18149 0 1000000 1000000000 1000000000 0 1
            lxc 20180313102454.709 ERROR    lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18149"
            lxc 20180313102454.709 ERROR    lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/cpuacct//lxc/peaceful-racer
            lxc 20180313102454.743 ERROR    lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18151 0 1000000 1000000000 1000000000 0 1
            lxc 20180313102454.743 ERROR    lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18151"
            lxc 20180313102454.743 ERROR    lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/blkio//lxc/peaceful-racer
            lxc 20180313102454.777 ERROR    lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18153 0 1000000 1000000000 1000000000 0 1
            lxc 20180313102454.778 ERROR    lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18153"
            lxc 20180313102454.778 ERROR    lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/memory//lxc/peaceful-racer
            lxc 20180313102454.810 ERROR    lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18155 0 1000000 1000000000 1000000000 0 1
            lxc 20180313102454.811 ERROR    lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18155"
            lxc 20180313102454.811 ERROR    lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/devices//lxc/peaceful-racer
            lxc 20180313102454.841 ERROR    lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18157 0 1000000 1000000000 1000000000 0 1
            lxc 20180313102454.842 ERROR    lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18157"
            lxc 20180313102454.842 ERROR    lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/freezer//lxc/peaceful-racer
            lxc 20180313102454.874 ERROR    lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18159 0 1000000 1000000000 1000000000 0 1
            lxc 20180313102454.874 ERROR    lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18159"
            lxc 20180313102454.875 ERROR    lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/net_cls//lxc/peaceful-racer
            lxc 20180313102454.903 ERROR    lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18161 0 1000000 1000000000 1000000000 0 1
            lxc 20180313102454.903 ERROR    lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18161"
            lxc 20180313102454.903 ERROR    lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/perf_event//lxc/peaceful-racer
            lxc 20180313102454.928 ERROR    lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18163 0 1000000 1000000000 1000000000 0 1
            lxc 20180313102454.929 ERROR    lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18163"
            lxc 20180313102454.929 ERROR    lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/hugetlb//lxc/peaceful-racer
            lxc 20180313102454.960 ERROR    lxc_conf - conf.c:lxc_map_ids:2736 - newuidmap failed to write mapping "": newuidmap 18165 0 1000000 1000000000 1000000000 0 1
            lxc 20180313102454.960 ERROR    lxc_conf - conf.c:userns_exec_1:3824 - error setting up {g,u}id mappings for child process "18165"
            lxc 20180313102454.960 ERROR    lxc_cgfsng - cgroups/cgfsng.c:recursive_destroy:1286 - Error destroying /sys/fs/cgroup/pids//lxc/peaceful-racer
            lxc 20180313102454.961 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
            lxc 20180313102454.961 WARN     lxc_monitor - monitor.c:lxc_monitor_fifo_send:111 - Failed to open fifo to send message: No such file or directory.
            lxc 20180313102454.963 WARN     lxc_commands - commands.c:lxc_cmd_rsp_recv:125 - Command get_cgroup failed to receive response: Connection reset by peer.

      

    lxc config --expanded show peaceful-racer
    architecture: x86_64
config:
  image.architecture: amd64
  image.description: Alpine 3.4 amd64 (20180312_17:50)
  image.os: Alpine
  image.release: "3.4"
  image.serial: "20180312_17:50"
  volatile.base_image: 2ef5588b926349408eb1689bda8aa2f42123248f1bb3fc34c2ad4d6c5bb02962
  volatile.eth0.hwaddr: 00:16:3e:67:65:8b
  volatile.eth0.name: eth0
  volatile.idmap.base: "0"
  volatile.idmap.next: '[{"Isuid":true,"Isgid":true,"Hostid":1000000,"Nsid":0,"Maprange":1000000000}]'
  volatile.last_state.idmap: '[{"Isuid":true,"Isgid":true,"Hostid":1000000,"Nsid":0,"Maprange":1000000000}]'
  volatile.last_state.power: STOPPED
devices:
  eth0:
    nictype: bridged
    parent: lxdbr0
    type: nic
  root:
    path: /
    pool: default
    type: disk
ephemeral: false
profiles:
- default
stateful: false
description: ""


    My system is using a squashfs root with an ext4 backed overlayfs.

  21. unable to install unbound, unmet libsodium dependency

    in General Help

    Posted

    Hi,

    I am unable to install unbound as I am getting the error saying there aren't any ebuilds to satisfy dev-libs/libsodium.  I suppose it may be related to a recent ebuild change, but am wondering how to address this: 

    emerge: there are no ebuilds to satisfy "dev-libs/libsodium[abi_x86_32(-)?,abi_x86_64(-)?,abi_x86_x32(-)?,abi_mips_n32(-)?,abi_mips_n64(-)?,abi_mips_o32(-)?,abi_ppc_32(-)?,abi_ppc_64(-)?,abi_s390_32(-)?,abi_s390_64(-)?]"

     

    Walter

  22. NetworkManager consistently segfaults (on a specific device)

    in General Discussion

    Posted

    I built NetworkManager with these settings:

    net-misc/networkmanager -dhclient -ppp -wext

     

    (I rebuilt it with -dhcpcd and have the same issue, and also ensure that my kernel had support for wireless extensions).

     

    However, I came across this bug and this post:

    https://bugs.funtoo.org/browse/FL-2372

     

    The segfault:

    NetworkManager segfault at 8 ip 00007fa89e102e16 sp 00007fff51f34be8 error 4 in libc-2.23.so[7fa89e084000+18e000]

     

    The interesting thing is that this issue is tied to shorewall.  Whenever I start my shorewall, I get this segfault.  I only get this issue with this particular device (router) and not my other devices (workstations).  The rulesets are different between my workstations and my router so that may be why I don't experience this issue on those devices.  Still though, I find it odd that shorewall or iptables would cause some sort of issue with NetworkManager.

     

    I just reverted back to 1.4.4-r1 and will use that until I can sort out this issue with 1.10.2.

×
×
  • Create New...