How To: Install Docker for Mac

Docker for Mac

Turns out, plenty of native macOS apps can be installed using the brew package manager. Among them is Docker, so I decided to try how it installs and works.

Docker for Mac

The easiest is, of course, just to use the native installer provided by Docker maintaners: you download the Docker.dmg file, install it and end up with an app called Docker Desktop:

Install Docker with brew

But since I wanted to try more automated install, I used brew:

greys@maverick:~ $ brew cask install docker
 ==> Satisfying dependencies
 ==> Downloading https://download.docker.com/mac/stable/37199/Docker.dmg
 Already downloaded: /Users/greys/Library/Caches/Homebrew/downloads/01aa470f5479ce702d59bc8d825681bca704ab964279558efd5a2187b126791c--Docker.dmg
 ==> Verifying SHA-256 checksum for Cask 'docker'.
 ==> Installing Cask docker
 ==> Moving App 'Docker.app' to '/Applications/Docker.app'.
 🍺  docker was successfully installed!
 You have mail in /var/mail/greys

That was it! Overall – great improvement of the steps I would normally take to install Docker.

Upon starting this /Applications/Docker.app for the first time, I got the security prompt:

But that’s it – after that Docker worked exactly the same and had the very same versions of all the components:

Will be trying my most used software installs using brew, it seems a great way to be downloading/installing software in bulk – should be great for new laptop setup (if/when I get it) – I have been upgrading macOS in-place for the past 5 years or so, and think it will be awesome to someday migrate to a brand new clean macOS setup.

Get X11 Forwarding In macOS High Sierra

I needed to forward X11 output from one of my Linux servers recently to run virt-manager (manager for virtual machines in KVM), and because it’s been a while I had to download and install X11 server again.

As some of you know, Xorg server is no longer shipped/installed with macOS by default. So you have to download it from XQuartz page: https://www.xquartz.org/releases/index.html. Usually you do it, install it and that’s it – no additional steps are needed.

But things are slightly different for the macOS High Sierra, apparently.

The latest release hasn’t been updated since 2016 which I believe is before High Sierra – which explains why things don’t “just work” anymore. Fear not though – I tracked the issue down and it’s explained below.

UPDATE 03/2019: MacOS Mojave works just great, you may skip Step 3 in the procedure below.

Steps to get X11 Forwarding in macOS High Sierra

Download and install the latest release from xquartz.org website
Start XQuartz
IMPORTANT: verify xauth location
SSH configuration file /etc/ssh/ssh_config might contain path to xauth tool, which may be incorrect depending on your OSX/MacOS version. Here’s how to check:
```
greys@maverick:~ $ grep xauth /etc/ssh/sshd_config
```
if this returns nothing, you can skip to Step 4 below. If this gives you an output, compare it to the path from the next command:
```
greys@maverick:~ $ which xauth
/opt/X11/bin/xauth
```
If the locations differ, update the /etc/ssh/ssh_config file:
```
greys@maverick:~ $ sudo vi /etc/ssh/ssh_config
```
Connect to remote server using -X option which does X11 forwarding for SSH:
```
greys@maverick:~ $ ssh -X centos.unixtutorial.or
```
Check the DISPLAY variable, it should now be set correctly:
```
greys@centos:~ $ echo $DISPLAY
localhost:10.0
```

That’s it for today!

Backblaze 6.0 released

Screen Shot 2019-02-09 at 11.25.41.png

Backblaze just updated to version 6.0 earlier this week. If you didn’t know, Backblaze is possibly the best cloud backup solution that exists for Mac/Windows clients. It also supports a lot of open-source, free and commercial tools for Linux backup (Duplicity, qBackup, etc) via Backblaze B2 solution – plus there’s an API you can use for programmatically managing your backups strategy.

Backblaze Hard Drive Stats

Before I start talking about Backblaze Cloud Backup, I just want to mention another great thing Backblaze do – and it’s actually how I discovered them many years ago: Backblaze Hard Drive Stats (for 2018).

Because Backblaze are using so many hard disks in their datacentres, they are going through a number of makes and models, so every few months there’s an updated chart of how many disks fail. These are enterprise grade disks, so you’re unlikely to be buying the same models for your desktop PC, but I found these useful when building my very first home-grown mdadm based RAID arrays. I’ve moved on to Synology NAS since then but consult Backblaze hard drive stats regularly when shopping for new disks. Highly recommended!

