Inspired by this
More of my guides: Debloating MEMu - Debloating Nox (Updated)
This mainly applies to LDPlayer9. They will probably work on the low end options (like LDPlayer5) but not guaranteed.
This emulator seems to have less stability issues than MEMu. I think we get the shtick that these emulators do spooky stuff.
Cloudflare announced a partnership with MailChannels that allows you to send free email via workers.
The example code that MailChannels supplied wasn't working so I fixed it here to make testing easy.
include:relay.mailchannels.net to your domain's SPF record.
| #!/bin/bash | |
| # script name: install_waydroid.sh | |
| # description: Install Waydroid on unsupported Debian based distro caused by incompatible python3-gbinder package | |
| # related to : https://github.com/waydroid/waydroid/issues/214#issuecomment-1120926304 | |
| # author : Wachid Adi Nugroho <wachidadinugroho.maya@gmail.com> | |
| # date : 2022-07-07 | |
| export distro=$(grep -oP '(?<=^NAME=).*' /etc/os-release) | |
| if [[ -f /usr/bin/dpkg ]]; |
| Task: | |
| Access OpenVPN or any Service on Home Network from Public Networks (Hotel) without configuring router and without static IP | |
| Step 1: | |
| Install OpenVPN on any device connected to Home Network (Raspberry mychoice with pivpn) | |
| - Change default OpenVPN protocol from UDP to TCP (Cloudflare doesn't support UDP) | |
| - Make a note of TCP port number (default is 443) | |
| - Grab the OpenVPN client config file | |
| Step 2: | |
| Install Cloudflared on Raspberry PI | |
| - Create a tunnel |
Inspired by this
More of my guides: Debloating LDPlayer - Debloating Nox (Updated)
Edit 22/8/2021: I have updated MEmu and it seems like it reinstalls the apps and re-enables the services. Repeat steps 5, 7, 8, and 9 if you update MEmu.
In my experience, Nox can be quite slow and choppy, and looks like I'm not the only person with this problem. A lot of people say that MEmu performs better than Nox, and I could agree with that. I have no chopping issues with it so far. But like Nox, there are kinda shady stuff going on.
| # Add your real IPv4 subnet settings here | |
| IPV4=X.X.X.X | |
| CIDR=X.X.X.X/28 | |
| GATEWAY=X.X.X.X | |
| DNS=1.1.1.1 | |
| # Add your real Interface settings here | |
| INTERFACE_NAME="enp2s0" | |
| VLAN_ID=4000 | |
| VLAN_INTERFACE_NAME="$INTERFACE_NAME.$VLAN_ID" |
Linux high IOwait is a common Linux performance issue. Today we will look at what iowait means and what contributes to this problem. Hope this can give you more ideas about high IOwait issue.
IO wait is related to the CPU resource on the server.
The iowait column on top command output shows the percentage of time that the processor was waiting for I/O to complete. It indicates that the system is waiting on disk or network IO. Because the system is waiting on those resources, it can not fully utilize the CPU.
I ran into the battle of running all of my VMs and the host node under a single public IP address. Luckily, the host is just pure Debian, and ships with iptables.
What needs to be done is essentially to run all the VMs on a private internal network. Outbound internet access is done via NAT. Inbound access is via port forwarding.
Here’s how it’s done:
UPDATED: 2024-05-19