indias growth is so important, it’s such a dense country so growth will be rapidly exponential unlike 95℅ of other countries. it’s the perfect mixing pot of technologically literate, dense, money conscious, and distrustful of western influence for linux to thrive in. once india is dominated by linux, it will expand outwards so fast.
Seriously, I’m impressed on just how much influence Linux has in India, not only as an OS, but as a community. I’m in charge of some of the Fedora social media accounts and it really impressed me at first how India is consistently one the top 3 countries our followers are from in all of them.
I’m going to start this article off by saying that you don’t have to be born in the boomer generation to be a boomer. You can be a boomer by acting like one. Hate new stuff? boomer. Run a desktop from the naughties? Boomer
Why even bother having words at all if we’re going to redefine them for clickbait?
What clickbait? Linux boomers is two words and it is common to call people a boomer if they act like one. Linux boomer describes a specific type of boomer.
after more than 25 years using linux I could not care less about those dramas, when my distro will drop xorg I’ll switch and that’s it. I’ve got way too much stuff to implement myself already, there is no time for that. I mean, I’ve even embraced systemd…
sorry, my rhetorical question was obviously intended as why I should bother. I don’t see any value in stopping you doing whatever you think is better for you, in fact it is exactly what annoys me the most :)
Well Xorg is pretty much unmaintained and is on its death bed. Modern hardware and software are slowly favoring Wayland due to it being much simpler by design.
To provide features that Xorg can't.
If you don't need features like fractional scaling, VRR, touchscreen gestures, etc. you won't notice a difference.
People who do use those, will. Because for them, those features would be missing or not complete on Xorg.
mmmh, I bet I will not notice any difference also if I don’t do shit and keep whatever is working until the day I’ll have to switch because my distro drops the packages 🤷🏼
I wish that was my experience, but Nvidia drivers on KDE Wayland have had a lot of oddities and issues that have caused me to go back to Xorg every time I’ve tried (12 times and counting). Wayland is a good move in the right direction, and I look forward to it, but it’s still being implemented.
Oh absolutely, this isn’t to say “Wayland bad”, it’s just to say that a large number of people may not have a smooth transition, so it’s hard to say “just do it”
It was a birthday gift from my wife, and lets not alienate people who don’t know computer hardware very well and pick up something from Best Buy. I agree that Nvidia sucks, and many of the issues are indeed their fault, but we also can’t neglect the fact that they own the vast majority of the market.
I’ve been a Linux user since the 90s, and nvidia has been a problem as long as I can remember. The wayland issues are just a new chapter in a long saga. ATI used to be the same, but they came around after having been bought by AMD.
If you’re already planning to use Linux on something a quick search will directly tell you that nvidia is a problem. If you got the hardware before nvidia that sucks - but again, it’s nvidias fault.
I think we absolutely should neglect nvidias market share, and just fully drop support for nvidia cards - either they’ll get pressured by angry users to no longer behave like dicks, or they keep doing it, and people will only make the mistake of buying nvidia once (or not use Linux) - either way, we’ll have gotten rid of a massive headache.
Running AMD/AMD right now for cpu/gfx, and I’m happy with my gaming laptop (and it’s price point).
Linux support and general support of open source was amajor factor in my decision. Intel is also really good on the CPU front, but I want to support AMD for its ooen source and speedy graphics offerings.
Also quite important to make sure we don’t have just a single strong x86 vendor - even though currently looking at price/performance you’d almost always go for AMD.
The time before ryzen was horrible - a 4-core-CPU was considered high end, and if you needed something more you needed to go for ridiculously overpriced Xeons. Similar for servers - you could get slightly higher core counts there, but when going for more than 8 cores it’d also get expensive very quickly.
Now we’re talking about 16 cores in high end notebook, and 64 cores in still reasonably priced pro workstations.
Eventually people will have to get new hardware. That’s the moment to avoid nVidia, that’s how simple this can be.
Also, the problem is nVidia giving shitty Wayland support, not Wayland providing no nVidia support. It’s nVidia who has to write the drivers since they themselves opted to keep their implementation details a secret. There’s nothing the Wayland people can do except plea, beg and shame. If nVidia then decide not to care, then I say fuck them.
Not supporting Nvidia cards will make Wayland unusable for at least half the Linux desktop users, probably more. Stats I recall range from 50-75%.
“Just buy non-Nvidia” is not, I repeat, a simple option. Lots of people stick with old GPU models because the price/performance ratio has gone out the window and they cannot afford to drop hundreds or thousands on one. Many others have Nvidia in their laptops.
There’s nothing preventing Wayland from working with Nvidia except the political insistence that it be open sourced. Which Nvidia is not interested in, never was, and never will be. And it’s a red herring to begin with.
TLDR either Wayland bends their stance on open source or their adoption will be severely limited.
Nvidia will feel enough pressure (likely from the ML / HPC space?) to provide open kernelspace support that they’ll actually make that happen.
Which… Has already happened.
Nvidia took a lot of the kernelspace logic that used to be in their proprietary driver, re-architected their GPUs to move that logic into a firmware blob (GSP).
And last year they released a completely Free driver that intefaces with GSP.
This allowed Nouveau developers to finally access critical features like power management (which were basically behind a wall of DRM, as Nvidia used legal and technical measures to lock Nouveau out of their firmware).
Now Nouveau has a new shader compiler, Vulcan support is growing rapidly, and people like me will soon prefer the Mesa stack for Nvidia over Nvidia’s own drivers.
And you can bet that Nouveau will work great with all of the Wayland compositors.
This is really the exact wrong point in history to be making the argument you’re trying to make 🤣.
Wow you got that backwards. They don’t do any of that for the sake of Nouveau or Vulkan or Wayland or whatever. They don’t care what people use their open scraps for.
They open up the minimum they can get away with because it’s ultimately meaningless — their proprietary stuff is still hidden away and it’s not like you can use the parts they open with anything else.
This, btw, applies to AMD and Intel too. The only choice you get with proprietary hardware that you have to use (like GPUs) is whose dick you want to suck. They’re not your friend and they won’t let community pressure then into decisions.
Why not use fwupd? (link is the Arch wiki but should be relevant for any distro). I've been using fwupd to keep my Dell XPS15 BIOS updated for the last few years, with no problems at all.
Doesn’t work on all dell laptops. Doesn’t on my inspiron. But dell bios has a “update bios from flash” option. So copy the .exe file into a fat32 USB and flash it there.lol. Done. I’ve done it a million times.
in Germany there’s a (somewhat) new law that makes it mandatory for all websites to ask you if it can store cookies on your harddrive. since then every time you visit a new page or on a new installation you have to click through three pop-ups, it’s sooooo annoying to navigate the internet since then. so yeah this feature is more then welcome here ^^
And the thing is afaik in the EU websites cant save anything nonessential unless you actively opt-in. In other countries its opt-out. So blocking cookie banners while not strictly cleaning or blocking may be harmful for privacy
As I understand it, the blocker has website-specific rules to automatically click the right buttons. For the first release, they've probably primarily tested those with German websites. I assume that if it works well there and they've ironed out most bugs, we can see it roll out more widely.
I think (and hope) tha the logical conclusion of the DNT lawsuit v LinkedIn will be that DNT will be deemed necessary and sufficient, and that this setting will replace all the cookie banners. But even if that comes to pass it will be years before all the banners will be gone.
This is a selling point I don’t often see people discussing but it has killed my need to swap distros… Possibly forever. I’ve been using it for a year now and have such a clean well organised config file. Version controlled, broken up into modules, with separate configurations for desktop laptop and server. Unlike any other distro, at any moment I can just hard reset to what that config describes. If I swap DEs, or python versions, or whatever else, the system no longer slowly builds up clutter and random arcane bugs and bloat. It feels like today my system is better, newer, and cleaner than when I started with it. And at any moment I can install my exact system down to every little detail on a new device. Nix is legendary for long term system maintenance.
That’s what I love about it, among all the other good things everyone talks about.
Even better it’s the first time I’ve actually felt the desire to learn to package apps that aren’t available, because the nix language makes it so easy.
Of course there is definitely a learning curve, compared to other distros. Going from… at the time arch/fedora to nix felt like just as big a change as going from Windows to Linux in the first place, such a big shift in how I did everything. But definitely worth it.
Just found this too, through the rust post some days ago…but its quite obvious that from a usability context that btop is easier to use. With bottom you have to memorize all hotkeys wheres btop is showing them right in the interface.
Yea. I was using bottom until I saw this and did a quick side-by-side comparison (nix-shell -p btop, I use NixOS BTW). btop’s UI is just so much better.
Mint has very nice tooling but its a weird Ubuntu derivate. One day a specific software doesnt install, or you have an XOrg problem that will never be fixed, or standard updates simply break something, and then…
Mint is nice and easy to get going, but its outdated a lot, and uses a Distro model that I dont like to install on random laptops that are never updated.
So you’re a power user? Case in point, you’d be better for Fedora.
Also my second distro was mint, after 3+ years of the old hdd’s non-use, I pulled it out last year when my install of some OS broke, updated it to zero issues (I was curious), used the software for a bit, all was good.
3 years without an update to zero issues.
Haven’t seen any issue with Mint updates yet like I’ve fought in Fedora
You could boot on an USB, mount the filesystem and change the permissions. But if the dude changed a whole lot of permissions, reinstalling might be the smart thing to do…
There’s got to be other tools though that could change the file permissions on chmod, right? Though I suppose you’d need permission to use them and/or download them.
You can dump the permissions from the working system and restore them. Quite useful when working with archives that don’t support those attributes or when you run random stuff from the web 😁
Yeah, a very unfortunate one: probably, the most painful to recover from. I’d just reinstall, honesty 😅 At least with mine I could simply add the necessary stuff from chroot or pacstrap and not spend a metric ton of time tracking all the files with incorrect permissions
@jordanlund@fl42v I think this one could be recoverable if they had a terminal still active by using the dynamic loader to call chmod — or by booting from a liveCD and chmodding from there.
That'd likely get you to a 'working' state quickly, but it'd take forever to get back to a 'sane' state with correct permissions on everything.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.