I know about Backports. It's just software from the next version of Debian.
Tbh I've given up on looking for an AUR equivalent for now.
I know about Backports. It's just software from the next version of Debian.
Tbh I've given up on looking for an AUR equivalent for now.
That makes sense! Most other laptops become junk when the keyboard eventually gums up or when the screen breaks, but if it's repairable you can easily fix it :D
Yeah. I called out someone here on Lemmy for just completely making shit up about some kernel feature, linked the documentation showing the actual meaning, and got downvoted for it.
Is there a way to limit download bandwidth of programs started with this systemd-run command? Without changing some network settings, I just want to do it temporarily on the fly with commandline options.
There's not much of a used market because the laptop is so repairable, I still have my 11th gen
Rust is slower... Shouldn't be used in the kernel...
True, huge W for german here
He also implies that cgroups are a systemd-only feature.
I remember way back when I was doing Ruby on Rails, we would always wrap the server processes in a manager (I forgot what it’s called) that watches the memory and restarts them when the leaks get too bad. What a ridiculous solution that was.
Or you could write it in English with German grammar:
Linux 7.4 Blockupdates range from Floppydiskdriverfixes to Apple M4 NVMe-Support.
Yeah! It got mentioned earlier, and I've started playing with it -- it's not perfect like you say, but it is good enough for what I need
Is that quoted part meant to be a better title? Because I'd say that's way too long.
This has been happening forever. This old post always pops up in my mind for some reason as a historic example from an earlier linux boom.
Unfortunately, people have been pushed to not call out such things, because it's "not nice", when as the blog above shows, not calling it out is what's not nice, and potentially dangerous.
I think so. And I understood the title, because I've been using Linux on and off for the last 30 years, so maybe he's hitting his target market. And a simple kernel release summary is hardly Pulitzer prize stuff, so I'm happy to cut him some slack.
But I still bemoan the loss of sub-editors in general.
You may have experienced this before. You have an agent write a script, perhaps to do some data analysis. It has a terrible memory leak, and suddenly your machine freezes and (hopefully) the kernel resumes after a bit with an OOM error I've had this a few times, and it's very annoying..
Holy fuck I can't stop laughing at their reason for systemd for some reason, probably need an agent summarising their article for me
Got a bit scared by those BitWarden news. Luckily it wasn't that bad, from my understanding.
More obvious, but systemd has a lot of features that a simple cron doesn't.
Which cron?
Oh wait. Why did I assume OP would know there are multiple implementations? 😄
Dude is doing this all alone, isn't he?
This is why we used to have sub-editors in the Before Times. They would catch and fix shitty titles - and a bunch of other grievous journalistic errors - before publication.
Linux 7.4 Block Updates Range From Floppy Disk Driver Fixes To Apple M4 NVMe Support
"Updates to the Linux 7.4 block device subsystem span 40+ years of personal computing, with floppy disk driver fixes as well as cutting-edge Apple M4 NVMe device support. "
it is not the default
I can't parse the title.
dtach is exactly what you're looking for.
There are other similar tools. I personally found zmx to be the best, but it's more feature rich than dtach, and might be more than you want. Dtach is pretty minimal. But my only issue with it is it struggles with reloading a terminal session for a TUI that needs non trivial redrawing.
Don't threaten me with a good time
If you don't want to move to Debian Testing, then the only similar thing is Backports https://backports.debian.org/
Log data, current status of a run, timestamp of an error, you name it.
These are oneshots. Of course you could use a proper workflow system with data provenance and lineage tracking baked in, but during the dev cycle of something new you usually want to play around and gather metrics first without worrying first about the architecture.
Please don't X/Y me.