• 3 Posts
  • 981 Comments
Joined 10 months ago
cake
Cake day: October 13th, 2024

help-circle




  • Sounds like you have issues maybe go touch some grass.

    The problem has been tso and linus. Neither have technical issues with kent’s work. They just cause drama over the entirely arbitrary timing of prs.

    Kent has no issues with the merge process for mature and stable code. The disagreement is over the process for experimental code. Which if linus and tso stfu for a minute and thought about it they’d reallze kent, and literally every active user of bcachefs atm, is right.

    Linus shouldnt have an opinion about the timing for bcachefs prs atm and if he wants to have an opinion he should stick to technical issues.

    You’ll notice how little drama there has been since the last nonsense caused by linus/tso/ and the peanut gallery like yourself. Just stfu and merge shit unless it somehow breaks builds or if someone actually notices a technical issue or if kent reaches outside of bcachefs’ tree.




  • oh its okay. for future reference these two statements were dead give aways.

    “To be honest, I wanted to come up with some kind of crazy AI video to respond to his, but I’m no good with all of that tech stuff,” Obama said. “Fortunately, there was real video of him when he was on trial, so I guess I lucked out.”

    At the White House, press secretary Karoline Leavitt blasted Obama’s post, stating, “Sharing actual footage of events that really happened is something that President Trump would never do.”












  • lol. child. we cant directly do anything if the program itself is compromised outside of sandboxing it. which we do have wrappers for. in fact we have a ton of them now. but sandboxing at the system level is more complicated than at the user level. because either you need to whitelist every possible system access and have it approved or deal with the occassional security issue as this post is about. one is much easier than the other.

    but sandboxing the installation process is fairly easy since thats in your package manager. basically just wrap up a bash implementation in a wasi runtime and restrict it and you’re golden, you’ll have blocked network and filesystem access. all the problems with the installation scripts can be directly controlled via that mechanism.

    we just dont do it because its a lot of work with minimal benefit and no one is paying for it to be done.

    just because you dont know what the solution space is doesnt mean others dont.

    again go touch some grass. you clearly need to.


  • You asked why people like the AUR and I informed you. not everything is a crisis. peoples computers get compromised every single day. (and yes it sucks for them)

    Now you may want to get into a pissing contest over how easy it is to containerize installations on linux today, I personally have no interest in educating peanut gallery commentators.

    the basics are: you essentially can’t do anything about the applications themselves but securing the installation process is straight forward these days. our package managers are just not funded so the work is slow as shit.

    now go outside and touch some grass for everyone’s sake.