drobbins

Good questions. The issues with blockers due to not having the correct version available will be disappearing with 1.3-release when it is available. It currently happens because we are using different snapshot dates for different parts of the tree, and we are not going to to do that anymore with 1.3+. 1.3-release will be a 'frozen' release when it is released, meaning it will gradually become out-of-date, though we will be bumping critical packages and backporting security fixes. But the process we use to create 1.3 will be used to launch 1.4 development immediately, so we are getting better at this and releases will come a lot more often ? The goal is to have a very stable and tested release that doesn't have unanticipated changes, until you want to pull them in by moving to the next release. So this is the pattern we are trying to establish. Hopefully we can get releases to the point where they are coming frequently enough people do not feel like packages are "stale". That is the goal. With the improvements in our tools, I think we will be able to achieve it. It is actually easier to do releases often rather than infrequently -- right now we are just in the "growing pains" stage where we are in the process of moving to a more rapid release schedule. As funtoo's team grows, we will have the person-power to actually move ahead of Gentoo in more areas. Right now, these areas are limited due to us only having a ~4 person team and Gentoo having several hundred developers.

Yep, we use snapshots and work on them but 1.3 is now tracking Gentoo current packages, but will be frozen at some point too. But we are going to really much, much more often so the packages won't get as old.

The Funtoo authentication system has recently been upgraded to use Authy, a SMS-based verification service. We're using this to protect the funtoo community against spam bots and other nasty things, which are unfortunately an issue we need to deal with. You will not be able to log in to Funtoo until you upgrade your account! To do this, go to https://auth.funtoo.org/login, log in, and you will be prompted to provide an SMS number to verify your account. This will only happen once -- it normally happens upon account registration only -- but existing Funtoo users will need to go through this extra step. Apologies for the inconvenience, but unfortunately this kind of thing is becoming necessary. Best, Daniel

Hey Everyone, We are doing a lot of heavy-lifting in the 1.3 kits to get them ready for human consumption. Please understand, though -- these kits have a Kit Stability Rating of "DEV" -- which means "developers only" -- if you use them, it's assumed you're helping and aligning/coordinating with our development efforts. This means -- for now, avoid reporting bugs on 1.3 kits as this doesn't really help us out (yet). Most things are broken as we move stuff around and reorganize our ebuilds for 1.3, so we don't need help finding broken things. :) That will change in a couple of weeks as we move into ALPHA and then BETA stability. Then we will be ASKING you to test it and report bugs. But not yet! :) Best, Daniel

Hi all, Please test ego-2.6.0, which is currently masked for testing. As many of you have noticed, there have been significant changes to kit generation and currently, ego is less "flexible" about mixing and matching kits from different releases. This is a side-effect of massively improved merge scripts, which now leverage python's asyncio, use a thread pool for database operations, and have much better internal design. I have put a lot of work into this new codebase and the new design is much better foundation for future development. Currently, it is possible to select a custom xorg-kit or gnome-kit, but all other branches are locked down to the release. For those who may be upset -- We have never "officially" supported anything but the standard collection of release kits anyway, with some tweaks of xorg-kit and gnome-kit, so users who push the limits of mixing and matching kits right now have been using Funtoo in a way that is beyond the scope of what we intended to deliver, likely without realizing it. So if you want to use an unusual combination of kits -- awesome -- we want to support this officially in time, but we are working on getting there the right way rather than committing to supporting all these unusual combinations all at once. If you have gotten accustomed to this flexibility in the past, know that this lack of flexibility is only temporary as we continue to build out our next generation of innovative technologies for managing kits. Re-enabling support for any old combination of kits is going backwards, in my opinion, and instead we need to move forward to OFFICIALLY support more combinations of kits. For the time being, you may need to write a small script to get things exactly how you want in meta-repo. We encourage people to use combinations we officially support if possible -- 1.2 with some variation of gnome-kit or xorg-kit. Things will be easier that way for the time being. Also, we now have the 1.3-release kit names and definitions finalized, so this will allow us to move forward with 1.3 release development. Best, Daniel

Also, as a side note, in the wiki editing guidelines I have updated the Translation section to contain info related to translating the new install guide.

Everyone, I hope you are enjoying the new wiki. I've added a catalog of all Intel 64-bit processors in existence, along with mapping each of these 1800 CPUs to the appropriate stage3 to download. You can see this database here: https://www.funtoo.org/Funtoo_CPU_Database When browsing 64-bit Intel subarch pages, they will now display a subset of this list -- the list of CPUs for which that particular subarch is recommended. Enjoy, everyone. Oh -- And AMD is coming next ;)

Just wanted to let everyone know if you don't visit www.funtoo.org often that we've updated our wiki with a new version of mediawiki (finally) and a new skin! Enjoy, everyone.

The Funtoo Linux Install Guide has been updated so it now displays as a chapter-by-chapter guide by default: https://www.funtoo.org/Install/Introduction It is still possible to view it as a single page if you prefer (or for printing/converting to PDF) .. there is a link to the full page version in the page above (or go to https://www.funtoo.org/Install)

The 1.0 release of Funtoo Linux is not going to be maintained after September 30, 2018. So please be sure to upgrade your systems to Funtoo Linux 1.2 using https://www.funtoo.org/Upgrade_Instructions so that you will continue to get updates! We will also be starting development on Funtoo Linux 1.3 in a few days, on August 31. We are moving to a new agile (scrum) process, where we will be doing 1-week sprints (time-constrained sets of work). Our work will include some portion of fixes for 1.2 and some new work on 1.3. When we as a team decide that 1.3 is ready for various milestones (alpha, beta, release candidate) we will mark it as such. Thus, we have no hard deadline for 1.3 as I do not want to try to hit arbitrary dates that are not based on the actual work. But we will get there, sooner rather than later!

