Antergos, as its father, Arch Linux, is a rolling release distro. This means that you don’t have to worry about if there’s a new version to download, like in Ubuntu or Fedora.
With a rolling release based distro, you will always have the latest updates. Just by making a regular update of your system software, the package manager downloads what you need.
Ready to use
Antergos comes with everything you need. The default configuration gives you a ready-to-use system. Elegant, simple and at the same time powerful.
After a successful installation. You are ready to go. No more steps needed. Just reboot your computer… and enjoy.
Available in different languages like Spanish, Galician, Catalan, English, German and many more, Antergos gives you the best experience in your mother tongue.
Install easily Antergos with our Multilingual Live Medium and our easy-to-use graphical installer.
Antergos is free. You can download it and make as many copies as you want. All you have to do is download the iso image, burn it on a CD/DVD or write it to a USB and enjoy.
We have a set of auto-generated images for testing purposes. These images are released every Sunday. They will contain the latest package versions and also the latest Cnchi code from our github stable branch.
We only store one week of these testing images on our servers. When new images are built, the old ones are deleted. The build logs are available for viewing in the same folder as the images. Feel free to check them out if you like.
The idea behind KaOS is to create a tightly integrated rolling and transparent distribution for the modern desktop, build from scratch with a very specific focus. Focus on one DE (KDE), one toolkit (Qt), one architecture (x86_64) plus a focus on evaluating and selecting the most suitable tools and applications. All work is geared toward packaging, not developing new tools or applications.
There is no goal to make the most possible software available, KaOS will stay limited in size of the repositories, and will work on quality instead of quantity. That goal makes it clear, a large user base is not what is intended or expected.
Moving away from proprietary Operating Systems to open source options (Linux-based, BSD based, Solaris based) is about wanting freedom and choice in almost all cases. But should any such Operating System or Distribution not make some choices of what it believes is the best fit? KaOS sees a lack of focus in that respect. To create the highest quality Distribution possible, there needs to be a focus to make sure the user gets the best possible for whatever choice they made.
It simply is not possible to package any and all to work perfect for every Desktop Environment or Toolkit.
KaOS has made the choice to use the Linux kernel as a base (though the Illumos kernel is under constant evaluation, and a future switch is a wish). After that choice, the best available package manager, most flexible way of package building, repository maintenance is pacman/makepkg for a rolling distro like KaOS.
As for the Desktop Environment, there will never be a change, whether it is Linux or Illumos based, KDE will be the choice, Qt the Toolkit.
With those choices in place, April 2013 package building for this independent distribution was started. KaOS is a build from scratch distribution, every package in every repository is build by and for KaOS. By July 2013 the initial goal of about 1500 packages was reached.
Making the choice for KDE/QT does not mean KaOS loses sight of the importance of having the best tool available for the job. Most of the time it is believed KDE/Qt provides the superior tool, but there are a few applications were the GTK option is the only available of that kind (Inkscape, Ardour to name two), or in the case of web-browsers for example, the Qt options do not stack up to their GTK counterparts. For those instances, GTK applications are available, though their number will stay limited.
The repository layout is simple, and consists of three groups, Core, Main and Apps. A regular complete system update will always give you the latest available, without the need for any re-install of the system.
“Core” has the base packages needed for a system to boot-up, communicate with the BIOS connect most hardware and set basic shell options. Example packages are the kernel, systemd, toolchain for building and basic command-line tools. This repository is carefully rolling, since any upstream update not thoroughly tested greatly affects the stability of the system.
“Main” repository consists of all the needed libraries, extra drivers and firmware needed to make the Desktop and Applications function. Many of these can be fully rolling and will move to the end-user after a seven to ten days testing period. Some more vulnerable packages will enter after enough upstream feedback is available that no regressions have occurred.
“Apps” consists of all packages seen and used by the users, including KDE and any needed tools. It is fully rolling and you can expect updates to reach this repository after a short testing period, unless it needed to be built on newer versions of Core or Main packages, than it will have to wait until those are ready to come out of their testing period.
“Build” is were all packages start, whether it is a rebuild, update or new addition, all goes to build, once gone through the proper testing, than they are moved to their respective repository.
Mozilla today officially launched Firefox 26 for Windows, Mac, Linux, and Android. Additions include Click to Play turned on by default for all Java plugins, more seamless updates on Windows, and a new Home design for Android.
First and foremost, the Click to Play revamp was supposed to be for all versions of all plugins, except the latest release of Flash. Unfortunately, Mozilla has pushed back this change and decided to focus on just Java.
In short, the feature means Firefox now only loads Java plugins when users click to interact with them. Previously, Firefox would automatically load Java whenever a site requested it, unless Mozilla had blocked it for security reasons (the company already blocks old versions of Java, Silverlight, and Flash).
Now, when a site tries to use Java, the user can choose whether to enable the plugin on that site. Firefox will only load it when you take the action of clicking to make it play. Alternatively, you can also configure Click to Play so that it always runs plugins on a particular website.
Java blocking isn’t the only change in this release; here’s the official changelog for Firefox 26:
- NEW: All Java plug-ins are defaulted to ‘click to play’.
- NEW: Password manager now supports script-generated password fields.
- NEW: Updates can now be performed by Windows users without write permissions to Firefox install directory (requires Mozilla Maintenance Service).
- NEW: Support for H.264 on Linux if the appropriate gstreamer plug-ins are installed.
- CHANGED: Support for MP3 decoding on Windows XP, completing MP3 support across Windows OS versions.
- CHANGED: CSP implementation now supports multiple policies, including the case of both an enforced and Report-Only policy, per the spec.
- DEVELOPER: Social API now supports Social Bookmarking for multiple providers through its SocialMarks functionality (see MDN docs).
- DEVELOPER: Math.ToFloat32 takes a JS value and converts it to a Float32, whenever possible.
- DEVELOPER: There is no longer a prompt when websites use appcache.
- DEVELOPER: Support for the CSS image orientation property.
- DEVELOPER: New App Manager allows you to deploy and debug HTML5 webapps on Firefox OS phones and the Firefox OS Simulator.
- DEVELOPER: IndexedDB can now be used as a “optimistic” storage area so it doesn’t require any prompts and data is stored in a pool with LRU eviction policy, in short temporary storage.
- FIXED: When displaying a standalone image, Firefox matches the EXIF orientation information contained within the JPEG image (298619).
- FIXED: Text Rendering Issues on Windows 7 with Platform Update KB2670838 (MSIE 10 Prerequisite) or on Windows 8.1 (812695).
- FIXED: Improved page load times due to no longer decoding images that aren’t visible (847223).
- FIXED: AudioToolbox MP3 backend for OSX (914479).
- FIXED: Various security fixes.
If you’re a Web developer, you should probably also check out Firefox 26 for developers.