Slashdot Mirror


Fedora 23 Released (fedoramagazine.org)

An anonymous reader writes: Today marks the release of Fedora 23 for all three main editions: Workstation, Cloud, and Server. This release brings GNOME 3.18, Libre Office 5.0, and Fedora Spins — alternate desktops that provide a different experience. Fedora 23 also includes a version optimized for running on ARM-based systems. You can read the full release notes on their website. "Fedora 23 also has important under-the-hood security improvements, with increased hardening for all compiled software and with insecure SSL3 and RC4 protocols disabled. We've also updated all of the software installed by default in Fedora Cloud Base Image and Fedora Workstation to use Python version 3, and the Mono .NET compatible framework is now at version 4. Perhaps most importantly, Unicode 8.0 support now enables the crucial U1F32D character."

9 of 57 comments (clear)

  1. Unicode 8 support by Guy+Harris · · Score: 3, Funny

    Perhaps most importantly, Unicode 8.0 support now enables the crucial U1F32D character.

    Hot dog!

    1. Re:Unicode 8 support by Guy+Harris · · Score: 2

      I thought there was a Unicode code point shortage?

      Nope. Originally, Unicode only had room for 65536 code points, but it was extended with Unicode 2.0 to 1,112,064 code points. At least if the Wikipedia page on it is to be believed, only 120,737 characters have been defined as of Unicode 8.0.

      Maybe that's just because UTF-8 because has to maintain backward compatibility with ASCII.

      Nope, UTF-8 can actually represent even more code points than that, but any encoding that results in a code point value past 0x10FFFF is invalid in UTF-8.

      From what I understand, in doing so, it wastes a few hundred other code pages.

      Nope. All that "maintaining backward compatibility with ASCII" involves is "encoding code points 0x000000 through 0x00007F as a single octet equal to the code point, and not using those octets in the encoding of any other code point"; the encoding scheme can represent everything up to 0x7FFFFFFF, i.e. it only loses the uppermost 2,147,483,648 code points, and can still handle the lower 2,147,483,648 code points. That's a lot more than the Unicode limitation of 1,112,064 code points.

  2. Improvements? by BarbaraHudson · · Score: 2

    We heard you liked
    More and more stuff
    So we had to add
    More and more cruft

    Bloat is the name
    Lines of code is the game
    Bumping version numbers
    Gets us attention again

    Sure you don't need
    These improvements but we
    Need them for vendor
    Lock-in you see.

    You want something simple
    Like green eggs and ham
    Don't be a fool
    Just eat our spam.

    Burma Shave

    This post was NOT brought to you by "the crucial U1F32D character," which many of us have survived without until now. What a bunch of hype!

    --
    "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
    1. Re:Improvements? by BarbaraHudson · · Score: 2

      Redhat is the one pushing systemd. Since they employ the main developers of systemd, if you're a company that wants to run the latest and greatest, you'd better stick with Redhat as they are the ones who are really in charge, or switch to one of the *BSDs. 'Nuff said?

      --
      "Transparent" is a shit show that trades on every stereotype going. A man in drag is NOT a transsexual.
  3. Spamming of audit messages to syslog fixed? by Anonymous Coward · · Score: 2, Interesting

    Fedora 22 user rant here

    Is it (audit spamming syslog) fixed ? I have no use for the audit daemon on a home machine.

    And no I don't need someone to tell me to filter them out with some convoluted command line to read the fucking system log.

    'less /var/log/messages' should be usable, as should the output of dmesg (how the hell they fucked that up I'll never know).

    I just checked and wtf is dnf spamming the system log now too? Is this a new fuck-up ? (yum never did this). Oh I see the problem "systemd: Starting dnf makecache..." figures systemd would be involved.

    1. Re:Spamming of audit messages to syslog fixed? by See+Attached · · Score: 2, Insightful

      Did anyone else immediately Equate DNF to DId not Finish???

      --
      Time for a new Political party in the US (or two!) One is off the rails Other cant pony up a leader.
  4. And finally VNC support? by SurfMan · · Score: 3, Interesting

    But the real question is: can we finally, after all these years, run a Gnome 3 session over a VNC connection without getting the "Oh no! Something has gone wrong" error and the ridiculous workarounds for that?

  5. Re:Running with kde5 since the beta by Lirodon · · Score: 3, Interesting

    No, it's just that Fedora hates KDE, and this is pretty much intentional. It's a Gnome distro, first and foremost. One of Fedora's KDE co-maintainers actually stepped down

  6. Follow the bug in Bugzilla for audit logging by Sits · · Score: 2

    The Red Hat Bugzilla link you want is Audit events in /var/log/messages.

    (dnf-makecache.timer is basically a "systemd-style" cron job for periodically updating your DNF cache)