Fedora 29 Released (techrepublic.com) 31
ekimd writes: Fedora 29 is released today. Among the new features are the ability to allow parallel installation of packages such as Node.js. Fedora 29 also supports ZRAM (formerly called compcache) for ARMv7 and v8. In addition to the more efficient use of RAM, it also increases the lifespan of microSD cards on the Raspberry Pi as well as other SBCs.
"Additionally, UEFI for ARMv7 is now supported in Fedora 29, which also benefits Raspberry Pi users," reports TechRepublic. "Fedora already supported UEFI on 64-bit ARM devices."
"Additionally, UEFI for ARMv7 is now supported in Fedora 29, which also benefits Raspberry Pi users," reports TechRepublic. "Fedora already supported UEFI on 64-bit ARM devices."
Re: Huh? (Score:1)
NP-complete problem (Score:5, Interesting)
Re: (Score:1)
There's a simple polynomial solution to this problem, and it doesn't involve solving a SAT problem.
(Hint: Find an offending library in linear time, and then either (a) factor out the parts everyone seems to want, or (b) tell one of the packages they can't use it if they want to be in the official distro.)
Re: (Score:2)
raspberry pi, really? (Score:3)
who would use a kitchen sink distro on the raspberry pi?
Re:raspberry pi, really? (Score:5, Interesting)
I use Fedora 28 on a raspberry pi for a local DNS. I want something that just runs without user intervention for months. I tried raspbian and raspBSD but neither of them seem to be ready for primetime. There was always some issue popping up whether it be updates not working automatically, or the network disconnecting for no known reason. Fedora just flawlessly does its thing in the background.
Re: (Score:1)
Ditto, I use Fedora 28 on a RPi3 Model B for monitoring my solar array. No problems, minimal IO, minimal idle usage.
I have however, given up on using microsd cards. Even with the official power supply and raspibian the RPi would usually corrupt the ext4 filesystem every three weeks or so.
No problems since switching to a USB drive. That was a general common problem I didn't find while researching.
Re: (Score:2)
Try Slackware ARM.
I can usually ignore it for most of a year; until some remote security vuln in bind or something pops up.
Great Move before IBM messes things up (Score:1)
Re: Great Move before IBM messes things up (Score:2)
Considering that IBM puts the E in Enterprise I doubt that they will
Re: (Score:2)
Software isn't really a forked until it starts going in it's own direction like how LibreOffice is a fork of OpenOffice, MariaDB is a fork of mysql and OpenIndiana is fork of OpenSolaris
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Discarding python 2 (Score:3)
Fedora 29 is, effectively, discarding Python 2 in favor of Python 3. This means that the leading edge packages from Fedora will no longer include options to compile for the older, standard Python 2 built into every RHEL or CentOS release without extensive manual revision.
Re: (Score:3)
Fedora 29 is, effectively, discarding Python 2 in favor of Python 3. This means that the leading edge packages from Fedora will no longer include options to compile for the older, standard Python 2 built into every RHEL or CentOS release without extensive manual revision.
Someone has to do it and a decade after release it's about time. This will trickle back to Centos/RHEL eventually but until then the easy thing is if you want to run on Centos/RHEL then build on Centos/RHEL
Re: (Score:2)
I'm afraid that this is not something that can "trickle back". It requires complete migration of critical system components like RPM, which I'd not expect to see done with Python 3 before RHEL 8. It also requires complex revision of the source packages from Fedora 29 or later. Those packages had tools to compile with and deploy for Python 2, and those hooks have been deliberately excluded.
I'm sad to say that I've not seen any hint of a beta or tentative release date for RHEL 8. There have now been _10_ Fedo