Content Count

Popular Content

Hi All,
I've created a new YouTube vlog entry for your enjoyment. This one is about the latest shocking news of being let go from a job. View it here -- I appreciate it if you help me get the word out about my channel, send me some upwardly-pointing thumbs and possibly even subscribe! ? Thanks!
Best,
Daniel

Hey everyone,
1.4 is almost ready to be released. Thanks so much to everyone who has contributed pull requests for 1.4 and tested 1.4. There's still a bunch of work to do, but there always will be and I believe 1.4 will be our most well-tested release so far.
After 1.4 is released, we will start development on 2.0, to be released some time in the Fall (Sept/Oct timeframe). I've been thinking about the release schedule a lot and I think that aiming for a .0 release every Fall seems to be a good idea. This means the work is completed well before the winter holidays, and fall in the US is a good season of change and looking forward to new things.
What I have left to do for 1.4 is to update the ARM builds to 1.4 and then also to update our documentation, release notes, upgrade steps and related docs. I want to incorporate the new video cards mix-ins into the official installation steps and not leave it to just be a "First Steps" item after install. This way, people can use the install docs to get their desktop environment of choice up and running, too.
I hope to get all this completed in the next few days.

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

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

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

Hi All,
ego-2.2.0 has been released, and is an important update, and will be appearing in meta-repo soon.
New functionality has been added to help you view kit configuration. To view your current kit settings, type:
# ego kit status
This will display your current kit settings, as well as their stability level. The stability level is set by Funtoo and lets you know if you are running something we consider 'stable' or not. We recommend that all our users use kits that have a 'prime' stability level. Note that this is different than the kit having 'prime' in its name! When I create a kit, I may call it 1.1-prime if the goal is to make it production-quality, but the moment it is created, it is still considered 'dev' (developers only) status. Type "man ego-kit" for more information on this.
It is now also possible to view a similar listing, but one that displays ALL available kits and their stability levels, by typing:
# ego kit list
This new release of ego also includes a host of other improvements, such as improvements to the "ego doc" MediaWiki parser.
Enjoy, Daniel

Greetings during unusual times --
I wanted to let everyone know that the following ebuilds are currently being auto-updated using our new, amazing autogen framework. That means we will always have current versions:
www-client/firefox-bin
www-client/google-chrome
www-client/google-chrome-beta
www-client/google-chrome-unstable
www-client/brave-bin
app-admin/pass
app-admin/passwordsafe
net-misc/anydesk-bin
mail-client/thunderbird-bin
net-im/discord-bin
net-im/zoom-bin
net-im/slack-bin
More are on the way! For those working remotely, I recommend checking out zoom-bin (Zoom meetings) as well as anydesk-bin (AnyDesk) for fast remote desktop. They work great under Funtoo.
Enjoy, and stay safe.
-Daniel

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

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!

Hi all,
A multitude of new kits are coming your way. I'll give you a list of what they are and share other kit-related updates with you.
The new kits you'll be seeing soon are: ruby-kit, haskell-kit, ml-lang-kit, lisp-scheme-kit, and xfce-kit. With the exception of xfce-kit, these kits are all essentially sub-kits of dev-kit (and now have their own kit, just to try to pare down dev-kit a bit.) xfce-kit is for the XFCE 4.12 desktop environment.
In addition, we have snapshotted/frozen the following kits: *java-kit*, ruby-kit, haskell-kit, ml-lang-kit, lisp-scheme-kit, *dev-kit*, xfce-kit and *desktop-kit*. Note that the kits in red are ones that previously following gentoo-current, and are now snapshotted as of today (Oct 22). The other kits listed are the new kits.
With this wave of new kits, I am pushing forward the kit paradigm. With additional snapshotting of previously 'current' kits, I am putting funtoo's developer focus on getting the new 1.1-prime core-kit, media-kit and friends truly ready for production. The goal is to shift major updates to that they come via kit upgrades rather than a trickle of new package updates.
What should you expect over the rest of the year? Expect further stabilization of our now-snapshotted kits. Also, when PHP 7.2.0 is released, expect a php-kit that will be snapshotted at 7.2-prime rather than following current as it does now. You should also expect to see a new generation of kits made available so you can select more recent packages. Also on the radar are automated features to help switch kits cleanly -- think of these as things like perl-cleaner and friends but that get automatically triggered when you switch kits to ensure a smooth transition. And yes, you will likely see a few more kits added to the mix, along with new ego features.
With these new kits, the kit paradigm has been further advanced and will continue to advance. Along the way, you may feel that Funtoo Linux updates are getting 'stuck' or not going as quickly as you like, due to kits being frozen. If this impacts you, please provide us with feedback so we are aware of what things you need updated and why -- and understand that the pause in version bumps is more of a temporary phenomenon rather than a permanent reality. The updates will come -- in the form of kit bumps! The adjustment of our dev process will happen, and soon will reap rewards by offering stability as well as the latest ebuilds for you to choose from.
Please feel free to share your questions and concerns on this thread.
Best Regards,
Daniel

