8 ms·
Fedora 33
- soulofmischief 6y agoKudos, guys! Time to wait three months for all the kinks to be worked out, though.
- ape4 6y agoIts working for me
- deleted 6y ago[deleted]
- gigatexal 6y agoFedora QA has gotten a ton better in the last years. I would use it as my daily driver if work would allow it, we're an all Ubuntu shop (at least for Linux devices).
- soulofmischief 6y agoI run a fully virtualized configuration and I frequently have encountered issues related to the virt stack during the initial months of new version cuts ever since switching to a virt configuration in 2016. There has also been a ton of improvement, too. So kudos to Fedora, and kudos to everyone out there maintaining those libraries!
- gigatexal 6y agoHmm, bummer then. Best to wait a bit before upgrading.
- bproven 6y agoIt is good to wait a few weeks at least but I have been running fedora the last few years and the last 2-3 fedora releases have been stellar. I have upgraded within a few days of release and had zero issues (with fedora 33 I upgraded last eve :) ). It has gotten much much better... Congrats to Fedora team! Thinkpad carbon X1 6th gen
- fanatic2pope 6y agoThis appears to be a solid release, just as stable as 32 for me.
- alphadevx 6y agoAs a long time nano user, this makes me happy! "To make the default Fedora experience better, we’ve set nano as the default editor. nano is a friendly editor for new users. Those of you who want the power of editors like vi can, of course, set your own default." I can only imagine the mailing list discussion around that one :-) Looking forward to upgrading as Fedora remains my daily driver, so thank you at all involved.
- cesarb 6y agoAs someone who used nano in the late 90s, it makes me nervous. I recall that you had to be careful to always use "nano -w" otherwise it would silently corrupt long lines, breaking configuration files which use one entry per line (like crontabs). Since then, I have always removed nano from every system I touch, to prevent accidents.
- pabs3 6y ago-w/--nowrap is now the default and I think it has been for a long time.
- Sunspark 6y agoNano is the first thing I install on a system. It is the closest thing you can get to Pico from the Pine email client from back then, and it's great because it's simple and gets the job done. No muss, no fuss.
- stinkytaco 6y ago> I can only imagine the mailing list discussion around that one :-) Here it is [1]. This was actually discussed on HN a few months ago as well [2]. I've used Linux for 20 years and still use nano for all quick config file edits. It's part of my setup so I didn't even realize that it wasn't set at all by default. [1]: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/U5C4CC2O44E7Q4MVTT772NP667HTP25S/#KHBUFJJIZA2V5TEIOKVDV6KXQ3N7E7VE https://lists.fedoraproject.org/archives/list/devel@lists.fe... [2]: https://news.ycombinator.com/item?id=23818199 https://news.ycombinator.com/item?id=23818199
- 6y ago
- Spivak 6y agoThis crowd will probably be more interested in https://fedoraproject.org/wiki/Releases/33/ChangeSet https://fedoraproject.org/wiki/Releases/33/ChangeSet which has all the good stuff. * btrfs is the default desktop fs * Java 11 is the default. * ifcfg scripts won’t work by default anymore in favor of NM keyfiles * systemd-resolved is used by default * earlyoom used by default on desktops * disabled automatic Python bytecompilation * xorg-utils is retired
- kapilvt 6y agoit seems weird that you can't easily find the kernel version on any of these release/change notes
- cesarb 6y agoFor Fedora, the kernel version is always "the latest with a lag of a couple of weeks". All the currently supported Fedora releases update to the same kernel version at the same time; currently, both Fedora 32 and Fedora 33 (and Fedora 31 if you're still using it) are using kernel 5.8, and when Fedora 33 updates to kernel 5.9, Fedora 32 will update to kernel 5.9 too.
- alex_duf 6y agoThis is exciting! Although I'm worried about BTRFS being their new default. I've had horrendous experiences with it and I wouldn't recommend it! I hope it has improved and requires to be less hands-on otherwise it's a massive turn-off
- Nux 6y agoBTRFS is the one change that makes me most excited. It has improved a lot, I am sorry they default to it only for workstations and not for servers, too. Hope to see it back in RHEL!
- curt15 6y agoBtrfs is notoriously ill-adapted to database workloads. Although interestingly, some people seem to run Postgres on ZFS just fine, even without disabling copy-on-write like one is advised to do for btrfs.
- ravi-delia 6y agoA lot of it comes down to the default settings. ZFS is just well tuned for a workload like that, and I believe automatically detects some features of the disk it's on. BTRFS by comparison is worse off by default, but if you tune it right it runs pretty much the same.
- Nux 6y agoIndeed, even OpenSuse disables checksumming etc on /var.
- xorcist 6y agoIt certainly has improved. Don't worry though, you can still select another filesystem at install time.
- skykooler 6y agoI've always thought Jolla's biggest mistake with Sailfish OS was using BTRFS as the default on a mobile operating system. (They later switched back to more conventional file systems.)
- kawsper 6y agoFor anyone using Docker and thinking of trying out Fedora, here is a warning: Fedora uses cgroupsv2 to push things forward, but no Docker release supports it yet, it's in master[0], but there are no release in sight as there is no ETA. [0] https://github.com/moby/moby/pull/40174 https://github.com/moby/moby/pull/40174
- danjac 6y agoWhat's the reason for no release/ETA?
- amarshall 6y agoAs an alternative, Podman works well, but some features may be missing. It does, however, allow running containers rootless and remove the need for a daemon. https://podman.io https://podman.io
- TrueDuality 6y agoI've made the switch entirely over to podman and haven't actually found any features to be missing besides docker-compose support, but their k8s style pods more or less have solved that for me. There is only one 'gotcha' that I've hit, when building images specifically for AWS's ECR or Docker Hub, you need to add the flag `--format=docker` to your build step. Quay and a few others don't have this issue.
- amarshall 6y agoThere is podman-compose, but it is most definitely missing features vs. docker-compose (as in whole subcommands are absent). I cannot remember what (if any) missing podman features remain, but I do run into occasional bugs and regressions with certain functionality. Curious you mention needing `--format=docker`; I’ve pushed images to Docker Hub without doing that without issue. https://github.com/containers/podman-compose https://github.com/containers/podman-compose
- TrueDuality 6y ago
- mwcampbell 6y agoInteresting to read about the new ARM64 boards. Does anyone have experience using one of these as a desktop computer?
- officeplant 6y agoI've lived off of each main release of the Pi and a few other SBCs. I've stuck to running 32bit releases for the time being because of bad experiences with 64bit issues. Things are much more livable currently with SBCs largely adopting faster USB, PCIE or EMMC storage. Even as an ARM enthusiast we are still years away from the average person being happy with the experience so tailor your expectations accordingly.
- bproven 6y agoCongrats Fedora team! I upgraded last eve on a thinkpad carbon x1 6th gen. Took 15 min and was seemless! My 4th upgrade on this laptop.
- dignan 6y agoI have the same laptop and this is also my fourth upgrade on it. Really excellent. It is impressive how much the upgrade process has improved over the years. Years ago you could either risk updating your repo files and yum updating, or just do a full reinstall. Then they built fedup which was a command line tool that made it easy, but still required several different commands. Now it’s driven through the GUI and a better experience than macOS upgrades in my opinion.
- m4rtink 6y agoFor the record you can still upgrade from the command line with the DNF system upgrade plugin: https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-upgrade/ https://docs.fedoraproject.org/en-US/quick-docs/dnf-system-u... Once started the upgrade process is preatty much the same as the GUI update - download all needed packages, check if there are no conflicts with what is already installed, then reboot to minimalistic systemd target and run the update here. Doing it like this makes sure that packaging conflicts, network connectivity or unrelated processes running on the machine can break your system.
- freedomben 6y agoBig concern I've seen is around btrfs being the default. I was concerned too, especially with the old versions losing data, but I've heard that a ton of work has gone into btrfs and it's maturing/stabilizing nicely. Has anybody used a recent (last couple of years at the most) btrfs as their main filesystem who can comment on how it has been?
- sebiw 6y agoI am running Btrfs on about a dozen machines (solid state and spinning disks). All of them are servers and run "business-critical" stuff. No issues during the last 2 years, everything flawless. The ability to scrub your data and have strong data integrity guarantees is just one of the benefits of Btrfs. I'm also using transparent compression (GZIP and ZSTD) and even RAID1 (disk replacement procedure worked flawless last time I had to use it). For workloads such as MariaDB (heavily updated-in-place files) you may want to go ahead and disable CoW features, though. This leaves you without data checksumming (InnoDB uses it's own checksumming - not losing much there) but you still get a lot of the other great Btrfs features.
- jbrnh 6y agoI used to run a couple of hundred servers and workstations with SLES and openSUSE with btrfs for /. Just SUSE's vanilla supported setup, and user data on smb/nfs filers. I tended to forget that btrfs was even involved. I can't remember a single time btrfs gave us any trouble. But snapper snapshots saved a customers ass on one or two occasions.. That was several yeas ago. I also imagine that btrfs has only improved since then.
- da-x 6y ago"... And no longer use swap partitions by default." [1] Finally! I've installed a 256GB RAM desktop recently, and swap is so 90's... [1] https://fedoraproject.org/wiki/Releases/33/ChangeSet https://fedoraproject.org/wiki/Releases/33/ChangeSet