No, thats not how it works now. You used to have to install docker-compose and run docker-compose, but now you don’t. Docker comes with compose, but you call it as docker compose rather than the old Python module based way docker-compose

https://www.docker.com/blog/new-docker-compose-v2-and-v1-deprecation/

I saw in your update you mentioned installing docker-compose. Modern docker has “compose” as a verb, and should work as docker compose. I haven’t tested this on raspberry pi though.

Not my last, but after using killall in Linux, I tried it on hpux, only to discover and later confirm in the man page that on hpux it doesn’t take any arguments, it just kills every process.

http://hpux.polarhome.com/service/man/?qf=killall&of=HP-UX

True, but nothing else looks like money. Lots of things have a similar shape as the barrel of a gun.

Money is also quite detailed, with a known list of configurations. Any counterfeit would need to match the details in those known configurations extremely well. Finding that match with a high degree of accuracy is a fairly well understood and common engineering task. This is not the same task as identifying anything that could possibly be used to represent money with a high degree of accuracy, which is essentially what would be needed in the gun printing problem.

Somewhat related, the US Gov provides play money that you can print for your kids, which I found helpful to teach my kids about how money works. https://www.uscurrency.gov/sites/default/files/download-materials/en/Printable-Play-Money.pdf

Next up: Smith and Wesson is granted a copyright for DRM on STL files.

Taking this purely as an engineering task, how is this remotely possible? I can barely begin to imagine how restrictions on what can be printed could be set. Am I missing something obvious? Some kind of contextual understanding of the object seems to be necessary… please don’t tell me their proposed solution is AI.

In any case it will never work because 3D printing is so easy for makers to do from scratch, so any solution will fail to prevent printed guns from being made.

Again, this is just the pragmatic engineering angle. Please don’t respond with political arguments.

deleted by creator

Related: a list and explanation of variable naming conventions https://www.pluralsight.com/blog/software-development/programming-naming-conventions-explained

My first line of investigation here would be virtualization. It will solve the “don’t mess with my Linux install” problem and will let you use the windows apps you need at the same time as the Linux apps you normally use. Also VMs have all their other useful features like snapshots and portability.

I did this in the distant past and it was quite convenient having the VM instead of a dual boot.

Microsoft has had an impressively positive impact on Linux, including the kernel directly. It started ramping up about 15 years ago. They were the 5th highest contributor to the 3.x kernel.

I recall reading about them working on improving Linux’s MS related features, like fat32 support, samba, and things to make Linux run better in hyper-v that also helped performance overall.

Microsoft owned company migrates from third party EOL OS to Microsoft distributed OS. No surprise.

I did this when traveling internationally in 2009. I used Skype-in to forward my USA phone number to my Skype account, but I think I made like 3 phone calls. I only used WiFi at cafes and hotels, no mobile internet service. Phones are overrated. Being offline is great.

Which of his amazing books is the “single good book” you’re referring to?

I’d personally do what others are suggesting and use bash, but you could also go with http://myrepos.branchable.com/

Also sgdisk https://man.archlinux.org/man/sgdisk.8.en

Sure, you can do whatever you want. You could even use non-rfc1918 addresses and nobody can stop you. It’s just not always a great idea for your own network’s functionality and security. You can use an unregistered TLD if you want, but it’s worth knowing that when people and companies did that in the past, and the TLD was later registered, things didn’t turn out well for them. You wouldn’t expect .foo to be a TLD, right? And it wasn’t, until it was.

Try using .com for your internal network and watch the problems arise. Their choice to reserve .internal helps people avoid fqdn collisions.

See also https://traintocode.com/stop-using-test-dot-com/

Breaking indeed.

Both, actually, and those things are directly related. If I need to migrate a single thing to another machine it’s just rsync and make run. Of course this requires the bare metal to have docker and make, so some bare metal configuration management is also needed.