drobbins

Hi All,
 
One new thing that we have had to deal with is the addition of the CPU_FLAGS_X86 variable to Gentoo and Funtoo Linux. As you may know, there are a lot of USE flags that deal with CPU instruction sets, such as "mmx", "sse", etc. These have been migrated to a CPU_FLAGS_X86 variable, which works similarly to other variables like VIDEO_CARDS.
 
Strangely, I couldn't find any good documentation on the USE flags that are now CPU_FLAGS_X86, so I created my own docs for everyone on this page:
 
http://www.funtoo.org/CPU_FLAGS
 
As you can see, the history of CPU instruction sets for x86 systems has been pretty interesting and complex.
 
One thing you might be wondering, especially if you are a new user, is what instructions are being used for your Funtoo Linux system. This is actually determined by the CFLAGS -march setting, primarily. This tells the compiler which instruction sets to use when building C programs. The additional CPU_FLAGS_X86 flags enable optional build-time functionality in ebuilds for these instruction sets that must be specifically enabled. Typically, these are special optimized parts that have been hand-written to run very fast on systems with these instruction sets. I hope this clarifies things.
 
Over the next week, expect updates to the Subarches page on the wiki to reference CPU_FLAGS_X86 instead of USE.
 
Regards,
Daniel

Hey everyone, I've written up a news item detailing all the stuff that's going on with Funtoo to keep it focused on you, our users. Give it a read:
 
http://www.funtoo.org/News:How_We%27re_Keeping_You_At_the_Center_of_the_Funtoo_Universe
 
Best Regards,
 
Daniel Robbins
BDFL

As in the topic, please post pics here of what badly modified car is the best visual metaphor for the devastation that is systemd.
 
-Daniel

All,
 
There is now a great page that will give you an introduction of how to help us add great documentation to the wiki. See here:
 
http://www.funtoo.org/Help:Funtoo_Editing_Guidelines -- also known as "How to 'Wiki'" - linked in the main nav column on the left.
 
Regards,
Daniel

Hi All,
 
If you are confused about recent changes to 32-bit compatibility in Gentoo and Funtoo, be sure to read this news item:
 
http://www.funtoo.org/News:ABI_X86_64_and_32
 
It explains what's going on.
Best Regards,
Daniel

Hey everyone, I've written up a news item detailing all the stuff that's going on with Funtoo to keep it focused on you, our users. Give it a read:
 
http://www.funtoo.org/News:How_We%27re_Keeping_You_At_the_Center_of_the_Funtoo_Universe
 
Best Regards,
 
Daniel Robbins
BDFL

As many of you have seen, I've bumped the Funtoo toolchain for x86 to linux-headers-4.0, glibc-2.20 with security patches, gcc-4.9.2 and binutils-2.25. The ARM toolchain has not changed, and we will bump as soon as we have confirmed that it is working okay.
 
Enjoy!
 
-Daniel

Thanks a lot, BDFL!

Hi All,
 
For a long while, the most time-consuming and potentially error-prone part of installing Funtoo Linux has been building a kernel. I worded to make this better by creating the debian-sources kernel, when combined with the "binary" USE flag will build you a kernel that just works. The problem: the compile time is excessive -- it can take an hour or more even on relatively modern hardware.
 
To make installing Funtoo Linux even easier, stage3's are now including debian-sources pre-built! We're using the Funtoo compute power made available by Funtoo supporters to save you time and hassle when installing Funtoo :) All you need to do is configure a boot loader and you're ready to go :)
 
I enabled this yesterday on our build servers, so it will take a few days before all stage3's are updated to include debian-sources. If they have a date of 2015-05-11 or later, they should have a kernel and initramfs included.
 
If you still want to build your own custom kernel, it is easy enough to unmerge, remove kernel and initramfs, and build your own.
 
Enjoy!
 
-Daniel

This might give you some idea of the amount of upstream bugs I am encountering while building a full build of GNOME. Many of these build failures are due to use of binary packages, which it doesn't appear that Gentoo actively tests:
 
https://bugs.funtoo.org/browse/QA-24

The stage3's are coming with kernels included.

I created an Funtoo wallpaper, also using the funtoo logo made by j-g-.
http://i.imgur.com/3tLhrSe.jpg
 

Hi All,
 
For a long while, the most time-consuming and potentially error-prone part of installing Funtoo Linux has been building a kernel. I worded to make this better by creating the debian-sources kernel, when combined with the "binary" USE flag will build you a kernel that just works. The problem: the compile time is excessive -- it can take an hour or more even on relatively modern hardware.
 
To make installing Funtoo Linux even easier, stage3's are now including debian-sources pre-built! We're using the Funtoo compute power made available by Funtoo supporters to save you time and hassle when installing Funtoo :) All you need to do is configure a boot loader and you're ready to go :)
 
I enabled this yesterday on our build servers, so it will take a few days before all stage3's are updated to include debian-sources. If they have a date of 2015-05-11 or later, they should have a kernel and initramfs included.
 
If you still want to build your own custom kernel, it is easy enough to unmerge, remove kernel and initramfs, and build your own.
 
Enjoy!
 
-Daniel

Hi All,
 
For a long while, the most time-consuming and potentially error-prone part of installing Funtoo Linux has been building a kernel. I worded to make this better by creating the debian-sources kernel, when combined with the "binary" USE flag will build you a kernel that just works. The problem: the compile time is excessive -- it can take an hour or more even on relatively modern hardware.
 
To make installing Funtoo Linux even easier, stage3's are now including debian-sources pre-built! We're using the Funtoo compute power made available by Funtoo supporters to save you time and hassle when installing Funtoo :) All you need to do is configure a boot loader and you're ready to go :)
 
