Jump to content


  • Content Count

  • Joined

  • Last visited

  1. Do you mean "emerge portage" or "sync portage directory"? Because if before syncing portage directory the directory must be empty it means before every syncing one should delete the whole portage directory content...
  2. @stone821, of course the portage directory is filled with usual content and up to date! And I've tried the default path, simply by linking my portage directory to /usr/portage, but with no avail. What do you mean precisely by saying you've encountered the same problem? ------EDIT I've emptied the portage directory and run eix-sync again. This works, the portage directory has been filled with desired content. Yet to check up whether it is going to update properly.
  3. Please, respond. What do you have in your /etc/portage/repos.conf configuration file? Please share it!
  4. Please review, my /etc/portage/repos.conf is: [DEFAULT] main-repo = gentoo [gentoo] location = /mnt/_tinies/_Funtoo/portage sync-type = git sync-uri = git://github.com/funtoo/ports-2012.git auto-sync = yes sync-rsync-vcs-ignore = true GENTOO_MIRRORS="http://gentoo.linux.no http://trumpetti.atm.tut.fi/gentoo http://ftp.rhnet.is/pub/gentoo/ \ http://mirrors.xmu.edu.cn/gentoo http://mirrors.stuhome.net/gentoo/ http://mirrors.sohu.com/gentoo/ \ http://mirrors.163.com/gentoo" and I got error message on portage syncing: # eix-sync * Running emerge --sync >>> Syncing r
  5. ulimit -n 1024 is set 1024 on Gentoo as default value, probably such a security measure. However interesting why Gentoo can emerge kernel with this and Funtoo can not?
  6. It looks like only this one is yet on the battlefield, actually, and the fresh install with compiling everything anew seems too cumbersome, not worth it. Sent from my Nexus 7 using Tapatalk
  7. As you probably read already about the original problem is covering from Gentoo. As you can see step by step it succeeds iteratively solving such issues like the abovementioned. Previously as yet branded as Gentoo the system worked well without any limits settings. Conversion something introduced. Sent from my Nexus 7 using Tapatalk
  8. After emerging debian-sources, preparing them with 'make modules_prepare' etc, then trying to emerge aufs4. However weird error pops up: y linux # make oldconfig scripts/kconfig/conf --oldconfig Kconfig * * Restart config... * * * Hardening features (from Grsecurity) * Hardening features (from Grsecurity) (GRKERNSEC) [N/y/?] (NEW) # # configuration written to .config # y linux # make modules_prepare scripts/kconfig/conf --silentoldconfig Kconfig CHK include/config/kernel.release CHK include/generated/uapi/linux/version.h CHK include/generated/utsrelease.h CHK inclu
  9. Voila :) : y y # epro show === Enabled Profiles: === arch: pure64 build: stable subarch: native_64-pure64 flavor: workstation mix-ins: X mix-ins: mediaformat-video-common mix-ins: xfce mix-ins: console-extras mix-ins: mediaformat-audio-common mix-ins: dvd mix-ins: mediadevice-base mix-ins: no-systemd mix-ins: audio mix-ins: media mix-ins: mediadevice-video-consumer mix-ins: no-emul-linux-x86 === All inherited flavors from workstation flavor: === core (from workstation f
  10. It's already solved (partially), as you can read here the culprit is ulimit settings, and the partial solution allows at least for emerging debian-sources.
  11. It's already solved. It's turned out -DNDEBUG -DG_DISABLE_ASSERT flags were the culprit why =dev-python/pygobject-3.16.2:3::gentoo didn't want to compile, in the file /etc/portage/make.conf CXXFLAGS="-Os -s -march=native -pipe -DNDEBUG -DG_DISABLE_ASSERT" CFLAGS=" -Os -march=native -pipe -DNDEBUG -DG_DISABLE_ASSERT" CPPFLAGS=" -DNDEBUG -DG_DISABLE_ASSERT" and commenting them out allows this ebuild to emerge.
  12. ------ EDIT: It turns out settings abovementioned work! :) Those in: /etc/limits while these in: /etc/security/limits.conf bring absolutely no effect! However only after rebooting computer they've came into effect, not just after logging out and in as people write in tutorials... And they hold just for graphical terminal, for ordinary user or when made su, for the text console when logging in as root it still says: # ulimit -n 1024 [\code] but ordinary user's console respects these settings.
  13. After doing some research about ulimit and linux limits at all through Google etc. have tried set such two configuration files: /etc/security/limits.conf * hard nofile 1028096 * soft nofile 1024000 and /etc/limits * N1024000 sysadm - root - portage - however, after logging out in in it has taken exactly no effect: # ulimit -n 1024 In order to make possible emerging debian-sources, have done simple thing: ulimit -n 1024000 and it works: # ulimit -n 1024000 of course just within the login session, and then it flees. It helped to eme
  14. As might already presume this is the first time I hear about it at all ;) What's more there isn't anything like /etc/security folder at all on my system. Wait, has it anything to do with pam? I entirely resigned of emerging pam and set use flags for it for ebuilds not to incorporate pam dependencies...
  15. ulimit -n yields: 1024 How to handle ulimit at all and what to do next with this value, please? Sent from my Nexus 7 using Tapatalk
  • Create New...