[-] alt@lemmy.ml 1 points 1 year ago
[-] alt@lemmy.ml 1 points 1 year ago

I don't own any devices with an Nvidia GPU. Therefore, I can't share my own experiences but only the ones from the community. If my memory serves me right, it should work. However, as usual, expect some strange behavior at times. Thankfully, getting back to a working system shouldn't cause you any troubles on Jovian-NixOS. Nonetheless, it's something to keep in mind.

[-] alt@lemmy.ml 1 points 1 year ago

Ow wow, that's a lot! Unsure to what degree you've used them; but if you feel confident talking about (at least some of) them, would you be so kind to offer us a rundown of what you liked and didn't like? Thanks in advance!

[-] alt@lemmy.ml 1 points 1 year ago* (last edited 1 year ago)

In case you're bored enough to read my ramblings and/or interested in what I understood and how, then consider reading the spoiler below.

spoiler


Fam, you're all over the place.

Because you did an awful job at pointing at the supposed contradiction, I'll have to analyze your excuse of an elaboration so that it somehow starts to make sense if at all:

A contradiction consists of N statements that logically contradict with each other; for the sake of making it more precise we'll refer to these statements as P, Q, R, S etc. After we've established this, we can move on to find what these alleged statements are from your comments. My best take would be:

(Supposed) Contradicting Statements:

  • P: systemd is the only init that's beyond a particular level of excellence and/or feature set.^[1]^
  • Q: Some combinations of distro + DE are cumbersome and unwieldy at best if systemd is not used.^[2]^

Perhaps some other related statements that are either implied or a given/fact:

  • R: Kicksecure uses systemd as its init.
  • S: Modern distros use an init.
  • T: Default init is chosen based on preference^[3]^.
  • U: Kicksecure has to use systemd because P despite not being in favor of some aspects of its design.

Please feel free to notify me if I missed the mark!

Don't you think that P and Q are actually complementary to one other?


No, not at all.