Backblaze backup for MacOS

I’ve been a Backblaze user for 3 years now, with backed up amount growing steadily over the years. I have yet to require a full restore (fingers crossed!) but have used the Backblaze cloud via desktop and especially on iPhone for quickly accessing a file or two. Because Backblaze is a continuous backup solution, it’s a great option for accessing any of my laptops’ (backed up) files remotely from my iOS devices.

Backblaze for personal use and small businesses charges per backed up computer and not per amount of data you backup. You can’t backup network drives, but can backup any USB disks – so what I do is plugin a 3TB disk every few weeks, make important backups from my network storage to it, and then Backblaze picks it up and puts it into the cloud.

Backblaze 6.0 improvements

apparently, it’s 50% faster app now!
it’s now possible to prevent backups on certain WiFi networks (like mobile hotspot ones) using built-in Network Management
it’s possible to save certain files into B2 cloud (enterprise offering) – this will cost extra ($0.005 gigabyte/month I think – so still pretty cheap at $5 per TB) but should allow API access to your backups and many other really cool things

Why I like Backblaze Cloud Backup

Backblaze Pricing Model

Pricing is per computer system, not per amount of data. So your data needs will grow, but that won’t mean you’ll have to pay more.

I have 2TB of data stored in Backblaze and think it’s a great value for money:

Screen Shot 2019-02-09 at 11.35.34.png

Steady and Fast Performance

Never had any complaints at all, very solid application on MacOS with straightforward interface and easy to read stats. You can throttle network traffic so that backups don’t kill your home internet, so it’s a well implemented solution.

Backup State Inheritance

This I had used a few times – needed to move from one disk to another. So if I replace my external hard disk with a newer and/or larger model – instead of having to re-upload everything from scratch, I can just point Backblaze to the new disk and help it inherit the backup state from the previous disk. Granted, I have to make sure new disk has the same data the old disk had first! 🙂

Backup Restores by mail

Never used it, but someday probably will! For large or full restores, it’s faster to get your backup data on a disk or USB flash disk, rather than download it all from the cloud. For a reasonable enough fee, Backblaze can send you a hard disk with your data so that you an restore faster it and then send the disk back.

That’s it for today! Just wanted to share and to recommend Backblaze. If you decide to check it out, please use my affiliate link: https://secure.backblaze.com/r/01gyum

Creating bootable USB from ISO in MacOS

I needed to reinstall one of my Windows PCs at home recently, and realised that I only have Windows 7 DVDs, but no Windows 10s.

Since it’s possible to boot and install Windows 10 from USB, that’s what I decided to do: download Window 10 ISO and burn it one of the USB sticks I have. This approach will be simpler for any other ISO image like Ubuntu or CentOS, so there’s a separate Steps 3-5 for them at the end of the post.

Here are the steps I had to take on my MacBook, originally procedure was written in macOS High Sierra, but I tested it in MacOS Mojave 10.14.2 as well. All of these need to be done in the Terminal app.

Windows 10 bootable USB vs Linux ISO USB

Windows 10 is a very specific bootable media, so the process is a bit involved. For generic Linux installation ISOs this procedure would be simpler. So the first two steps are the same, then Windows and Linux have separate procedure.

Here’s what we will do for Windows ISO:

erase USB stick and create MBR (master boot record)
format USB stick with FAT-32 filesystem
mount Windows 10 ISO image as a folder
copy all the files from that folder onto the USB stick

Here’s what we would do for Linux ISO:

use dd command to burn Linux installation ISO onto USB stick

Step 1: Confirm partitions before inserting USB

Use the diskutil command to list all disks and partitions on your Mac. This is simply so that you can run the same command again after inserting USB and easily spot the USB device.

greys@maverick:/ $ diskutil list
/dev/disk0 (internal):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme 500.3 GB disk0
1: EFI EFI 314.6 MB disk0s1
2: Apple_APFS Container disk1 500.0 GB disk0s2

