moonpiedumplings

joined 2 years ago
[–] moonpiedumplings@programming.dev 3 points 5 months ago (6 children)

It's not just protection against security, but also human error.

https://github.com/MrMEEE/bumblebee-Old-and-abbandoned/issues/123

https://hackaday.com/2024/01/20/how-a-steam-bug-once-deleted-all-of-someones-user-data/

Just because I trust someone to write a program in a modern language they are familier in, doesn't mean I trust them to write an install script in bash, especially given how many footguns bash has.

[–] moonpiedumplings@programming.dev 17 points 5 months ago* (last edited 5 months ago) (2 children)

#1 things holding back Nix adoption is piss poor documentation

The docs are bad because there is this massive split between flakes and nonflakes , where flakes are considered "unstable" and "experimental" but a ton of people use them. The official docs, due to flakes being experimental, can't really touch on that topic at all, and the unofficial docs will mostly be flakes only. And some things can only be done via flakes or only via channels, so that furthers the issue.

There was another discourse post about it, and it was agreed that the nix team just needs to choose something, as the problem is the split and indecisivice, rather than flakss or channels (old way) being uniquely bad.

where Nix “3rd party” tooling shines is in documentation

Determinate systems nix ships with flakes enabled by default. Official nix does not. This means thay determinate nix has a much easier time documenting their product as they exclusively use flakes.

The problem and potential conflict of interest documented in that thread, is that many of the determinate systems employees are big nix contributors with much power over nix official


including Eelco Dostra, the inventor of nix and the creator of flakes. Despite clearly doing recent work with flakes, and clearly contributing to making flakes the "default" in determinate nix, very little effort has been put into making flakes official by these same contributors.

The fear is that nix official is being intentionally kept bad, in order to push the product of determinate systems nix.

[–] moonpiedumplings@programming.dev 6 points 5 months ago (1 children)

The documentation has long since been changed.

Note that the anon user is able to become root without a password by default, as a development convenience. To prevent this, remove anon from the wheel group and it will no longer be able to run /bin/su.

https://github.com/SerenityOS/serenity/commit/a2a6bc534868773b9320ec3ca7399283cf7a375b (this seems to have also switched to gender neutral language in other parts.'of the documentation and comments as well).

Original drama: https://github.com/SerenityOS/serenity/pull/6814

The FSF doesn't seem to have teeth when it comes to things like this, instead it's the SFC who intervenes.

In January, the Software Freedom Conservancy, an open source advocacy group that intervened to help Suhy several years ago, submitted an amicus brief to the Ninth Circuit

[–] moonpiedumplings@programming.dev 2 points 5 months ago* (last edited 5 months ago) (1 children)

Give us your fstab and lsblk.

Or, the specific piece of information I want is where the kernels are located. When /boot is part of the root subvolume (not the default setup, sadly), then the kernels will be snapshpotted along with the rest of the filesystem. /boot/efi would be where the efi system partition is, and where the bootloader is installed.

If /boot is instead the efi parition (default setup lmao), then this means that when you restored a snapshot of your root subvolume, your kernels were not downgraded. I suspect that older kernels attempting to read/view newer kernel modules would cause this boot failure.

If the root account is locked, which cachyos does by default, then you won't get anything from this screen.

I had to fix by usb booting and troubleshooting (a different issue though, I was playing with initramfs generation).

[–] moonpiedumplings@programming.dev 1 points 5 months ago (1 children)

What are you using to view this? Nushell?

Kinda. I think it's definitely true that docker is used as a distro-agnostic package manager for services, and if we only had one distro we might not need that.

It should be noted that projects like cosmo attempt to make things portable to and across BSD's as well as Linux's, so people definitely want distro agnostic packages (or a package manager), even on the BSD operating systems.

However, on the other end, docker is also powerful because it (and tools that use docker containers, like kubernetes), orchestrate services and allow people to bring them up very, very quickly. Like, to bring up a service called pairdrop, I just take this file:

***
services:
  pairdrop:
    image: lscr.io/linuxserver/pairdrop:latest
    container_name: pairdrop
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - RATE_LIMIT=false #optional
      - WS_FALLBACK=false #optional
      - RTC_CONFIG= #optional
      - DEBUG_MODE=false #optional
    ports:
      - 3000:3000
    restart: unless-stopped

and type docker-compose up -d. And it's really quick, and arguably only possible due to the way containers are isolated and it's easy to create and destroy them. There exist solutions for automation and scripting like ansible, but they just aren't as good as the container solutions for automatically putting services up.

[–] moonpiedumplings@programming.dev 3 points 5 months ago (1 children)

I'm not personally trying to argue for telegram's use. I'm just pointing out why people end up using it. When convincing people to use Matrix, I find that calling them flies isn't really helpful for my arguments.

[–] moonpiedumplings@programming.dev 3 points 5 months ago (3 children)

people flock to Telegram, a centralised and insecure service.

Telegram isn't a chat app. It's an unlimited free file upload, storage, and sharing service that ignores any DMCA or takedown requests. It masquerades as a chat app, but that's why people flock to it despite the fact that it's not truly private.

And then of course, if people are already there, why not chat on Telegram?

https://moonpiedumplings.github.io/blog/docker-registry/

I threw together a list of a few dockerhub alternatives, including the fact that apparently google has a public mirror.

It's because you go to a Linux conference and meet interesting people and you ask for their contact, and they offer either signal or matrix.

XMPP is still being maintained and stuff, and still works fine, it's just not as widely used.

view more: ‹ prev next ›