The crux might be here. But I'm not sure where exactly you might have tripped over. Was it because I said "opponents" instead of "(some) opponents"? Was it because I said "out of necessity", while elsewhere I said "don’t allow any differentiation in init or make it very cumbersome and unwieldy at best", but in this case they aren't contradictory statements. Was it the fact that Devuan exists? But, this assumes that any of the inits found on Devuan are somehow as mature and feature-rich as systemd. Which, unfortunately, is simply not the case. (I'm hopeful that dinit and s6 might reach maturity soon, though.)

So trying to use Kicksecure without systemd would be very cumbersome and unwieldy at best.

Exactly, that was my point.

Perhaps Madaidan should’ve used Devuan as a starting point instead.

It's a team effort, I don't even know if he started working on Kicksecure from its inception^[4]^. They might also simply be victims of the sunk-cost fallacy. Furthermore, I wouldn't be surprised if -to them- systemd's pros simply outweigh its cons. Which, curiously, gets us back to the entire point of my original comment; viable alternatives to systemd don't exist. This painful truth is not only sad and unfortunate, but perhaps even worrisome for the future of Linux.


  1. From: "systemd has become so good that even opponents can’t deny its merits and continue to make use of it for the time being out of necessity"
  2. From: "some combinations of distro + DE don’t allow any differentiation in init or make it very cumbersome and unwieldy at best."
  3. Preference is arguably too broad of a term, but I wanted to make clear that distro maintainers have different priorities.
  4. This page suggest otherwise, simply because someone else is referred to as founder. Though, ultimately, I don't know.

If not 😜; did I understand you correctly in that the mere existence of Devuan is the supposed contradiction?

[-] alt@lemmy.ml 1 points 1 year ago

Nope I downloaded VLC through the software manager.

Interesting to hear that it caused so many issues then 🤔. FWIW, I've personally been using MPV since I'm on Linux. I don't remember the exact reason, but if my memory serves me right; support for it on Linux somehow seemed superior compared to VLC. Related; e.g. it's actually found in Fedora's repos.

I’m going to do this for one week, doing daily updates and trying my god-damned best to get this shit software to do what the community says it can do.

Kudos for sticking with it for a bit longer! Please feel free to seek help from the community; though be mindful of your language if possible, I'm sure it will contribute to more people reaching out.

I managed the get Nvidia working on 39, which looks like an accomplishment given the other post linked about Nvidia and issues with 39.

Well done! Please note that a random update related to Nvidia might break your system in the future. If you don't want to deal with that in the future, running one of those Nvidia Images from uBlue ensures that from happening in the first place. This offers some explanation to what it achieves and how. TL;DR:

"We've slipstreamed the Nvidia drivers right onto the operating system image. Steps that once took place on your local laptop are now done in a continuous integration system in GitHub. Once they are complete, the system stamps out an image which then makes it's way to your PC.

No more building drivers on your laptop, dealing with signing, akmods, third party repo conflicts, or any of that. We've fully automated it so that if there's an issue, we fix it in GitHub, for everyone.

But it's not just installation and configuration: We provide Nvidia driver versions 525, 520, and 470 for each of these. You can atomically switch between any of these, so if your driver worked perfectly on a certain day and you find a regression you just rebase to that image."

Btw mounting a NAS is basic, basic office environment functionality. I don’t know how Linux ever expects to take over in the office if mounting a NAS drive is this stupid and difficult.

I ~~hope~~ am sure there's an easy way, we just have to figure out what that is. Wish you the best of luck, though!

Btw, if the idea of Nobara did interest you, perhaps you should consider Bazzite; which is a project related to uBlue, but which -like Nobara- tries to be properly setup for gaming from the get-go.

[-] alt@lemmy.ml 1 points 1 year ago

I have something like 70 AUR packages installed and it’s very seldom I have problems.

I'm glad to hear that you're able to dodge problems more often than not. But even if you wouldn't have any problems at all, it's undeniable that the model of Manjaro + AUR is fundamentally broken. No amount of copium, Stockholm-syndrome or masochism would change that.

There isn’t any significant difference in AUR compatibility between Manjaro, Arch or any other Arch based distro. I believe this to be an often misunderstood issue.

Don't you think that Manjaro's model of holding back packages conflicts with the AUR that primarily targets Arch which (by design) doesn't hold back packages? And, if you agree that it conflicts, don't you think that this actually is a very significant difference as two distinct programs/binaries/software/whatever might rely on two different versions of the same dependency? It's like a schoolbook example of what dependency hell is*.

When you install an AUR package it will work now, on the current state of the distro (current package versions). Later, as you upgrade packages, AUR packages will gradually start failing to work. This is the same on any Arch distro and it depends on how often you upgrade. If anything, by delaying packages by 2 weeks Manjaro will also delay potential incompatibility.

Fam, with all due respect, I'd like to invite you to educate yourself on this matter. Because, apologies for saying this, there's just an awful lot of misinformation, conflation and confusion present in this paragraph.

TLDR is that all AUR packages will break eventually and have to be reinstalled periodically, on any distro.

I agree that packages everywhere on all distros may break at some point; that's just how software is. Though, nothing condones taking on a defeatist stance towards package breakage.

[-] alt@lemmy.ml 1 points 1 year ago

I don't even think it should be avoided at all times. Just approach it through an Arch-container, Distrobox can streamline that process, and everything should be gucci.

[-] alt@lemmy.ml 1 points 1 year ago* (last edited 1 year ago)

I looked into distrobox and checks all the boxes but there is the issue of my lack of storage space(currently only 130 GB left out of 240)

It can definitely fill up space if you're not careful. Just ensure that only the minimal amount of containers and their respective images are on the system.

I would assume one container each for Ubuntu and Arch should suffice for most people. Sure; this will likely take up to 10 GB of extra storage in total (eventually), but foregoing this solution means that you'd likely have to settle for Arch (because of the AUR) or something like Gentoo (because no other distro does compiling and building from source like Gentoo does).

If you feel particularly adventurous, you could also consider Nix and/or NixOS; though you'd have to ensure that said packages are available as a nixpkg. Nix can also be installed on Fedora; consider Determinate Systems' installer for that*.

[-] alt@lemmy.ml 1 points 1 year ago

I see this as save scumming for real life!

Hehe, great analogy :P !

[-] alt@lemmy.ml 1 points 1 year ago* (last edited 1 year ago)

Ah, I got it now thanks for the explanation!

Indeed, in your case acquiring uBlue through its ISO was probably the best option; but I'm glad to hear that it worked out in the end!

Anyways, doing it the hard way is helping me learn the intricacies of an immutable system, so I am having fun.

Well said!

Just in case; consider the following:

  • Pin your current working deployment with the aforementioned sudo ostree admin pin 0 command. After which it remains accessible regardless unless you unpin it later on. This should allow you a working deployment if all else fails and thus a safe haven to rely on.
[-] alt@lemmy.ml 0 points 1 year ago* (last edited 1 year ago)

Unfortunately, you didn't -to my knowledge- support nor retract your claim on Chromium using flatpak sub-sandboxes. Therefore, I find it hard to continue taking your words at face value.

I have enjoyed these interactions, so don't get me wrong; but if I (possibly) catch you on spreading misinformation (even if unintentional), then I find it hard to keep engagement up as there's no guarantee that anything else coming from you is actually correct.

I would love to be corrected on this though, so please feel free if I have misunderstood you or anything else that would revive this conversation. If not, then I would still like to thank you from the bottom of my heart for this friendly interaction we've had. Take care!

[-] alt@lemmy.ml 1 points 1 year ago

you’re not going to get GUI apps that way though

I should have known better :P. Thanks for the input!

view more: ‹ prev next ›

alt

joined 1 year ago