Jump to content

niltsiar

Members
  • Content Count

    8
  • Joined

  • Last visited

About niltsiar

  • Rank
    Newbie

Recent Profile Visitors

732 profile views
  1. Hi, I've just updated to the latest LXC version, 3.2.1.20191211, and two of my LXC containers stopped working. Both of them have systemd, one is a Centos 7.5 and the other one is an Ubuntu 16.04. I'm also running some Alpine Linux containers which work without any problem. Reverting to LXC 3.0.4 solved the issue. The error I'm getting in the container's console: Failed to insert module 'autofs4' Failed to mount cgroup at /sys/fs/cgroup/systemd: Operation not permitted systemd 219 running in system mode. (+PAM +AUDIT +SELINUX +IMA -APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +
  2. It worked like a charm. I've also added the dropbox.stop so it stops the service while shutting down. Thx a lot @drobbins
  3. I'm in the same situation. What should be do in order to get Dropbox sync without login in into the server?
  4. niltsiar

    eix and kits

    In order to get the eix-sync functionality i've created the following alias alias eixsync="ego sync && eix-sync -u" When we pass -u to eix-sync it does all its work without the "emerge --sync" part so it syncs through ego and then it updates eix databases and run eix-diff Hope this can help someone :)
  5. That's how I do it and it's working great for my i7-6700
  6. Hi, ports-2012 are dead. You can read it here: http://www.funtoo.org/News:Kits_are_Go_(Switch_to_Them!) I'm still waiting to migrate to them because of some issues that seem to be raising and waiting for a migration guide from ports-2012 stable to the new Kits system and a new ego version which can handle the sync process properly with different branches, as it was stated https://bugs.funtoo.org/browse/FL-4020
  7. Thx Oleg. I'll wait for it then. If you want me to try something just let me know.
  8. And this is the output with the suggested options neptuno ~ # emerge -auDN @world --with-bdeps=y --verbose-conflicts --backtrack=30 These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] dev-lang/python-exec-2.4.5 [2.4.4] [ebuild r U ] sys-libs/ncurses-6.0-r1 [5.9-r5] USE="{-test%} -threads%" [ebuild U ] sys-devel/gnuconfig-20170101 [20161104] [ebuild U ] sys-apps/gentoo-functions-0.11 [0.10] [ebuild U ] sys-apps/groff-1.22.3 [1.22.2] [ebuild U ] sys-apps/debianutils-4.8.1 [4.7] [ebuild U ] sys-apps/install-xatt
  9. Hi Oleg, this is the output you asked: neptuno ~ # epro build current WARNING: build already set to stable -- typically, user should not change this. === Enabled Profiles: === arch: x86-64bit build: current subarch: intel64-broadwell flavor: server mix-ins: no-systemd >>> Set build to current. neptuno ~ # emerge -auDN @world --with-bdeps=y These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] dev-lang/python-exec-2.4.5 [2.4.4] [ebuild U ] sys-devel/gnuconfig-20170101 [20161104] [ebuild
  10. Hi, I'm currently in a stable system. Should I run epro build current and update @world before changing to meta-repo? Thx
×
×
  • Create New...