• 0 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: June 19th, 2023

help-circle
  • Damn, these rpm-ostree distroes are taking off. I mean tbf, having a “cloud native” approach (a two buzzword combo) with system images is kind of great for testing, and it shows people can now actually carve out some systems in a relatively effective manner. Good show!

    That is supposing it is rpm-ostree, because ostree can actually rebase to an entire different distribution. There’s people getting arch working as an ostree install, and eventually, we’ll have gone over to a new dawn, where you don’t need to reinstall, just rebase.

    Goddamn open source is awesome.





  • TL;Dr you’re a dog whistling fool.

    I challenge you to go live in Gaza and pretend you’re Palestinian…

    See how stupid that sounds? Though you’re probably so delusional, you think you’d be fine, running around safe and protected areas within Israel screaming "WHERE’S THE APARTHEID?!?!!’ Not only that, but your ignorance of geopolitics needs to be broken down as well.

    “basically every Muslim country”… oh, you mean the middle east? That place that keeps getting invaded and overthrown? Why did we invade Afghanistan… again and again? Thank you the three stooges of western geopolitics , the US, France and Britain - the tag team of degenerates in fancy suits. Why was the democratically elected government of Iran overthrown? Oh right, the only thing worse than liberalism, SOCIALISM. Let’s help install a a very socially conservative Ayatollah instead… also, let’s destroy Iraq and install yesmen - y’know, for oil. Surely that’s not a bad idea… it’s like Yosemiti Sam shooting and being pushed back over, and over, and over again, as western society takes another geo-political black eye.

    And you wonder why they go against western ideals? It’s that problem where sovereignty doesn’t mean shit the second you step over the border, and after DECADES of meddling and destroying economies, literally colonizing a place, the entire region becomes authoritarian nationalist, and you go “lol Muslims”?

    Bro, go back to school. Stop being retarded with your smooth brain. Learn what the word “precedent” means in a social historical context. Unless, y’know, you ignore it for a specific purpose…

    “Uh, but they are authoritarian nationalist based on religion, but not the authoritarian nationalism based on religion that I want”. I bet there is no LGBTQ persecution in Israel by nationalist, orthodox Jews… right… right? Or here in the west? No? “No, it’s the mozlems”.

    To conclude: either everyone is free, or no one is free. Any exception is some authoritarian mental gymnastics bullshit by smooth brained westerners who got skullfucked by instituonal parties - and then, and then having the balls to pretend they are fighting against authoritarianism…

    Stfu, bro. You can shove your ignorance, fear mongering, dehumanization and dog whistling straight up your hypocritical, delusional ass. We got healing to do, and you are against that movement - mostly because you won’t seek therapy instead of doing stupid hot takes online.


  • Unless they’re called Microsoft. In that case, they care a lot. Also, PreSonus Studio One is getting ported, DaVinci Resolve runs on Linux, Bitwig, Lightworks has run on Linux for a long while, and we’re not even including all the Electron wrappers out there.

    No joke though, vendors would have a bit more control - if they used Nix instead of Flatpaks or Snaps :P We could bring the NSIS installer and DRM on Linux in the worst way as well. But, still: DRM dees nuts.





  • Tl;Dr “I want my~ I want my~ I want my NixOS~”. Yes, I am that old. Shut up.

    I love the enthusiasm… but I must disagree :( unfortunately, much to my sheegrin bacuse I want to spite Linux commenter on this sub so badly because they are a bunch of brogrammers, but for me the year of the Linux desktop has to happen at the hands of device manufacturers. “Monopoly-by-default” is real, always has been, and never ever really left. Don’t take your eyes off Microsoft or Apple for one second - the bastards - because when you do, you fall into the vendor lock-in trap.

    I personally think the EU should publish a bespoke bootloader with a gallery of operating systems that can be fetched using PXE, with image signing and checking of course, sort of like the “browser choice” alternative for OS’s. It doesn’t need to be the main bootloader, but it has to be available - and most likely GRUB2… because GRUB2 is everywhere. It’s what boots MacOS on M* machines. It’s the one boot loader to rule them all. What I’m saying is we’re in the year of GRUB2.

    Anyways, outside my ideal there’s really nothing that will bring the “year of the Linux desktop” popularity wise, besides a large vendor relying on the actual Linux desktop stack - which is possible, but there’s probably a reason why Samsung bet on Enlightenment, and it’s not because it’s creator is so enlightened. MIT spelt in South Korean translates to MINE.

    One thing 2024 has also stood for is cleaning house. GNOME was caught breaking their own strict rules, KDE keeps ironing out the ancient from the Plasma desktop paradigm, though now KWin has better Wayland support than Mutter for some reason, even though one has had Wayland support for years (a real tortoise and the hare situation this), and people are obsessed with a display server that nobody develops for anymore. (XWayland is XWayland, not X11). So finally we’re in the year of Wayland. Good bye, screen tearing. Hello breaking with protocol and causing screen corruption. Oy vey.

    In regards to developers, developers, developers, developers, developers, developers, developers, developers, developers, developers, developers, developers, developers, and developers, then I look at the Rust stack, I look at the Zed stack, even the C# stack, or even a certain GUI framework with its own IDE built entirely using its own Emscripten SDK (can’t remember the name for the life of me). Here I see some new ways of doing the same thing and creating cross-platform solutions from the get-go, that might bring in new products and services on the Linux side.

    But we already have access to more private and public services in software form on Linux than ever before before, so maybe the year of the Linux desktop passed us by but as a lackluster metric and Linux as a desktop (or LaaD as I’d like to call it, because I’m a moron) really won’t be popularized until one of the major vendor completely screws the Pooch, and then someone brings a solution based on the Linux stack. Come on, Copilot+ and System76…

    Also, NixOS is finally trying to fix it’s issues, which is great, because Nix could realistically be a reproducible stack across systems, which can be tested by spitting out a single flake file. I see it as an addition to Flatpaks, Snaps and even AppImages. I want to petition Ableton to bring Live Linux, because I know in my heart of hearts that they’ve hired people with NixOS experience and that the Push 3 standalone needs some form of OS. But NixOS is a perfect example of why people are asking what happened to the year of the CoC’s? Maybe we can do a reboot.

    So in conclusion, I’m over here waiting for the year of NixOS, which will be a lackluster event where nobody is happy with, most likely celebrated by another institutional figure having to walk it off. See you in 10-15 years.


  • I love GNOME, but Gnome Software is hot garbage. If KDE gets their gtk/adwaita tweaks in place, I might recommend Discover instead.

    Also, arguably, by the most argumentative people, AppStream is also hot garbage, which is what was supposed to solve your problem regarding “too many package managers”.

    I personally would wish AppStream didn’t suck and that it was also aware of NPM and crate packages. They’ve sort of been forgotten or relegated “developer tools”… even though you can pull full applications and system libraries.

    How many “it’s 2025 already” problems do we have to encounter this year?


  • Good. No offence to him, as he is the architect behind nix, but nixos suffers from major governance issues, largely thanks to indecision, infighting and actively distilling conflict within the community.

    At the end of the day, that whole “benevolent dictator” schtick is just not sustainable.

    Also, it’s 2024 already. Finish the implementation of flakes. Either that, or strip it out. One or the other. Get off the pot or piss.




  • It’s a weird time to live in, but not confusing. It’s obvious to see that what you really want as a vendor is control over the operating system stack itself, and relying on Microsoft has become challenging.

    In essence what NVIDIA is doing is bringing it’s entire GPU driver stack open source side, so that entire industries say go on buying tons more hardware.

    Us Linux enthusiasts get to reap the benefit, what with entire open source movements bringing libraries to Linux side first that can turn GPU hardware into whatever tool you’d like. Projects like PyTorch and ffmpeg run as first class citizens on Linux.

    Windows still relies on either shared DotNet stack (which will make a monkey out of you - cough cough) or the nearly ancient MSYS2 build environment. Microsoft of course prefers you run all that software inside their Linux container system known as WSL - and there’s a reason for that.

    The Linux graphics stack is looking more “feature complete” by the month, bringing up the question of where you actually get the best hardware support. This is a good question to have.

    Now, if only the open source desktop movements could clean house, figure out funding and get their stacks in order, we might finally, for the umpteenth time, maybe see the year of the Linux desktop.

    I grow old with anticipation, but seeing what NVIDIA did in the before time versus what they do in the now puts a smirk on this haggered face.

    Onwards to the future.


  • Seeing that user Flatpaks are installed in the home folder, I see this as an interesting strategy. EXT4 still beats BTRFS in certain read/write benchmarks. My only problem being that you lose provisioning.

    I don’t see a lot of people talking about this here, but BTRFS subvolume provisioning is probably the best reason to use BTRFS - and BCacheFS - not just CoW or snapshotting.

    The old way, of having a set beginning and end of a partition, is like caveman technology to me now. Subvolumes are here to stay and I am happy about that.

    If I need to do a little distrohop now, even though I wouldn’t (rpm-ostree rebase go brrrr), all I’d do is delete an recreate the “@” subvolume (or the root subvolume) without touching another partition or subvolume. All storage space is shared between subvolumes, basically, removing that boundary distinction between them, so I get to keep the files, permissions and meta data in my “@home” and my “@var” subvolumes, even though I get rid of the old “@” to replace it with a new one.

    Therefore the idea of having storage that is reliant upon partitioning, ordering sectors one after another, having to defragment and keep strict separations between them is absolutely archaic to me. I’ll gladly take a slight performance hit just for the convenience of avoiding all that.



  • I think we have to step back once in a while to get a wider perspective.

    Both GNOME and Plasma are not just simply desktops. Oh no. They are entire stacks, complete with SDKs, for the user and desktop applications to use. They are orchestrated collections of libraries, services and apps, that together combine to make huge projects.

    All of this requires contributions, all of this requires developer time. And in this economy? Open source is taking a kick to the pants.

    You also got feature creep and tech debt galore, as well as needing to replace various bits and pieces when things become outdated, deprecated and unmaintainable.

    Let’s put it plainly though: there’s a reason GNOME is reorganising, and why it’s all about the money, dum-dum-didi-dum-dum. I think that it would be great if GNOME managed to restructure to facilitate more developer time, because the lofty goals they have set means having to put some elbow grease in it. The same goes for KDE.

    Yes, it’s the funding issue again. It’s all about prioritization. With the economy being what it is, money doesn’t stretch that far anymore either.

    With all this in mind, I think we should all show some appreciation for the good work of the folks who make GNOME and Plasma. We are given two great options, with each their approaches, that show us what true competition looks like, and they are really giving it their all - despite what some people may be saying.

    We should do better to remind ourselves this


  • taanegl@beehaw.orgtoLinux@lemmy.mlSo... how to fix this?
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    8 months ago

    Firstly, check the logs directly to get a more concise error that we can analyse. journalctl is the standard systemd logging client you can use in the terminal. By specifying the unit (units can be socket files, timers, services) you can get logs specifically for said unit.

    journalctl -u udisks2.service
    

    You can also specify binary, if said binary logs to journalctl, like so (if the binary path exists):

    journalctl /usr/lib/udisks2/udisksd
    

    You can also check kernel messages (dmesg) by using the -k flag, like so:

    journalctl -k
    

    You can utelize flags such as -e to scroll to the end of a journal, -f to follow a journal in realtime and utelize the -p flag to set priorities like error, crit, warning (-o error) and others to filter away common journal entries so you don’t have to scroll through every line in the log.

    Secondly, and this is gonna sound weird, but reboot into windows twice. The first time you boot windows run diskchk on the partition(s) in terminal/powershell/command as administrator. If it tells you it needs to do an offline scan, reboot and you’ll see an offline diskchk screen on boot before login. If not, reboot again into windows anyways, and then reboot into Linux.

    The reason is that NTFS has a weird failsafe flag that NTFS on Linux considers a no-go, and it’s usually set if the system crashes more than twice, but not always. If Linux NTFS drivers see the flag, it won’t mount as a precaution. The only way to reset the flag is to reboot in windows twice. Not once, not three times, but twice.

    This might be outdated info, but that was the fact some years ago. There might be a way to fix it with modern day Linux, but I don’t know, especially when I have no direct and informative errors to go by.

    journalctl is your friend :)