I feel like why not just print to pdf from your pdf viewer?

Eff has a better list imo. Diceware has a tonne of short abbreviations like “1st”. Eff is words that are mostly 5 to 8 characters long. Much more xkcd like and easier to make a mnemonic out of.

Because 48 bits over 32 bits does not really solve the problems with ip4. 128 bits basically gives one ip4 address space to each square meter of earth. Ip6 also drops all the unused and silly parts of ip4 too.

Yea, this is not cheap companies doing cheap things. This is companies getting annoyed by stupid licencing and restrictions, getting around the problem.

It’s been getting “more and more use” since 2001. To start with the isps said that they were not going to do any work to implement it until endpoints supported it. Then vista came with support by default. Next they wanted the backbones to support it. All tier 1 networks are now dual stack. Then they said they were not going to do anything until websites supported it widely. Now all cdns support it. Then they said, it’s ok we will just do mass nat on everyone so won’t do any work on it.

Starting June 2024, iFixit will no longer be Samsung’s designated third-party parts and tools distributor. Also starting next month, we will no longer have a quantity limit of seven Samsung parts per repair shop per quarter.

Wow that is quite a limit Samsung. I can see why no one would want to be a partner with them. (Which was obviously the point.)

It depends where you want the complexity.

Since ssh is a layer4 tunnel if you don’t run a proxy on your home box, you’ll need a new network connection for each service, if you are fine with that, I would set it up only on the VPS. This means if the tunnel goes down, you should at least get 502 error rather than a timeout or connection refused.

Alternatively you could forward 80, 443 to a proxy service on the home server. That would require two ports for the ssh.

You can drop it to a single ssh connection by having a proxy on both and just have the VPS proxy Http and https to the same port on the home server.

In the how this works section they detail that it comes from MDM solutions. In English this is a feature for it admins of companies who use the intune management software from Microsoft. You probably need pro or better to even use the feature.

At a quick glance, it looks to be a way of whitelisting domains at a DNS level, but with the added feature of having allowed DNS servers.

Where getter?

I think you might be thinking of a different black hole. This one is in our galaxy, the first one imaged was in m87. The one in our galaxy is actually harder to “see” as there is stuff in the way.

Make sure the columns in your csv are named properly, my code assumes it’s named just “name”

For csv import, use import-csv and loop on the results:

Import-csv myfile.csv | foreach-object {

Templates should be easy, just copy the template to a new file with the docx extension. Use one of the columns (in this case “name” as the column header,) from the csv for the name:

    $newname = $_.name + '.docx'
    Copy-item 'template.dotx' $newname
}

I use it with WAC on my home server and it’s good enough for anything I need to do. Easy to create VMs using that UI, PS not even needed.

For real, I’ve had problems where I specifically checked if it was DNS, concluded it was not, but it still turned out to be DNS.

Last time I did this domain accounts needed to include their domain/upn to logon, so there won’t be any account confusion. However if they were accessing the nas from a domain joined machine, it would use Kerberos anyway so shouldn’t be getting prompted to logon. Obviously that is only for SMB shares, other connection types didn’t use Kerberos.

For real, at the minimum use a virtual machine.

No, that is not what it means. i386 is specifically the set of instructions that the 386 introduced. Later processors from intel added additional instructions, those were rolled into i686 as a set. i686 contains i386 so it can still run programs that target that, but a 386 can’t run a i686 program.

i386 and i686 are both x86 32 bit instruction sets.

What is happening is that the kernel will no longer support i386 as a target. So any processor that does not support at least i686 will stop working. This is basically anything before around a pentium 3 (iirc might be wrong about exact CPU.) Vista era computers should not be effected.

The confusing part is that some distros have already dropped all 32bit for other reasons, but it would mean it would be hard for distros going forward to support 386 era processors.

Look for usb floppy emulators, you can have the floppy images in a usb flash drive. No moving parts or need to find expensive floppies.

At least if a modder picks a random spot for their content it’s unlikely to conflict with any other mods.