There are many different Sabayon variants. Each one is designed for a specific purpose and designed to bring out the best in your hardware
We provide Live versions of most of our variants, so you can try out Sabayon without touching your Computer's Hard drive.
There is no way in the entire World we couldn't have our very own Facebook Group! We are there. So, what are you waiting for? Join us.
You don't have to be able to code to help the Sabayon Community. There are many ways to contribute, be it your passion, your skills, your time or a monetary donation.
Sabayon is user powered, created solely on freely given user contributions, so why not help out and give back to the community?
Sabayon 13.04 is a modern and easy to use Linux distribution based on Gentoo, following an extreme, yet reliable, rolling release model.
This is a monthly release generated, tested and published to mirrors by our build servers containing the latest and greatest collection of software available in the Entropy repositories.
The ChangeLog files related to this release are available on our mirrors.
Linux Kernel 3.8.8 (3.8.10 available through updates, 3.9 available in hours) with BFQ iosched and ZFS, GNOME 3.6.3, KDE 4.10.2, MATE 1.6 (thanks to infirit), Xfce 4.10, LibreOffice 4.0, production ready UEFI (and SecureBoot) support and experimental systemd support (including openrc boot speed improvements) are just some of the things you will find inside the box.
Please read on to know where to find the images and their torrent files on our mirrors. Pay attention that there were unreleased 13.04 ISO images previously on our mirrors. Make sure to download images with the correct MD5 checksum though (or just re-download the ISO images).
Sabayon 13.04 is the first release coming with systemd optionally available for early testers. systemd is going to replace openrc as the default init system in the following months, this however doesn't mean that OpenRC will be abandoned. We do believe however that it's time to move on, and leave the 90s and VHS once and for all. Systemd gives Sabayon a 4x (or even more) boot speed boost if compared to OpenRC: you can now enjoy a 10 seconds boot on Sabayon as well. Please take into consideration that as of today, systemd support in Sabayon is still experimental and we don't have plymouth yet (so you get a nice static splash screen). Booting with systemd is easy: if you're on an UEFI system, just go into the Advanced options menu and select Enable systemd, while if you're still using a BIOS from the 80s, just press F5 and select real_init=/bin/systemd. If you boot the live image with systemd and start the installation, you will get systemd enabled by default. If you want to migrate your current Sabayon 13.04+ installation to systemd, just type: eselect sysvinit set systemd and eselect settingsd set systemd and reboot. If the system won't boot, just add this to the boot parameters: real_init=/sbin/init.d/sysvinit/init.
If you are interested in writing or porting systemd units and you have some experience with Portage, have a look at the systemd-love overay on GitHub. For each fully working, previously missing, systemd unit submitted to our Bugzilla we're willing to give you a 3.5€ bounty through PayPal. There are around 490 packages in Gentoo still missing systemd love.
We have successfully migrated all our development repositories to GitHub. You can have a look at our stuff at the Sabayon org page. If you wonder how to start contributing to Sabayon now it's clear: send pull requests. If you wonder how to be part of our project: send pull requests.
If you however don't know how to code: donate us money! we always need funds!.
While Sabayon 11 introduced an experimental support to UEFI and UEFI SecureBoot, with Sabayon 13.04 we're happy to consider such support production ready. We have been able to squash all the reported bugs during this cycle.
/tmp is now mounted on a very small tmpfs with nodev,noexec,nosuid options by default for greater security. Some exotic programs that insist on writing to /tmp may fail to run and they should be fixed upstream. Writing to /tmp is bad, and you should not use any software that behaves like this.
There is a lot more, but we're lazy and this is a monthly rolling release announcement, which means that we're in hurry again! But please, just download the ISO image you like and see the improvements yourself.
Please find the official file names and hashes below.
We started to roll out systemd today.
But don’t panic! Your system will still boot with openrc and everything is expected to be working without troubles.
We are aiming to support both init systems, at least for some time (long time I believe) and having systemd replacing udev (note: systemd is a superset of udev) is a good way to make systemd users happy in Sabayon land. From my testing, the slowest part of the boot is now the genkernel initramfs, in particular the modules autoload code which, as you may expect, I’m going to try to improve.
Please note that we are not willing to accept systemd bugs yet, because we’re still fixing up service units and adding the missing ones, the live media scripts haven’t been migrated and the installer is not systemd aware. So, please be patient 
Having said this, if you are brave enough to test systemd out, you’re lucky and in Sabayon, it’s just 2 commands away, thanks to eselect-sysvinit and eselect-settingsd. And since I expect those brave people to know how to use eselect, I won’t waste more time on them now.
While Spring has yet to come here, the rainy days are giving me some time to think about the future of Sabayon and summarize what’s been done during the last months.
As far as I can see, donations are going surprisingly well. The foundation has now enough money (see the pledgie.com campaign at sabayon.org) to guarantee 24/7 operations, new hardware purchase and travel expenses for several months. Of course, the more the better (paranoia mode on) but I cannot really complain, given that’s our sole source of funds. Here is a list of stuff we’ve been able to buy during the last year (including prices, we’re in the EU, prices in the US are much lower, sigh):
Plus, travel expenses to data centers whenever there is a problem that cannot be fixed remotely. That’s more or less from 40€ to 60€ each depending on the physical distance.
As you may understand, this is just a part of the “costs”, because the time donated by individual developers is not accounted there, and I believe that it’s much more important than a piece of silicon.
Besides the money part, I spent the past months on Sabayon 11 (of course), on advancing with the automation agenda for 2013. Ideally, I would like to have stable releases automatically produced and tested monthly, and eventually pushed to mirrors. This required me to migrate to a different bittorrent tracker, one that scrapes a directory containing .torrents and publishes them automatically: you can see the outcome at http://torrents.sabayon.org. Furthermore, a first, yet not advertised, set of monthly ISO images is available on our mirrors into the iso/monthly/ sub-directory. You can read more about them here. This may (eheh) indicate that the next Sabayon release will be versioned something like 13.05, who knows…
On the Entropy camp, nothing much has changed, besides the usual set of bug fixe, little improvements and the migration to an .ini-like repositories configuration files syntax for both Entropy Server and Client modules, see here. You may start realizing that all the good things I do are communicated through the devel mailing list.
I spent a week working on a Sabayon systemd system to see how it works and performs compared to openrc. Long story short, I am about to arrange some ideas on making the systemd migration come true at some point in the (near) future. Joost and I are experimenting with a private Entropy repository (thus chroot) that’s been migrated to systemd, from openrc. While I don’t want to start yet another flamewar about openrc vs systemd, I do believe in science, facts and benchmarks. Even though I don’t really like the vertical architecture of systemd, I am starting to appreciate its features and most importantly, its performance. The first thing I would like to sort out is to be able to switch between systemd and openrc at runtime, this may involve the creation of an eselect module (trivial) and patching some ebuilds. I think that’s the best thing to do, if we really want to design and deploy a migration path for current openrc users (I would like to remind people that Gentoo is about choice, after all). If you’re a Gentoo developer that hasn’t been bugged by me yet, feel free to drop a line to lxnay@g.o (expand the domain, duh!) if you’re interested.
Sabayon 11 has been released and it seems like every time we do a release, people get confused with their current system and upgrades. Our releases are just a present day snapshot to save a user from having to do a pile of updates on a brand new install. A rolling distro really doesn’t have a version per say. Do your updates and you are current, simple as that. So than I see people wondering why Sabayon 11 has a newer kernel than their fully updated present system. Well, you need to manually upgrade your kernel with kernel-switcher. Kernel upgrades in general are not automatically done to prevent users from having possible issues. Kernel-switcher will make the job simple for you.
In the past while I have noticed users are not properly updating and that can give a user issue(s). A quick order of things:
Now you’re thinking that is a lot of steps, but break it down it makes sense to do it in this order. Update your repositories, install the latest package manager, do your upgrades, check for dependencies, check for config file updates and check for sanity. Problems happen when you don’t install latest package manager and proceed to do a large amount of updates, or a dep is missing or forget to update config files. These steps can save you hours of hunting down a fix.
There is an easy way to save yourself from having to repeatedly do the commands over and over. Simple create yourself an alias. In your /root/ directory is a file called .bashrc (period means it’s hidden file) and you can edit that file to save some typing. Open the file up as root and go to the bottom of the file and enter in your alias word with command you want. Now you can call that command with a simple word and it will do it’s thing. So for example, I use the word world with a string of chain commands to perform my updates.
I enter the above line at the bottom of the .bashrc file and save it. I open up terminal, switch to root and than type in the command world and I sit back and watch entropy update my system. Follow along with it and if it needs user interaction it will stop and wait for you to interact with it, such as a license or config file. You can use any word you want, just remember what the word is and if you forget what your alias is, simply enter alias into your terminal and it will display all of them.
Doing the above will help cut down issues. Another thing you can do, pay attention to the notice board of important announcements from the package manager. Such as [1] [Sun, 14 Oct 2012 20:12:39 +0000] Title: Important AMD GPU related changes in Linux Kernel 3.6+ that could apply to you. Upstream is constantly changing and one day you upgrade and upon reboot you are at a black screen cause all of a sudden your video card is no longer supported. You may need to mask or use a different driver to prevent the black screen. So beware of changes happening with your upgrades. If I had a dollar for every time I saw a post of ” I just did my upgrades, rebooted, and now all I get is a black screen what could be the problem? ” I could take a lot more vacations. Of course the user never supplies one single log file so it’s anybody’s guess as to what is wrong. I can’t stress it enough, nobody has a crystal ball to figure out your problem if you give them nothing to go on. Get to know your log files and know your hardware. You’re going to be asked for that information anyway, so you might as well provide it and save the cat and mouse game.
As a community we have our social sites like facebook, twitter, google+ and so on. These social sites are not designed for doing support related events. Our forum is the official place for support. By using the forum you can help others narrow down their searching for similar issues. So by posting your questions and getting your issues resolved can help another user and it helps those that do support others to focus on one website instead of multiple sites. Keep the wealth of information in one area instead of spreading it out across the internet leaving users chasing links.
If you’re not the upgrading your system all the time type of person, Danilo has you covered with frozen repos of Sabayon 10 and 11. This allows you to use your system as normal and install additional software without doing upgrades.
Happy Rolling!
We're here once again to announce the immediate availability of Sabayon 11 in all of its tier-1 flavours. If you really enjoyed Sabayon 10, this is a release you cannot miss!
There you have it, a shiny distro for your home computer, your laptop and your servers, virtualized or not.
Linux Kernel 3.7 with BFQ iosched, GNOME 3.6.2, KDE 4.9.5 (upgraded to 4.10.1 as soon as it is available), Xfce 4.10, LibreOffice 3.6.3 are just some of the things you will find inside the box.
Complete EFI/UEFI and UEFI SecureBoot support, greatly improved NVIDIA Optimus support through Bumblebee, MATE 1.4 for those missing GNOME 2.x, a selection of MySQL flavors, including Google MySQL and MariaDB, up to 14000 packages now available in the repositories per architecture, and much, much more.
As many of you know, Sabayon is a rolling distribution with some tweaks to the model to make the experience less painful and more predictable. This also mean that our official releases (or snapshots) are becoming stale very quickly, which is a reason why we have "daily" live media images available as well. Now, we want to take it further and, in the near future, offer semi-automatic monthly (or bi-monthly) releases. During this release cycle and the upcoming one, the focus has been and will be on distribution-wide continuous integration and testing. This also means that your contribution in terms of feedback, bug reporting and donations is going to be even more important for us!
Starting from Sabayon 11, all the x86_64 live images can boot and install on {U,}EFI only systems through GRUB bootloader. While we debate the way SecureBoot is implemented and its key management governed, we decided to make Sabayon bootable on systems where SecureBoot is enabled, through shim-signed, by Matthew Garrett. The process is simple: at the first live boot, you will be asked to enroll the Sabayon SecureBoot key, which is available in the "/SecureBoot" directory on the live media. However, in order to give you full control of your system, during the installation a new and personal SecureBoot keypair will be generated (and put into /BOOT/EFI/sabayon/enroll-this.cer). This means two things: you must also enroll this new key at the first boot after install and you will be able to sign your own binaries without depending on any third-parties (including us).
To learn more about SecureBoot in Sabayon, also read this blog post.
Sabayon 11 gained out of the box support for NVIDIA Optimus through Bumblebee (and bbswitch). Optimus systems are automatically detected and configured on your behalf if a NVIDIA GPU, an Intel GPU and NVIDIA proprietary drivers are installed.
As always, the amount of software updates is huge, and you can search for your favorite software through our web interface. Here are some worth a mention: all our Linux kernels (server, desktop, hardened, ec2, arm) at the time of this writing, have been updated to 3.7.4, GNOME has been updated to 3.6.2, KDE to 4.9.5 (and 4.10.1 is in the works), LibreOffice to 3.6.3.2 (and 4.0 will arrive soon), MATE saw its 1.4 release and XBMC 12 is finally here. Last but not least is Steam! Yes, we now have it in our repositories as well.
The Sabayon repositories have now reached almost 14000 packages available for each of the main architectures currently supported (i686, x86_64). This has been made possible by our new internal continuous building tools (Matter and Cosmos), and your donations of course.
Rigo, the Google-style graphical application browser, received a tremendous set of small but important speed and usability improvements thanks to your feedback. For example, a whole new set of keyboard accelerators has been implemented: CTRL+F for switching to the search bar, CTRL+M to load the preferences menu and CTRL+P to move the focus to the results list area.
For those of you who love Equo more, it may be interesting to know that the whole Equo codebase has been rewritten from scratch and the old stinky code that was around since 2007 has been eventually thrown away. While the command interface is still the same, you will be able to realize that some new features have appeared here and there, and most importantly, that now every equo sub-command has built-in support for bash completion and man pages. Fore more details about the new Equo, have a look at this blog post.
Three MySQL flavors are now available in our repositories, and I personally feel quite proud of this: Google MySQL 5.1, Oracle MySQL 5.5 and MariaDB 5.5. We expect to migrate to MariaDB as the default MySQL implementation once version 10.0 is released as stable.
As Sabayon 11 comes in many different flavors, which one are you supposed to pick? Good question! First of all, it depends on your computer architecture, whether it’s 64bit or 32bit. Usually, any modern computer has 64bit support and we encourage you to only consider the live images containing the "amd64" identifier. As you may have now realized, "amd64" stands for 64bit while "x86" stands for 32bit. Now, if you don’t know anything else about a Linux distribution and its different Desktop Environments and you have a decent computer, just pick the one ending with _G.iso. "G" stands for GNOME. However, if you think that GNOME 3.x sucks, don’t worry, you are not alone! In this case, we suggest you to consider the KDE version of Sabayon, marked with a "_K.iso" suffix. If you then realize that your system is really slow with either one of them, well, you have no choice other than picking the MATE and/or Xfce ones, respectively marked with a "_MATE.iso" and "_Xfce.iso" suffix. If you don’t know how to install Sabayon or you are afraid to make a mistake, just click on the "Get Live Help" icon you can find on the Desktop or simply go to our WebChat or our forums.
CoreCDX is a minimal install for those wishing to configure the system more to their liking, and uses the Fluxbox Window Manager. HardenedServer is an Xfce powered image that comes with a Gentoo Hardened kernel (the base system is compiled with hardened flags on all the Sabayon releases). ServerBase and SpinBase instead, are respectively base images for creating server oriented and desktop oriented Sabayon distributions.
There are several things you can do, depending on your free time or your financial resources.
Donations are for sure the easiest way to help Sabayon growth. You can make them by going to http://www.sabayon.org/donate. If money is a problem for you, but you still have some free time, you may want to join us, as external contributor or core team member, by subscribing to the devel mailing list and joining us on freenode in #sabayon-dev.
If time and money are a no-go for you, just use Sabayon and spread the word! If you will ever meet one of the developers, just offer them a beer.
During 2012, we have been able to improve the speed and reliability of our infrastructure thanks to your support and we hope to be able to raise the same funds in 2013 as well! In particular, four SSD drives (2x256Gb Samsung 830 and 2x480Gb OCZ Vertex 3), a bunch of new hard drives and a completely new tinderbox server have been purchased.
Please find the official file names and hashes below.
If you are looking for help or advice, the friendly and helpful people on the Official Sabayon Linux Forums are the people you need to be talking to!
Cómo Instalar Canon Pixma 495 series por Red ... Re: The config could not be loaded Re: Equo wants to install linux-server kernel... Re: The config could not be loaded Re: log di output di equo Re: log di output di equo Re: nuova installazione ma il Bluetooth? Re: Magneto Re: Apper/Packagekit Re: Debugging a system crash
Housing our Entropy build server inside the Faculty Network Center at the Department of Electronics.
Sponsors Sabayon by housing our Entropy build servers and WWW inside DISCo
Sponsors Sabayon by housing our Entropy build server inside CISCA.
© 2004-2011 Sabayon Promotion (CF: 93018620224).
Unless otherwise stated, content on this page is licensed under a Creative Commons Attribution-ShareAlike 3.0 License.
Linux is a registered trademark of Linus Torvalds. - All other trademarks are property of their respective owners.