Hey all, welcome to the new forums! Our old forum software has been upgraded to the latest version and I'm going to be working hard to help make this a really great resource for everyone.
Our "Funtoo Universe" section is set up in a traditional forum style, and "Help Central" is now in a Q&A-style mode. Let me know how you like the Q&A style mode. Both sets of forums allow you to tag posts as being answered and we have the ability to flag the best answer.

Hi folks O/
few years ago I wonder about a friendly version of Gentoo and Funtoo, the gentoo community don't liked, but I keep did some tests but I didn't continue, well, few week ago I start again, but this time only a Funtoo Friendly version, and now I have something really beginning.
the project will resume in few flavors and one version with a overlay with update packages and few extra.
the funtoo flavors are X+openbox, gnome and Plasma, they are just the Funtoo Stage3 Generic with few packages and some configuration.
and has one version with plasma, but with an overlay with few update packages and other stuffs, a stage more out of the box, I want make something to people learn about gentoo/funtoo or for who use the system without spent hours to build the system.
the webiste will be done in the next weeks, and the stages will be available in the next days "sorry, I'm with one pc now, and the net is a turtle".
website -> https://bentoo.info/
binhost -> http://binhost.bentoo.info
github repos :
overlay -> https://github.com/lucascouts/bentoo
configurations -> https://github.com/lucascouts/bentoo-cfg
I don't know if the funtoo community will like but anyway I'll forward with this project, but will be great if few users could help with feedback or criticisms.
thank you anyway ?

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

Hi All,
Within 12 hours, I plan to move 1.3-release to BETA status.
Along with this comes the very important change on 64-bit platforms -- I am removing multilib and making "pure64" compatibility the default. This means that 1.3-release builds with the x86-64bit arch will be 64-bit only.
This is done for a variety of reasons, most important of which is that the world has had a 64-bit PC instruction set for approximately 15 years. It is time to drop 32-bit support. For those who still need 32-bit support, it will be available via a Funtoo 32-bit chroot setup.
The story behind multilib is rather complex and interesting, and might be the focus of a future blog post, but for now, you will just have to trust me -- multilib support in Gentoo is a pain in the butt. It takes a lot of effort to work with and slows us down. Our efforts are best spent in other places, and chroot should work for the vast majority of users who truly are running a critical 32-bit application (other options are 32-bit containers, etc.)
EDIT: Upgrade Instructions Here: https://www.funtoo.org/Upgrade_Instructions/1.3-release
Best,
Daniel

