drobbins
-
Posts
513 -
Joined
-
Last visited
-
Days Won
282
Content Type
Profiles
Forums
Blogs
Posts posted by drobbins
-
-
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
-
OK, great -- glad to hear! ?
-
-
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
-
@seaofash sorry you are having problems -- you can reach me on freenode IRC in #funtoo and we can figure out what's going on. Thanks!
-
Hey Everyone,
We have a new FAQ developed that allows you to more easily browse answers. See:
You can also submit your own FAQ questions which I will answer! ? Hope you enjoy it.
Best,
Daniel
- nrc, NikosAlexandris, AdiosKid and 1 other
-
4
-
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
-
-
Hey all,
We are about to switch Release 1.2 to use debian-sources-lts as the default kernel. What this means is that on stage3's, you will soon be greeted with debian-sources-lts pre-built instead of the regular debian-sources. This may be surprising to you because you will notice that on new installs, you won't have a 4.14+ kernel but an earlier one. But there is a good reason for this, as I'll explain.
Many of you know that "debian-sources-lts" is Debian's "long term stable" kernel, and is based on the 4.9 series. I know, I know... some of you might not like this choice, particularly if you are used to running a more recent kernel. I'll remind those who are in this camp that as always, Funtoo supports running whatever kernel you like -- we're simply changing our default.
From our perspective, the benefits of this change are numerous. First, Debian's "LTS" kernel is considered to be production-ready for servers and is kept up-to-date with the latest Spectre and Meltdown mitigations. This by itself is a good reason for us to switch. Other nice things are that because it is a 'stable' kernel, we can expect good driver compatibility with things like nivida-drivers, so it should reduce breakage experienced by third-party modules.
It's also the kernel we use ourselves for production servers, so we simply pay more attention to it overall than the regular debian-sources. It's always best if the kernel we ship to you is the one we use ourselves, as it gets the most testing and validation.
-
I would say you should work on an English translation of the site so the project is also open to English-speaking users. It should be a full international project.
-
-
OK, done.... ?
- NikosAlexandris and AdiosKid
-
2
-
Hey, can you send me a logo graphic and I'll add an announcement about it to the main Funtoo page? Thanks.
-
-
Hi All,
As we move to our third-generation infrastructure, I am currently migrating containers to BTRFS+SSD (from ZFS and HDD+Optane) which may result in up to an hour of downtime, especially if you have a lot of data stored in your containers. But the result will be much, much, much faster IO. So if you have seen your uptime on your container change recently, this is why.
Best,
Daniel
-
There is nothing wrong with some branches having "detached head". You will see this when there has been a recent update to our 1.3 development branch.
If you see this at the end:
Sync successful and kits in alignment! :)Then it means things are OK.
-
I believe the root cause of this is that we used different snapshot dates for various parts of 1.2. We are getting away from this with 1.3, so it should go away with 1.3 when it is released. We'll use a unified snapshot for that release.
However, these issues should be fixed in 1.2 when found, if possible.
If you can point out bugs that you feel were improperly closed without being correctly addressed, I can investigate.
-
As Funtoo matures, we keep evolving our own infrastructure. This is the infrastructure we use for user containers as well.
Progress on this is going well. All of Funtoo (www, forums, bugs, auth) is now hosted on this brand-new infrastructure and performance of all the funtoo sites now appears to be very very good. We did initially have some issues we were experiencing with ZFS so we are now using another approach which will be detailed in future docs, and it is running much better.
Soon, we will be launching new things related to funtoo hosting in regards to the new infrastructure. Much more automation, rather than having to send us an email to get things done. Some surprises -- and that's one of the reasons why we added authy integration to the funtoo logins -- because they will be used to manage your containers in the future so we want to have more sophisticated security capabilities.
Best,
Daniel
-
-
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.
- iwoloschin and ixti
-
2
-
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
We have a new FAQ!
in News and Announcements
Posted
@nrc question answered -- https://www.funtoo.org/FAQ:What_Are_Funtoo_Kits