Jump to content


  • Content Count

  • Joined

  • Last visited

About dutch-master

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Managed to install lxd and everything that comes with it on my AMD k10 system (Phenom II X4 965 proc, 16GB RAM, 120GB SSD). Then I proceeded by getting the lxd image for k10 arch and set up lxd following the Wiki by DRobbins. but launching the testcontainer as per the instructions failed with an error. After some trial and continues errors I managed to get both the lxd-generic_64 and intel westmere images installed and associated with a testcontainer: # lxc list +---------------+---------+------+------+-----------+-----------+ | NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS
  2. Oh, apols, didn't catch that 😳
  3. Sorry to see you stop JFS support, as I use it pretty much exclusively. (not just Funtoo, but on my Devuan installs as well) At the time I choose JFS over XFS as the former had slightly better performance for small file storage, while being on par for large files. What does this mean though for JFS support in Funtoo? Will JFS remain an option to install on? Or is this just for a personal project you run?
  4. Did you sync your local repo with the online one? Do ego sync Then run the emerge command again.
  5. Could a dedicated fork for -bin packages be an option? A bit like a "Debianized Funtoo", just -bin packages to install. Great way to get going on older hardware! Case in point: my CPU dates from 2012-ish and I'm not in a position to upgrade to a Ryzen system any time soon. Building libreoffice-bin takes up a lot less time then libreoffice, which is often newer then the -bin package, but libreoffice-bin doesn't always build successfully whereas libreoffice usually succeeds. Other big packages like mesa, ffmpeg etc also eat enormous amounts if install time to get a fairly basic working desktop.
  6. Ah, many thanks again. I'll retrace my steps and see if I can get a working system this time 🙂 (crosses fingers!)
  7. Well, that didn't work. Blocked the 1.8 release globally in make.conf but the 1.4 version it wanted instead is no longer available. For some reason, the libvpx line was missing in funtoo-cautionary (at least on my system) so it wasn't blocked to start with from that layer. No idea where the blockage comes from then. As I was quite fed up by now, I tried reverting the 1.4 release back to 1.3 by first removing everything outside the core flavour, setting ego.conf back to 1.3, then deleting the existing package cache (and rebuilding it with ego sync) before running emerge -auDN @world
  8. Ah thanks, I wasn't aware there was a bug filed already (didn't think checking the bugs list). I'll have another go later.
  9. Reviving my attempts to install Funtoo 1.4, I've run into an issue with libvpx-1.9.0. This package is masked by package.mask but it is required for installing Mate. Several packages depend on libvpx, including ffmpeg, gst-plugins-[libav,meta], brasero and mate (meta-package) itself. Is there an alternative/workaround/fix for this? TIA!
  10. Belated (attempted) answer: You can use 64-bit Linux on 2GB main-board systems. I happen to have a Shuttle All-in-one system with an Atom D525 as well and 64-bit Funtoo compiled fine. Takes a looooonngggg time, but it works.
  11. Welcome (a bit belated, but still 😉 ) Given that you currently have no working system, consider starting afresh with the Funtoo install-guide: https://www.funtoo.org/Install Don't try short-cuts, take it step-by-step. Keep your make.conf as clean as possible, likewise epro mix-ins. Alternatively, use emerge to remove all X-related packages from your current system. emerge -aG xorg-x11 xinit xdm emerge -a --depclean Let it finish, then reboot. Emerge uses a separate build-directory for each package, including log and build files. Any issues emerge runs into t
  12. The Wiki page on Mate (<- link!) stipulates it needs dbus as a prerequisite, so: rc-update add dbus default rc HTH!
  13. OK, performed the usermod command again, minus the plugdev group, tried again to log in remotely and now it works as it should. Thx for the pointers!
  14. The output is only the group name of the regular user. I had performed the usermod command as per the wiki install page, but it bombed out with an error about plugdev group not existing. I'll redo the usermod command w/o the plugdev group tomorrow. In 4 hrs the alarm goes to get to work... 😴
  15. Right, this is pretty annoying, Just succesfully installed a fresh Funtoo 1.4 (on some not-so-fresh hardware: Core2 Duo, 4GB RAM, 120GB SSD) and rebooted. - bare metal, not a VM! - logging in locally on the cli works (as root) - remote login (ssh) as normal user works - elevating permissions to root (su) fails - I've had this on a different system (Devuan Beowulf) and the recommendation was to revert to the old Unix way: su - - using su - fails with "permission denied" error, repeatedly - alternative was to add ALWAYS_SET_PATH yes into /etc/defa
  • Create New...