/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +500.0 GB disk1
Physical Store disk0s2
1: APFS Volume Macintosh HD 466.2 GB disk1s1
2: APFS Volume Preboot 24.3 MB disk1s2
3: APFS Volume Recovery 519.0 MB disk1s3
4: APFS Volume VM 12.3 GB disk1s4

/dev/disk2 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme +30.0 GB disk2
1: EFI EFI 209.7 MB disk2s1
2: Apple_APFS Container disk3 29.8 GB disk2s2

/dev/disk3 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +29.8 GB disk3
Physical Store disk2s2
1: APFS Volume Photos 9.2 GB disk3s1

/dev/disk4 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: Apple_partition_scheme +173.1 MB disk4
1: Apple_partition_map 32.3 KB disk4s1
2: Apple_Driver_ATAPI 4.1 KB disk4s2
3: Apple_HFSX Firefox 173.0 MB disk4s3

/dev/disk5 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme +80.0 MB disk5
1: Apple_APFS Container disk6 80.0 MB disk5s1

/dev/disk6 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +80.0 MB disk6
Physical Store disk5s1
1: APFS Volume Raven-Core 70.1 MB disk6s1

/dev/disk7 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme +18.1 MB disk7
1: Apple_HFS F-Secure XFENCE 18.1 MB disk7s1

/dev/disk8 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *3.0 TB disk8
1: EFI EFI 209.7 MB disk8s1
2: Apple_HFS Backups 3.0 TB disk8s2

Step 2: Insert USB stick an re-run diskutil list

This time I can see there’s a disk9 showing up, with 64GB of size which matches my USB stick size:

greys@maverick:/ $ diskutil list
/dev/disk0 (internal):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme 500.3 GB disk0
1: EFI EFI 314.6 MB disk0s1
2: Apple_APFS Container disk1 500.0 GB disk0s2

/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +500.0 GB disk1
Physical Store disk0s2
1: APFS Volume Macintosh HD 466.2 GB disk1s1
2: APFS Volume Preboot 24.3 MB disk1s2
3: APFS Volume Recovery 519.0 MB disk1s3
4: APFS Volume VM 12.3 GB disk1s4

/dev/disk2 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme +30.0 GB disk2
1: EFI EFI 209.7 MB disk2s1
2: Apple_APFS Container disk3 29.8 GB disk2s2

/dev/disk3 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +29.8 GB disk3
Physical Store disk2s2
1: APFS Volume Photos 9.2 GB disk3s1

/dev/disk4 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: Apple_partition_scheme +173.1 MB disk4
1: Apple_partition_map 32.3 KB disk4s1
2: Apple_Driver_ATAPI 4.1 KB disk4s2
3: Apple_HFSX Firefox 173.0 MB disk4s3

/dev/disk5 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme +80.0 MB disk5
1: Apple_APFS Container disk6 80.0 MB disk5s1

/dev/disk6 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +80.0 MB disk6
Physical Store disk5s1
1: APFS Volume Raven-Core 70.1 MB disk6s1

/dev/disk7 (disk image):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme +18.1 MB disk7
1: Apple_HFS F-Secure XFENCE 18.1 MB disk7s1

/dev/disk8 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *3.0 TB disk8
1: EFI EFI 209.7 MB disk8s1
2: Apple_HFS Backups 3.0 TB disk8s2

/dev/disk9 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: NONAME *62.1 GB disk9

Chances are, your USB stick has a PC standard FAT16/FAT32 filesytem, and will be mounted automatically. Let’s check:

greys@maverick:/ $ df -h | grep disk9
/dev/disk9 4.1Gi 4.1Gi 0Bi 100% 18446744073707414141 2138557 1704874683337099264% /Volumes/NONAME

Sure enough, it’s mounted as /Volumes/NONAME!

Creating Windows bootable USB

IMPORTANT: these steps are only needed for Windows ISOs. If you’re burning a Linux ISO, skip this and go to the Creating Linux bootable USB section below, it has its own steps.

Step 3: format USB stick for Windows boot

This single command will erase the USB stick, make it bootable by adding a Master Boot Record (MBR) and create a Windows-friendly filesystem (FAT) on it:

