Newsletter # 27 - rderik.com guides Jun 27 2020
Hello, and welcome to issue #27!
This week is an exciting week for all the Apple fans out there. A lot of new changes, as is the custom for WWDC. We finally got the announcement of the move to Apple Silicon (Apple's own ARM processors), which has been a rumour for some years now. If you are a macOS developer and are interested in building universal binaries that will run on both the Intel and ARM processors, you can apply to the Universal App Quick Start Program. The program costs $500.00 (USD), it includes a small computer with the new ARM processor, which sadly is owned by Apple and you have to return. But if you are interested, and meet their criteria, you'll have fun playing with it before anyone else.
If you want more information on the new ARM architecture I would suggest checking this WWDC20 session:
Explore the new system architecture of Apple Silicon Macs
Apple also introduced a lot of privacy enhancements to the Apple ecosystem( Build trust through better privacy - WWDC20 session). Now it'll be more visible what data are apps collecting when they are running. Which has made people aware of how some apps collect even the data in your clipboard. I could write here more about the most interesting sessions in WWDC20, but I'll save you from that. I wrote a list of the WWDC20 sessions that I'm more interested in, you can find it here:
I grouped them into categories, and I'm going to be adding some notes or related posts I've written in the past that might give some additional context to each session.
Ok, with WWDC20 out of the way, I wanted to share with you some useful links. First, an interesting article explaining the history of the UNIX man pages:
History of UNIX Manpages
The article gives a very detailed history of the Unix man pages, from where they started to the present state of man pages. Man pages contain a lot of useful information. They are not tutorials that go in-depth into how to use a specific command or system information. Man pages are helpful as references. For me, they serve as starting points where I can get enough information to solve a problem, and if I can't solve the problem with the information in the man page, at least I know what to search for.
Another cool link I want to share with you is this:
Amazon Web Services explained in one line each
Amazon has a gigantic list of services. The list is so long that it makes it hard to navigate and keep it straight. But the list in the link summarises and clearly groups the services for easier understanding. If you are searching for platform as a service and you were thinking of using AWS, this might help. I hope you find the links useful.
As you know, I've been playing around with FreeBSD, and I'm really enjoying my time. So much so that I decided to write a small guide on jails and virtual networks. You can check it here:
I plan on releasing more guides in the future for different topics. The guides focus on solving specific problems and cover topics that are hard to cover on a blog post. They are longer and go more in-depth. So if you would like me to write a guide on a specific topic, let me know.
You can pay whatever amount you like at the checkout. You can set $0.00, and you'll get it for free :). I would encourage you to download it for free first, read it, and if it was useful and you would like to support my work, buy it and pay what you think is reasonable.
If you are looking for a simpler read on how to jail a service in FreeBSD, I also wrote a post on running a jailed web server in FreeBSD the easy way:
I hope you find it useful. Ok, that's it for this newsletter.
Let me know what you think about the guides section, any suggestions and feedback are always welcomed.
Have a good weekend,
Tip of the week
Talking about man pages, as you might know, man pages are divided into different sections:
1 2 3 4 5 6 7 8 1. User Commands 2. System Calls 3. C Library Functions 4. Devices and Special Files 5. File Formats and Conventions 6. Games et. Al. 7. Miscellanea 8. System Administration tools and Deamons
If you haven't noticed when I mention a command, I always try to include the man section the command belongs to so you can search the man page for more information. For example,
If you are checking the man page of a term you'll get different entries depending on the section you are searching for. For example:
1 2 3 4 5 #Show the entry for printf in the user commands $ man 1 printf #Show the entry for printf in the C library functions $ man 3 printf
This weeks tip is for you to read the Intro for each of the man sections. They are very informative and will give you a better grasp of where to search when you need information on any part of your system. To do this do a:
1 $ man <SECTION> intro
1 $ man 3 intro
The introduction sections are short but packed with a lot of useful information.