Jump to content
funtoo forums

drobbins

Funtoo Linux BDFL
  • Content Count

    322
  • Joined

  • Last visited

  • Days Won

    138

Everything posted by drobbins

  1. Everyone, Please check out https://www.funtoo.org/LXD -- I have begun rewriting this page to give everyone a tutorial-style introduction to LXD and to guide you through the process of setting it up. I have tested these steps myself and it should ensure a fairly pain-free setup of LXD. Note that the second half of the page isn't rewritten yet (Starting with the "features" section) but the top half is.
  2. Hey all, I've been really busy this month -- in Funtoo-land as well as on other projects (currently in Washington, DC area doing some work.) I've just moved 1.4-release to ALPHA status (it was "in development" status) and will be working on getting some alpha builds available. I've updated the snapshot that 1.4 is based upon and frozen 1.4 so 1.4 will be based on a June 21, 2019 snapshot of Gentoo. I will also be looking to start a non-frozen variant of Funtoo again... New Firefox and firebox-bin are now in the tree to address security issues. I've also added the latest version of dev-lang/dart to the tree. This is a very interesting language that comes from Google and recently received a major revamp to make it really nice. Here's an interesting article about it: https://hackernoon.com/why-i-moved-from-java-to-dart-8f3802b1d652 . I am using Dart to do multi-platform development using Google's flutter (which uses Dart) -- and I've enjoyed my experience so far. More updates to come... Best, Daniel
  3. I am seeing only one issue with libevent not rebuilding correctly against the new openssl. I'll be pushing a fix for this shortly... workaround for now is to manually merge or unmask 2.1.8 of libevent and merge. This builds fine against openssl-1.1.1 -- it just happens to have an old mask entry preventing emerge from seeing it.
  4. Folks, The Funtoo Linux 1.3 Maintenance Release 1 is now live, and contains the following updates in order to modernize the distro as well as to allow for a smoother transition to 1.4-release, currently in development: OpenSSL updated to 1.1.1b Ruby stack updated to current 2.6.3 release and moved to independently-maintained status rather than auto-generated. node.js updated to 12.3.0. webkit-gtk updated to 2.24.2. wpa_supplicant update to 2.8 to resolve some connectivity issues. updates to dev-libs/icu, libuv, http-parser, nghttp2, genkernel, eudev System updates should be pretty pain-free with no conflicts or other issues. To upgrade, simply ego sync and then emerge -auDN @world. For security reasons, all packages that use openssl will be automatically rebuilt by emerge. If you encounter complications, a bug report to bugs.funtoo.org would be appreciated. Upgrading from openssl 1.0 to 1.1.1 did require several packages to be updated and there could be a few that were missed and still need patches. Enjoy! -Daniel
  5. Container users, All containers now have private meta-repos now. If you previously had a shared meta-repo, you can fix meta-repo by performing the following steps: # rm -rf /var/git/meta-repo # ego sync Then run ego sync to update your meta-repo as needed. Note that 1.2 is no longer receiving updates and many of you need to upgrade to 1.3. I can assist by loading up a new 1.3 container for you to migrate to -- email me if you are interested in this. ?
  6. Everyone, I have just started getting kit-fixups ready for 1.4-release development. Some key changes that are coming in 1.4-release: move away from eselect opengl and to libglvnd. official support of container-based solution for steam, etc. updates to pam and pambase 1.4-release will be tracking "current" gentoo for a while and will freeze sometime this summer, likely in June 2019. If you want to get involved, chat on #funtoo and look at the latest commits to kit-fixups on code.funtoo.org. I'll also be doing some introductory videos on how to get involved with the new release of Funtoo. -Daniel
  7. And to expand on this some more -- While it's true that we don't have a dedicated security team and rely on users to report CVE's, this doesn't mean that we trail behind Gentoo in all areas. For example, we have a fix in gettext for CVE-2018-18751 that gentoo does not appear to have. We also had important fixes for avahi remote exploits before Gentoo. In general this means that our ability to be up-to-date with CVEs depends upon our users' ability to report these. In areas where we have had good reports, we have sometimes had things fixed sooner.
  8. Hi All, Forums have been updated to the latest version and I have re-enabled a new version of member map. Let me know if you encounter any issues. -Daniel
  9. Just to expand on this, it is perfectly fine for us to be a bit behind Gentoo in terms of updates, and even quality of ebuilds in some areas. We will improve, as I get more videos out to help our community do better and my job is to keep our bug tracker responsive to reported issues. I think it is important to be realistic and realize where we are now, it would be foolish to think that a small community is doing everything it needs. That is fine -- we are improving. That is the key thing.
  10. Hi all -- We are in the final stages of prepping a total rewrite of the graphics stack in Funtoo which is based on libglvnd rather than "eselect opengl". This work was done by TemptorSent and improves our NVIDIA support but also essentially updates how GL is handled under Funtoo for everyone to be more modern. If you want to play around with this and have NVIDIA hardware, see https://www.funtoo.org/Package:NVIDIA_Linux_Display_Drivers#TemptorSent's Experimental NVIDIA ebuilds . I actually have libglvnd running fine on my Intel-based laptop as well, so these steps can be used on any hardware -- just re-emerge mesa and skip nvidia-drivers. Debian-sources-lts 4.9.168_p1 is now unmasked for everyone. I have also significantly updated and rewritten the pam and pambase ebuilds. These incorporate the latest updates from gentoo plus a bunch of funtoo changes. Basically, the new pam-1.3.1.20190226.ebuild contains the very latest upstream fixes for pam, and also incorporates the old pambase ebuild. The new pambase ebuild -- pambase-20190426.ebuild -- is simply a 'virtual' package. It just depends on pam to satisfy any dependencies of packages that require pambase. The other funtoo-specific changes in pam are: Relax pam_limits so that it attempts to set resource limits but does not prevent you from logging in if it somehow fails to do this. This is important for preventing lxd users from being locked out due to /etc/security/limits.conf changes in containers. Incorporation of pam_faillock, which is optional functionality that can disable an account login after multiple failed login attempts. This is required by some security standards. (This patch comes from Red Hat.) Deprecate consolekit and systemd support in the ebuild. Deprecate multilib support in the ebuild. This stuff is currently keyword masked and expert users are encouraged to unmask them and test them -- but be prepared for the possibility of login issues on your test system, which means have a livecd or liveUSB handy. Best, Daniel
  11. @zogg if you are looking for others to do the work for you and keep everything up-to-date for you, this is not the right distro for you. We track CVEs that are reported on the bug tracker and we actively incorporate any CVE fixes. But they need to be reported on the bug tracker. Definitely use Gentoo if you want a bunch of developers to do all the work for you.
  12. Also, the 3 kernel config warnings you see on emerge don't appear to be problematic. I think they can be safely ignored.
  13. Just for everyone else, I resolved this for @skygunner -- If you ever have an issue running docker in your container, just let me know and I'll take care of it.
  14. Hey I just want to jump in and say it's OK, I understand if there are some people that are disappointed about us not having pure rolling releases anymore. It's fine to express your opinions here. I think that's totally understandable, frankly. Now yes, these changes were totally needed and like I said earlier, there is a strategy that is being very successful so far even though it's in its early stages. The strategy is that I support our users (with things like YouTube videos, code.funtoo.org, fchroot) to be contributors to Funtoo. So yes, right now I think it's fair to say we are playing a bit of catch-up with Oleg moving on to other things -- BUT, considering we just started this effort, I also think it's fair to say that in time we will likely catch up and even go beyond what we were capable of before. And that means that we can push ahead more with many more updates and possibly even a more up-to-date release (betas?) or a true rolling release again. In the mean time, I ask @lazlo.vii and others to be supportive of those expressing disappointment since I want people to have a place to vent their disappointment -- I don't see it being overboard or in poor taste at all -- and in my experience, the worst thing for a community is if any disappointment is bottled up and never expressed (and then we need to guess why people are unhappy) so I would much rather have people share how they feel. As long as they understand the reason for the decision, it's fine to share feedback and vent a bit.
  15. Note to all -- this kernel has been unmasked and is ready for general use.
  16. Hey Everyone, @temptorsent has graced us with completely rewritten-from-scratch nvidia-drivers and related ebuilds that will be serving to replace the ones we are currently using from Gentoo. Please help us out and test them! See the instructions here for how to start using them for testing: https://www.funtoo.org/Package:NVIDIA_Linux_Display_Drivers#TemptorSent's Experimental NVIDIA ebuilds These ebuilds will be enhanced to support our upcoming GPU accelerated container support. Best, Daniel
  17. Also note that @temptorsent has rewritten all the nvidia ebuilds from scratch, and we're going to use these improved ebuilds as a basis for steam support. We're trying to launch the beta of these drivers today. I'll be testing to make sure that containers pick up and properly use the 32-bit nvidia libs that are required for GPU acceleration to work with steam.
  18. All, @bcowan has made our day better with a new debian-sources-4.9.161_p1 ebuild which is available for testing, but currently package-masked so it doesn't install by default. To get emerge to see it, add the following to /etc/portage/package.keywords: =sys-kernel/debian-sources-lts-4.9.161_p1 ** Then do: # emerge debian-sources-lts # ego boot update # reboot Please report any bugs or issues to https://bugs.funtoo.org. Thanks ?
  19. Yes, the install docs should be updated. The defaults in /etc/boot.conf are sufficient and I always just install the boot loader and then run "ego boot update" and all is good. if you would like, please update this page to make it better. You want to edit the one that's part of the section-by-section guide (not the "all on one page" install guide.)
  20. Cool, can you provide info on the steps you used -- I'd like to test this out.
  21. @dkg Sorry that Funtoo is not working for you but unfortunately the multilib implementation in Gentoo that 'works' for people has serious technical issues that make it hard to maintain. It is getting in the way of certain important efforts in Funtoo. We are likely going to circle back to multilib at some point but with a better implementation. The containerization solution for steam and friends is moving forward nicely and is near-complete. Based on testing, the solution using lxd is the easiest to use. The delay has been related to getting all the NVIDIA bits properly integrated so we can do CUDA/OpenCL and NVIDIA GPU acceleration seamlessly inside containers. I am also working on GPU-accelerated docker support but I think docker is a bit more of a pain to use than lxd.
  22. We are not doing rolling release for the following reasons: Too much time is spent on fixing various breakages coming in from Gentoo, which takes time away from other things... other things are more important such as new technology like fchroot and the upcoming containerization solution... If users are interested in certain packages being updated, I am encouraging them to submit a pull request and maintain these ebuilds themselves, so I am going to focus on helping YOU maintain ebuilds rather than have a few people (this has generally been Oleg) maintaining them for everyone. This model doesn't scale -- we all need to do a little bit rather than a few people doing a lot. See the YouTube channel here: https://www.youtube.com/channel/UCKmOY6p3c9hxv3vJMAF8vVw for tutorials Short-term, this means development slows down. But in reality, it will speed up development greatly. For those hanging out on IRC, you know that Oleg who has helped to maintain Funtoo for years has moved on to a new chapter in his life, so he is no longer active on Funtoo. But even though I am not slaving away over here, thanks to incoming pull requests Funtoo is continuing to move forward and be responsive to user needs. So think of it as a course correction as we become more agile and community-oriented, and be part of the solution. If you are reading this, it means you are part of the Funtoo community and just as able to contribute to Funtoo as anyone else (maybe with some tutorials/videos to help). When I work on technologies, I am trying more to work on key tools that help the community be more productive (like fchroot) rather than focusing on specific ebuilds, which I am leaving to the community to manage using pull requests. Best, Daniel
  23. There is some upgraded forums software available which I will upgrade to soon.
  24. Hey Everyone, I want to officially announce 'fchroot', Funtoo's new QEMU-based chroot tool which allows you to chroot into ARM stage3's and live systems using your 64-bit PC. It is pretty neat stuff. Check out this video for a demo: Enjoy ? -Daniel
×
×
  • Create New...