Jump to content

drobbins

Funtoo Linux BDFL
  • Content Count

    438
  • Joined

  • Last visited

  • Days Won

    217

Everything posted by drobbins

  1. Just a note -- I forgot to re-enable gdm for GNOME, so SDDM is still the default for GNOME. Some notes here -- By default, SDDM will try to start a "GNOME on Wayland" session which will fail. Just toggle it to "GNOME on Xorg" in the top-left drop-down. And if you want to switch to GDM, just edit /etc/conf.d/xdm as root and change "sddm" to "gdm" and reboot. Then you'll be using GDM.
  2. This is just @pnoecker talking about his personal systems, not funtoo...
  3. That's a shame, always thought it was cool that you were using JFS. JFS is the filesystem I have played with the least. When I was writing IBM developerWorks articles, it was time for me to write about JFS (which came from IBM) and I could not get it to work at all. IBM wasn't happy about that and I was no longer writing IBM articles after that.
  4. @nrc not retired but the account in AWS Marketplace I used to create it went away. We will be working on getting updated 1.4 images and there is a bug open for this.
  5. I have posted an announcement on www.funtoo.org that we are doing an official "End of Year" pause for 2020. 2020 has been an interesting year and this is a good time to take a break if you have vacation. Funtoo will be back in 2021. Tree updates will be minimal during the break.
  6. Hey everyone -- the latest Funtoo stages have arrived! (they have dates from 2020-12-14 to 2020-12-15). Improvements: Docker images updated on DockerHub: https://hub.docker.com/u/funtoo VMware Workstation Guest Support in GNOME stages: By default, GNOME stages are now able to run inside VMware Workstation by simply following the Install Guide. Just be sure to enable 3D acceleration in your VM config (this typically is not turned on by default.) Open-vm-tools has been added to the GNOME stage3 and will enable itself if it detects that it's running in a VMware VM. Also, VirtualBox
  7. I do not have the UI built out for this yet, but you can contact me via PM on the forums and I can change it for you.
  8. @rekena I am not seeing anything obvious from what you posted indicating a problem. As @lego12239 asked, what specifically are you seeing? Based on what you originally said, it sounds like GRUB is not even loading for you? If this is the case, then we want to make sure grub bootloader has been installed, so.... Make sure you have run the "grub-install (with arguments from install docs)" command from the install instructions. This will install the boot loader. Then run "ego boot update" in chroot. Then when you reboot grub should load. If grub is loading, but the kernel can't find the
  9. This is normal. The grub.cfg paths are relative to /boot.
  10. This is probably not the problem and shouldn't be the first advice to try to address the issue.
  11. Hey everyone, I have updated our Development Guide to contain information on the "Funtoo Way". The "Funtoo Way" is a really important philosophy about how we do things at Funtoo and I strongly encourage everyone to read it, even if you don't consider yourself a "developer". It helps to explain how our community works and how we can work together. https://www.funtoo.org/Development_Guide Best, Daniel
  12. Note that basic stage3 is up. GNOME stage is being worked on.
  13. Now that the Sabayon collaboration has been announced, yes, it does open up the possibility that Funtoo might provide binaries in the future. It is not a high priority at the moment but I could see this eventually being added to what Funtoo offers.
  14. @davidvs If there is a package in Gentoo that you want in Funtoo, you can open a bug for it explaining why you would like it and we can most likely add it. This is the easiest way rather than messing with getting it working yourself.
  15. I tried to make this clear in the announcement, but it is worth explaining in more detail -- Sabayon Linux and Funtoo Linux are going to remain distinct things. We will make the Funtoo tree work for Sabayon so we can all contribute to the same set of packages. There is no implied change to either Funtoo or Sabayon, besides Sabayon moving to use the Funtoo tree, by announcing this collaboration. Each project continues to make decisions for its own community with no obligation to switch to different technologies unless one project decides it wants to. Over time, we will be collabo
  16. The short answer is that Funtoo is going to remain independent of systemd upstream. I do believe that startup scripts and management of the system are part of what give a Linux distribution its personality. It is central to the experience. Sabayon needs systemd. It will be added to Funtoo's tree for Sabayon, but not enabled in Funtoo. That way, everyone is happy.
  17. The situation with the -bin packages can best be explained this way. For some browsers such as Chrome, we are getting security fixes from Google at the pace of at least once a week, sometimes more. Chrome is a big thing to compile over and over again. It is also some effort to keep the ebuild updated to deal with all upstream changes at this pace. So a big part of this is based on the many releases we are getting from upstream projects that have a huge amount of source code. For us, it is easy to auto-update these -bin packages using metatools (which happens automatically) than
  18. Hey everyone, I'm pleased to announce that Funtoo Linux and Sabayon (https://www.sabayon.org) are joining forces! Now to explain what this means and how it came about. Sabayon is one of the great Open Source projects and has an amazing reputation for delivering an easy-to-use Linux desktop that is built using Gentoo. For quite a while, Funtoo has been supporting the Sabayon effort because we believe in what they do. Over the past several months, in chatting with the Sabayon team, it became really clear that we had a shared vision for creating a friendly and innovative commu
  19. Funtoo Linux stages have been updated to contain the latest stuff in Funtoo: GNOME 3.36.2, latest Mesa/GL stack, support for Intel Iris graphics ("epro mix-in -gfxcard-intel +gfxcard-intel-iris; emerge -auDN @world for those who want to try), and many other updates. Download here: https://www.funtoo.org/Subarches Install docs here: https://www.funtoo.org/Install Enjoy!
  20. If this is still a current issue, it should be reported to the bug tracker, not the forums.
  21. Just going to follow up with some more info. First, thanks to pross for pointing out I had a typo in the 'epro' command above, now fixed! 🙂 The difference between Intel Iris and 'classic' Intel is that 'classic' Intel uses the xf86-video-intel driver (with ebuild of same name), which has classically been the way you get accelerated video with Intel Integrated graphics. The Iris graphics uses the more generic 'modesetting' driver (no special ebuild for this), and uses a gallium-based driver which is now a part of media-libs/mesa so xf86-video-intel is not used at all. During
  22. Hi All, core-gl-kit is now on 2.0-release by default. You will see updates to many packages. Now available are Intel Iris graphics, which is much faster and supported on modern Intel integrated graphics chipsets. To use Intel Iris, perform the following steps: # epro mix-ins -gfxcard-intel +gfxcard-intel-iris # emerge -auDN @world --jobs=3 If you want to continue with the classic drivers, or are not using Intel integrated graphics at all, you can just do the world update to get updates. Please report any issues you encounter to bugs.funtoo.org! There have been major
  23. Please report bugs as needed. Also, yes, currently xf86-video-intel will keep getting pulled in if you have the mix-in for it enabled. You can either disable this mix-in or emerge --exclude xf86-video-intel for now.
  24. Hi All, If you are interested in testing Intel Iris graphics (new accelerated graphics for newer Intel chipsets), here's how you do it: First, make sure your system is up-to-date and you have the latest available version of ego installed (2.8.1) Next, add the following to /etc/ego.conf: [kits] core-gl-kit = 2.0-release xorg-kit = skip This will result in our 2.0-release core-gl-kit being activated, which completely replaces xorg-kit, as all of xorg has been integrated into core-gl-kit 2.0-release. We do not have a mix-in yet for intel Iris graphics. For now, set the
  25. I've already found the issue and resolved it. 🙂 Fix should be in the tree on next regen, in about 25 minutes.
×
×
  • Create New...