Linux Basics for Technicians: A CompTIA Study Guide

WEBVTT
00:00:26.640 --> 00:00:28.480
And welcome to Technology Tap.
00:00:28.559 --> 00:00:29.359
I'm Professor J.
00:00:29.519 --> 00:00:29.839
Rod.
00:00:30.079 --> 00:00:33.920
In this episode, we're going to talk about other operating systems like Linux.
00:00:34.079 --> 00:00:35.280
Let's tap in.
00:01:14.319 --> 00:01:16.719
They don't really actually understand computers.
00:01:16.959 --> 00:01:18.560
That they understand interfaces.
00:01:18.719 --> 00:01:19.599
They understand buttons.
00:01:19.680 --> 00:01:22.319
They understand menus and where to click.
00:01:22.640 --> 00:01:30.959
But they don't understand what the system is actually doing, why commands exist and how the OS is structured.
00:01:31.519 --> 00:01:34.640
And Linux exposes that immediately.
00:01:35.439 --> 00:01:37.280
Welcome back to Technology Tap.
00:01:37.359 --> 00:01:38.480
I'm Professor J Rod.
00:01:38.719 --> 00:01:47.120
I love helping students pass their A, Network Plus, and Security Plus Camp Tia series of exams.
00:01:47.519 --> 00:01:52.480
I'm also like to dabble into technology history.
00:01:52.799 --> 00:02:03.840
I'm an author of Scamproof for Seniors, which is available on my website, Professor Jrodj R O D.com slash books, and it's also available on Amazon.
00:02:04.879 --> 00:02:14.719
You can reach me all sorts of social media, TikTok at Professor Jrod, Instagram at Professor Jrod, Facebook, TechnologyTap Podcast.
00:02:15.199 --> 00:02:26.719
And today we're stepping into something that separates users from technicians because supporting multiple operating systems is not about memorizing command, it's about understanding how systems think.
00:02:26.960 --> 00:02:32.080
And Linux is the best place to start because Linux does not hide anything from you.
00:02:32.800 --> 00:02:35.759
When most people first open Linux, they feel lost.
00:02:35.919 --> 00:02:40.479
There is no smart menu, no familiar layout, no click here to fix it.
00:02:40.639 --> 00:02:42.800
And that's not the weak, and that's not a weakness.
00:02:42.879 --> 00:02:44.000
That's the design.
00:02:44.240 --> 00:02:46.639
Linux assumes something very important.
00:02:47.199 --> 00:02:49.280
You are responsible for the system.
00:02:49.919 --> 00:02:59.360
Linux is an open source operating system that provides direct control over systems operation, command line interaction, and flexible configuration across environments.
00:02:59.599 --> 00:03:02.800
Unlike Windows, there is no single standard interface.
00:03:02.960 --> 00:03:08.240
There's no assumption of simplicity, and there's no protection from mistakes.
00:03:08.560 --> 00:03:15.039
In enterprise environments, servers run Linux, security tools run on Linux, and cloud infrastructure run on Linux.
00:03:15.199 --> 00:03:19.039
So when you learn Linux, you're not learning another operating system.
00:03:19.199 --> 00:03:23.199
You're learning how systems are actually controlled under the hood.
00:03:24.319 --> 00:03:28.560
In Windows, actions are often clicked, confirm, and done.
00:03:28.719 --> 00:03:32.719
In Linux, actions are command, intent, and consequences.
00:03:33.039 --> 00:03:39.599
That difference matters because Linux forces you to answer what exactly am I trying to do?
00:03:40.159 --> 00:03:42.879
At the center of Linux is something called a shell.
00:03:43.680 --> 00:03:49.039
A shell is a program that interprets users' commands and communicates with the operating system kernel.
00:03:49.439 --> 00:03:53.360
It is not visual, it is not decorative, it is functional.
00:03:53.759 --> 00:03:56.879
And this is where many students struggle.
00:03:57.199 --> 00:03:59.680
Terminal is what you interact with.
00:04:00.000 --> 00:04:03.039
Shell is what processes your command.
00:04:03.599 --> 00:04:08.240
You open a terminal, you type ls in the command.
00:04:08.319 --> 00:04:09.120
What happens?
00:04:09.280 --> 00:04:13.759
The terminal sends input, the shell interprets ls.
00:04:14.400 --> 00:04:18.879
The OS executes the command and the output is the return.
00:04:19.120 --> 00:04:21.360
And ls is like DIR, right?
00:04:22.240 --> 00:04:23.519
List structures.
00:04:23.759 --> 00:04:24.720
Why this matters?
00:04:24.879 --> 00:04:28.879
Because when something breaks, you're not clicking around hoping.
00:04:29.120 --> 00:04:32.000
You are issuing instructions to the system.
00:04:32.800 --> 00:04:37.519
Linux commands are not random, they follow structure.
00:04:37.839 --> 00:04:41.600
Command plus options plus arguments.
00:04:42.079 --> 00:04:43.600
So here's an example.
00:04:43.920 --> 00:04:46.720
Command, the action which you want to perform.
00:04:46.800 --> 00:04:49.040
So the example will be ls.
00:04:49.600 --> 00:04:52.240
The options modifies the behavior.
00:04:52.399 --> 00:04:58.959
Example, if you type minus L right after LS, you want detailed view.
00:04:59.120 --> 00:05:01.439
And the argument, you specify the target.
00:05:01.680 --> 00:05:03.519
Example slash home.
00:05:04.000 --> 00:05:10.079
So full example will be ls space minus l space slash home.
00:05:10.399 --> 00:05:15.839
This means list files show detailed information in the home directory.
00:05:16.079 --> 00:05:17.279
Now why does this matter?
00:05:17.439 --> 00:05:23.519
Because if you misunderstood or misunderstand the structure, you just don't get the wrong results.
00:05:23.680 --> 00:05:28.000
You can modify the wrong file, delete the wrong directory, or break the system.
00:05:29.040 --> 00:05:31.199
Linux is also case sensitive.
00:05:31.439 --> 00:05:37.600
Case sensitive means upper and lowercase are treated as completely different values.
00:05:37.920 --> 00:05:44.079
File.txt with capital F is different from file.txt with lower F.
00:05:44.399 --> 00:05:46.079
There are two different files.
00:05:47.199 --> 00:05:55.360
A student runs CD space documents, but the folder is documents with a lower D results failure.
00:05:55.600 --> 00:05:59.920
Not because the system is broken, because precisions matter.
00:06:01.120 --> 00:06:08.480
One of the biggest mistakes new technicians make is that they try to fix things before understanding where they are.
00:06:08.959 --> 00:06:10.800
Where am I in the system?
00:06:12.160 --> 00:06:21.839
Linux has a command called PWE, which is defined as prints the working print the working current directory.
00:06:22.160 --> 00:06:24.480
Or print the working directory, right?
00:06:24.800 --> 00:06:30.240
So if you type in PWD, it should give you what directory you are now at.
00:06:31.439 --> 00:06:34.639
Because without context, you're operating blindly.
00:06:36.720 --> 00:06:38.480
Another example is CD, right?
00:06:38.639 --> 00:06:39.759
You should be familiar with that.
00:06:40.000 --> 00:06:42.079
Changes the current directory, right?
00:06:42.160 --> 00:06:52.319
So for if you want to do CD space backslash etsy or etc, it moves you into the system configure configuration directory.
00:06:52.560 --> 00:06:54.079
Again, ls, right?
00:06:54.319 --> 00:06:56.959
Gives you a list of contents of a directory.
00:06:57.199 --> 00:07:04.160
Ls minus space minus L shows full permission, ownership, size, and date.
00:07:05.199 --> 00:07:08.160
A user comes up to you and says, My file is gone.
00:07:08.399 --> 00:07:10.000
A user guesses.
00:07:10.560 --> 00:07:13.199
You as a technician verifies.
00:07:14.560 --> 00:07:20.879
You go to the computer, you do PDPWD, you want to know what working directory you're at.
00:07:21.040 --> 00:07:29.600
You do ls, cd space, home, cd space backslash home, backslash user, ls, cd documents, ls, right?
00:07:29.680 --> 00:07:32.000
You're not searching RAM randomly.
00:07:32.160 --> 00:07:35.360
You are walking the file system logically.
00:07:36.079 --> 00:07:39.839
Now that you know where you're at, you must understand how to change things.
00:07:40.160 --> 00:07:44.160
You have your CP command, which is copy files, right?
00:07:44.240 --> 00:07:50.240
You can want to do, for example, cp spacefile.txt space backup.txt.
00:07:51.439 --> 00:07:57.120
Move or sorry, not move, mv is moves or renames the file.
00:07:57.600 --> 00:07:57.839
Right?
00:07:58.000 --> 00:08:04.720
For example, you want to mv space file txt space slash home slash user directory.
00:08:05.519 --> 00:08:09.439
Rm deletes the file permanently.
00:08:10.319 --> 00:08:12.800
Linux does not protect you.
00:08:13.040 --> 00:08:14.399
There is no undo.
00:08:16.079 --> 00:08:16.560
Right?
00:08:16.879 --> 00:08:19.759
Rm once you use it, it is permanent.
00:08:20.240 --> 00:08:27.600
So if you use rm space minus r minus f space slash, this deletes everything.
00:08:27.759 --> 00:08:29.920
Not theoretically, actually.
00:08:30.639 --> 00:08:33.440
Linux assumes if you type it, you meant it.
00:08:34.240 --> 00:08:36.720
Large systems contain thousands of files.
00:08:36.960 --> 00:08:38.879
You don't scroll, you search.
00:08:39.200 --> 00:08:46.000
You have your find definition, your find command with searches for files based on criteria.
00:08:46.080 --> 00:08:51.440
You have your grep command, GREP, searches inside files for patterns.
00:08:51.759 --> 00:08:52.159
Right?
00:08:52.399 --> 00:08:57.519
You might, for example, you do grep error system.log.
00:08:58.080 --> 00:09:01.919
This is tracks only lines containing the word error.
00:09:02.480 --> 00:09:03.679
Why this matters?
00:09:03.840 --> 00:09:11.120
This is how you analyze logs, detect breaches, and identify things that are failures.
00:09:12.000 --> 00:09:13.200
File systems.
00:09:13.440 --> 00:09:18.080
A file system is the structure used to organize and store data on a system.
00:09:18.320 --> 00:09:24.320
In Linux, slash is the top of everything, or they call it root, the root directory.
00:09:24.559 --> 00:09:26.159
Everything branches from root.
00:09:26.639 --> 00:09:28.159
Home, Etsy, var.
00:09:28.879 --> 00:09:30.159
Why does root matter?
00:09:30.320 --> 00:09:33.919
Because understanding structure means you know where the problems live.
00:09:34.799 --> 00:09:35.440
Mounting.
00:09:35.679 --> 00:09:41.440
Mounting is attaching a storage device to the file system so it becomes accessible.
00:09:41.679 --> 00:09:46.639
Without mounting, the system cannot see the drive and the data is inaccessible.
00:09:47.600 --> 00:09:59.279
So for example, Etsy F stab or etsy slash etc slash F S T A B defines how file systems are mounted at startup.
00:09:59.519 --> 00:10:00.480
Why does it matter?
00:10:00.639 --> 00:10:08.240
If configured incorrectly, drives fail to mount, systems fail to boot correctly, and data becomes unavailable.
00:10:09.360 --> 00:10:11.039
At this point, something has happened.
00:10:11.200 --> 00:10:16.879
You move from I know commands to I understand why commands exist.
00:10:17.919 --> 00:10:26.399
You now understand how Linux receives instructions, how files are structured, how systems are navigating, how actions have consequences.
00:10:26.639 --> 00:10:28.879
And now we move to the next layer.
00:10:44.559 --> 00:10:48.720
Because control without restriction is not power, it's a risk.
00:10:49.600 --> 00:10:52.720
In the real world, multiple users share systems.
00:10:53.120 --> 00:10:57.679
Sensitive data exists, and critical files must be protected.
00:10:57.919 --> 00:11:00.639
So the system must reinforce something.
00:11:01.120 --> 00:11:02.080
Boundaries.
00:11:04.000 --> 00:11:05.519
What are permissions in Linux?
00:11:05.679 --> 00:11:11.120
Permissions are rules that define who can access or modify files and system resources.
00:11:11.679 --> 00:11:16.639
Without permission, any user can delete system files.
00:11:16.879 --> 00:11:23.679
Any process could modify critical data and mistakes become catastrophic.
00:11:24.639 --> 00:11:28.159
Linux security is built on two simple questions.
00:11:28.480 --> 00:11:31.120
Who are you and what are you allowed to do?
00:11:32.879 --> 00:11:33.600
Users.
00:11:33.759 --> 00:11:35.200
The first layer of control.
00:11:35.440 --> 00:11:36.639
What is a user?
00:11:36.879 --> 00:11:41.600
A user is an account that represents a person or process interacting with the system.
00:11:41.919 --> 00:11:46.240
Not all users are equal, and Linux makes that very clear.
00:11:46.559 --> 00:11:48.559
What kind of users are there in Linux?
00:11:48.639 --> 00:11:50.960
They have the root user or the super user.
00:11:51.200 --> 00:11:54.639
You have your regular users and then service systems account.
00:11:55.039 --> 00:11:57.600
Root user is absolute control, right?
00:11:57.759 --> 00:12:03.120
Root is the highest level account when uninstrict unrestricted system access.
00:12:03.440 --> 00:12:11.120
Root can modify any file, install or remove software, change system configurations, shut down or destroy the system.
00:12:11.360 --> 00:12:12.720
Why is it dangerous?
00:12:13.039 --> 00:12:16.799
Because root has no restrictions and no safety net.
00:12:17.279 --> 00:12:23.039
Again, so technician runs RM space as removed, right?
00:12:23.200 --> 00:12:29.279
RM space minus RF slash var slash log as root.
00:12:30.000 --> 00:12:31.440
All the logs are gone.
00:12:31.600 --> 00:12:36.399
There is no undo, there is no warning, there is no recovery.
00:12:36.960 --> 00:12:39.519
Root is not for inconvenience.
00:12:39.840 --> 00:12:44.159
Root is for precision, intention, and necessity.
00:12:45.279 --> 00:12:47.440
Regular users have controls with limits.
00:12:47.519 --> 00:12:53.919
A regular user has limited access to protect the system from accidental or malicious changes.
00:12:54.159 --> 00:13:00.879
Regular users cannot modify system files, cannot install critical software, and cannot affect other users.
00:13:01.120 --> 00:13:02.480
Why does this exist?
00:13:02.960 --> 00:13:07.840
Because the most damage is not malicious, it's accidental, and I've seen it.
00:13:07.919 --> 00:13:10.720
You can accidentally do stuff.
00:13:10.960 --> 00:13:12.159
So now we have a problem.
00:13:12.320 --> 00:13:19.279
Regular users are safe, but sometimes you need to install software, modify configuration, or fix system issues.
00:13:19.440 --> 00:13:22.399
So who do you give power without giving full control?
00:13:23.120 --> 00:13:25.120
The solution sudo.
00:13:25.600 --> 00:13:27.919
Sudo stands for super user do.
00:13:28.399 --> 00:13:33.519
It allows a user to execute a command with elevated privileges temporarily.
00:13:33.679 --> 00:13:37.600
So for example, you want to do sudo app update.
00:13:38.240 --> 00:13:41.039
You want to update your applications.
00:13:42.399 --> 00:13:43.360
What just happened?
00:13:43.519 --> 00:13:50.559
A user remains a regular user, commands runs with root privileges, and access is only temporary.
00:13:50.879 --> 00:13:56.159
Because instead of giving someone full control, you give them control monetary power.
00:13:57.039 --> 00:14:02.559
So root is the master key to the building, and sudo is temporary access batch.
00:14:03.840 --> 00:14:04.159
Right?
00:14:04.320 --> 00:14:09.200
Sudo versus sudo sudo versus sudo in the exam in the real world, right?
00:14:09.840 --> 00:14:13.919
Definition switch user off into root.
00:14:14.320 --> 00:14:14.639
Right?
00:14:14.799 --> 00:14:18.399
So you do su space minus.
00:14:19.600 --> 00:14:20.000
Right?
00:14:20.159 --> 00:14:21.840
What does what just happened?
00:14:21.919 --> 00:14:24.240
You become a root, you stay root.
00:14:24.639 --> 00:14:26.320
Every command is dangerous.
00:14:26.559 --> 00:14:29.279
Because once you're root, there is no boundary anymore.
00:14:31.519 --> 00:14:33.840
S U is full roll switch.
00:14:34.080 --> 00:14:39.279
Sudo SU do D O is single command elevation.
00:14:39.840 --> 00:14:46.639
For the Compte exam, you want to understand that least privilege is always preferred.
00:14:48.000 --> 00:14:49.039
Now go deeper.
00:14:49.200 --> 00:14:52.000
Every file and directory in Linux has three levels.
00:14:52.320 --> 00:15:00.480
Owner, the user who created the file, group, a set of users with share access, and others, everybody else.
00:15:01.279 --> 00:15:15.360
Each level has three permissions read, ability to view the contents, write, ability to modify contents, and execute, ability to run a file, like a program or script.
00:15:16.000 --> 00:15:23.200
So if you look at it at the visual structure, you'll see something like RWX, right?
00:15:23.679 --> 00:15:24.559
So break it down.
00:15:24.799 --> 00:15:27.600
RWX is owner permission.
00:15:27.759 --> 00:15:30.000
Well, I'm gonna read the whole thing, right?
00:15:30.240 --> 00:15:35.279
Because you you're gonna see it in in different in lines of threes, right?
00:15:35.440 --> 00:15:42.799
So you're gonna see, for example, RWX R dash X, R dash dash.
00:15:43.039 --> 00:15:43.360
Right?
00:15:43.519 --> 00:15:44.559
Let me repeat it.
00:15:44.799 --> 00:15:49.519
RWX R dash X R dash dash.
00:15:49.840 --> 00:15:50.799
So what does it mean?
00:15:51.039 --> 00:15:56.559
RWX, which is the first three sets, that's the owner, right?
00:15:56.720 --> 00:16:01.200
It's telling you that the owner has read, write, and execute permissions.
00:16:01.679 --> 00:16:08.639
RX means it's group permission and they have read and execute power.
00:16:08.799 --> 00:16:11.440
And then everybody else just has read.
00:16:11.679 --> 00:16:11.919
Right?
00:16:12.080 --> 00:16:16.480
Owner has full control, group has read and execute, and all others just read only.
00:16:16.960 --> 00:16:18.080
Why does this matter?
00:16:18.240 --> 00:16:21.759
Because this line answers who can touch this file and how.
00:16:23.120 --> 00:16:27.840
They have what they call numeric or octo permissions, right?
00:16:27.919 --> 00:16:34.960
So read gets a value of four, write gets a value of two, and execute gets a value of one.
00:16:35.360 --> 00:16:39.919
So if you're doing RWX, that value is seven.
00:16:40.080 --> 00:16:44.159
If you do R mod X, that value is five.
00:16:44.399 --> 00:16:47.519
And you do just R, that value is four.
00:16:47.759 --> 00:17:04.799
So when you do CH mod 754 on file.txt, what you're really saying is owner is seven, which is full, group is five, read and execute, and others are four, read.
00:17:05.359 --> 00:17:07.279
Why do technicians use numbers?
00:17:07.359 --> 00:17:11.839
Because numbers are faster, precise, and scriptable.
00:17:12.160 --> 00:17:16.240
CHON changes the owner of a file.
00:17:16.559 --> 00:17:20.400
For example, ch own user one file txt.
00:17:21.039 --> 00:17:23.119
Ownership determines control.
00:17:23.519 --> 00:17:27.519
Wrong wrong owner equals wrong access.
00:17:28.559 --> 00:17:29.920
A website fails.
00:17:30.160 --> 00:17:30.640
Why?
00:17:30.880 --> 00:17:33.519
Because the file belongs to the wrong user.
00:17:33.680 --> 00:17:36.960
The result is server cannot read the file, the website breaks.
00:17:37.680 --> 00:17:44.720
Fix ch own www-data space file.txt.
00:17:46.400 --> 00:17:50.160
Permissions behave differently for directories.
00:17:50.480 --> 00:17:56.799
Read, list contents, write, add and remove files, and execute, enter the directory.
00:17:57.359 --> 00:17:58.720
This is a critical insight.
00:17:58.880 --> 00:18:02.640
You can have read but not execute, see the names, but not enter.
00:18:02.799 --> 00:18:06.720
Have execute but not read access files if you know the names.
00:18:07.039 --> 00:18:09.039
Why do permissions fail in real life?
00:18:09.200 --> 00:18:15.440
Most common issues is either wrong ownership, missing execute permissions, or overly restricted settings.
00:18:15.599 --> 00:18:19.839
So a user comes to you and says, I can't open a file, you check, right?
00:18:20.000 --> 00:18:22.000
Ls dash L, right?
00:18:22.160 --> 00:18:26.480
Then you just see dot dot dot dot dot file.txt.
00:18:27.039 --> 00:18:27.920
No permissions.
00:18:28.079 --> 00:18:29.119
We're given.
00:18:29.440 --> 00:18:35.279
So you go chmod 644 file txt, right?
00:18:35.440 --> 00:18:40.960
Read write for the owner, read for the group, and read for everybody else.
00:18:41.680 --> 00:18:47.599
You always, even in Linux, you always want to follow the doctrine of least privilege.
00:18:47.920 --> 00:18:54.559
Least privilege means users should only have the minimal access required to perform their task.
00:18:54.799 --> 00:18:55.440
Why?
00:18:55.680 --> 00:19:01.119
Because this limits damage, reduces the tax surface, and prevents accidental mistakes.
00:19:01.279 --> 00:19:06.160
Instead of giving full admin access, you grant specific permissions.
00:19:07.359 --> 00:19:16.000
Now that you understand something deeper than commands, you understand control is not about access.
00:19:16.160 --> 00:19:17.920
It's about boundaries.
00:19:24.400 --> 00:19:24.720
Right?
00:19:25.200 --> 00:19:28.720
Why they exist, right?
00:19:29.039 --> 00:19:31.039
Why why you need them.
00:19:33.039 --> 00:19:33.680
Right?
00:19:34.240 --> 00:19:38.559
And why root exists.
00:19:38.880 --> 00:19:45.519
Why does sudo, why sudo is safer than just regular suit, su.
00:19:46.079 --> 00:19:52.240
How permissions define control and how ownerships impact the systems.
00:19:53.440 --> 00:19:54.000
Right?
00:19:54.160 --> 00:19:56.079
So I'm gonna make this a two-parter.
00:19:56.720 --> 00:20:00.799
So this is gonna be part one of Linux, right?
00:20:00.960 --> 00:20:04.319
Because you need to know a little bit about Linux on the Comp Tier 1 exam.
00:20:04.480 --> 00:20:07.119
I know Linux frightens a lot of people.
00:20:07.279 --> 00:20:15.599
You know, it's one of these things that I don't know a lot enough about it to be able to, you know, to say I'm an expert at Linux.
00:20:15.680 --> 00:20:17.519
But you you don't need a lot.
00:20:17.759 --> 00:20:21.519
You know, you just really need to know the basics to read, write, execute, right?
00:20:21.599 --> 00:20:22.960
The 764, right?
00:20:23.039 --> 00:20:25.039
The you know, that example that I gave you.
00:20:25.279 --> 00:20:27.119
Ls command, right?
00:20:27.440 --> 00:20:28.960
Remove, rewrite.
00:20:29.200 --> 00:20:34.240
You don't need there's not a lot, they don't this is not a Linux exam, right?
00:20:34.319 --> 00:20:45.039
Actually, Comtia actually has a Linux command, a Linux test, a Linux Plus, and it's actually two exams, like the A Plus.
00:20:45.200 --> 00:20:50.480
So if you're really, really interested in Linux, take that exam.
00:20:50.799 --> 00:20:54.160
I uh you know, I'm okay with Linux, I'm not a Linux expert.
00:20:54.240 --> 00:20:56.880
I probably will never take the Linux Plus exam.
00:20:57.759 --> 00:21:02.160
But you know, we'll see what happens.
00:21:02.319 --> 00:21:07.680
But this is you know part one of the Linux commands that you're gonna need for the Comp T networks.
00:21:07.759 --> 00:21:09.440
But don't don't be don't be nervous.
00:21:09.519 --> 00:21:23.200
What you could do is install you know Oracle VirtualBox on your PC and then download a copy of Linux and then have it installed virtually.
00:21:23.839 --> 00:21:25.519
That's one thing that you can do.
00:21:25.759 --> 00:21:33.839
If you have Windows Pro and you download, I think you have to download a version.
00:21:33.920 --> 00:21:34.640
I don't think so.
00:21:34.799 --> 00:21:53.119
I think if if you download if you have Windows Pro and you go to Hyper-V and you do create, if you go to Hyper V and you do quick create, I think one of the one of the things that allows you to install is a version of of Linux, Debian, the Debian version.
00:21:53.599 --> 00:21:56.240
So I'm just looking it up in my system now.
00:21:56.400 --> 00:21:57.440
It's a quick, easy way.
00:21:57.519 --> 00:21:59.200
Yo, oh Ubuntu, Ubuntu.
00:21:59.519 --> 00:22:04.559
So You know, it it a quick easy way to install it.
00:22:04.640 --> 00:22:05.519
You don't need VirtualBox.
00:22:05.680 --> 00:22:06.799
You don't need to download the ISO.
00:22:07.039 --> 00:22:10.720
I think if you don't, but the thing is, you might need the ISO in order to install it.
00:22:10.799 --> 00:22:12.400
I'm not 100% sure.
00:22:12.640 --> 00:22:14.400
But I don't think you need it.
00:22:14.720 --> 00:22:20.799
You might I got a lot of stuff on my computer, so I don't I can't really test it because I would have to start deleting stuff, which I'm not gonna do.
00:22:21.039 --> 00:22:36.799
But I think if you go to quick create, if you go to Hyper-V, right, do quick create it on the right hand side where it says actions, you should be able to install a copy of Ubuntu on your PC.
00:22:37.279 --> 00:22:40.960
And it will be a virtual, you know, virtual Ubuntu.
00:22:41.519 --> 00:22:43.759
But you have to have Windows Pro.
00:22:44.559 --> 00:22:47.759
If you don't have Windows Pro, if you have Windows Home, you're not gonna be able to do it.
00:22:48.319 --> 00:22:49.680
You're not gonna be able to do it.
00:22:50.079 --> 00:22:52.079
So you gotta have Windows Pro.
00:22:52.400 --> 00:22:56.240
I mean there's a way of doing it, of installing Hyper-V.
00:22:56.559 --> 00:23:01.440
If you don't have if you only have Windows Home, there is a way to doing it.
00:23:01.519 --> 00:23:02.960
You have to look for it on the internet.
00:23:03.279 --> 00:23:05.839
I don't advise you doing it unless you know what you're doing.
00:23:06.000 --> 00:23:06.960
I actually have it.
00:23:07.200 --> 00:23:12.640
My laptop is home and I actually installed it.
00:23:12.880 --> 00:23:14.880
You know, I looked it up on on YouTube.
00:23:15.200 --> 00:23:16.880
They have there's a video on it on YouTube.
00:23:18.240 --> 00:23:19.039
And I have it.
00:23:19.200 --> 00:23:27.279
The only thing is that if you upgrade, anytime you upgrade your PC or you update your PC, right?
00:23:27.440 --> 00:23:34.960
When Windows says, Oh, we have an update for you, it will automatically remove that, and you have to go and do it again.
00:23:35.279 --> 00:23:37.200
So that's the that's the only bad thing.
00:23:37.279 --> 00:23:39.680
But if you have Windows Pro, it should, it's seamless.
00:23:40.000 --> 00:23:49.119
So there's my advice for you if you want to learn a little bit about Ubuntu and and be and play around a little bit in the Linux environment.
00:23:49.279 --> 00:23:51.680
Uh again, it's not the end of the world.
00:23:51.839 --> 00:23:55.920
They would ask you maybe four or five questions on the Comp T exam.
00:23:56.079 --> 00:23:59.200
I think totaling both, they were only gonna you're only gonna get four or five questions.
00:23:59.279 --> 00:24:02.799
You're not gonna get like 20 questions on on Linux.
00:24:03.440 --> 00:24:04.240
You're not.
00:24:05.200 --> 00:24:11.119
You will get some, but simple questions, not not anything radical.
00:24:12.160 --> 00:24:14.880
Alright, that's gonna do it for today.
00:24:15.759 --> 00:24:18.000
We'll do part two on this next week.
00:24:18.160 --> 00:24:31.119
Also, want to remind everyone with Mother's Day quickly, quickly approaching a great Mother's Day gift will be my book, Scam Proof for Seniors.
00:24:31.440 --> 00:24:43.440
How to recognize, avoid, and stop scammers, right, from scamming your mom, your dad, your grandparents, right, your aunt.
00:24:43.759 --> 00:24:47.440
It makes a great Mother's Day gift, the Mother's Day being around the corner.
00:24:47.759 --> 00:24:50.079
You can buy it on Amazon.com.
00:24:51.440 --> 00:24:56.400
Just type scam proof and my name Juan Rodriguez.
00:24:56.480 --> 00:25:05.359
As of this date, I am my book is number 38 on the social media books that are out there on Amazon.
00:25:05.519 --> 00:25:20.400
And you can also buy directly from me, professorjrodjrd.com slash books, and you can buy it either paperback or you can do a Kindle version or PDF version if you want.
00:25:20.559 --> 00:25:23.359
Download it directly to your PC.
00:25:24.319 --> 00:25:26.720
All right, that's gonna do it all for me today.
00:25:26.880 --> 00:25:32.400
Thank you very much, and we'll see you next week for part two.
00:25:32.640 --> 00:25:38.240
And remember, Professor J Rod, and keep tapping into technology.
00:26:00.079 --> 00:26:05.039
This has been a presentation of Little Cha Cha Productions, art by Sarah, music by Joe Kim.
00:26:05.119 --> 00:26:19.279
If you're not part of the Pod Match Network, you can follow me at TikTok at Professor Jrod at J R O D, or you can email me at ProfessorJrod at J R O D at Gmail.com.