Don’t be discouraged. This may not have worked out like you hoped and planned, but keep doing awesome things. Somebody will love you for it and you’ll have a lot of fun.
Don’t be discouraged. This may not have worked out like you hoped and planned, but keep doing awesome things. Somebody will love you for it and you’ll have a lot of fun.
For usb, make sure to get one with UASP https://www.jeffgeerling.com/blog/2020/uasp-makes-raspberry-pi-4-disk-io-50-faster
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.
I can’t believe it’s real. 🤦♂️
I stared at it for like 3 minutes and suddenly it flipped and all made sense, like a proper optical illusion.
The metal comes down and to the right, then bends back to the left. The shadow is the reflection off the metal. The metal is coming down and out of a hole. The white area is a completely flat surface.
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.
No joke, I hesitated to even click on the thumbnail. That’s what this bullshit modern internet has conditioned me to do.
deleted by creator
I’d personally do what others are suggesting and use bash, but you could also go with http://myrepos.branchable.com/
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.
HTML is open, you could easily scrape websites and generate some stats about how often they’re used.
But no, ul and ol are for exactly what you’d expect them to be used for.
Incidentally the Mozilla docs for ol say:
Unless the type of the list number matters (like legal or technical documents where items are referenced by their number/letter), use the CSS
list-style-type
property instead.
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.
Personally I run almost everything in docker, with the launch configs stored in git, backed by zfs. This means that if the host dies I can import that zpool, docker compose up -d
and be done with it.
I suppose the same could be done with VMs or LXC. The main thing is to keep it all separate from the bare metal OS, and in a technology that allows quick provisioning from a launch config of some sort, be it makefile, shell script, docker-compose, or whatever.
Yeah, Reddit is Digging its own grave.
Show your effective sshd server config:
sudo sshd -T