Slashdot Mirror
Fedora 21 Released
linuxscreenshot writes: The Fedora Project has announced the release of Fedora 21. "As part of the Fedora.next initiative, Fedora 21 comes in three flavors: Cloud, Server, and Workstation. Cloud is now a top-level deliverable for Fedora 21, and includes images for use in private cloud environments like OpenStack, as well as AMIs for use on Amazon, and a new "Atomic" image streamlined for running Docker containers. The Fedora Server flavor is a common base platform that is meant to run featured application stacks, which are produced, tested, and distributed by the Server Working Group. The Fedora Workstation is a new take on desktop development from the Fedora community. Our goal is to pick the best components, and integrate and polish them. This work results in a more polished and targeted system than you've previously seen from the Fedora desktop." Here are screenshots for Fedora 21: GNOME, KDE, Xfce, LXDE, and MATE.
I got it installed on my laptop a few hours ago, and so far no dramas. Nice work everyone.
"If it has systemd it can get right back into custody." It does http://docs.fedoraproject.org/...
http://chimpbox.us
High traffic due to F21 release: http://status.fedoraproject.org/
Fedora 21 Public Active Mirrors: http://mirrors.fedoraproject.org/publiclist/Fedora/21/
It's had it since Fedora 15.
Umm...a lot of us who did not like SystemD moved to BSD already. You're still whining at the Linux side?
Yup, that's where I'm going. Building a database server and it's going on FreeBSD. I was a loyal Debian user up until this fiasco.
The world's burning. Moped Jesus spotted on I50. Details at 11.
A list of the torrents for F21: http://torrents.fedoraproject....
It does, and I like it so far. It's been in Fedora for a while now.
Funny people even ask about it. A lot of posters talk like systemd is a brand new scary thing, when it fact it's been in Fedora for a long time. Two and a half years, if I recall correctly.
Funny people even ask about it. A lot of posters talk like systemd is a brand new scary thing, when it fact it's been in Fedora for a long time. Two and a half years, if I recall correctly.
Actually, it's been three and a half years. Fedora 15 was the first Fedora with systemd and that was released in May, 2011.
It's readily apparent you haven't even used Fedora in years. So why bother commenting on it? Systemd has been in Fedora for over two and a half years. You're a little late to the whining party. I highly doubt you've even used PulseAudio before. PulseAudio has pretty much just worked for several years now (yes it was a disruptive change at the time) and I for one am extremely glad to have it. It makes audio in Linux not suck. Don't know what world you live in, but it appears to be stuck a few years ago when there actually were problems. Occasionally I have a glitch of some kind, but I also had problems with straight ALSA too. Having multiple devices and multiples streams is an awesome feature that brings Linux a little bit more feature parity with Windows. Note that PulseAudio and Jack serve different purposes. Use whichever one supports your needs at that moment. PA happily gets out of Jack's way when you need to do some real-time audio processing.
I sound like a broken record, but at least for enterprise distros like RHEL, standard syslogs are pretty much required (possibly under certain legal frameworks some enterprises operate under). Therefor RHEL 7 has rsyslog and it works fine. You can also enable in Fedora if you want. Using rsyslog as a long-term audit-able log, and then using journald as a short-term, highly-detailed debugging log is a good compromise, IMO. The level of detail journald can capture is very nice when you need it. Not sure where Fedora wants to go with this issue ultimately. We'll have to see.
The server/workstation/cloud flavor thing is lame especially given you can't ever switch. Why can't we just pick software we want and be done with it?
The ultra-modern ultra-spartan mobile meme website sucks. Impossible to find anything without hitting from goggle. You declutter and hide everything predictable result is nobody can find anything.
Upgrade from F20 added a firewall daemon that fucked up my iptables configuration.
Quick check using nmap shows something new listening on port 9090 some "cockpit" management BS. This is really what I want in my life is a management web server.. right up there on my Christmas wish list next to a Supermicro IPMI module.
Upgrade was "stuck" at the end with a message saying writing logs and then we'll reboot.. this is just below a cool ascii hotdog man mascot... This writing logs thing appears to have been quite busy writing a copy of every system log entry since dawn of civilization to a new file labeled /var/log/upgrade.log ... after about an hour and 400mb log file.. I finally said F this and rebooted.
Hey I can't complain too much upgrade actually worked and it actually booted. The only reason I upgraded is because if I don't then updates stop working after about a year... I really need to bite the bullet one day and switch to a distribution that does not worship at the church of bleeding edge.
Anymore it is akin to improving design of electrical sockets... sure you might make them "better" in some way but dealing with associated change is a net negative value prop considering what the system is used for.
> "While it's not impossible for journald'd logs to get corrupted, it's no more likely than most other files in the filesystem."
*cough* BULLSHIT! *cough*
- Laptop failure to resume from suspend = corrupted logs
- Power loss or hard off on systems = corrupted logs
- Too long a log retention = corrupted logs
From an amazon cloud server running RHEL7 last couple of weeks: /var/log/journal/2dd5724e1e1542fc9a4aa75nov26cc150/system@f0282a3cd24344648a0bbe3a801ead66-000000000001b5d4-0004cfd1dbb89d83.journal:191117416 (of 233118464, 82%).
File corruption detected at
journalctl absolutely needs to be improved to handle corrupt logs better... maybe something to repair them instead of switching to "clean" them?
FreeBSD 9.0+ supports GPT and FreeBSD 10.1 supports UEFI now.
Installed since Alpha, using full time since Beta. No major issues - just lxdm user switch doesn't work. Hope it is fixed in final release.
Switched to lightdm, so not checked lxdm issue yet.
Bingo Dictionary - Pragmatist, n. A myopic idealist.
Once its installed and running it's fine though.
SystemD has a "journal" that is sensitive to unexpected shutdowns. The purpose of a journal is to protect from corruption. You'd think they would use a data structure that is safe from unexpected interruptions.
Yep and thats why it's irresponsively for any server admin to not pipe journald output straigt into rsyslogd, and thats how it is with all of the "systemd" selling points.
Journald was introduces as a hack to workaround the rare edge case where systemd needs to write a log entry about a syslogd crash and sort of grew into the one true log system with 1/10 of the features and none of the reliance of more modern syslog deamons.
It's not that systemd is bad pr see it that is being sold by morons to morons as a cure for problems that either dont exist or is not fixed by systemd. Hopefully nobody outside of redhat decide to go all in and replace all of the old scaffolding that systemd pretend to make obsolete need but in practice dont replace by anything that works better.
FreeBSD is moving to launchd, maybe you should try plan 9.