

@GreenKnight23 I don’t see that behavior. Rebooting into a new kernel and then running dist-upgrade, it always _always_ keeps one older kernel around. Bookworm and trixie.
he/him. from the birdsite (@Andres4NY and before that @NEGreenways).
#Dad #NYC #Bikes #FreeTransit #SafeStreets #BanCars #Debian #FreeSoftware #ACAB #Vegetarian #WearAMask
My wife’s an #epidemiologist, so you’ll get some #COVID talk too.
Trans rights are human rights.


@GreenKnight23 I don’t see that behavior. Rebooting into a new kernel and then running dist-upgrade, it always _always_ keeps one older kernel around. Bookworm and trixie.


@GreenKnight23 @oong3Eepa1ae1tahJozoosuu I’ve never seen that behavior in Debian. Is that some different type of configuration?


@djdarren @frongt That’s not how SyncThing is designed. It’s intended to be a full mirror.
I kind of emulate what you’re talking about with restic’s mount command. It’s a lot less intuitive than what you’d get from a cloud storage platform, but it’s Good Enough For Me. If you want to match cloud storage, you probably want nextcloud or seafile or something.


@IratePirate @eightys3v3n Snapraid offers scrub/bitrot protection - check out ‘snapraid scrub’.


@IratePirate Combine this with restic (or borgbackup, if that’s how you swing) for a bombproof selfhosting solution.
@Bazoogle @1hitsong First of all - when it comes to creating programs, you want the output to be deterministic. Stochastic program output is a serious problem, as you _will_ get unreproducible bugs. Second, plain language is _not_ easy except for the simplest of tasks. Actual programs need to handle all kinds of corner cases and hardware weirdness and human weirdness. Your “plain language” goes from “do a thing” very quickly to “do a thing. but not that thing. or that other thing. and and and…”