For every major Fedora update I’ll try to perform the upgrade from the Gnome Software app just to see if it works, and every time it breaks and I fall back to good ol’ dnf system-upgrade. This is the first time upgrading from Software worked for me, and it was fast too. Nice to see all the Software improvements finally paying off.
Seems like you’re annoyed that I pointed out that what you were saying was irrelevant? And so you reply with more irrelevant crap (on a very nerdy, not-fun-at-parties internet forum for Linux discussion)? Let me know if I got that wrong.
If you’re doing it for the memes then you don’t really need to worry about malware. Your machine is probably too old for anything that’s still floating out there to even work on it.
Many people browse 4-5 pages a day, see a few emails, print a few pdfs, and a core2duo, or x4, for 40#/$/Eu a box run flawlessly with linux and xfce/lxde for example.
Even video-conferencing works fine.
Driver code is still there, you can add it back if you want, same with ide drivers and such, support was removed but code still exists, just add it and compile your own kernel, there are alot of tutorials in internet about it
The drivers were removed in 6.3. Debian 12 is still running on 6.1. Debian 12 just came out and still has many years of support ahead of it (at least 5). You can get plenty of use out of these cards before they stop working.
Someone needs to maintain them for them to keep working. Nobody else is willing to do that anymore, but you can still volunteer as a maintainer. If you don’t, it’s as much your fault as anyone elses.
Now I understand why some people in the comments from other platform said “Fedora is the new Ubuntu”; in popular perspective today! Loud applause to the Fedora Dev team! Respect.
I haven’t used it yet personally, but I would bet as soon as Debian/Ubuntu LTS/CentOS/openSuse/other stable Linux distros get kernels new enough to it will be not just a btrfs killer, but a ZFS killer too.
The tiered write and read layers and SMR support put ZFS caching to shame.
Nobody uses SMR for live data anyway unless it’s in very particular circumstances.
Bcachefs is still at least a couple of years away from serious use. But sure, if it’s available and you have a good backup strategy you can use it today.
As for “years away” I agree. As my first post said people should wait till you can use bcachefs in the stable distros. Debian isn’t getting kernel 6.7 any time soon 😆. So years away is right in any case.
I think bcachefs addresses the reason why people don’t use SMR HDDs. (Aka changes resulting in cascading writes)
You could have a data pool with the following tiers.
Tier 1: SSDs
Tier 2: HDDs
Tier 3: SMR HDDs
With bcachefs you would only ever write to your tier 1 storage. In the background, as able, bcachefs would offload the data from the faster lower tiers to the slower higher tiers based on frequency of data access.
You would only ever read from the SMR HDDs and would never write to them. They act as a sort of async backing to your data.
Personally I would love a data pool with a few SSDs, backed by a few HDDs, backed by many SMR HDDs. You would save so much money just with good architecting.
Bcachefs should be a ZFS killer. All the features of ZFS with storage tiers being a superior version of ZFS’s L2arc with none of the DKIM kernel license incompatibility nonsense.
Damn, I didn’t think to include SMR drives when it comes to bcachefs. Your whole comment made me appreciate the whole concept under a whole new light actually, thanks!
It’s super impressive to see Wayland having its big breakthrough moment. I remember reading about Wayland 10 years ago and worrying it was going to end up as a dead project.
Until my distro forces wayland on me I’ll stick with xorg+XFCE. I’ve played with sway and hyprland but I need my application choices to actually work well. (no I’m not going to list them).
As for the cube desktop in the image: We had this with compiz and learnt then that this is pointless.
There’s a big difference between Working on vs is working. They’re Working on a full port, other than that you have preliminary access that’s not intended for casual users; only developers, tinkers/enthusiast & testers.
This design document is intended for Xfce developers to begin brainstorming ideas for future development. This is a work in progress and does not imply any future implementation commitments.
No blame on the XFCE devs because they’re trying to get a lot done with few people, but XFCE just managed to transition to GTK3, I wouldn’t hold my breath for comprehensive Wayland support any time soon.
They’ve made great strides towards Wayland support, considering that the vast majority of the work is being done by 1 guy.
It’s not just a lack of devs that’s contributing to slow development time either, it’s also the fact their goal is to port every single component to native Wayland without relying on Xwayland at all; which is obviously going to take way longer than just porting the essentials and saying “fuck it, use Xwayland”.
Yeah, I mean if you want to get picky, the actual i386 processor family hasn’t been supported by the Linux kernel since 2012, and was dropped by Debian in 2007.
Most people were generally not particularly affected by that, seeing as the last i386 chip was released in (I think) 1989!
Debian’s choice to refer to the whole x86-32 line as i386 has always been a weird historical quirk.
phoronix.com
Top