I'm unpacking my electric motorbike[1] and its moped sister[2] from winter storage and preparing them both for a summer in a city in a nation which energy supply is mostly renewables.

Of course, it took a lot of gasoline to get them here, but I sure as heck won't be using much gasoline to put them to solid use clocking up the kilometers, 100 at a time.

Got a few deals on solar panels for the backyard that'll get me completely off the grid for the most part, and from then on it'll be maintenance mode and solar powered travel as priority number one ..

[1] - https://www.blackteamotorbikes.com/

[2] - https://unumotors.com/

Isn't this what -HUP is supposed to be for in the first place? Maybe a -STOP/-HUP/-HUP situation?

HUP is short for "hangup" which was supposed to be sent when the tty controlling the session the process is in hung up.

Right, so tty's go stale prior to the freeze and they must be renewed after the freeze .. seems to me there's a missing system heuristic here.

Nice.

Now I want the ability to freeze the VM cryogenically and move it to another machine automagically, defrosting and running as seamlessly as possible.

I know this is gonna happen soon enough, I've been waiting since the death of TandemOS for just this feature ..

I once worked for a mainstream headphone manufacturer who added a volume control to a product that was so widely despised that a special firmware release had to be done to disable it completely, or else the returns bin would overflow almost overnight ..

So this had me chuckling so hard, having worked professionally in the pro audio world for decades - I can say that some of these 'solutions' would actually be accepted in certain market segments .. I especially love the designs which use a built-in accelerometer.

It seems the good ol' knob is not going anywhere any time soon.

>scaffolding

The purpose of scaffolding is to create persistent memories.

>claim "persistent memory"

Just look at it as a build product.

>abstractions that don't work

Look at this as a testing problem.

This is exactly what I have wanted for a while, so thank you very much!

Disclaimer: I haven't dug into axe enough yet, just going on first impressions.

>No daemon, no GUI.

I love the world we developers live in right now. ;)

>What would you automate first?

In a sense, I have wanted to be able to just add AI to a repo, and treat it like the junior developer it is. Its okay if the junior developer will do literally any stupid thing I tell it to do, because I won't tell it to do stupid things.

So, exactly: refactor this code, implement a shim, produce docs for <blah>, construct a build harness, write unit tests, produce a build, diff these codebases, implement this API, do all this on your own branch, and build and test things so that I can review the PR over coffee.

Essentially, three word commands which will encourage the AI to produce better software. Through my repo, so I can just review through the repo.

Okay, that's how I hope things work, now off to actually dig in to axe and give it a try on a few things, thanks very much again ..

Well, Deckards Dream comes pretty close to attaining a modern analog manifestation of the CS80 ideal:

https://black-corporation.com/shop/

And, well, its a lot more feasible to gig with, by comparison.

It sounds different but it is great in its own right and priced adequately to how amazing it sounds. Maybe 'alternative' is a wrong word. I think I meant 1:1 replica.

Also it doesn't come with ring modulator nor ribbon. I think black corp synthesizers are inspired by the original vintage devices and are great on their own but there are justified reasons to also avoid them mostly because of common issues that arise when you buy a niche product from a tiny company thousands of kilometers away.

>common issues that arise when you buy a niche product from a tiny company thousands of kilometers away.

Sorry, this is just negative - but anyway, have you played with both?

I have. There are differences but they are minor and you can very definitely accomplish an approximation of the CS80 'sound' with the DD. It sold out for a reason.

Either way though, if you have an opportunity to have a real CS80 in the studio, as I do, you are very right in saying that it is an amazing beast.

Native builds are always a safer/more reliable path to take than cross-compiling, which usually requires solid native builds to be operational before the cross environment can be reliably trusted.

Its a bootstrapping chain of priority. Once a native build regime is set in stone, cross compiling harnesses can be built to exploit the beachhead.

I have saved many a failing projects budget and deadline by just putting the compiler onboard and obviating the hacky scaffolding usually required for reliable cross compiling at the beginning stages of a new architecture project, and I suspect this is the case here too ..

I don't care as long as it keeps my soldering iron hot.

Laughs in uucp!bangpath.