opfar.v30

If outputting separate programs to separate outputs: install Pavucontrol (yes, for Pipewire); change outputs per-program in the first tab.

If trying to output the same stream(s) to both: install Helvum; drag lines around to connect to additional outputs.

No, both work for both but tee will yap back at you.

Look into man 8 systemd-suspend.service

Immediately before entering system suspend and/or hibernation systemd-suspend.service (and the other mentioned units, respectively) will run all executables in /usr/lib/systemd/system-sleep/ and pass two arguments to them. The first argument will be “pre”, the second either “suspend”, “hibernate”, “hybrid-sleep”, or “suspend-then-hibernate” depending on the chosen action.

t. fellow suspend-then-hibernate user.

On the privacy front, that would be cat, I think. Well, except on Ubuntu.

Shout out to tee.

alias cal="cal -m"

You know how to tell that it wasn’t?

It’s using careful hedging language — “could be used to attempt”, “have the potential to”, “more effective”.

AI would just plow through that shit, hallucinating facts like there is no tomorrow.

This is nonsense. Passwords might have an interesting distribution, key space is flat. There is nothing to learn.

And I hope you didn’t mean letting an LLM loose on, say, the AES circuit, and expecting it will figure something out.

encryption

You can train AI to crack encryption

Oh do provide details.

You silly goose. Sweden, a major arms exporter and one of the world’s top 3 arms exporters per capita is, in fact, the western military-industrial complex.

It’s bluca, yo.

As a random example, here is bluca breaking suspend-then-hibernate, then being a complete asshole about it, while other systemd devs are trying to put the fire out. Do read his code reviews on the latter. yuwata and keszybz have nerves of steel.

The current behaviour is fully expected and documented

bluca is cancer.

Yo, setup hibernation and use hybrid sleep as your default sleep.

ln -s /etc/systemd/system/suspend.target ../../../usr/lib/systemd/system/suspend-then-hibernate.target

Now any sleep is hybrid. The machine suspends, then wakes up after a timeout, and enters hibernation. The timeout is configurable in systemd-sleep.conf(5).

With this combo I find that I prefer S0 to S3. S0 drains the battery about twice as fast, sure, but it resumes instantaneously, while S3 takes about 30 seconds (!) to resume on this machine. And the thing hibernates and powers off if I leave it for an hour anyway.

I have a fist-gen Framework 13 (Intel 11). If I want to upgrade to fully match the new gear, what needs upgrading…?

Off the top of my head:

• display,
• mobo,
• my 64GB of DDR4 must be swapped for DDR5 IIUC,
• camera,
• the new 61Wh battery, and
• there were these new speakers, I think.

I should probably get a new keyboard as well, as I’m one of the people with the DEL key randomly going dead.

I already replaced:

• hinges, and
• the top cover.

I can hold on to the £10 wireless card, the PCIe3 SSD that I bought after WD just died one day, and the compressed alufoil that is the main body.

Well fuck me.

Yall understand that what actually changed is a symlink? That systemd-run is now linked from run0, and that’s enough to make a SUID-less sudo?