There has been a lot of updates to Funtoo Linux 1.4 since its release -- most of these not officially announced. So it would be a good idea to make an official announcement of many of them:
SELinux Updates
Firefox and Firefox-bin 69, updated thunderbird.
New gfxcard-nvidia-legacy mix-in for older drivers.
Updated NVIDIA drivers to latest releases.
Conky updated.
kde-plasma merge fixes.
mesa merge fixes and version bump.
ffpmeg updated to latest release, with fixes for arm-64bit.
Latest Spotify release added.
Openrc net-online major improvements.
New Language added: crystal (check it out)
debian-sources/debian-sources-lts updates and now compile using your -march settings (since custom-cflags is now enabled by default.) Prior to this they compiled using generic 64-bit optimizations on x86-64bit.
New encrypted-root mix-in to be used to enable LUKS in genkernel/debian-sources(-lts). To use, enable this mix-in and re-build your debian-sources(-lts) kernel.
Rust-kit is now at 1.37-prime
New dev-lua/lua and fixes for lua-using packages. Ebuilds using lua-5.2+ should use the new dev-lua/lua ebuild (not the legacy dev-lua/lua.)
fwupd bumped to 1.3.1
nginx, nginx-unit, dovecot, php, mariadb
vivaldi updated
dovecot updated
Anything I forgot? Follow up in this discussion thread.
MANY OF THESE FIXES WERE SUBMITTED BY OUR USERS! Thanks to bcowan, perfinion, jhan, tux, tczaude, KlipKyle, scottfurry and anyone I forgot to mention for making Funtoo better for everyone 🙂 🙂 🙂

Everyone,
arm-32bit and arm-64bit builds of Funtoo Linux 1.3 are now available. Search for "arm" on this page using the search field right above the table to see them:
https://www.funtoo.org/Subarches
Enjoy. Also note that we could use some help with updating install docs for raspberry pis as well as odroid-xu4, which I hear now should run fine with our debian-sources-lts? If you look at our odroid-xu4 page here, you'll see that at the top we link to an install guide specific to this board. I'd like to have docs like this for all the raspis as well:
https://www.funtoo.org/ODROID-XU4
Thanks,
Daniel

Hey Everyone,
We have a new FAQ developed that allows you to more easily browse answers. See:
https://www.funtoo.org/FAQ
You can also submit your own FAQ questions which I will answer! ? Hope you enjoy it.
Best,
Daniel

Hi Everyone,
I'm very happy to announce that we are now offering official Funtoo AWS images in the AWS Marketplace:
https://aws.amazon.com/marketplace/pp/B07KT3VN7Q/
Please test them out. They are optimized for specific instance types to offer the best performance possible in AWS. Please leave us a positive review (or file a bug ? ) and take advantage of these free images to Funtoo-ize AWS and advance the benefits of building software from source, optimized for the underlying CPU architecture -- Funtoo style!
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

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

I just fixed login-related issues. Funtoo users who had not used the forums before were unable to log in.
I've also fixed the password reset link to go to our official password reset page, as well as the create account link. So logins should be working well.
One note is that if you were are user of the old forums, and you changed your 'displayname' to show something other than your username, then your forums account username will be your displayname. You can alternatively try logging in with your email as your username instead.
Everyone else should be good to go using their funtoo username (and password, of course) to log in here.

Everyone,
New 1.4 Maintenance Release 4 stages have been built. These include GNOME 3.34.5 as well as updated Firefox and other packages. As we continue to expand the use of our autogen framework (metatools) , more and more desktop packages are staying up-to-date automatically. Enjoy the new builds -- they are now available for download via www.funtoo.org and our CDN77-powered CDN.
Best,
Daniel

