When somebody calls your TwiML number, this markup will tell TwiML to dial +155555555 and if someone answers the call, it will record the call to 155555555. This may be illegal in your country if neither party has consent of the recorded call.
Dial with the record=”record-from-answer” can also be set to record-from-ringing-dual if you want it to record before 155555555 even answers, or even if they don’t answer.
This tutorial outlines how to install the rEFInd Boot Manager on a GPT partition. When using UEFI boot, you should understand you will require a bootable esp partition that houses either the Windows Boot Manager, GRUB2, or rEFInd. I don’t know much about MacOS so do not follow these instructions exactly if you are using Mac (some may apply).
To install and use rEFInd, you need a little EFI partition with rEFInd on it or by copying the files and setting up the boot entry manually.
Most people can just install rEFInd and then run refind-install. Work out if you’re on GPT or MBR partition table, how many drives you have, which one you want to boot from. Don’t run all the commands on this page until you’ve read it all. It’s not a perfect guide but it worked for me:
I now have:
Arch on GPT NVME SSD (unbootable, no grub)
Second GPT Hard Disk with 2GB fat32 following by 968GB of free space/ext4
If you don’t have a little ESP partition, this guide may be for you.
During this tutorial we will be making a new fat32 partition on an unmounted disk that is bootable and installing rEFInd to that little partition.
If you only have one hard drive, you need to do all of this from the rEFInd live disk. I read that it doesn’t work on the Arch live USB because kernel files from the live USB are copied instead of the Arch kernel files.
If you have two hard drives on the computer, connect the drive you want to install boot partition on (rEFInd) with a caddy or HDD Drive Housing to USB and edit the partitions that way.
Be very careful resizing partitions with data as you can lose the data when resizing, no matter how careful you are.
It’s possible to use GPT on a data disk even on a BIOS-based computer, or to use an MBR data disk even on an EFI-based computer. Thus, if you examine the wrong disk, you can be led to an incorrect conclusion about your computer’s boot mode. Another caveat relates to the use of a hybrid MBR, which is a variant on a GPT disk that’s most often used on Macs to permit booting Windows in BIOS mode and OS X in EFI mode. Most Windows tools will identify a hybrid MBR disk as an MBR disk, but most non-Windows tools will identify it as a GPT disk. Of course, as hybrid MBRs are generally used to enable dual-booting Windows and OS X, and as OS X boots in EFI mode, you should be able to install rEFInd from OS X to help manage such a dual-boot configuration.
There are many different scenarios that need to be discussed before deciding where to install the esp partition and with what software too.
The most important thing is to build a recovery USB first. If you don’t build a boot recovery USB and you modify your GRUB or rEFInd files, you will most likely leave your system unbootable. The most common reasons for not being able to boot are (I have experienced all of these lol):
if you delete the Windows Boot Manager partition
if you install Windows in GPT/MBR and your Linux installation is MBR/GPT
if you delete GRUB2 entries
if you auto-install GRUB2 or rEFInd
if you try to install GRUB2 or rEFInd on a mounted disk (OS running)
if you try to boot Windows in UEFI mode or legacy mode and installed Linux in the opposite of the one you booted in
if you delete GRUB2 without installing rEFI
if you delete boot or kernel files, or move them to abnormal places
if you delete the wrong partition
if you format the wrong partition into ext4 or fat32 or else
if you leave Secure Boot on and cannot boot from USB
Step 1: Build a recovery USB to absolutely make sure you can boot again
Reboot now and test the recovery USB but only if you haven’t changed anything yet! Make sure your USB works. You might need to turn on Legacy Support, USB Boot, disable Secure Boot or change the boot order.
If you don’t have a USB, use a CD and burn the Super Grub2 Disk ISO onto the CD.
If you don’t have a CD or a USB stick, you must be very careful because you are making changes to boot processes of your computer. If you reboot, or power goes out, or your battery dies during the changeover process, you will have a big problem and most likely be unable to boot.
Do not proceed without a bootable drive, or second computer handy. I once had to install bootable EFI files onto my phone’s SD card and then try to boot into the SD card slot! Waste of time, get a USB handy.
Step 2: Check if you are using GPT or MBR partitioning
Since Arch linux is 64 bit by default, we skip a step here in figuring out whether we want 32bit or 64bit rEFInd.
Get GParted and Gnome Disks to edit disks with the GUI as command line will take hours.
sudo pacman -S gnome-disks gparted
Open BOTH gparted and Gnome Disks and check ALL the drives in both of those programs to check which drives are connected to your PC.
Make sure GPARTED and Gnome Disks show the EXACT same drives and order of all the partitions. I have experienced a discrepancy before where a drive was showing “Empty/Unallocated” in Gnome Disks but showing up perfectly in GParted. This is scary stuff. <– If this error happened to you, scroll to bottom I will explain how I saved my data
Check your drives in the shell terminal by first listing your removable media
And checking all of the sdX and nvmeX drives with fdisk -l to verify what Partition Tabling they are using.
DOS/MBR Partition can boot from the normal MBR partition and you should install GRUB or rEFInd there.
If you have a MBR linux disk without the Master Boot Record, or Windows Boot Manager, it won’t boot and you should either change the disk to GPT by moving all the data first to a separate disk and then back after the partition table change or you should install GRUB2/rEFInd to another whole disk. If you have Windows (I don’t) you will probably have to install it .
For GRUB or rEFInd to boot from a GPT-partitioned disk on a BIOS-based system, a BIOS boot partition is required. This is the little ESP I’ve been mentioning.
If the device you want to install your boot partition on is GPT then rEFInd will attempt to mount this partition and install on the esp boot partiition that we will be making in this tutorial.
If you have DOS/MBR partitioning and you want GPT partitioning, you need to move all your files on that entire disk to a backup disk, change the partition table in GParted, and after we finish the tutorial, move your files back. If you only have the one drive you can’t do this and need to install rEFInd in the MBR partition.
If you don’t have an MBR partition and you’re on a MBR drive, you need to move files first.
Step 3: Partition the GPT disk with a fat32 esp partition
Serious error was incurred during this tutorial.
I used GPARTED to resize a MBR SSD disk to include a fat32 esp bootable partition after the main file system. Once changes were saved, the disk showed EMPTY and UNALLOCATED on Gnome Disks and did not even show the changes made on GParted. If this happens, use GParted to backup the partition with your data on it and start again. If you start creating new partitions over the top you will overwrite your data on that disk…
If it is a brand new drive with no data, open GParted, and select the device from the drop down menu, then select Device > Create Partition Table and choose GPT.
If you change the Partition Table on a drive with data on it, it will wipe the drive and make it GPT. You will lose all the data on that disk.
Once your drive is GPT, in GParted, create a little 2GB or so partition at the start with fat32 format and edit the flags to say esp.
Note: you can’t resize or create a little esp boot partition on the drive that you are currently booted on right now.
To install the rEFInd partition, you need to have a second disk inside the PC or you will not be able to partition the disk you are currently reading this on as it is live and mounted. GParted won’t let you resize this partition.
Once you have a little fat32 partiton (minimum 1-2GB) then you can run the rEFInd install script:
sudo pacman -S refind-install refind-install
# run again as first time it will mount the esp partition refind-install
Run it twice as it will mount the disk on the first run.
Having been using Photoshop on Linux since 2014, I have tried many approaches to running Photoshop CS 6 or the new Photoshop CC series on Wine and PlayOnLinux, but nothing came close to using Crossover.
Crossover is free to trial, but you can keep extending the trial, and use it for as long as you really want. To extend the trial just keep deleting the .eval file in your cxoffice folder:
# one of these commands will remove the evaluation file for Crossover on your PC once installed rm ~/.cxoffice/default/.eval rm ~/cxoffice/default/.eval
Photoshop Arch System Requirements:
Minimum 6GB of RAM
+ Swap Memory as Wine Server may hang and crash (LOSE UNSAVED WORK)
First, edit your pacman.conf to allow multilib packages to be used on Arch. Wine uses many lib32 32 bit libraries to run Windows based software.
sudo nano /etc/pacman.conf
Uncomment both the square bracket [multilib] line, and also the line under it that starts with “Include…”
[multilib] Include = /etc/pacman.d/mirrorlist
Update your system and it should show Multilib in package database.
sudo pacman -Syuu base-devel
Install the following bunch of required lib32 files that Wine needs:
How to enable Realtek Lenovo Wifi Card drivers in a 2019 Lenovo Ideapad built in 2019. Lenovo Ideapad needs a specific new WiFi driver called rtl8821ce. This package is only available on the Arch User Repository AUR at the time of writing from a guy named tomaspinho.
If you are doing a fresh Arch install on a new Lenovo ideapad, you will need an ethernet cable or a USB internet dongle or possibly hotspot/tether your mobile phone to get connected because the WiFi is not present on the Arch Live USB at time of writing.
Once you have internet, you will need an AUR manager or to build rtl8821ce from the git. You will also need dkms.
The following tutorial was done after the base install.txt was completed and may not work if done while chroot’ed in arch-chroot.
This installs linux-headers, required to match the kernel package and dkms.
Since our last dist-upgrade from Debian 8 Wheezy to Debian 9 Stretch, we’ve encountered quite a few new issues. By issues, I am referring to incompatibilities with any manual changes that I have made to my PC.
Most of the repositories that I have manually added have to be manually adjusted from wheezy to stretch. After that, we tried the usual sudo apt-get update and it never completed it’s course.
Stuck on 0% [Working]?
sudo apt-get install apt-transport-https
This one line solved the 0% Working issue where the package list downloading would hang and become stuck on Debian 9.
Only recently I found out Etcher.io didn’t make bootable Windows USB’s properly, or rather, did not support it at all.
There are 3 ways to make Windows Bootable USBs on Debian Ubuntu of any Linux distro, but first you’ll need a Windows ISO which Windows themselves now provide. Just search “Windows ISO” and make sure you’re at microsoft.com. At the time of writing, Windows was providing the Windows 10 ISO here.
1) Use WoeUSB on Ubuntu or Debian to make Bootable Windows USBs from ISO.
The deb packages for WoeUSB are found here, ignore the .exe files in this directory.
You’ll need to install VirtualBox (sudo apt-get install virtualbox) and then install a virtual Windows machine using the ISO from Microsoft.com at the start of this article.
You will also have to install VirtualBox Guest Additions to be able to passthrough the physical USB stick straight into the VirtualBox. To do that, boot your virtual machine, select Devices on the toolbar, and select insert Guest Additions CD. Install it, reboot, and you’ll now be able to connect your USB. To connect your USB, go to the virtual machine settings and add USB 2.0 or USB 3.0 support. You can only add USB support when the machine is off. If you haven’t installed the guest additions correctly, it will give you an error on booting.
If your VirtualBox doesn’t recognize the USB or fails to install drivers etc., make sure it’s formatted as Fat32 (use gnome-disks or gparted, might need to reformat it a few times with both programs).
When you boot the machine, bottom right of the virtual machine window has a small USB icon, right click it, and select the desired USB that you’d like to pass straight through to the VM.
Here is a screenshot of me successfully making a Bootable Windows USB using Rufus on a VirtualBox Windows 7 while my host OS is Debian.
3) Use another Windows PC to create the bootable USB.
Hacks, Tips, Tools, Setup, Tutorials, Guides and Reviews!