Ryzen stages are now available for download at the following links: https://build.funtoo.org/funtoo-current/x86-64bit/amd64-zen/ https://build.funtoo.org/funtoo-current/pure64/amd64-zen-pure64/ A new pure64 stage is building right now. Also, many thanks to CDN77 for sponsoring Funtoo -- our downloads now use a combined funtoo/CDN77 infrastructure for world-wide speed rather than a mirroring infrastructure. This applies to stage3 downloads as well as fastpull downloads.

Anything helps. If you can put some good ebuilds in an overlay, with a README.rst, often we can take it from there.

I think a "faillock" USE variable should be introduced to install the updated /etc/pam.d/system-auth and enable faillock. Right now this is too difficult and error-prone to use.

We need maintainers for non-GNOME desktop environments who will help us test and maintain kits. Please let me know if you are interested in doing this. The primary reason the DE's are out-of-date is because we need some people to volunteer to maintain the DE's and apply funtoo-style testing to them. We don't want to just track Gentoo's changes since we then have no process to ensure things are working as things get updated.

The following ebuilds are available for testing by end users and are currently keyword-masked. Add the following to your package.accept_keywords to test: =sys-apps/portage-2.3.47 ** =sys-devel/gcc-7.3.1-r3 ** =sys-apps/corenetwork-1.6.4 ** =x11-drivers/xf86-video-intel-2.99.917_p20180609 ** Here is a quick review of changes in the above packages. Portage is a new version from Gentoo, which has passed all unit tests. Gcc-7.3.1-r3 is a much-improved ebuild from @Temptorsent which now enables SSP by default for improved security. Corenetwork-1.6.4 has some bug fixes that have accumulated in git, and the new xf86-video-intel is the latest from git and needs testing, particularly on newer intel hardware like Coffee Lake and Kaby Lake refresh -- and it always seems like google chrome has rendering issues, so be sure to test Chrome with this driver. Please test these things and report back your experiences.

Hey everyone, A large number of home routers are vulnerable to malware and can be used to scrape your passwords and other important data. Please take a look at https://blog.talosintelligence.com/2018/06/vpnfilter-update.html -- specifically the "Known affected devices" part -- and see if your router has an exploitable security hole. Affected devices listed below.... Given our observations with this threat, we assess that this list may still be incomplete and other devices may be affected. ASUS DEVICES: RT-AC66U (new) RT-N10 (new) RT-N10E (new) RT-N10U (new) RT-N56U (new) RT-N66U (new) D-LINK DEVICES: DES-1210-08P (new) DIR-300 (new) DIR-300A (new) DSR-250N (new) DSR-500N (new) DSR-1000 (new) DSR-1000N (new) HUAWEI DEVICES: HG8245 (new) LINKSYS DEVICES: E1200 E2500 E3000 (new) E3200 (new) E4200 (new) RV082 (new) WRVS4400N MIKROTIK DEVICES: CCR1009 (new) CCR1016 CCR1036 CCR1072 CRS109 (new) CRS112 (new) CRS125 (new) RB411 (new) RB450 (new) RB750 (new) RB911 (new) RB921 (new) RB941 (new) RB951 (new) RB952 (new) RB960 (new) RB962 (new) RB1100 (new) RB1200 (new) RB2011 (new) RB3011 (new) RB Groove (new) RB Omnitik (new) STX5 (new) NETGEAR DEVICES: DG834 (new) DGN1000 (new) DGN2200 DGN3500 (new) FVS318N (new) MBRN3000 (new) R6400 R7000 R8000 WNR1000 WNR2000 WNR2200 (new) WNR4000 (new) WNDR3700 (new) WNDR4000 (new) WNDR4300 (new) WNDR4300-TN (new) UTM50 (new) QNAP DEVICES: TS251 TS439 Pro Other QNAP NAS devices running QTS software TP-LINK DEVICES: R600VPN TL-WR741ND (new) TL-WR841N (new) UBIQUITI DEVICES: NSM2 (new) PBE M5 (new) UPVEL DEVICES: Unknown Models* (new) ZTE DEVICES: ZXHN H108N (new) * Malware targeting Upvel as a vendor has been discovered, but we are unable to determine which specific device it is targeting.

OK, I'm testing out CDN77, a worldwide content delivery network which should massively improve download speeds in "slow" areas. Please, let me know if this makes a positive difference for you. It should.

I will look at doing a European mirror for fastpull.

Just added one -- should pop up under official funtoo announcements soon.

We now have detailed instructions on how to upgrade to release 1.2, available here: https://www.funtoo.org/Upgrade_Instructions Enjoy. -Daniel

Funtoo containers /var/git/meta-repo has been upgraded to release-1.2. For information on how to upgrade your containers, see these detailed instructions. If anyone needs their container to be wiped and reloaded to a fresh 1.2 installation, please email us at support@funtoo.org and let us know. Best, Daniel

Since we are now using kits to manage stability, the stable (and experimental) profiles have been deprecated. If you are using one of these profiles, you will notice ego sync/emerge complaining. To fix this, do: # epro build current This will resolve the issue.

We experienced about 7 hours of downtime today (early AM to morning US time) due to wildfires in southern Colorado that melted our network uplinks. We are now utilizing a southbound uplink until the northbound links are repaired. All is well in Funtoo land -- just... fires! :)

Hi All, gnome-kit 3.26-prime has been made the default gnome-kit, upgraded from 3.20-prime. emerge -auDN @world and a restart of xdm should be sufficient to upgrade to the new GNOME. I did keep the older gnome-control-center due to really bad multi-monitor configuration in 3.26's control center. Everything else is upgraded to 3.26. -Daniel

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.