greys@maverick:~ $ diskutil eraseDisk MS-DOS "WIN10" MBR disk9
Started erase on disk9
Unmounting disk
Creating the partition map
Waiting for partitions to activate
Formatting disk9s1 as MS-DOS (FAT) with name WIN10
512 bytes per physical sector
/dev/rdisk9s1: 30000480 sectors in 1875030 FAT32 clusters (8192 bytes/cluster)
bps=512 spc=16 res=32 nft=2 mid=0xf8 spt=32 hds=255 hid=2048 drv=0x80 bsec=30029824 bspf=14649 rdcl=2 infs=1 bkbs=6
Mounting disk
Finished erase on disk9

You’ll have the new filesystem mounted automatically, as you can see it’s empty (1.1MB used of 14GB):

greys@maverick:/ $ df -h | grep disk9
/dev/disk9s1 14Gi 1.1Mi 14Gi 1% 0 0 100% /Volumes/WIN10

Great stuff, now we’re moving to the next phase: we need to mount the Windows ISO image as a folder and then copy all the files onto the freshly formatted /Volumes/WIN10 USB stick.

Step 4: Mount Windows ISO

Simply go to the directory where you have the ISO image and run the open command for it:

greys@maverick:/Volumes/SSD $ open ./Win10_1607_English_x64.iso

You’ll have the MacOS Finder window with Windows ISO content pop-up, just ignore it and go back to the terminal.

You should now have it mounted under folder like this:

greys@maverick:/Volumes/SSD $ df -h | grep EN-US
/dev/disk8 4.1Gi 4.1Gi 0Bi 100% 18446744073707414141 2138557 1704874683337099264% /Volumes/CCSA_X64FRE_EN-US_DV5

Go into that folder and do ls to make sure you can see Windows DVD files there:

greys@maverick:/Volumes/SSD $ cd /Volumes/CCSA_X64FRE_EN-US_DV5/
greys@maverick:/Volumes/CCSA_X64FRE_EN-US_DV5 $ ls
autorun.inf boot bootmgr bootmgr.efi efi setup.exe sources support

Excellent!

Step 5: Copy Windows files onto USB stick

Right, now we have to copy all the files from DVD ISO image onto our new USB stick.

IMPORANT: you should be in the /Volumes/CCSA_X64FRE_EN-US_DV5 directory when running this command below. That’s exactly where you are if you just completed Step 4.

The copy will take good 10-15min:

$ sudo cp -r . /Volumes/WIN10/
Password:

There should be no errors returned.

If you remember, in Step 3 we did the df command and the USB filesystem /Volumes/WIN10 was empty.

Just to get an idea that the copy was successful, let’s run the df command again to make sure the USB stick has roughly the same amount taken up now – 4.1GB as per output fragments in previous step.

greys@maverick:/ $ df -h | grep WIN10
/dev/disk7s1 14Gi 4.1Gi 10Gi 29% 0 0 100% /Volumes/WIN10

Looks good! What’s left now is to eject the USB stick:

greys@maverick:/ $ diskutil unmountDisk /dev/disk9
Unmount of all volumes on disk9 was successful

and to boot it on the PC as shown below.

Step 6: Boot USB stick on your PC

IMPORTANT: recent enough PCs will likely offer you both legacy boot and UEFI boot. The rule of thumb is to boot UEFI if it’s available, especially if you’re booting Windows USB stick:

Select UEFI Boot Device - USB.jpg

Creating Linux bootable USB

As I said earlier, non-Windows ISOs are much easier to deal with! So after the first 2 generic steps at the start of this post, we’ll be taking separate steps for Linux as shown below.

We need to unmount the USB disk we found in Step 2. It’s /dev/disk9 in our case:

greys@maverick:/ $ diskutil unmountDisk /dev/disk9
Unmount of all volumes on disk9 was successful

Step 3: convert ISO into bootable DMG

WARNING: this is an important step, without it your USB stick won’t boot.

So I have this DVD ISO of the CentOS 7.4, let’s convert it before burning onto the USB stick.

$ hdiutil convert -format UDRW -o centos ./CentOS-7-x86_64-DVD-1708.iso
 Reading Master Boot Record (MBR : 0)… 
