Forgot your password?
Red Hat Software GNOME GUI KDE Operating Systems Upgrades Linux

Fedora 20 Released 147

Posted by timothy
from the is-it-a-true-fedora? dept.
sfcrazy writes "The Fedora Project has announced the release of Fedora 20, code named Heisenbug (release notes). Fedora 20 is dedicated to Seth Vidal, the lead developer of Yum and the Fedora update repository, who recently died in a road accident. Gnome is the default DE of Fedora, and so it is for Fedora 20. However unlike Ubuntu (where they had to create different distros for each DE) Fedora comes with KDE, XFCE, LXDE and MATE. You can install the DE of your choice on top of base Fedora."
This discussion has been archived. No new comments can be posted.

Fedora 20 Released

Comments Filter:
  • Re:Whoopty do (Score:4, Informative)

    by Desler (1608317) on Tuesday December 17, 2013 @01:12PM (#45715761)

    There has been a minimal Ubuntu install that you can then install your DE of choice on top of since at least 8.04.

  • Re:Whoopty do (Score:3, Informative)

    by Fwipp (1473271) on Tuesday December 17, 2013 @01:20PM (#45715879)

    And even if you install Unity-flavored Ubuntu and want to switch to, say, Cinnamon, just add the PPA and go.

  • Re:Whoopty do (Score:5, Informative)

    by AdamWill (604569) on Tuesday December 17, 2013 @01:59PM (#45716375) Homepage

    We (Fedora) didn't write anything comparing the way we provide desktops to how Ubuntu does it. That's something the person who submitted the story wrote. It's not a comparison we'd find particularly interesting, I don't think.

  • by kthreadd (1558445) on Tuesday December 17, 2013 @02:07PM (#45716477)

    Fedora does not provide an LTS like release. Every release is maintained for 13 months, and new releases are usually released about every six months. The idea is that if you want a more long term release you should really go with Red Hat Enterprise Linux which is based on Fedora.

  • Re:Yes! (Score:2, Informative)

    by Peter H.S. (38077) on Tuesday December 17, 2013 @04:11PM (#45717967) Homepage

    You are trying to be sarcastic but that doesn't help one bit. Some people don't seem to like systemd, and that is ok with me, but what I find hilarious about the systemd haters are that they can't seem to argue their case in any coherent technical way, they always seem to use ad hominem attacks combined with a considerable dose of paranoid conspiracy speculation. I think your problem is that you actually doesn't have any real knowledge or experience with systemd, that way you are bound to loose any technical argument.

    The plain fact is that I am right and you are wrong. It is hard for newbies that they have learn several different programs and the concept of piping just to view logs. Getting to know 'grep' is only part of their problems, they also need to know what to grep for. grepping for "error" doesn't help if the crucial message is "critical failure".

    With systemd a single line can tell them about all the errors that has happened since they booted the system, and the output is even nicely color coded.
    It is simple to perform log filtering on a systemd box, that would otherwise requires pretty advanced grep, sed/awk skills.

  • Re:CentOS (Score:4, Informative)

    by kthreadd (1558445) on Tuesday December 17, 2013 @05:12PM (#45718737)

    GCC 4.4 is just the system compiler. Red Hat provides supported installations of GCC 4.8 as part of what they call Red Hat Developer Toolset. It includes modern versions of the GNU stack as well as the latest version of the Eclipse development environment.

  • Re:Yes! (Score:2, Informative)

    by Peter H.S. (38077) on Tuesday December 17, 2013 @05:45PM (#45719149) Homepage

    > journalctl -b -1 -p err

    is of course straight forward compared to

    grep "some error" log

    The AC brigade is out in force tonight I see. Anyway.

    Your example shows exactly what is wrong:
    1. What error? How does the newbie know what to grep for without knowing what is written in the log? A 'grep "some error"' will of course miss both "Error" and "", but also miss errors indicated with "Failure" or "Warning".
    2. The newbie can be swamped with error messages since your simplistic grep (without -i switch and path, and no pager too) just dump every "some error" logged the last couple of months unto the terminal. The journalctl example just showed errors generated since previous boot, something that is much harder to do with grep only.

    The journalctl example shows how simple it is to filter the log so that only essential information is shown.

    I really recommend you try to actually learn systemd. Get F20 and hack away.
    This is a good starting point: []

    You can still use all the grep, sed, awk Kung Fu you know with journalctl, it just makes it so much easier.

"Consistency requires you to be as ignorant today as you were a year ago." -- Bernard Berenson