Erlang 3: Syntax in Functions

Introduction

Comments to the book "Learn You Some Erlang For Great Good" by Fred Hébert, Chapter 3 - Syntax in Functions. Pattern matching is much easier to achieve in Erlang than in many other languages, but the syntax takes some time to get used to. Instead of if-else or similar conditional branching, in Erlang you simply use functional declarations with a pattern. Learning goals: Being able to create pattern matching, retaining unbound vs unboundvariables, and how to work with guards. Challenges: Differences between unbound vs unboundvariables. Fully understanding how to work with guards.

Read more: Erlang 3: Syntax in Functions

XenServer Lab Setup: USB NIC

I am trying to set up a small footprint XenServer lab environment that does not have any single point of failure. That means two hosts in a pool, two NICs on every host and SR (storage repository), multiple paths between hosts and SR, and raid on the SR. The hosts are mini-PCs with only one PCI NIC. XenServer has been made for hardware with several PCI NICs, but with our setup, we will need to use USB NICs. That represents a few challenges.

In fact, USB NICs present so many challenges that they should not be used for production systems. Challenges include difficulties in setting up the USB NICs, reordering such NICs after installation, and the setup getting overwritten by XenServer updates (and possibly patches).

Read more: XenServer Lab Setup: USB NIC

Eric Eikrem posted a comment in Erlang 3: Syntax in Functions
You are right! Fixed. Thanks for heads-up
mammon88 posted a comment in Erlang 3: Syntax in Functions
You say that andalso, orelse can be nested inside guards. Example pls.
The Penguin posted a comment in Erlang 3: Syntax in Functions
Seems something's missing after "Running the code gives us:" ...
Erlanger posted a comment in Erlang 2: Modules
These Erlang articles are the same as those on https://erlangexplained.com? Good job, btw... ...
Eric Eikrem posted a comment in Two-Host XenServer Pool With Manual Fail-Over
Your question is a little short on detail, @KenoZ. If you could provide error messages and details o...