Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by walterw

  1. 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.
  2. 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 -fort
  3. 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
  4. 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?
  5. Thanks - I tried that many times. I also started over with a new stage3. My systems with zfs in them all have this problem, the systems without do not. I have no idea why yet.
  6. Thanks - the bug report is closed, what are the next steps for this?
  7. 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
  8. Hi cafaia, File received, I see it is compressed with gzip. I see that scandelay actually supports no args, it waits 3 seconds by default (when passed as an argument with no parameters) 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 update
  9. 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?
  10. I masked gentoo-sources > 4.15.0 and rebuilt everything since apparently 4.17 is not ready yet and the newer ZFS ebuilds are not yet available.
  11. 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 sh
  12. I thought scandelay took a numerical argument. I use this to boot off of USB devices because it sometimes takes a second or 2 to see them
  13. 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).
  14. 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. H
  15. Thanks, that fixed it - I followed the gentoo docs and not the funtoo ones.
  16. 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 n
  17. Jira closed, talk about speedy service! I am emerging the package now!
  18. raised: https://bugs.funtoo.org/browse/FL-4844
  19. Understood, I should say that I want to support dnscrypt and in fact I currently am using it; however, I recently updated my systems after March when that change was made and now I cannot install / update unbound. Walter
  20. 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
  21. 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 segfau
  22. I am unable to reproduce this as I did this on another machine and didn't record the entire sequence of events. I will mark this as closed.
  23. I am marking this as solved as editing /etc/ego.conf works and is simple enough for me.
  24. I am just editing /etc/ego.conf, this works fine for me.
  • Create New...