Difference between revisions of "Funtoo Linux FAQ"
(→How many developers are working on Funtoo Linux?)
(→How many developers are working on Funtoo Linux?)
|Line 210:||Line 210:|
=== How many developers are working on Funtoo Linux? ===
=== How many developers are working on Funtoo Linux? ===
Funtoo Linux development is led by Daniel Robbins, along with a [[
Funtoo Linux development is led by Daniel Robbins, along with a [] that also makes significant contributions to Funtoo Linux development and Funtoo infrastructure.
=== Is Funtoo Linux a fork of Gentoo Linux? ===
=== Is Funtoo Linux a fork of Gentoo Linux? ===
Revision as of 17:49, 8 November 2010
Funtoo Linux FAQ
Common Misconceptions, Rumors, etc.
Does Funtoo Linux use a Red Hat kernel?
Funtoo Linux users are free to choose their own kernel, just like in Gentoo Linux, although RHEL kernel compatibility is a priority of this project, so that enterprise users have the option of using such kernels. We maintain instructions for how to get a RHEL5-based kernel running under Funtoo Linux, and ensure that this option is supported. See RHEL5 Kernel HOWTO.
Does Funtoo use an overlay?
Yes and no. We do have an overlay at GitHub that contains all the Funtoo modifications to Gentoo. However, the overlay is intended for developers, and users should use our integrated git-based Portage trees with all the overlay changes merged in. The reason for this is that our integrated Portage trees also have profile patches applied, which are stored within our overlay at funtoo/patches, if you want to check them out. So if you just use our overlay on top of the Gentoo tree, it will not work properly.
Is there a lot of junk in your Portage tree?
At one point, we had a lot of overlays merged in to our Portage tree, such as the sunrise overlay. We now have a very clean Portage tree, and sunrise is no longer part of the tree. All Funtoo changes to the tree can be found in our overlay at GitHub. All other changes come from Gentoo. Funtoo Linux changes are all very well-maintained and organized in our overlay. So no, there is no junk in our Portage tree - at least that originates from us :)
Using Funtoo Linux, Portage and Git
How do I start using Funtoo Linux?
For information on how to start using Funtoo Linux, see the Funtoo Linux Quick Install Guide.
Is it possible to convert an existing Gentoo Linux install to Funtoo Linux?
Yes, it is possible, but I am no longer supporting this method as it can be problematic and is always sub-optimal to installing Funtoo Linux from a stage3.
I can't use emerge --sync to download an initial Portage tree.
Yes, Portage doesn't do that yet. To grab an initial Portage tree, download a `current git-based snapshot`_ from from the `Funtoo Portage snapshot repository`_. Then, type the following commands:
# cd /usr # tar xf /path/to/portage-current.tar.xz # cd portage # git checkout funtoo.org
Once you have git-based Portage tree in place, Portage 2.2 will realize that you are using Funtoo Linux and will perform git updates rather than rsync updates when you type emerge --sync.
You will need to add the following to /etc/make.conf to use Portage mini-Manifests:
I try to emerge something and Portage complains that a digest is not found.
You are using a Funtoo mini-manifest tree and forgot to enable mini-manifest. To do this, add the following to /etc/make.conf:
What is mini-manifest?
Funtoo's default Portage tree has gone on a diet - Manifests now include only entries for distfiles (source tarballs.) For everything else, we rely on git's internal integrity-checking mechanisms which is based on SHA1 digests.
In addition, our mini-Portage tree does not include ChangeLogs for additional space savings. This allows us to offer a Portage tree snapshot that is under 30MB in size when compressed.
How do I update my git-based Portage tree?
If you already have an existing git-based Portage tree, you can update it by typing:
# emerge --sync
I set up my initial git-based Portage tree, but /usr/portage seems to be empty.
You forgot to type:
# cd /usr/portage # git checkout funtoo.org
Funtoo Linux's portage tree snapshot ships with a mostly empty branch active by default to reduce the size of the resultant snapshot tarball.
What is different with Funtoo's UTF-8 support?
Funtoo Linux has UTF-8 enabled by default, even for the root user. This allows UTF-8 files to be edited without issue, root GNU screen sessions to display UTF-8 character sets properly, etc. The classic sort order of ls -a has been preserved by setting LC_COLLATE to POSIX. All other locale settings inherit the system default defined in the LANG variable, which is set to en_US.UTF-8.
What if I want to use a non-English locale/language?
I recommend two things. First, it's strongly recommended that you always use a UTF-8-based locale.
The next thing I recommend is to try to avoid changing the global system LANG setting, and instead set the LANG setting on a per-user basis by adding the desired LANG setting to your ~/.bashrc. This will preserve English log output in /var/log and make it easier to search for more common matching English strings on the Internet when you need help.
If you really want to change the default system LANG setting (taking into account the paragraph above,) then it's recommended that you create your own /etc/env.d/02locale file that contains something like this:
You will need to run etc-update and source /etc/profile to apply changes immediately to any open shells, and reboot to apply changes fully.
What is different with Funtoo's Ruby?
Funtoo Linux tracks Gentoo's Ruby, but we do have one change for ruby-1.9 and greater - the binary name is changed with /usr/bin/ruby1.9 instead of Gentoo's /usr/bin/ruby19. This makes the versioning consistent with Python binaries and MacOS X. This means that for ruby-1.9 and greater. While the path to the binary has changed, all Portage variables are the same as Gentoo, so you should use "ruby19" for the RUBY_TARGETS setting in /etc/make.conf.
Ruby 1.9 is masked. How do I use it?
Add the following to /etc/make.conf:
Then unmask ruby-1.9 as follows:
# install -d /etc/portage # echo "dev-lang/ruby:1.9" >> /etc/portage/package.unmask
If you are using Funtoo stable, then you will also need to do this:
# echo "dev-lang/ruby:1.9" >> /etc/portage/package.keywords
Why is Funtoo Linux still an older udev?
Funtoo Linux currently uses udev-160 and generally updates udev less frequently than in Gentoo Linux.
What is the minimum kernel version I can use with Funtoo Linux?
Without making changes to the default version of the udev package, Funtoo Linux is compatible with kernel versions 2.6.27 and greater. To use earlier kernels or enterprise kernels, see below.
I need to use a kernel earlier than 2.6.27. What should I do?
To use a RHEL5 or RHEL5-based kernel, you will need to use udev-146 or earlier. Funtoo Linux provides these versions in its portage tree. All you need to do is add the following line to /etc/portage/package.mask:
Then, emerge udev:
You can now reboot with a RHEL5-based kernel and udev will still work properly. udev-135 is also available for even earlier kernels.
How do I use a RHEL5-based kernel, such as openvz-sources-2.6.18* with Funtoo?
The steps required to do this, including downgrading udev and emerging gcc-4.1.2, can be found in the RHEL5 Kernel HOWTO
Why is package.mask a directory?
I decided to convert /usr/portage/profiles/package.mask to a directory as soon as I discovered that this was a supported feature in the current Portage. This allows us to maintain package.mask data more effectively.
Git complains and aborts when I emerge --sync.
It appears that a previous git merge was interrupted or did not complete, leaving your portage tree in an intermediate state. Typically, this can be fixed by typing:
# cd /usr/portage # git reset --hard origin/funtoo.org
This should restore your portage tree to a consistent state and allow future emerge --sync commands to complete successfully.
If this doesn't work, then you may have a conflicted merge. Maybe you modified some local ebuilds? To view conflicts, type git diff --stat from within the /usr/portage directory. You can choose to either resolve these conflicts or revert back to the official Funtoo Portage tree.
If you want to throw away your local changes and simply use the Funtoo Portage tree, you'll need to remove all the files in /usr/portage besides the .git directory, and then trying the git reset --hard origin/funtoo.org command again, as follows:
# cd /usr/portage # mv distfiles .. # rm -rf * .gitignore # git reset --hard origin/funtoo.org # mv ../distfiles .
Now everything should be working again.
I can't seem to use overlays with Funtoo Linux. What's wrong?
To use overlays with Funtoo Linux, create an /etc/portage/repos.conf file containing the following lines:
[funtoo] aliases = gentoo
Information regarding this change is covered in Zack Medico's blog post.
How do I tell if a problem I am having originates from Gentoo or Funtoo?
You can tell if there are any Funtoo changes to an ebuild by browsing the `Funtoo overlay`_. All the Funtoo-specific ebuilds can be found in our overlay. If you see an ebuild in my overlay, then we use my version instead of the Gentoo version. If you don't see it in the funtoo overlay, then it comes from Gentoo.
How can I see the differences between the Gentoo and Funtoo Portage trees?
In the old days, this was tricky, but now you just look at the `Funtoo overlay`_ for a complete repository of all the Funtoo-specific stuff. Everything not in the Funtoo overlay comes from Gentoo.
Is Paludis compatible with the Funtoo Portage tree?
Paludis does not appear to be compatible with the Funtoo Portage tree, unfortunately. It does not support the package.mask directory without additional hooks, and also does not support merging device nodes. These features are supported by by Portage and we use both of these capabilities. I think that both package.mask (and package.keywords, etc.) directories are a good idea, and I also think it's a good idea for the package manager to support device nodes, which is particularly useful for the udev and baselayout ebuilds. Funtoo Linux has separate versions of these packages, and these ebuilds are easier to maintain if device nodes are correctly supported by the package manger, and the package.mask directory is a great help to us as well.
We could maintain a patched version of Paludis that would be useable with the Funtoo Portage tree, but I don't want to get into the business of supporting a non-standard package manager as the upstream project seems not seem very supportive of getting these compatibility issues resolved, and thus this could turn into a maintenance burden for Funtoo. So I'd rather just not support Paludis for now.
What about pkgcore?
Pkgcore is not currently compatible with Funtoo Linux but efforts are under way to resolve this.
How do I report a bug?
The best way to report your bug is to describe the issue you are having on the `funtoo-dev mailing list`_. Another option is to ask for support in the `#funtoo irc channel`_. In general, it's best to contact us first about an issue you are having, rather than opening a Gentoo bug report, unless you are quite familiar with the issue and are fairly certain that it is not a Funtoo Linux issue.
If you report a bug to Gentoo that may impact Funtoo Linux in some way, please post information about it to the `funtoo-dev mailing list`_ so we are aware of the issue.
How do I become a Funtoo developer?
Funtoo is a personal project of mine, so I'm the only real developer. However, I involve everyone on the `funtoo-dev mailing list`_ and `#funtoo irc channel`_ in what I am doing so that patches, feedback, requests, etc. can be shared. My advice is to get involved in the Funtoo community on the mailing list and irc channel.
General Funtoo Stuff
What is funtoo.org?
Funtoo.org is the online home of Daniel Robbins (me) and is a place to put all my stuff.
What kind of stuff?
Well, I have `Funtoo Linux`_, which is a Gentoo Linux variant. Then I have technical articles -- some new, and some updated versions of originals that appeared on IBM developerWorks.
Then I have `Metro`_, an operating system build tool, and I have `keychain`_, which is a tool to help you manage RSA and DSA keys for ssh.
So Funtoo is not just `Funtoo Linux`_.
What is 'Funtoo' all about? And 'Funtoo Linux'?
Funtoo by itself refers to this site, or the larger Funtoo project run by Daniel Robbins. That's just a fancy way of saying that Funtoo refers to all the stuff I'm doing.
`Funtoo Linux`_ refers specifically to my variant of Gentoo Linux.
If you see me use the phrase Funtoo Portage tree or Funtoo ebuild, I'm just talking about our separate (and slightly different) Portage tree, or our version of an ebuild.
What is 'tnufoo'?
tnufoo is funtoo rotated 180 degrees vertically.
ooÊunÉ is funtoo rotated 180 degress horizonally and vertically.
How many developers are working on Funtoo Linux?
Funtoo Linux development is led by Daniel Robbins, along with a Core Team that also makes significant contributions to Funtoo Linux development and Funtoo infrastructure.
Is Funtoo Linux a fork of Gentoo Linux?
It depends on your definition of fork. Officially, I am calling Funtoo Linux a Gentoo Linux variant, meaning that it is more like another flavor of Gentoo than a fork.
We share our changes and bug fixes with the Gentoo project, so Gentoo is free to merge in any of our changes at any time. We also merge in Gentoo's changes every 12 hours.
I could officially call Funtoo Linux a fork of Gentoo Linux, but Gentoo could merge most of our changes into Gentoo proper and then what would Funtoo Linux be? It'd be my variant of Gentoo, that's what it'd be. So let's just call it a variant of Gentoo.
What is the best way to interact with the Funtoo community?
I recommend joining the `funtoo-dev mailing list`_ and, if desired, hanging out in the `#funtoo irc channel`_ on freenode.
The `funtoo-dev mailing list`_ as well as the `#funtoo irc channel`_ are unmoderated, open discussion forums for both Funtoo Linux users and developers. In addition, these are also the official lists for discussing other Funtoo projects such as `Metro`_ and `Keychain`_.
What Architectures does Funtoo Linux support?
While Funtoo Linux can run on any architecture that Gentoo Linux supports, we are only maintaining Funtoo Linux for x86 and amd64 architectures. Adding support for other architectures may require a little bit of unmasking work in our Portage tree -- or not. We're not testing anything but x86 and amd64, so we don't know :)
How should a developer use package.mask?
We currently have four files in the package.mask directory -- gentoo, funtoo, funtoo-cautionary and sunrise. Gentoo is an almost pristine version of the upstream gentoo package.mask. It differs from gentoo only in that we will remove stuff from it that we no longer want in it, but we don't add masks to this file. So if there is a mask in gentoo, you know it came upstream from Gentoo.
funtoo is where we place our masks. funtoo-cautionary is where we place masks that are designed to shield us from upstream unstable version changes to core packages, since we don't want to simply follow Gentoo unstable -- instead, we want to control when gcc and glibc switch to new versions. sunrise contains a bunch of sunrise and other miscellaneous masks from the mpd overlays. It is currently sort of our "junk drawer" that we'll get around to cleaning up at some point.
Do you use the normal Gentoo system profiles?
I've made some minor changes to the Funtoo Linux profiles/ directory, and I'll continue to make improvements as time goes on. The most recent change I made (as of 17 Jul 2009) was to add net-dns/openresolv to the core system profile. Since Funtoo development focuses primarily on the core system, you can expect our system profiles to be somewhat different from Gentoo's. However, from a user perspective, you use them the same way and we have the same profile names that are in Gentoo.
Is Funtoo Linux More Stable Than Gentoo Linux?
That is a hard question to answer directly, as one person's definition of "stable" may be different than another person's, and I do not know how you intend to use Funtoo Linux. So rather than tackle the question head-on, I can give you some additional information that may help you decide:
- The goal of Funtoo Linux is to allow me to improve the Gentoo core system and tools. That does mean that I will be periodically changing various parts of Gentoo plumbing from time to time. When I do this, I try to be careful and provide notices of upcoming major changes on the mailing list, Atom feed and on the Web site.
- Both Funtoo Linux and Gentoo Linux have a stable and unstable (~) tree
- The Funtoo and Gentoo trees are 99% identical. However, there are signficant differences in certain areas, particularly the core system and Perl, Python and Ruby.
- Funtoo and Gentoo trees do have some significant differences for core packages, particularly openrc, baselayout, udev and lvm2.
- If it is important to you, Metro is tested daily to ensure that it can build Funtoo Linux (and Gentoo Linux) successfully. However, these builds are not performed in advance of the changes hitting the public git-based Portage tree.
- Any Metro Funtoo Linux build failures found are typically fixed in the Funtoo Portage within 0-1 days. Gentoo build failures are only fixed if they are related to an issue with Metro. So there is very fast response in Funtoo to core system build failures. In Gentoo, this process is not as integrated.
- Funtoo merges in upstream changes from Gentoo Portage every 12 hours.
- I focus on testing the core, non-GUI/non-X system. Sometimes Funtoo will trail behind in udev revisions that cutting-edge desktop users want to run.
- Both Funtoo Linux stable and unstable have OpenRC 0.6.0, dhcpcd-5 and OpenResolv integrated by default.
- Funtoo Linux unstable tries to upgrade certain core packages such as udev, gcc and glibc much less frequently and in a more controlled manner than Gentoo unstable. This may or may not be a benefit to you, depending on what you are looking for. Basically, I am trying to offer the package updates of Gentoo Linux unstable without as much of the (too frequent, in my opinion) core system changes that can often cause problems for people.
- The Funtoo receives Gentoo changes once every 12 hours. In contrast, the Gentoo rsync tree receives updates hourly. This means that the changes in the Funtoo tree are compressed into a single monolithic event, whereas the Gentoo tree undergoes more continual, but less signficant, change every hour.
- Significant build-related bugs found by Funtoo that also impact Gentoo Linux are sent upstream to bugs.gentoo.org.
Do you use Gentoo's Guide XML for Documentation?
I originally created Gentoo's Guide XML format (which I originally created for Gentoo) for documentation, and started to transition away from it in favor of ReStructuredText. However, now I am trying to support Guide XML and ReStructuredText as they are both useful for different types of things.
Many funtoo.org articles and documents are maintained in ReStructuredText format. HTML versions of the ReStructuredText documentation are generated by first converting the .rst file to XML using rst2xml.py (part of the docutils distribution), and then using XSLT to convert the resultant XML to HTML.
Are you looking for translators?
Many kind people have provided translations of the funtoo.org pages, and the old version of the site used to contain these translations. However, after much consideration, I've decided to not provide translated versions of funtoo.org pages, for several reasons:
- Translated documents tend to become out-of-date
- Updating the translated documents is quite a bit of work
- Most people online seem to have at least a basic grasp of English
For these reasons, I'm going to focus on improving the quantity and quality of English documentation, and not focus on translations for now.
Forking the Portage Tree
I want to fork the Portage tree. How do I do this?
The old way used to involve forking our huge, complete Portage tree. Currently, the best way to do it involves forking the `Funtoo overlay`, which is much smaller, or creating your own overlay. I have scripts that combine the Funtoo overlay and the Gentoo tree to create a unified Portage tree.
I have forked my own Portage tree. How do I generate metadata for it?
You should only do this if you are creating a unified Portage tree for distribution to users. Otherwise, it is much more efficient to use an overlay for this purpose.
First, add FEATURES="metadata-transfer to your /etc/make.conf file. Then type the following commands:
# cd /usr/portage # egencache --update --jobs=4 # cd metadata/cache # git add . # git commit -a
egencache is part of sys-apps/portage and was kindly integrated by Zack Medico, Portage maintainer.
Where can I learn more about git?
So, you want to learn more about git, do you? Here's some inside information -- take the time to get familiar with how git's architecture works internally. This will help you to truly understand git, and make your journey much more rewarding. To get this in-depth understanding of git, I strongly recommend you take a look at the following resources as soon as you're able:
- Git From The Bottom Up - Highly Recommended
- Git Internals PDF from PeepCode - Highly Recommended - Full version is $9 - Free Preview
- Git for Computer Scientists
In addition to understanding git's internal architecture, you'll also need to know how to do things both complex and mudane using git. Here is a bunch of documentation, articles and videos that will help you to become productive with git:
- Git Community Book - a site devoted to teaching you how to use Git.
- Development with Git - great overview with real-world yet simple use cases
- Official Git Tutorial - terse intro to git
- git.or.cz Documentation Links - lots of doc links
- Git - SVN Crash Course - an overview for those familiar with Subversion of the different commands and syntax Git expects
- Git Magic - a great, in-depth tutorial covering topics both simple and complex
- CodeMac.net: Git's Killer Feature - git add -i usage for non-linear development
- Tomayko.com: The Thing About Git - learn about git add --patch
- Git-grep - fast, easy, and smart - learn how to search source code
- Git for mortals - a quick cheat sheet
- Handling and Avoiding Conflicts in Git - a tutorial that does just what it says