TunaCowboy

a remnant from the old times

This comment demonstrates a misunderstanding of shepherd and guix. Using an actual programming language vs some bastardized version of a markup language to describe complex configurations is increasingly popular because it is better. guix is inspired by nix and allows you to specify the entire system as code in a reproducible manner - which you don’t want to do in ‘human readable’ toml+, yaml+, etc. because it fucking sucks.

I like when tools abstract away the programming parts

You can use scheme to abstract away scheme lol. These are advanced tools for advanced systems.

*I use systemd all the time, but a direct comparison between systemd and shepherd without additional context is misleading and flawed.

Who’s dumber, ‘AI’ or the person who took the time to screenshot this and post it?

Because Debian is known for its up to date software, right? Gave me a good chuckle.

stable is not the only debian release. Additionally, while ubuntu may be great for beginners or corporate offices, it really does suck compared to other distros. They’ve added so much garbage and guardrails the performance is dog shit (in comparison to other distros like debian).

echo 'main;' | gcc -w -x c - && ./a.out

I never said it does, are you intentionally ignoring the context in which my comment was made?

I have no love for the c-suite, but framing the OP as simply ‘asking for money’ is either ignorant or disingenuous.

You get to choose the license (or write your own) when you develop software. If you don’t want a permissive license don’t license your software that way, your motivation clearly doesn’t align with these licenses anyway.

Seems intentionally adversarial.

pass: the standard unix password manager

https://ifuckinghatejira.com

Generally speaking the OS is your universe and you interact via syscalls. Linking libc is also an option.

In some instances you may need to roll your own, but it’s likely to be small and specialized.

Syscalls are sitting right there, and you can always just link libc…

What if I prefer this?

#define CURLYOPENRIGHTCLOSEDLEFTBRACKET {
#define CURLYOPENLEFTCLOSEDRIGHTBRACKET }
#define CURVYOPENRIGHTCLOSEDLEFTBRACKET (
#define CURVYOPENLEFTCLOSEDRIGHTBRACKET )
#define PERIODWITHPERIODONTOP :
#define COMMAWITHPERIODONTOP ;

int main CURVYOPENRIGHTCLOSEDLEFTBRACKET CURVYOPENLEFTCLOSEDRIGHTBRACKET CURLYOPENRIGHTCLOSEDLEFTBRACKET
  if CURVYOPENRIGHTCLOSEDLEFTBRACKET 1 CURVYOPENLEFTCLOSEDRIGHTBRACKET CURLYOPENRIGHTCLOSEDLEFTBRACKET
    asm volatile CURVYOPENRIGHTCLOSEDLEFTBRACKET
      "mov $1, %%rax\n"
      "mov $1, %%rdi\n"
      "lea message(%%rip), %%rsi\n"
      "mov $4, %%edx\n"
      "syscall\n"
      PERIODWITHPERIODONTOP
      PERIODWITHPERIODONTOP
      PERIODWITHPERIODONTOP "%rax", "%rdi", "%rsi", "%rdx"
    CURVYOPENLEFTCLOSEDRIGHTBRACKET COMMAWITHPERIODONTOP
  CURLYOPENLEFTCLOSEDRIGHTBRACKET
  return 0 COMMAWITHPERIODONTOP
CURLYOPENLEFTCLOSEDRIGHTBRACKET

asm CURVYOPENRIGHTCLOSEDLEFTBRACKET ".section .data\n"
  "message: .ascii \"wut\\n\"\n"
  ".section .text\n" CURVYOPENLEFTCLOSEDRIGHTBRACKET COMMAWITHPERIODONTOP

regex feels like the kind of magic you get by consorting with dark forces

AKA reading the manual.

Just use -j, --jobs: https://doc.rust-lang.org/cargo/commands/cargo-build.html#miscellaneous-options

That doesn’t mean it is loading dynamic kernel modules, which also require enrolling a machine owner key.

If secureboot is enabled try disabling it. If disabling secureboot resolves the issue re-enable secureboot and add the dkms signing key with mokutil: https://wiki.debian.org/SecureBoot#Making_DKMS_modules_signing_by_DKMS_signing_key_usable_with_the_secure_boot

Wrong.

deleted

sq

git commit -m 'sq'
git reset --soft HEAD~
git commit --amend
git push origin +release

You should not be pushing into your main/master/whatever branch.

All the main/master replies completely miss the point, further emphasizing sirsirsalot’s statement.

git whoosh --hard