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.
Meet our crazy community on Facebook. Alternatively, have fun with the guys and gals on Google+, or simply +1 us our Google+ page.
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?
So, this started as a personal project. One of the projects you start during a rainy day. Actually, it did not rain at all, but I wanted to take a day off from my readings (just completed this btw).
You cannot really stop hobbyists from doing what they’re best at, after all. You cannot even stop enthusiasts from being enthusiasts when, eventually, somebody puts some love into the Linux ecosystem.
So, my question is, while we wait for the official SteamBox (and perhaps Half-Life 3…), why don’t we make our own? And this is what I did.
I want to share with you a (personal but publicly available) Sabayon image called: “Sabayon SteamBox Edition (md5, torrent)“.
Sabayon SteamBox Edition is a remastered 64bit only Sabayon live image that contains Steam. This image can be either run off USB storage or DVDs or installed, like any other Sabayon image. The difference is that, once booted, Steam is automatically started in Big Picture mode.
Well, as written above, Steam is automatically started in Big Picture mode at boot. However, you can exit Steam and logout through an application running in background called “Steam Manager” and then, log into GNOME and use the system as a normal Sabayon distro. This allows you to make changes to it, like for instance, setup a wireless connection, configure Steam the way you want or just update the system, and then dive back into the “SteamBox” mode.
This is pretty much the way I converted my Windows Steam (gaming) machine into a Sabayon SteamBox, and I’m sure that some of you may want to do the same.
Seriously, get a NVIDIA GPU. If you really want to play complex games that’s the easiest solution. However, I also managed to run Steam off open source radeon and even intel drivers, but I got the best experience when using the nvidia ones. Sabayon SteamBox also experimentally supports NVIDIA Optimus (it uses optirun, but I will migrate to primusrun soon) if you boot the system appending “optimus” to the kernel command line.
Simple, just “equo install sabayon-steambox“, enable the “steambox” service (with systemd: systemctl enable steambox), append “steambox” to the kernel command line and reboot.
Thanks Valve.
We are happy to announce that the systemd migration is now complete and systemd became our default init system. However, openrc is still actively supported and working but we suggest you to try it out by using the latest Sabayon images available. In particular, GNOME 3.8 is the last release that we're planning to support with openrc. If you don't know anything about systemd vs openrc, keep calm and visit our forum. A way to switch from openrc to systemd or vice versa is using the eselect init command line tool.
Many people know that GNOME 3.8 was held back due to its hard dependency against systemd and Sabayon was still running with openrc as default init system. However, this has changed. Now that systemd became our default init system, and the current GNOME 3.8 works with openrc (thanks to the systemd-love Portage overlay), we were able to deliver the latest and greatest stuff to you.
KDE 4.11 is just a couple of weeks away but we've already done the preparatory work to host this new stable release. If you can't wait, just keep your eyes at the official release schedule.
The reworked Sabayon Linux kernel release process made possible to follow the weekly stable release schedule madness and newer kernels enter the sabayon-limbo (unstable) repository with no more than 36 hours delay average. This is a great thing for users that can benefit from usptream bug fixes (and regressions...) without too much delay. Long Term Stable kernels like 3.4 (and in future 3.10) will continue to be updated as well.
UEFI support in 32bit flavors of Sabayon has been dropped as per Matthew Garrett advice and an important Installer bug related to the UEFI Boot Partition filesystem type has been fixed (commit 292781b37763b28dbd583eec93bd3349b61b43fd).
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.
I’ve been seriously slacking on the Sabayon stuff, but been hanging with the community on the Official Sabayon Facebook page and watched a thread on a background image erupt into a mountain. It really is amazing at how a small change to a GUI send people running for their pitchforks and torches. I’ve been guilty of this in the past myself and probably will be in the future too. The GUI is very important to us and it’s drastic unchangeable changes really ticks a guy off. Gnome and KDE both felt the feedback when they revamped their GUIs. I abandoned Gnome cause of the gnome shell. Some love the gnome-shell and brag it up and down. Gnome maybe pays them to do it….
Anyway, I finally took some time tonight to test latest daily Sabayon Forensics to make sure all was well. It’s probably been a month since I test a daily. I pop in the freshly made live usb stick and boot it up. I see some of the new artwork very briefly cause my computer booted up so damn fast. I remember the good old days of enjoying a song while my computer booted. What is going on here? I turn on my computer and it’s like booted instantly. No music, a brief flash of artwork and I am at my desktop. So I had to browse to the backgrounds directory to see the new artwork and change my desktop wallpaper to it since Sabayon Forensics has different wallpaper and ya know what? I like it. If ya don’t like it, the fix is so easy, it’s not permanent unlike gnome-shell. So lets put the pitchforks and torches away and enjoy. If I like it, it has to be good right? At least it’s not blue, green or yellow. Although, a SpongeBob SquarePants desktop would be pretty sweet. Hey, I saw you do that facepalm!
Oh and by the way, if you miss the boot up song, No fear - http://www.youtube.com/watch?v=BgiMpxb-lC4 even has the lyrics so you can sing along. Regardless guys, I still <3 our community no matter what colors ya are in to 
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 [email protected] (expand the domain, duh!) if you’re interested.
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!
Re: modify permissions for a partition sabayo... Re: Desktops - Show Off Your Desktop Re: modify permissions for a partition sabayo... Re: Desktops - Show Off Your Desktop Re: Desktops - Show Off Your Desktop Re: Desktops - Show Off Your Desktop KDE: Nepomukfileindexer makes external harddr... Boot from ZFS Root: How? Re: Rigo fails to start. Re: Rigo fails to start.
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.