Reading CentOS 7 x86_64 (Apple_ISO : 1)…
 Reading (Type EF : 2)…
 Reading CentOS 7 x86_64 (Apple_ISO : 3…
............................................................. 
Elapsed Time: 10m 15.681s
 Speed: 7.0Mbytes/sec
 Savings: 0.0% 
created: /Volume/Stuff/dist/centos.dmg

Step 4: write DMG image onto USB stick with dd

Exellent, now we are ready to burn the ISO image. Let’s cd into the directory with all the ISOs that you have and burn it using the dd command.

dd command runs with the help of 3 command line parameters:

if – specifying source data, that’s our ISO image file
of – specifying the destination file or device, /dev/disk9 in our case
bs – block size, just needs to be something big enough like 1m (meaning 1 megabyte)

greys@maverick:/ $ cd /Volumes/Stuff/dist 
greys@maverick:/Volumes/Stuff/dist $ sudo dd if=./centos.dmg of=/dev/disk9 bs=1m

Depending on the ISO size and the USB stick speed, you’ll have to wait 10-20min for this to complete.

Useful tip (cheers Jim!): if you want to confirm your current process, press Ctrl+t in the Terminal app and it should update output with dd progress (I highlighted the output below every tipe I pressed Ctrl+t):

load: 2.53 cmd: dd 11985 uninterruptible 0.00u 0.05s
83+0 records in
82+0 records out
85983232 bytes transferred in 7.441006 secs (11555324 bytes/sec)
load: 2.48 cmd: dd 11985 uninterruptible 0.01u 1.26s
2248+0 records in
2247+0 records out
2356150272 bytes transferred in 222.985555 secs (10566381 bytes/sec)
load: 2.24 cmd: dd 11985 uninterruptible 0.01u 1.94s
3422+0 records in
3421+0 records out
3587178496 bytes transferred in 339.752252 secs (10558218 bytes/sec)

finally, dd will complete a message like this:

4177+1 records in
4177+1 records out
4380387328 bytes transferred in 415.014562 secs (10554780 bytes/sec)

Step 5: Boot USB stick on your PC

That’s it, we’re done! Eject the USB stick (no need to run any diskutil commands as it wasn’t mounted automaticaly) and boot on your PC.

IMPORTANT: recent enough PCs will likely offer you both legacy boot and UEFI boot. The rule of thumb is to boot UEFI if it’s available:

How To List Disks and Partitions in MacOS

Not every Mac user is aware that we’ve got one of the truest Unix operating systems under the great look user interface in MacOS.

That’s why almost everything that you can do using graphics interface and MacOS apps, can also be accomplished using a command line (start the Terminal app).

To get the list of partitions in MacOS, and to learn their sizes and filesystem types, use the diskutil command:

greys@maverick:~ $ diskutil list
/dev/disk0 (internal):
# : TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme 500.3 GB disk0 1: EFI EFI 314.6 MB disk0s1 2: Apple_APFS Container disk1 500.0 GB disk0s2

/dev/disk1 (synthesized):
# : TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +500.0 GB disk1 Physical Store disk0s2 1: APFS Volume Macintosh HD 446.2 GB disk1s1 2: APFS Volume Preboot 27.9 MB disk1s2 3: APFS Volume Recovery 519.0 MB disk1s3 4: APFS Volume VM 9.7 GB disk1s4

/dev/disk2 (disk image):
# : TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme +30.0 GB disk2 1: EFI EFI 209.7 MB disk2s1 2: Apple_APFS Container disk3 29.8 GB disk2s2

/dev/disk3 (synthesized):
# : TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +29.8 GB disk3 Physical Store disk2s2 1: APFS Volume Photos 9.2 GB disk3s1

/dev/disk4 (external, physical):
# : TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *120.0 GB disk4 1: EFI NO NAME 536.9 MB disk4s1 2: Linux Filesystem 21.5 GB disk4s2 3: Linux Filesystem 98.0 GB disk4s3

Mounting NFS shares on Mac OS X

I’ve recently decided to give Mac OS X a try. For the past week or so I’ve been spending a good few hours a day working in Snow Leopard installed on a MacBook Pro borrowed from a friend.

While Mac OS is unlike any Unix-like operating system I’ve managed so far, there are certainly some of similarities. I can honestly say that I’m enjoying the Mac Book Pro so far, and hope to discover most of the differences compared to my previous Unix-like desktop which is Ubuntu 9.10.

Mounting NFS on MAC OS X

One thing which I noticed immediately was that out of the box it was impossible to mount any NFS shares from my Ubuntu NAS server. Any attempt to mount a remote filesystem would give me an error like this:

mbp:~ root# mount nasbox:/try /mnt
mount_nfs: /mnt: Operation not permitted

This error was happening for a relatively simple NFS share on the Ubuntu box:

nasbox# cat /etc/exports
/try            (rw)

… so I started looking around and realised that the reason for this strange problem is quite simple.

Mac OS X uses non-standard port for outgoing NFS connections

That’s right! Apparently, Mac OS X uses a non-privileged port (2049) for TCP and UDP connections serving the NFS transport. What this means is that most likely attempts to mount remote filesystems will fail, because most NFS servers don’t really like connections from insecure ports.

There are two ways to approach this problem:

Fix it on the client side (probably makes more sense)
Fix it on the NFS server side (if you manage both systems)

Using reserved NFS port number on Mac OS X

There’s a mount option supported by the mount_nfs command, which allows you to force the NFS client connections to originate from a privileged port. This will magically make your attempts to mount remote filesystems successful. The option is called resvport.

First we double-check that default mounts still don’t work:

mbp:~ root# mount nasbox:/try /mnt
mount_nfs: /mnt: Operation not permitted

… and now let’s use the resvport option:

mbp:~ root# mount -o resvport nasbox:/try /mnt

… and make sure we’re actually looking at a mounted filesystem:

mbp:~ root# df -h /mnt
Filesystem   Size   Used  Avail Capacity  Mounted on
nasbox:/try    61Gi   56Gi  2.6Gi    96%    /mnt

Allowing connections from non-privileged ports on NFS server

Like I said, if you manage both the Mac OS based client and the NFS server, perhaps it makes more sense to relax the default NFS server security and allow the connections from non-privileged ports.

Just to remind you about the validity of such a decision, the option to allow non-privileged connections is called insecure.

Here’s how you use it:

nasbox# cat /etc/exports
/try            (rw,insecure)

After making this change to the /etc/exports file, you’ll have to restart your NFS server. On my Ubuntu NAS box, it’s done like this:

nasbox# /etc/init.d/nfs-kernel-server restart
* Stopping NFS kernel daemon
...done.
* Unexporting directories for NFS kernel daemon...
...done.
* Exporting directories for NFS kernel daemon...
...done.
* Starting NFS kernel daemon
...done.

We know are ready to attempt the default mount of the same filesystem on the Mac OS X client:

mbp:~ root# mount nasbox:/try /mnt

That’s it! I won’t promise any Mac OS posts just yet, but if there is enough interest – I’d love to do the research and to post all the discoveries on the Unix Tutorial pages.

How To: Install Docker for Mac

Docker for Mac

Install Docker with brew

See Also

Get X11 Forwarding In macOS High Sierra

Steps to get X11 Forwarding in macOS High Sierra

See Also

Backblaze 6.0 released

Backblaze Hard Drive Stats

Backblaze backup for MacOS

Backblaze 6.0 improvements

Why I like Backblaze Cloud Backup

Backblaze Pricing Model

Steady and Fast Performance

Backup State Inheritance

Backup Restores by mail

See Also

Creating bootable USB from ISO in MacOS

Windows 10 bootable USB vs Linux ISO USB

Step 1: Confirm partitions before inserting USB

Step 2: Insert USB stick an re-run diskutil list

Creating Windows bootable USB

Step 3: format USB stick for Windows boot

Step 4: Mount Windows ISO

Step 5: Copy Windows files onto USB stick

Step 6: Boot USB stick on your PC

Creating Linux bootable USB

Step 3: convert ISO into bootable DMG

Step 4: write DMG image onto USB stick with dd

Step 5: Boot USB stick on your PC

See Also

How To List Disks and Partitions in MacOS

Mounting NFS shares on Mac OS X

Mounting NFS on MAC OS X

Mac OS X uses non-standard port for outgoing NFS connections

Using reserved NFS port number on Mac OS X

Allowing connections from non-privileged ports on NFS server

See Also