Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


jmmc last won the day on November 1 2014

jmmc had the most liked content!


  • Interests
    gnu/linux, compute environments, electronics, music, craft beer

jmmc's Achievements


Newbie (1/14)



  1. Hi - More just looking for confirmation, but given that the Install documentation follows pretty much the same all-around, the only real difference for a new/fresh 1.4 installation would be to change: wget https://build.funtoo.org/1.3-release-std/x86-64bit/generic_64/stage3-latest.tar.xz to wget https://build.funtoo.org/1.4-release-std/x86-64bit/generic_64/stage3-latest.tar.xz Y, realize that seems pretty obvious, but I'm thinking about new people maybe looking at the distro within the past couple weeks. When the new version is released, should this link get updated in the install guide as part of the release process?
  2. Re: 'pure64'. Can ref what I see in 'man epro': I do believe that is equivalent to a no-mulitlibs-type setup, from what I understand. Q. what does: epro show display in your case? I'm running a fairly default install, with debian-sources on (atm) a Dell Optiplex 960 unit. I actually never even set a subarch as yet in my env just as I haven't had the time this Spring to really optimize that box. (apolog. for the 20 questions - trying to get a idea of how your env is currently set while I'm VNC'd into my Funtoo station trying to compare notes) Glad the compile is (hopefully, still) running successfully.
  3. @patty.yivi Re: ...'--exclude gcc glibc'...was going to my next suggestion. Hm. Not sure I can get you much farther along, but out of curiosity and if not too much bother, could you post what you currently see when you do the following two commands: (?) 'equery list gcc' and 'gcc-config --list-profiles'
  4. Oleg: would it be possible to simply have an 'Unsupported' category under the 'HOWTO' listing and re-post the doc? E.g. 'HOWTO -> U -> 'Unsupported' or 'Unsupported/Gentoo_to_Funtoo', with the implicit idea that the directions are unsupported and the expectation of assistance, even in the forums might be limited or non-existent.
  5. Hi - Re: backup/snapshot: only meant here if the Gentoo installation you were trying to 'convert' was backed up so you could return to that baseline if you wanted to retry the entire process....which... now I see has been removed from the site. The link you have above does not seem to exist as of 20160519 1135 UTC. Re: eix-sync. Ah, ok - well, if eix did install cleanly, then likely it would be a PATH issue with the user which is trying to run the command. Re: World update 'all-at-once': most would probably agree. You might try to rebuild just the @system set first, reboot, then try the @world set next, etc.
  6. Gently, so I know you saw those directions are _not _ officially supported by Funtoo (it's right at the top of the doc with a big red word of Warning at the top). But I and many here are former Gentooians, so will try to help if I can. You made a snapshot/backup of your Gentoo install before trying the Funtoo migration, right? ;) Sorry, (way too) long time IT-guy - hadda ask ;) Then, 'eix-sync' comes from the eix package - you need to emerge that first, then eix-sync can be run. But just to clarify, realize the 'eix' package is not an absolute 'must' for a Funtoo installation - you can maintain a Funtoo system without it - but of course, most of us find it very useful for querying package details. e.g. (as sudo/root, of course) emerge -aq app-portage/eix then try... emerge --sync (I suggest always making sure this command works first, before trying the eix-sync) But once you sync with emerge, it's a little redundant to do it with eix, so maybe just do a eix-update at that point) However, if you'd like the one-shot approach, then: eix-sync (there are a decent number of options for this command, so a 'eix-sync --help' would prob be in order if you're not familiar with it) Personally, I run: 'emerge --sync && eix-update' as a single command when I update portage. Anyway, that would only solve your eix-sync command problem. So, did this gcc rebuild error happen when you did the 'world' rebuild command down near the end of the directions(emerge -vauDN world)?
  7. Q: Did you achieve first boot with the default debian-sources - or are you just trying to get to first (initial) boot? Q2: Do you have hardware or a filesystem not supported by the stock debian-sources kernel?
  8. Hi subtlelotus - My experience is I've wrangled/wrestled w Funtoo on decent variety of Dell hardware, but I since 2015 I usually find the debian-sources to almost universally boot on almost anything I toss at it these days, typically without any edits to the config. Just first pass musing/question here: are your partitions for this drive aligned to 4096 bytes? They have some info over at Arch on this drive/driver: (you've probably seen it, but just reposting in case not) https://wiki.archlinux.org/index.php/Solid_State_Drives/NVMe Not sure this would prevent actual booting/usage if it's not aligned as such, but it sounds like it's recommended for this particular model drive. Also, any chance the microcode in the drive itself is in need of an update? I had an OCZ SSD I was wrestling with in Linux a couple years ago which cleared up after I updated the microcode in the drive. Again, just a thought. Also a question: (from your initial post): so, you mention you tried SystemRescuecd. Q: we're you able to actually fdisk/access/partition/save on the NVMe SSD once SysResc booted?
  9. Many thanks cardinal! All is well. Creating/editing the package-specific env vars enabled the packages to compile without error. Sl?inte!
  10. Hi - Is anyone having issues with these two ebuilds in the last two or three days? After recent update of @world, I am left with only two these packages which fail to build. Thought I would quick post here to see it anyone else had noticed issues with these two packages recently. Checking at bugs.funtoo.org, a search shows no recent trouble with these. Best Regards
  11. Glad you got genkernel to work. As a note, I've just done a series of Funtoo installs since December on various hardware (mostly Dell boxes from the past few years) and have found the 'debian-sources' method described in the (main) Install documentation to work very reliably in all those cases (~10 installs since late December). Once booted, and only if really necessary, I then use the debian-sources kernel as the platform to go back and build a lean 'vanilla-' or 'ck-' sources kernel. But 95% of the time, the debian-sources is a good choice for a decent, desktop kernel, imho.
  12. Technically, Grub does not require the boot (/boot) partition to be mounted to reference/locate the kernel and boot the machine. Generally, the arguments for having /boot mounted for normal system usage are few. As mentioned, it's been quite some years that 'noauto' has been set as the default for /boot in the template fstab file provided in the stage-3 tarballs from Gentoo and Funtoo. But it's not some type of hard 'law' or anything - if you'd like to always see your boot partition mounted, feel free to go ahead and removed 'noauto' from that line in fstab. In the Gen/Funtoo-verses (and well, in Linux-verse generally), it's really only necessary to mount /boot when performing a kernel upgrade. Otherwise, it's a best practice to leave it as 'noauto' in fstab, imho. It has happened that newer users in years past have accidentally cd'd into /boot and deleted the kernel. Not the end of the world, by any means, but a pita to correct when you have to reboot the box.
  13. Hi, there's also this: http://www.funtoo.org/System_Administration_Practice Which has a section on just this topic (distfiles).
  14. I compiled GNOME 3.14 last Sunday using VIDEO_CARDS="vga vesa intel i915 i965" (just used the on-board video) on an Optiplex 960 (E8400 @3Ghz, 8GB RAM) most of 400+ packages compiled very fast, but the two webkit-gtk compiles took almost two+ hours...each. I also thought it had hung as well (at first), but saw no other signs of trouble, so I let it go and everything finished, afaict, cleanly and GNOME fired up without real issue. I'm going to repeat the this again this evening, but this time with an tmpfs in RAM (maybe 4 or 6GB) for /var/tmp, and monitor the effect
  • Create New...