Hi All,
To get ready for future improvements to Funtoo, I am adopting a multi-phased approach to 'fix Python'. First step is to address some issues that exist in the Gentoo python eclasses. I've updated these eclasses to be at least somewhat better than they are in Gentoo. These changes will be hitting the tree in an hour or so. For new ebuilds, you can now use the following rather than enumerating every single version of Python:
PYTHON_COMPAT=( python3+ )
Because the minimum version of python3 we support is 3.7, this will ensure that the ebuild will be marked compatible with 3.7 and later versions of Python. Using the '+' symbol is the preferred way to mark ebuilds using PYTHON_COMPAT because it eliminates the time-consuming process used in Gentoo of tagging every single python-using ebuild when a new version of Python comes out. I don't know how they deal with this but it is a lot of wasted energy.
Also supported in the new eclasses are the following:
PYTHON_COMPAT=( python2+ ) # python2_7, python3_7, and beyond
PYTHON_COMPAT=( python3_7+ ) # same as python3+ since we start counting at 3_7
PYTHON_COMPAT=( python3_8+ ) # should be self-explanatory...
PYTHON_COMPAT=( python3_9+ )
Note that pypy and pypy3 still need to be manually specified, and it is fine to combine as in the usual way:
PYTHON_COMPAT=( python3+ pypy3 )
And another important change I made to the eclass is that any ebuilds still referencing python3_5 or python3_6 will be 'auto-upgraded' to python3_7 compatibility with no user intervention. So this could close a whole slew of bugs. I'm also enabling eclass support for the upcoming Python 3.9.
IMPORTANT FOR ALL USERS: These changes will result in all of your Python-based and Python-using packages being rebuilt. This rebuild is for cosmetic purposes only -- it's due to a weirdness in emerge and the eclasses -- and really is optional and doesn't actually result in any changes except changes to the /var/db/pkg database USE flags. Therefore, these rebuilds can be completed at your convenience as they are not important. More adventurous users may look for ways to write a script to update /var/db/pkg so that these rebuilds are unnecessary -- if you attempt this, please back up /var/db/pkg first and read the following technical note!
TECHNICAL NOTE: Due to how Gentoo implemented the python eclasses, our deprecation of python3_5 and python3_6 in PYTHON_TARGETS will result in some ebuilds going from 'PYTHON_SINGLE_TARGET' mode to just regular 'PYTHON_TARGET' mode. What you will see is that some ebuilds will be turning off python_single_target_python3_7. This is OK. This is just how the eclasses were written by Gentoo -- PYTHON_SINGLE_TARGET is only enabled when there is more than one active implementation of Python in PYTHON_COMPAT. Otherwise it just falls back to using PYTHON_TARGETS.
On another note, our continued use of auto-generation continues to go well with many more packages now in the tree that are auto-generated. Expect this direction to continue.
Best,
Daniel

GNOME 3.34.1 is ready for use and will become the default version of GNOME in 1.4-release in a few days. If you would like to use it now, you can add the following to /etc/ego.conf:
[kits]
gnome-kit = 3.34-prime
Then ego sync, emerge -auDN @world, emerge @preserved-rebuild, and restart xdm and you should be in business.
If you would like to avoid upgrading to GNOME 3.34, now is the time to insert the following code into /etc/ego.conf:
[kits]
gnome-kit = 3.32-prime
Then, in a few days when 3.34-prime becomes active, you will stick with 3.32-prime and not get the updates until you want them.

Please see the following for more info:
Release Notes: https://www.funtoo.org/Release_Notes/1.4-release
Upgrading from 1.3: https://www.funtoo.org/Upgrade_Instructions/1.4-release
Download and Install: https://www.funtoo.org/Install/Introduction

Hey everyone --
Funtoo Linux 1.4 is now to be considered officially released! Some changes in the last several weeks include:
Updating to gcc-9.2.0 to address an upstream compilation bug (thanks: calrama)
Additional testing/fixing of dependencies (thanks: sandro and others)
New debian-sources and debian-sources-lts kernels (thanks: bcowan)
Debian-sources-lts will now default to using "custom-cflags" USE by default, which will give you a more optimized kernel. -march settings from your subarch mix-in will be applied to your kernel compilation as well. This appears to result in a noticeable performance improvement.
Many thanks to jhan, digifuzzy, klipkyle, librin.so.1, niranjan, sandro and everyone else (sorry if I forgot to mention you) for making this the most tested and most community-focused release of Funtoo ever!
I will continue to update documentation on the wiki relating to 1.4, and of course, 1.4 development continues with pull requests and issues reported to bugs.funtoo.org.
I hope to start 2.0 development in about a month.
Also note -- we now have a "Announcement Discussion" forum visible from the main forums page which allows posts and is open to discussing any announcements.
Best,
Daniel