I enabled this yesterday on our build servers, so it will take a few days before all stage3's are updated to include debian-sources. If they have a date of 2015-05-11 or later, they should have a kernel and initramfs included.
 
If you still want to build your own custom kernel, it is easy enough to unmerge, remove kernel and initramfs, and build your own.
 
Enjoy!
 
-Daniel

Hi All,
 
For a long while, the most time-consuming and potentially error-prone part of installing Funtoo Linux has been building a kernel. I worded to make this better by creating the debian-sources kernel, when combined with the "binary" USE flag will build you a kernel that just works. The problem: the compile time is excessive -- it can take an hour or more even on relatively modern hardware.
 
To make installing Funtoo Linux even easier, stage3's are now including debian-sources pre-built! We're using the Funtoo compute power made available by Funtoo supporters to save you time and hassle when installing Funtoo :) All you need to do is configure a boot loader and you're ready to go :)
 
I enabled this yesterday on our build servers, so it will take a few days before all stage3's are updated to include debian-sources. If they have a date of 2015-05-11 or later, they should have a kernel and initramfs included.
 
If you still want to build your own custom kernel, it is easy enough to unmerge, remove kernel and initramfs, and build your own.
 
Enjoy!
 
-Daniel

Something like this will be offered relatively soon.

Hey all,
 
Metro now has the ability to perform QA tests and to file JIRA bugs :)
 
Tell me what you'd like me to have tested for you. I'll explain what we are testing so far:
 
Before anything is updated in your Portage tree, we make sure that all the stuff in a stage3 merges cleanly for both funtoo-current and funtoo-stable.
 
QA bot's first job is to make sure that gnome always merges cleanly in funtoo-current. The test involves peforming a full merge of gnome and reporting any failed packages.
 
The first sets of tests we'll be doing involve build testing like this -- which ensures that the required ebuild(s) build cleanly, all deps are resolved, and and emerged packages that depend on said ebuilds find all the stuff they are expected to find.
 
As we improve our QA efforts, I will support the ability to perform arbitrary QA tests that are not just about build testing and dep resolution. But that's where I want to start.
 
One good source of ideas of packages that are important to you are in /var/lib/portage/world. Let me know what you want to see tested.
 
Regards,
 
Daniel

Something like this will be offered relatively soon.

Guys, you are not really supposed to change the arch. That is set when the stage3 is built. Quit doing that, and eselect may work fine for you :)

Open a bug for this on bugs.funtoo.org, if the issue persists and the deps aren't quite right.

You shouldn't run wpa_supplicant -- only add NetworkManager to your runlevel, and use the "addwifi" command to add your connection. I typically don't have a NetworkManager.conf at all. "addwifi" will create an entry in /etc/NetworkManager/system-connections.

Hi All,
 
If you have installed a new Funtoo Linux system in the last week, you may have noticed something interesting -- /etc/make.conf is EMPTY and eselect profile show shows something new -- a subarch profile:
 
test / # eselect profile show   Currently set profiles:     arch: gentoo:funtoo/1.0/linux-gnu/arch/x86-64bit    build: gentoo:funtoo/1.0/linux-gnu/build/current   flavor: gentoo:funtoo/1.0/linux-gnu/flavor/core  subarch: gentoo:funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/corei7   What's going on? This is part, or maybe culmination of an ongoing effort to simplify /etc/make.conf. While it is still possible to set CFLAGS in /etc/make.conf, by default, these settings are now defined in a subarch profile. By default, new stage3's will have a subarch profile set, but existing Funtoo systems don't need to have one set. If you'd like to set a subarch profile, you can do so by ensuring you have the latest eselect installed and using the "eselect profile set-subarch" command.   What are the benefits of subarch profiles? Of course, the first big benefit is to keep /etc/make.conf clean. Subarch profiles, along with flavors and mix-ins, are designed to help keep /etc/make.conf tidy and only contain the tweaks you personally need for your system. It also assists with Metro, our stage building tool. Metro no longer has to store all the CFLAGS settings for each subarch -- these are now integrated into the Portage tree, in one place. And also, this allows us to fix and improve subarches over time, and you automatically benefit from any improvements with an emerge --sync.   Hope you enjoy the new system,
Daniel

Hi All,
 
If you have installed a new Funtoo Linux system in the last week, you may have noticed something interesting -- /etc/make.conf is EMPTY and eselect profile show shows something new -- a subarch profile:
 
test / # eselect profile show   Currently set profiles:     arch: gentoo:funtoo/1.0/linux-gnu/arch/x86-64bit    build: gentoo:funtoo/1.0/linux-gnu/build/current   flavor: gentoo:funtoo/1.0/linux-gnu/flavor/core  subarch: gentoo:funtoo/1.0/linux-gnu/arch/x86-64bit/subarch/corei7   What's going on? This is part, or maybe culmination of an ongoing effort to simplify /etc/make.conf. While it is still possible to set CFLAGS in /etc/make.conf, by default, these settings are now defined in a subarch profile. By default, new stage3's will have a subarch profile set, but existing Funtoo systems don't need to have one set. If you'd like to set a subarch profile, you can do so by ensuring you have the latest eselect installed and using the "eselect profile set-subarch" command.   What are the benefits of subarch profiles? Of course, the first big benefit is to keep /etc/make.conf clean. Subarch profiles, along with flavors and mix-ins, are designed to help keep /etc/make.conf tidy and only contain the tweaks you personally need for your system. It also assists with Metro, our stage building tool. Metro no longer has to store all the CFLAGS settings for each subarch -- these are now integrated into the Portage tree, in one place. And also, this allows us to fix and improve subarches over time, and you automatically benefit from any improvements with an emerge --sync.   Hope you enjoy the new system,
Daniel