Updates alert shortcodes in learning articles.
This commit is contained in:
@@ -21,72 +21,72 @@ It's not really _that_ complicated.
|
||||
|
||||
At its core, the Internet is simply a bunch of computers that are connected together so they can pass data between them. People thought this was a good idea from the beginning with computers, but it was always hard to physically connect them, the data moved slow, and it was hard to make sure that the data got to to the other side uncorrupted. Also, even if you get two computers connected with a wire between them, what if you want to connect a dozen computers? Do you run a wire through all of them like a big circle or do you make it like a spider web with one sort of "hub" in the middle? And what if you want to connect one group to another group?
|
||||
|
||||
{{<alert icon="circle-info">}}
|
||||
{{<definition>}}
|
||||
**Network**: A group of computers connected together so they can pass data around.
|
||||
{{</alert>}}
|
||||
{{</definition>}}
|
||||
|
||||
Lot's of people and companies worked on a lot of ideas for a few decades to solve all these challenges. In 1969, some people working at UCLA, Stanford, UC Santa Barbara, and the University of Utah figured out a way to connect their computers together to pass data around. Do you think they knew at that moment that they had created something that would connect most of the computers in the world together!?
|
||||
|
||||
{{<alert icon="circle-info">}}
|
||||
{{<definition>}}
|
||||
**ARPANET**: The original network that connected these early computers together, and the precursor to the modern Internet. This public research project was funded by the U.S. Department of Defense's Advanced Research Projects Agency (ARPA), so they named their network ARPANET.
|
||||
{{</alert>}}
|
||||
{{</definition>}}
|
||||
|
||||
Over the next ten years, they connected more than 200 nodes (the name for a computer that is part of a network). Some as far away as London and Norway.
|
||||
|
||||
{{<alert icon="circle-info">}}
|
||||
{{<definition>}}
|
||||
**Node**: A computer that is part of a network (a "network node").
|
||||
{{</alert>}}
|
||||
{{</definition>}}
|
||||
|
||||
|
||||
{{<alert icon="heart" iconColor="red" cardColor="pink">}}
|
||||
{{<bring-it-home>}}
|
||||
Your wild cloud is a network of at least 8 nodes all running on your Local Area Network (LAN) and connected through a router to the Internet, also known as the Wide Area Network (WAN).
|
||||
{{</alert>}}
|
||||
{{</bring-it-home>}}
|
||||
|
||||
|
||||
## Introducing a common language (TCP/IP)
|
||||
|
||||
But, in the 1970s, other groups kept working on other ways to connect computers, and they developed their own networking protocols that were incompatible with the ARPANET. How could these different networks communicate with each other?
|
||||
|
||||
{{<alert icon="circle-info">}}
|
||||
{{<definition>}}
|
||||
**Protocol**: An agreed-upon way of doing something. If two people, or companies, or schools, **or machines**, use the same protocol, they can work together. People or machines using different protocols have a hard time getting along. Two computers that can talk together on a network are using the same "network protocol".
|
||||
{{</alert>}}
|
||||
{{</definition>}}
|
||||
|
||||
So, they figured out a common language to connect all these different networks, named it TCP/IP, and switched the ARPANET over to it in 1983.
|
||||
|
||||
{{<alert icon="circle-info">}}
|
||||
{{<definition>}}
|
||||
**TCP/IP**: The common language that connects different networks together. It if flexible because it breaks the problem into two parts, the Transmission Control Protocol (TCP) and the Internet Protocol (IP).
|
||||
{{</alert>}}
|
||||
{{</definition>}}
|
||||
|
||||
{{<alert icon="graduation-cap" cardColor="#ffdf78ff" iconColor="#fa6b0cff">}}
|
||||
{{<go-deeper>}}
|
||||
Vint Cerf and Bob Kahn developed TCP/IP, and explained how it works in their paper, [“A Protocol for Packet Network Intercommunication”](/papers/cerf74.pdf), which was published in IEEE Transactions on Communications, May 1974. Want to have some fun digging in? Try uploading this paper to ChatGPT or some other assistant and have a conversation about it! You'll know more about networking in an afternoon than many career software engineers. 😁
|
||||
{{</alert>}}
|
||||
{{</go-deeper>}}
|
||||
|
||||
TCP/IP gives every node on the Internet a unique address you can use to find it and talk to it. These are called "IP Addresses". Every device that talks to another device on the Internet has an IP address. These are the "###.###.###.###" format numbers where section is a number from 0-255. So, 192.168.1.0 is an IP address, and so is 10.10.10.10, and so it 56.122.200.27. TCP/IP can route data to your device just using its address... very similar to how letters get to your mailbox.
|
||||
|
||||
{{<alert icon="circle-info">}}
|
||||
{{<definition>}}
|
||||
**IP Address**: A unique string of numbers separated by periods that identifies _every_ computer on a TCP/IP network like the Internet. For example, `192.168.1.1` is an IP address.
|
||||
{{</alert>}}
|
||||
{{</definition>}}
|
||||
|
||||
{{<alert icon="heart" iconColor="red" cardColor="pink">}}
|
||||
{{<bring-it-home>}}
|
||||
Every computer that is a part of your wild cloud has a unique, local, IP address. Your LAN router, which also has an IP address, assigns unique IP addresses to each device on your LAN and keeps track of them.
|
||||
{{</alert>}}
|
||||
{{</bring-it-home>}}
|
||||
|
||||
|
||||
## Making it friendly (DNS)
|
||||
|
||||
But people don't think in numbers, people think in words or names, so a guy at the University of Southern California figured out a system he called the Domain Name System (DNS) in 1983. His system allowed IP addresses to be mapped to "domain names", so that now, somebody could use `wikipedia.org` instead of `198.35.26.96` (see that's easier to remember!) to address a particular computer. The DNS system is particularly interesting because it's design is much of the reason we have a resilient, distributed, non-centrally controlled Internet today. Any individual or organization can register their own unique domain name and control what computers IP addresses it maps to.
|
||||
|
||||
{{<alert icon="circle-info">}}
|
||||
{{<definition>}}
|
||||
**DNS**: The Domain Name System, which maps IP addresses to human-readable domain names (like `wikipedia.org`).
|
||||
{{</alert>}}
|
||||
{{</definition>}}
|
||||
|
||||
{{<alert icon="graduation-cap" cardColor="#ffdf78ff" iconColor="#fa6b0cff">}}
|
||||
{{<go-deeper>}}
|
||||
Paul Mockapetris wrote up his design in a working group he was a part of in 1983. You can read his paper ["DOMAIN NAMES - CONCEPTS and FACILITIES"](/papers/rfc882.txt.pdf). The design has been adapted a bit over the years, but if you spent an afternoon with ChatGPT digging into this paper, you'll know more about how the Internet works almost anyone. 😁
|
||||
{{</alert>}}
|
||||
{{</go-deeper>}}
|
||||
|
||||
{{<alert icon="heart" iconColor="red" cardColor="pink">}}
|
||||
{{<bring-it-home>}}
|
||||
When you set up a wild cloud, you will register a domain name at a domain registrar (Wild Cloud currently supports CloudFlare). You will then map this domain name to the applications on your wild cloud.
|
||||
{{</alert>}}
|
||||
{{</bring-it-home>}}
|
||||
|
||||
|
||||
## Conclusion
|
||||
|
@@ -9,9 +9,9 @@ summary: "Linux is more than just an operating system; it is a cornerstone of di
|
||||
|
||||
Back in the days before every desktop and laptop was sold as a "PC" or an "Apple", and every phone was an "Android" or an "iPhone", people had a better idea of what an "operating system" was. As the tech landscape consolidated around a few dominant players, their brands hid the reality that hardware and software were different things and that users had more than two choices. In fact, today, it is difficult to even find a computer that isn't pre-installed with one of the two dominant operating systems, Windows or macOS.
|
||||
|
||||
{{<alert icon="circle-info">}}
|
||||
{{<definition>}}
|
||||
The **operating** system is the name for the core software that makes individual hardware components of a computer work together, gives the user a way to interact with them, and makes it easy to write and run software applications on top of them. Operating systems make storage drives accessible as folders and files, turns screens into desktops, and allows you to use keyboards and mice to drive things. Operating systems load programs into memory and execute them on purpose-tailored hardware chips like central processing units (CPUs), graphical processing units (GPUs), and neural processing units (NPUs).
|
||||
{{</alert>}}
|
||||
{{</definition>}}
|
||||
|
||||
Apple makes all of their own hardware and they work hard to only allow only _their_ operating system, macOS run on it. Most of the rest of the hardware on the market, though, was created by a bunch of different companies who, in order to and compete, made their hardware more openly, collaborating together to specify standard ways of using and assembling their various components. Before Microsoft there were dozens of different operating systems that worked with this open hardware. Microsoft introduced one of the first text-based operating systems that could run on IBM and Intel hardware in 1982 (MSDOS), and their graphical operating systems (Windows 3.1) in 1993 and, through savvy business and legal positioning came to be the default operating system on over 90% of all personal computers.
|
||||
|
||||
@@ -61,9 +61,9 @@ To install Ubuntu on a virtual machine, follow these steps:
|
||||
|
||||
Wild Cloud recommends installing Ubuntu directly on a dedicated computer to be your operator machine. This provides the best performance and compatibility for running Wild Cloud operations.
|
||||
|
||||
{{<alert icon="circle-info">}}
|
||||
{{<definition>}}
|
||||
When you install Ubuntu directly on a computer without using WSL or a virtual machine, it's known as installing on "**bare metal**". ⚡
|
||||
{{</alert>}}
|
||||
{{</definition>}}
|
||||
|
||||
You can use just about any desktop or laptop computer made in the last 10 years as your operator machine. You can't install Ubuntu on Apple hardware, though. Just keep in mind you will probably want a lot of disk space for backups of your Wild Cloud either on your operator machine or on an attached external drive.
|
||||
|
||||
@@ -74,8 +74,8 @@ To install Ubuntu on a dedicated machine, follow these steps:
|
||||
3. Boot the dedicated machine from the USB drive. Many computers will allow you to do this by simply inserting the USB drive and restarting the computer. Some computers are not set to boot from the USB drive, though, so you'll need to access the boot menu (usually by pressing a key like F12, Esc, or Del immediately after turning on the computer) and select the USB drive as the boot device. If you can't figure out how to get to the boot menu, search for your computer model + "boot menu" the the search engine of your choice.
|
||||
4. Follow the prompts to install Ubuntu on the dedicated machine. There aren't a ton of options to pick and it usually doesn't take long, maybe a half-hour.
|
||||
|
||||
{{<alert icon="heart" iconColor="red" cardColor="pink">}}
|
||||
{{<bring-it-home>}}
|
||||
You will be doing everything to operate your Wild Cloud from your operator machine. Treat yourself and make it a nice one!
|
||||
{{</alert>}}
|
||||
{{</bring-it-home>}}
|
||||
|
||||
🛟 Need help with these instructions? Ask questions in the [Wild Cloud forum](https://forum.civilsociety.dev/t/wild-cloud-support/15).
|
Reference in New Issue
Block a user