Jump to content
funtoo forums

Oleg Vinichenko

Funtoo Linux Developer
  • Content count

  • Joined

  • Last visited

  • Days Won


Oleg Vinichenko last won the day on December 26 2017

Oleg Vinichenko had the most liked content!


About Oleg Vinichenko

  • Rank

Recent Profile Visitors

309 profile views
  1. X suddenly not working

    paste following output from both working and then non-working box: ls -dl /var/db/pkg/*/*/*
  2. X suddenly not working

    to understand problem, it's required to get the following: 1. the state of working box 2. the state of non-working box To me it looks that update of some ebuilds, such virtualbox or virtualbox-related ebuilds happened in case 2. Also, it could be kernel update.
  3. About eselect python

    yes, this is known bug. i reported it to usptream https://bugs.gentoo.org/635678
  4. TTY (console) colour changed after OpenRC start

    Hi! Its very difficult to follow the entire thread. To understand the patterns of a problem a following information could help: 1. using same kernel but different OpenRC versions will reproduce the bug. 2. using same OpenRC version but different kernel will reproduce the bug
  5. xfce-base/libxfce4util-4.13.1 fails to emerge

    su - or su -l is recommended as in this case you're getting clean environment not contaminated with any variables such as XDG_CACHE_HOME and which was the origin of a failure.
  6. xfce-base/libxfce4util-4.13.1 fails to emerge

    so, that's the problem. normally XDG_CACHE_HOME=/root expected. How do you use your terminal root? Via su, sudo, etc?
  7. xfce-base/libxfce4util-4.13.1 fails to emerge

    this failure could happen if your XDG environment incorrectly set. Thats when you start compilation in GUI (terminal emulator), some XDG* variables have special values. TO check, run following in terminal you used: declare -p ${!XDG*}
  8. Hiya! Having no dedicated stages is indeed because of hardware lack. It is possible to convert the gentoo ppc64 stages into funtoo stages with some efforts, it could be challenging task, though.
  9. Realtek r8168 module install

    what exact guide used for this configuration?
  10. Realtek r8168 module install

    well, this is not entirely 100% true about necessity of disabling module in kernel. Because it can be blacklisted at runtime. but it's correct that debian-sources has the r8169 enabled as module. This ebuild maybe need correction
  11. 20 GiB of free space?

    peak size used by temporary directory where debian-sources compiling is about 17GB. 20GB is set in ebuild with some exceeding margin to ensure it's enough space.
  12. Meltdown patches

    containers are sharing the host node kernel. Update has to be performed on that servers.
  13. Meltdown patches

    yes, there is a new kernel for the containers.
  14. The new debian-sources-4.14.12 release now available which has the fix for severe security problem, known as meltdown. https://meltdownattack.com/
  15. ANSWERED How to upgrade and patch kernel?

    currently there is no patch for the debian kernels. For tracking: https://security-tracker.debian.org/tracker/CVE-2017-5753 https://security-tracker.debian.org/tracker/CVE-2017-5715 https://security-tracker.debian.org/tracker/CVE-2017-5754 currently, only Wheezy kernels getting a fixes: https://anonscm.debian.org/git/kernel/kernel.git/commit/?h=wheezy-security