Jump to content
funtoo forums


Funtoo Linux BDFL
  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by drobbins

  1. A lot of users have been unable to log in to the forums over the past few weeks. This is now fixed! Apologies for this issue. Please contact me on IRC (freenode #funtoo) or send me an email if you are continuing to have issues.
  2. I've gone ahead and updated dropbox so that we now have the latest version for Linux.
  3. Hi All, By default, we are now building stage3's using Funtoo Linux 1.2 release as default. This means that new installs will have this in their /etc/ego.conf: [global] release = 1.2 If you are still using release 1.0, that's fine -- your system will continue to use 1.0. When you upgrade to ego 2.4.1 or later, you will be able to set the release as above in your ego.conf, re-run "ego sync", and you will be upgraded to the 1.2 release. The release= setting is simply a short-hand for setting the various 1.2-related kits individually in the [kits] section, so many of you are already running 1.2. Best, Daniel
  4. Gentoo has completed an audit of the compromise, which is visible here: https://wiki.gentoo.org/wiki/Github/2018-06-28 A few repositories had some attempts at malicious changes, -- inserting "rm -rf /" at the top of quite a few ebuilds, etc. None of these malicious changes made it into Funtoo.
  5. Today, Gentoo's GitHub account was compromised. From initial observation, this was a pretty blatant attack, akin to vandalism, and not an attempt to stealthfully compromise the integrity of Gentoo systems. However, the Gentoo project is urging caution until GitHub has restored the git repos to proper function and ensured their integrity, and for safety to treat all repositories as "compromised." As a precaution, we are now pulling updates directly from Gentoo rather than from Gentoo's GitHub account. Reference: https://www.gentoo.org/news/2018/06/28/Github-gentoo-org-hacked.html
  6. @Jean you are probably correct -- as it is a wiki, please, if you could help us out, log in and fix it :) Thank you.
  7. Yes, the docs in the README for meta-repo are outdated and I will update them soon. Sorry for the confusion.
  8. Hey Everyone, Thanks to some good work by @temptorsent, we now have gcc-7.3.1 in core-kit 1.2. This version of GCC has spectre V2 fixes, so if you compile the latest debian-sources-lts or latest debian-sources kernel after gcc-7.3.1 is installed, and reboot, you should be protected against spectre V2. Please use this tool to test your vulnerability, both before and after your kernel upgrade, to make sure everything went as planned: https://github.com/speed47/spectre-meltdown-checker See https://www.phoronix.com/scan.php?px=GCC-7.3-Released&page=news_item for info on gcc-7.3. Best, Daniel
  9. I would say just skip that step.
  10. Hi All, The Funtoo Linux 1.2 release is now available for use. Many of us are now running Funtoo Linux 1.2. Here's how to upgrade your system to Funtoo Linux 1.2. Note that soon, 1.2 will be the "default" version of Funtoo Linux. For now, you need to perform certain steps to switch over. We're doing this so that power users can switch over right away, and so we can make things a lot easier for less-experienced users to upgrade to Funtoo Linux 1.2. One of the features I have been working on behind-the-scenes is an "easy upgrade" functionality for ego, to perform big updates automatically. This functionality is not yet ready, but is being worked on. When this "easy upgrade" functionality is ready, 1.2 will be released via "easy upgrade" to systems who have not yet upgraded. For now, power users can upgrade by performing the following steps. First, select the new kits in your /etc/ego.conf: [kits] core-kit = 1.2-prime security-kit = 1.2-prime kde-kit = 5.12-prime media-kit = 1.2-prime java-kit = 1.2-prime ruby-kit = 1.2-prime haskell-kit = 1.2-prime lisp-scheme-kit = 1.2-prime lang-kit = 1.2-prime dev-kit = 1.2-prime desktop-kit = 1.2-prime Then, perform the following steps, as root: # ego sync This will activate the new kits. Now, if you have a /etc/portage/repos.conf/funtoo symlink, remove it: # rm /etc/portage/repos.conf/funtoo Next, # emerge -u1 gcc This will upgrade gcc. Next, # emerge -u1 glibc libnsl libtirpc rpcsvc-proto Glibc will now be upgraded. Next, # emerge -auDN @system This will upgrade your core system set of packages. Next, # emerge -auDN @world This will upgrade all other packages. Next, # emerge @preserved-rebuild This will rebuild packages that are linked to old libraries. Now, final step: # revdep-rebuild --library 'libstdc++.so.6' -- --exclude sys-devel/gcc This will rebuild all remaining packages that need to be linked against the new libstdc++. At this point, you are now upgraded to Funtoo Linux 1.2! Please report any bugs to https://bugs.funtoo.org and let us know of any issues you experience, either as part of the upgrade, related to dependencies, or related to functionality on your upgraded system. Best, Daniel Robbins
  11. Hi All, After some recent upgrades to the forums, there were some login issues, in particular issues with new users logging in to the forums for the first time, and other bugs. I believe I have tracked these down and resolved them, but if you for some reason still do experience issues, please hop on to IRC (freenode) and jump in #funtoo-dev and let us know. Or #funtoo, for that matter. Thanks, and apologies for the issues. -Daniel
  12. Hi All, Thanks to funtoo supporters, we now have a new fast download service that is available for everyone. Upgrading to the latest portage-2.3.25_beta2 will enable this service. The fastpull service consists of a lot of different moving parts, but it adds up to distfiles downloading very fast and being available. Here's how it works. When we regenerate meta-repo and kits, ebuilds are scanned for new SRC_URI tarballs, etc. These new distfiles are queued for download. Our fastpull spider then downloads these distfiles automatically, and uploads them to Google Cloud Storage. When you try to download a SRC_URI, you hit https://fastpull-us.funtoo.org first, which redirects you to the download on fast Google Cloud Storage. The design of fastpull is to ensure that all distfiles are always available going forward. It will also help us to identify situations where for some reason or another we are missing a distfile for download, although these situations should happen less and less frequently (and hopefully disappear) now that fastpull is deployed. Best, Daniel Robbins
  13. We're running a bit late, primarily due to flu stuff.... 1.2 is almost ready.
  14. One note that when we upgrade to core-kit-1.2, the minimum kernel supported will be linux-3.2. This upgrade should be happening within a week. You can choose not to upgrade and stay at core-kit 1.0 if you need OpenVZ RHEL6 compatibility. So it does appear that we will be moving away from OpenVZ for our default build.
  15. We will continue to support the OpenVZ RHEL6 kernel. This kernel will still be maintained upstream for several years. LXD runs on newer kernels and is getting mature enough to use in production, so it worked well for us.
  16. Migration typically involves 1-5 minutes of downtime. Typically if you do not have a ton (like 100GB of data) the downtime is closer to one minute. So pretty painless.
  17. New LXD containers should allow full use of iptables. We need to ensure the modules you need are loaded but beyond that, things should be pretty well-supported.
  18. We currently offer iptables support and have for a long time. For IPv6, our datacenter doesn't have native IPv6 but we will likely set up a tunnel soon to provide IPv6 addressing. That's kind of a bummer. It is more than offset by our datacenter powering our servers using solar power, and passively cooling them (no AC needed) for over half of the year, giving our tiny datacenter an efficiency that rivals Facebook and Google's build-outs. As for new technology, we are now using ZFS RAID-Z, Intel Optane to accelerate our IO, have 40 core (80 cores hyperthreaded) systems, and are now using LXD and kernel 4.14.12-2 (migrating away from OpenVZ and RHEL6 kernels.) And we also document our setups so others can do the same. (Docs for our 2nd generation infrastructure are in the works.)
  19. Hi All, We have deployed our second-generation compute infrastructure and have begun the process of moving containers over to it. This funtoo-based infrastructure is running on faster hardware and is using ZFS for storage. For more information on our second-generation platform, see https://www.funtoo.org/Funtoo_Containers Also note that plans have been upgraded. Our base plan for $15/mo now comes with 8 cores and 60GB of storage (was 6 cores and 50GB previously.) The medium plan now has 16 cores and 120GB of storage (was 12 cores and 100GB). And our large plan now has 32 cores and 240GB of storage (was 24 cores and 200 GB). All existing containers will be automatically upgraded to these new resource levels when they are migrated to the new infrastructure :) Best, Daniel
  20. We are currently deploying our 2nd-generation compute infrastructure which runs on LXD and debian-sources-4.14.12-2, which provides some mitigation for the recent exploits. We are also running the latest Intel microcode and will continually update as new fixes become available.
  21. Hi All, In order to have more predictability for users, Funtoo Linux is going to adopt a six-month release schedule starting in 2018. Our kits are currently at 1.0-prime, and we are going to skip over 1.1-prime (it didn't get done fast enough) and jump to 1.2-prime. We are going to start development on 1.2-prime today, December 28, 2017, with a planned release of the production 1.2-prime on January 21, 2018. We will then maintain the 1.2-prime kits for the next six months, until they are replaced with 1.3-prime. The schedule in detail is as follows: December, 28, 2017: start development on 1.2 January 1, 2018: we will be rolling out a python-modules-kit and perl-modules-kit as new kits (for 1.0+) January 4, 2018: Alpha release of 1.2 January 11, 2018: Beta release of 1.2 We will have a release candidate when we feel we are ready, with a scheduled production release on January 21, 2018. On February 1, 2018, the 1.0-prime kits will be deprecated and users will be migrated to the 1.2-prime kits (this should be seamless unless you've hard-coded 1.0 or 1.1-prime kits in ego.conf.) For 1.2-prime, what we are going to attempt to deliver is a default gcc of 6.4 and all ebuilds updated to be in sync with Gentoo as of January 2018. We will be using a 'current' (non-snapshotted tree) until around January 4th when we will freeze the tree and then will start backporting security fixes and updates. In a few hours, the 1.2-prime kits will appear but will be tagged as DEVELOPMENT quality, so they should not be used until they are made default. I will post updates here on our progress. Regards, Daniel
  22. It looks like mesa-17.2.7 is something that we should bump since it is the latest stable version and fixes a lot of bugs since 17.2.0.
  23. I like the idea. We can collect usage data on ebuilds and thus know what ebuilds we should prioritize for users. As long as there is an opt-out for people, I think it's ok. We can add this functionality to ego.
  24. Also, just a note, I don't recommend -O3 and it is not always faster. -O2 contains all the 'almost always good' optimizations, and -O3 contains some questionable ones.
  25. OK, I've gone ahead and made the change.
  • Create New...