Funtoo isn't dying. Funtoo is changing just like it always has. You know far better than we do what you want from your Linux distro so ask yourself if you have liked all of the past changes to Funtoo. Then stick with it and have some faith in the wisdom of our BDFL. If you don't like what you see in a year or two you can go to another distro and have not lost anything.
I originally switched to Funtoo because too many things in Gentoo and Debian stayed the same. Having bleeding edge packages wasn't why I used Gentoo. It was because it gave me a greater degree of control than any other OS. The reason I love Debian is because the stable release is always stable but unfortunately I have to give a lot of control to use it. Funtoo can give me the control that I want and at the same time give me the stability that I need so I am keeping an open mind.
If you have the skills to contribute to the code base and improve things for all of us I encourage you to get involved. If you are like me and couldn't write a program if your life depended on it then I encourage you donate a bit of money to Funtoo every month.

Just a note for the future: When removing a feature many people are relying on, it often pays of to have the replacement ready. I get the feeling that essentially disabling Steam and Wine and telling people to hold of on playing games for a couple months is going to drive many people away.
I understand that there is too much to do for too few people, and dropping features you don't feel are needed seems like a good option, but you are also serving a community of users. Telling a portion of that community that they are not wanted and should go elsewhere seems like a bad strategy, even if it frees up development time.
Personally I'm going to hold off on the 1.3 upgrade for as long as possible, and see how that turns out.

Hello Everyone --
I want to highlight some improvements that have been made to the wiki besides our new FAQ (https://www.funtoo.org/FAQ)
We now have a new Subarches page that is a lot easier to navigate: https://www.funtoo.org/Subarches
And the look of various things like notes, tips, warnings, etc. have been improved for a cleaner, more consistent look. This is a good sample page to browse the new look. Note that you may need to "hard reload" the page to get the new CSS: https://www.funtoo.org/Upgrade_Instructions
Enjoy!
-Daniel

Hey Everyone,
We are starting to build Funtoo Linux 1.3 ALPHA builds. We will let you know when these are uploaded and ready for testing.
UPDATE: Ryzen 1.3 Alpha builds now available for download and testing: https://build.funtoo.org/1.3-release-std/x86-64bit/amd64-zen/
-Daniel

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)

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.

Hi All,
I've just massively reworked the net-misc/dropbox ebuild to provide a much better experience in Funtoo and you should see this showing up in the next few hours. I couldn't get the Gentoo dropbox working reliably. Here is a list of all the changes:
Updated to dropbox-39.4.49.ebuild
No longer has an initscript
It now sets up ~/.dropbox-dist for each user who sets up dropbox (rather than having a system dropbox install)
You don't need to be in the "dropbox" group to use the dropbox nautilus (gnome file browser) extension
gnome support is built-in (as long as "gnome" is set in USE, which it is if you are using the GNOME mix-in.)
Reworked the python 'dropbox' script to provide a better user experience and be optimal for Funtoo:
if you start "dropbox" for the first time from GNOME, it will start a GTK+ installer to set up dropbox for you.
if you don't have a GUI, you can still install dropbox
The above two features are existing features of dropbox that were somewhat borked in Gentoo.
At the end of the setup process, you are given instructions on how to enable dropbox on startup.
dropbox command-line tool is also included.
Please note that if you have nautilus-dropbox installed, you will need to remove it.
This should result in a really nice experience for dropbox users.
Use as follows:
# emerge dropbox (make sure it's 39.4.49 -- this is the new version.)
(as regular user:)
$ dropbox start -i
This will initialize the ~/.dropbox-dist directory for the user via a command-line or GTK+ interface. Once this is done, dropbox start should be added to your .bash_login and/or .xprofile and can be run immediately to start dropbox in your current session.
Since the ebuild is completely new, the possibility of bugs exist. Please report bugs at https://bugs.funtoo.org . Thanks.
-Daniel

