I mean, in this era of containers, it's not like you'd need this very often, but if you do, you do.
https://cloud-images.ubuntu.com/releases/hirsute/release/unpacked/ubuntu-21.04-server-cloudimg-amd64-vmlinuz-generic https://cloud-images.ubuntu.com/releases/hirsute/release/unpacked/ubuntu-21.04-server-cloudimg-amd64-initrd-generic https://cloud-images.ubuntu.com/releases/hirsute/release/ubuntu-21.04-server-cloudimg-amd64-disk-kvm.img
https://github.com/opensearch-project/opensearch-py/blob/main/guides/connection_classes.md
connection_class = Urllib3HttpConnection
pool_class: Any = urllib3.HTTPConnectionPool
self._urllib3_pool_factory = lambda: pool_class(
self.hostname, port=self.port, timeout=self.timeout, **kw
)
self.pool = self._urllib3_pool_factory()
response = self.pool.urlopen(
| #!/bin/env python | |
| # journalctl -u wpa_supplicant -f -o json | python event_listener.py | |
| import json | |
| import sys | |
| import subprocess | |
| __BEACON_LOSS = 'CTRL-EVENT-BEACON-LOSS' |
| # Ubuntu 18.04 and various Docker images such as openjdk:9-jdk throw exceptions when | |
| # Java applications use SSL and HTTPS, because Java 9 changed a file format, if you | |
| # create that file from scratch, like Debian / Ubuntu do. | |
| # | |
| # Before applying, run your application with the Java command line parameter | |
| # java -Djavax.net.ssl.trustStorePassword=changeit ... | |
| # to verify that this workaround is relevant to your particular issue. | |
| # | |
| # The parameter by itself can be used as a workaround, as well. |
| package io.mikael | |
| import java.time.LocalDate | |
| object SystemProperties { | |
| operator fun get(key: String): String? = System.getProperty(key) | |
| fun get(key: String, default: String): String = get(key) ?: default | |
(I also reported this to AWS: awsdocs/amazon-ec2-user-guide#123)
The "Running Amazon Linux 2 as a virtual machine onpremises" page describes a fairly cumbersome way of running Amazon Linux 2 in local virtual machines through using various tools to provision ISO9660 seed.iso files just to serve the VM instance two small data files.
It would be great it the documentation also pointed out that since the VM provisioning is being done with cloud-init, and the image has configured a fairly extensive datasource_list: [ NoCloud, AltCloud, ConfigDrive, OVF, None ] which starts with NoCloud, that NoCloud also allows you to serve these files over HTTP.
There are two easy ways of using network configuration instead of seed.iso. Either you tell GRUB to add a parameter to the kernel boot configuration, or you tell KVM/VMWare/Virtualbox to set the virtual machine's SMBIOS value to something which cloud-init's NoCloud understands.
The documentation page https://cloudinit.readthedocs.
| import pandas as pd | |
| df = ... | |
| df.to_parquet("foobar.parquet.zst", compression='zstd', compression_level=22) |
| date | title | tags | |
|---|---|---|---|
2020-02-29 |
Proper CUDA and cuDNN installation |
|
You're here, so you're probably already hurting because of CUDA and cuDNN compatibility, and I won't have to motivate you, or explain why you'd want to have standalone CUDA and cuDNN installations, if you're going to develop using Tensorflow in the long term.
| internal inline fun <reified T : Any> T.getClassLogger() : java.util.logging.Logger | |
| = java.util.logging.Logger.getLogger(T::class.java.name) |