mystik @ mystik @lemmy.world

Posts

0

Comments

92

Joined

2 yr. ago

You can extract the SLIC value from the ACPI table, and then pass it through to QEMU

See more details here: https://gist.github.com/Informatic/49bd034d43e054bd1d8d4fec38c305ec

It is my understanding that this can only be used to run the OEM license one one instance in a VM, on the specific hardware that is originally licensed. IE, you virtualize the license if the bootOS is Linux, but you can't run 2 instances of the same windows license inside each other.

Because dead people in other countries don't buy US exports.

Trump or Trump's puppet masters?

If you use gitea, it's just a few steps to enable it to be an OAuth2 provider. See Oauth2 Provider Docs

The American people have spoken, and have agreed on a law that disqualifies them. Lets put it to a vote and see if we should change that law?

Never give it up, and never let it down.

Not only do they not federate, they also seem to suggest they are not making the self hosting option as easy as it could be because they would prefer one instance that everyone connects with.

It seems pretty solid otherwise, and the self hosted option can work if you are willing to spar with it, but that position makes it super easy for one organization to buy or somehow influence all the primary devs and turn the project closed in no time at all.

Personally, I will use both: On servers with fixed network connections I will tend to use ifupdown; but on my linux laptops I'll use networkmanager or networkd which tend to have nice UI's for joining various forms of wifi networks. On my laptops for some VPN's i"ll use the ifupdown configuration, which lets me setup all sorts of exotic configurations (bridges, vlans, vxlan,, vpns, namespaces, etc.) The linux command line tooling has a litany of functions to check/test/diagnose/tweak networking settings, and they work across all the distros, AND they can reveal the full details of the network, as the kernel sees it. NetworkManager, networkd, connmann, etc, often omit details in the name of simplifying for the most common scenarios.

As an anecdote -- I have been sitting on an elastic IP at AWS for years, with reverse DNS configured properly for it. Way early on (years ago), some spam filters would block the whole netblock, but I can't remember the last time the IP Block was wholesale blocked. I think AWS is very much on top of any spam complaints from their Elastic IPs, and as long as you don't abuse your specific IP, you are in good shape for light volume, non-spam mail.

LMTP support would be nice too: existing mail routing infrastructure could send messages into stalwart-managed mailboxes. (Edit: reading the docs, they do support LMTP! This is awesome)

A single binary can be invoked with different privilege levels. OpenSSH, for example is a single binary, but uses OS privilege separation when setting up connections from the root-owned daemon. (Just to be clear, I'm not sure that stalwart is using this technique, just that single binary apps do not exclude the possibility of OS privilege separation.)

We need that slashdot system of vote + mark "insightful", "flamebait", "funny", etc etc. add more categories as necessary so posts can be scored on multiple axes.