A full set of Funtoo Linux 1.4 maintenance release 2 stages has been uploaded to build.funtoo.org.
These stages include:
GNOME 3.34.2
Updates to debian-sources-lts (4.19.87_p1)
Updated Linux firmware
Updated firefox
Various other fixes
If you are already using 1.4, you can get all these updates via a regular ego sync and world update. But if you are planning to install 1.4 from scratch, these builds are up-to-date.

@tux yes LXD has its limitations compared to OpenVZ -- I still miss OpenVZ a lot. But LXD is gradually improving. I have plans to offer a lot more to users with hosting and I am hoping to actually realize these plans in a month or so -- let's see if things go as planned 🙂 (Note: it should help with this issue.)

Hey All,
I've gone ahead and updated Funtoo Linux 1.4 to contain the latest implementation of SELinux from Gentoo. SELinux is working well under Funtoo now. To use it, see the SELinux page on the Funtoo wiki. Also reference the https://wiki.gentoo.org/wiki/SELinux/Installation and https://wiki.gentoo.org/wiki/SELinux pages for documentation reference. These Gentoo wiki pages were originally put together by SwiFT and are excellent, and the SELinux team has kept them up-to-date (I must give credit where credit is due 🙂. We need to work on our modest SELinux wiki page here to improve it: https://www.funtoo.org/SELinux
If you are new to SELinux, here are the basic steps. Enable the SELinux mix-in, emerge the SELinux tools as well as policies, rebuild world and etc-update, apply security labels to files, enable in kernel in "permissive mode" -- where it just logs things but doesn't "block" anything, and then start to play.
In your /etc/boot.conf, you'll want to add "security=selinux enforcing=0" to your "params +=" line and re-run "ego boot update" to get the kernel booting properly. This is assuming you are using debian-sources or debian-sources-lts.
Funtoo is also helping perfinion (find him in #gentoo-base on freenode) in Gentoo test the SELinux-next security policies. Here is how you can test them:
1. Add the following to package.keywords: sec-policy/selinux-* **
2. Then emerge @selinux-rebuild to reinstall all the 9999 policies (to be used with 2.9 userspace)
3. Do a full relabel.
4. Reboot.
Then, you can run and start auditd which will generate logs of what SELinux activity is going on. After your initial reboot into the new SELinux, start auditd with empty logs, and keep it running as you go about your business. After a few days of using Funtoo as you normally would, these logs can be useful to the SELinux team to determine if the new policies are working as expected.
Of particular interest is the use of elogind under SELinux. Once using the new SELinux-next policies, 'ps auxfZ | grep logind' should be in the systemd_logind_t domain.
Thanks to perfinion and the SELinux team for moving SELinux forward! Let's help them 🙂

Hey everyone, I have added documentation on how to essentially get Steam running in Funtoo using LXD. First, you will want to follow these instructions to get LXD running:
https://www.funtoo.org/LXD
Then, follow these instructions, which will get you to the point of setting up a multilib Gentoo container that can run glxgears. At that point, getting Steam running should be pretty straightforward:
https://www.funtoo.org/LXD/GPU_Acceleration
Please test it out and let me know how it works.

So, upgrade is pretty easy this time around.I will have instructions soon. But you can basically use "standard" upgrade steps. I recommend emerge -1 glibc gcc first, then emerge -auDN @world should generally work. Report any bugs related to upgrade like failed builds because often this can be fixed by tweaking dependencies. Overall the upgrade is MUCH easier than 1.2 -> 1.3.
One trick is to remember to "eselect python set --python3 python3.7" after python-3.7 is emerged to make it default. Also, mesa right now is very picky about USE flags related to video card. For example, if you don't have a card that supports vulkan, you cannot have vulkan in USE. Same with xa and other things that were more "permissible" before.
As of yesterday, I am now happily running gnome 3.32 and it is working perfectly. I would still call things "in beta" but the remaining issues (there is a "reboot doesn't work" issue currently active, due to a missing /run/initctl -> /dev/initctl symlink) should be worked out with minor package updates.

Got a (new to me) Thinkpad T420s and decided Funtoo would be the primary OS.
I'm happy to say I went through the install today and I now have Funtoo installed and booted.
Just need to setup everything I want on it now.

We’d love to help you. To improve your chances of getting an answer, here are some tips:
Search, and research
...and keep track of what you find. Even if you don't find a useful answer elsewhere on the site, including links to related questions that haven't helped can help others in understanding how your question is different from the rest.
Write a title that summarizes the specific problem
The title is the first thing potential answerers will see, and if your title isn't interesting, they won't read the rest. So make it count:
Pretend you're talking to a busy colleague and have to sum up your entire question in one sentence: what details can you include that will help someone identify and solve your problem? Include any error messages, key APIs, or unusual circumstances that make your question different from similar questions already on the site.
Spelling, grammar and punctuation are important! Remember, this is the first part of your question others will see - you want to make a good impression. If you're not comfortable writing in English, ask a friend to proof-read it for you.
If you're having trouble summarizing the problem, write the title last - sometimes writing the rest of the question first can make it easier to describe the problem.
Examples:
Bad: Is there command to do what it needs?
Good: How can I apply changes proposed by emerge?
Bad: Problem update system
Good: Why does the compile of dev-libs/boost-1.63.0 fail with x86_64-pc-linux-gnu-g++: internal compiler error: Killed (program cc1plus)?
Introduce the problem before you post any code
In the body of your question, start by expanding on the summary you put in the title. Explain how you encountered the problem you're trying to solve, and any difficulties that have prevented you from solving it yourself. The first paragraph in your question is the second thing most readers will see, so make it as engaging and informative as possible.
Help others reproduce the problem
Not all questions benefit from including code. Here are some guidelines:
Include just enough code to allow others to reproduce the problem.
For portage errors include all the relevant info and output.
Include all relevant tags
Try to include a tag for the language, library, and specific API your question relates to. If you start typing in the tags field, the system will suggest tags that match what you've typed - be sure and read the descriptions given for them to make sure they're relevant to the question you're asking! See also: What are tags, and how should I use them?
Proof-read before posting!
Now that you're ready to ask your question, take a deep breath and read through it from start to finish. Pretend you're seeing it for the first time: does it make sense? Try reproducing the problem yourself, in a fresh environment and make sure you can do so using only the information included in your question. Add any details you missed and read through it again. Now is a good time to make sure that your title still describes the problem!
Post the question and respond to feedback
After you post, leave the question open in your browser for a bit, and see if anyone comments. If you missed an obvious piece of information, be ready to respond by editing your question to include it. If someone posts an answer, be ready to try it out and provide feedback!
Look for help asking for help
In spite of all your efforts, you may find your questions poorly-received. Don't despair! Learning to ask a good question is a worthy pursuit, and not one you'll master overnight. Here are some additional resources that you may find useful:
Writing the perfect question
How do I ask and answer homework questions?
How to debug small programs
Meta discussions on asking questions
How to ask questions the smart way — long but good advice.

Following ebuilds now available for testing in Funtoo/Linux
sys-fs/zfs-0.7.9
sys-fs/zfs-kmod-0.7.9
sys-kernel/spl-0.7.9
These versions have a portion of upstream fixes and also support for newer kernels. Ebuilds added without keywords and do require manual setting of /etc/portage/package.keywords before update.
https://github.com/zfsonlinux/zfs/releases

Also, in addition, I'm no longer updating master on the following kits: core-kit, security-kit, xorg-kit, gnome-kit, kde-kit, media-kit, perl-kit, python-kit. I made this change to reduce the clock time required to update our kits.

Ego-2.2.1 has been released. This release includes fixes for the accuracy of information shown by "ego kit list", a helpful informational message at the end of the "ego kit" commands, and some minor unit test improvements.