More mirrors here, but not all servers are synced with 20 yet: https://mirrors.fedoraproject.org/publiclist/Fedora/20/
No announcement yet, link in title leads to release notes.
x86_64 DVD: http://torrent.fedoraproject.org/torrents/Fedora-20-x86_64-D...
magnet:?xt=urn:btih:724bcc8a53b854daa844e6bc204b95124a1074d6&dn=Fedora-20-x86%5F64-DVD&tr=http%3A%2F%2Ftorrent.fedoraproject.org%3A6969%2Fannounce
i386 DVD: http://torrent.fedoraproject.org/torrents/Fedora-20-i386-DVD...
magnet:?xt=urn:btih:d6d123d9a9b108971ecb09ca6593d2593cd564a4&dn=Fedora-20-i386-DVD&tr=http%3A%2F%2Ftorrent.fedoraproject.org%3A6969%2Fannounce
- Journald logs the whole boot process
- Journald can make sure that an item really came from some process. It also tries to seal the journal so that it can't be tempered with.
- It's built into the other systemd tools. For example, when you notice a daemon doesn't start through systemctl, it'll show you the error messages in systemctl status.
http://www.freedesktop.org/software/systemd/man/sd-journal.h...
One needs to look no further than what their plans for cgroups are to see the future. Not to mention the plans to get rid of /bin/login and VTs.
Anyway, your entire complaint is explained at every systemd presentation. The maintainers want to have something which can be used as the basic building block for Linux. Various other projects now rely on that.
So systemd is successful, but surely it is a conspiracy! hahaha
yum install rubygem-rails
Fedora seems to have one of best ruby support. Way to go!
What's the typical time lag before a package get updated after a gem does?
In today's cloud-based hosting environment, you want to preserve mobility whenever possible, and Bundler does a better job of managing Ruby dependencies than dpkg/yum does. You can then use configuration management to get a system bootstrapped to a base where all your Ruby projects can run, then Bundler can take care of project-specific dependencies. It's not perfect, a lot of times a project gem will require system dependencies, like MySQL, but the separation of concerns does help a bit.
You should, however, use system Ruby because using RVM / Rbenv in production vastly increases complexity, and because the system dependencies that your gems have will be the right versions. It's much easier now that the latest Ubuntu packages Ruby 2. It took me all of an afternoon to redo the configuration management and provisioning and migrate my projects when Ubuntu 13.10 came out.
On the plus side, you get security updates, and any gems that are packaged should be compatible with each other to some extent. In general, I think ruby packages are good for end-users, but maybe not great for developing ruby applications or other gems.
(I don't mean to rag on Fedora packaging here — I'm a Fedora packager! I just want people to be aware of the limitations of distro packaging.)
I think it has lots in common with this:
"Fedora 20 includes the WildFly 8 Application Server, formerly known as the JBoss Application Server, a very popular Java EE platform. WildFly is a very fast, modular and lightweight server."
keep producing more and more bloatware, without any other reasons than "because we have done it".
I think that blindly allowing freedesktop guys to mess up all the traditional Unix startup and now logging tools with some MS-inspired crap for a very questionable reasons is quite a step back.
It is also an example of an over-engineering bias (which comes from OO-only approach) - building up an unnecessary complexity. syslog and shell script based startup procedure are good-enough (and still good enough for sane systems such as BSDs or Plan9), while those who need a specialized logging (or startup) service could create it for themselves, as so many do.
Changing reasonable defaults just because someone is cocksure that we need more xxxxctl and xxxxx-bridge instead of plain old text-files looks like ignorant over-confidence. Those who cannot live without journald could install it manually, why to cause a headache to the rest of us.
I do remember that commercial variant of Suse Linux have tried "an innovative approach" to what a Linux server is. They introduced a set of some in-house made utilities (inspired by Netware I suppose) with non-intuitive logic and millions of command line options no one knows (which cannot be googled). Why, it is a way to success, now you could teach courses, do certification, issue meaningless titles, etc. Thank god its dead. ESX servers, btw, were (or still are) even bigger mess.
I doubt that Fedora is going this way, but the signs are bad.)
This is like complaining that any disto is "bloatware" because their repositories include software that you happen to dislike and think is "bloat". $distro is bloated because KDE/GNOME/whatever is an option, right?
Get a grip.
I think that the only reason to re-write something that is good-enough is to make it even simpler, more clear and, in some rare situations, more general (but what could be more general than text files and pipes?)
Imagines someone in physics would say "this equation is not clever-enough, it lacks linear algebra, let's rewrite it using vector notation". Guys in physics are using vectors because it is the most convenient way to represent some aspects of reality, not because it is clever or popular. Similarly, the mantra should be "simplify" (and generalize).
Anyway, thank god, they didn't bring some nice, little "real-time, non-blocking log collector" written in a nice, object-oriented, modular NodeJS with some nice little MongoDB-powered clustered storage.
If you opt for #2 submit it here.
- I've been using Fedora (VM, test, production server) since release 4 or 5. - I have a VM that has been updated without full reinstall since release 11. It will be destroyed soon, as I'm reinstalling the host. - I've been using Fedora as my main desktop since Fedora 16.
My experience varies, depending on the sh*t they decide to push (like Gnome 3 or systemd). It takes time so that things get stable (or I get more used to them).
As a full stack developer, I almost never use distro packages like gems or python libs or java libs. Even tools like Eclipse I prefer to install them separated.
Overall, I'm satisfied.
I'm sure I'm going to forget about that... I can't wait for the first WTF :)
I'd like to install Fedora 20 and use it as my main desktop, but both systemd and journald will somehow have to be avoided and worked around because I don't want to touch those with a ten foot pole.
As far as mainstream Linux distributions go, it's like choosing between 2 evils nowadays:
* Ubuntu: decent base system, lousy desktop
* Fedora: lousy base system, decent desktop
The former is almost fixed by Elementary OS, but the latter I'm still looking for a spin or derivative that fixes it. What attracts me most to these mainstream distributions is the vast amount of available packages and their ease of maintenance.
$ grep shiz /var/log/messages
grep: /var/log/messages: No such file or directory
$ ls /var/log
README dnf.log wtmp Xorg.log.0 ...
$ head /var/log/README
You are looking for the traditional text log files in /var/log, and
they are gone?
Here's an explanation on what's going on:
As for servers, I wouldn't use Fedora. Each release is supported for only 13 months and upgrades are not as seamless as in Debian.
So for me Fedora is a very decent desktop if you want the new shinies with ease of use. Most of the time works and it's great (even with the "Gnome 3 surprise factor", that keep _breaking_ things every now and then).
You mean the unity stuff? I installed the KDE Desktop package and it's great and works great =)
Retina and retina-like users rejoice!
More mirrors here, but not all servers are synced with 20 yet: https://mirrors.fedoraproject.org/publiclist/Fedora/20/
No announcement yet, link in title leads to release notes.
Anyone has succeeded dual botting Fedora 20 with Windows 8.1 in a UEFI system with secure boot?
When I tried the beta it made Windows 8.1 unbootable.
http://download.fedoraproject.org/pub/fedora/linux/releases/...
(Might still give a 404 until your mirror is in sync.)