WEBVTT

1
00:00:00.360 --> 00:00:02.720
<v Speaker 1>Let's unpack this. You know, it's kind of wild when

2
00:00:02.720 --> 00:00:05.639
<v Speaker 1>you think about how much tech around us is actually

3
00:00:05.679 --> 00:00:08.839
<v Speaker 1>powered by Linux. Yeah, like often completely behind the scenes.

4
00:00:09.199 --> 00:00:11.880
<v Speaker 2>Servers, yeah, smart TVs.

5
00:00:11.320 --> 00:00:14.400
<v Speaker 1>Definitely, even those little e readers, point of sale systems.

6
00:00:14.519 --> 00:00:18.440
<v Speaker 1>Linux is just well everywhere. So today we're doing a

7
00:00:18.480 --> 00:00:23.320
<v Speaker 1>deep dive into Linux Mint. It's a really popular user

8
00:00:23.359 --> 00:00:27.559
<v Speaker 1>friendly version, specifically for you know, your own computer. We're

9
00:00:27.559 --> 00:00:31.519
<v Speaker 1>pulling insights from this comprehensive book that one of you shared,

10
00:00:31.559 --> 00:00:35.079
<v Speaker 1>Thanks for that, which really gets into the essentials, like

11
00:00:35.399 --> 00:00:39.320
<v Speaker 1>everything from install the desktop basics, the command line, system management,

12
00:00:39.640 --> 00:00:40.679
<v Speaker 1>the whole nine yards.

13
00:00:40.799 --> 00:00:42.240
<v Speaker 2>Yeah, it's pretty thorough stuff.

14
00:00:42.280 --> 00:00:44.560
<v Speaker 1>So our mission here is basically to walk you through

15
00:00:44.560 --> 00:00:47.079
<v Speaker 1>this material, pull out the really important bits, give you

16
00:00:47.119 --> 00:00:51.119
<v Speaker 1>those aha moments if you like, and hopefully you walk

17
00:00:51.159 --> 00:00:53.560
<v Speaker 1>away feeling pretty clued up about Mint, but without you know,

18
00:00:53.719 --> 00:00:56.280
<v Speaker 1>getting totally lost in the weeds. Let's jump in.

19
00:00:56.560 --> 00:00:59.600
<v Speaker 2>Sounds good, Yeah, the source material it covers a lot

20
00:00:59.600 --> 00:01:03.960
<v Speaker 2>of ground. We've tried to distill the core ideas. It

21
00:01:04.000 --> 00:01:07.280
<v Speaker 2>starts with the big question really why Linux at all?

22
00:01:07.400 --> 00:01:07.640
<v Speaker 1>Right?

23
00:01:07.760 --> 00:01:10.879
<v Speaker 2>Then it walks through installation, the interface, the terminal, and

24
00:01:10.920 --> 00:01:15.799
<v Speaker 2>then gets into the nuts and bolt, storage, software, users, security,

25
00:01:16.640 --> 00:01:17.799
<v Speaker 2>even some advanced stuff.

26
00:01:17.959 --> 00:01:20.359
<v Speaker 1>Okay, so let's start right there. Then, the big why,

27
00:01:20.640 --> 00:01:23.280
<v Speaker 1>if you're used to Windows or maybe mac os, why

28
00:01:23.359 --> 00:01:27.280
<v Speaker 1>even think about Linux and why Mint specifically?

29
00:01:27.920 --> 00:01:31.239
<v Speaker 2>Well, technically, Linux itself is just the kernel, right, the

30
00:01:31.920 --> 00:01:35.359
<v Speaker 2>core engine of the operating system. But that kernel is

31
00:01:35.439 --> 00:01:38.560
<v Speaker 2>the base for literally hundreds of different operating systems. We

32
00:01:38.640 --> 00:01:42.760
<v Speaker 2>call them distributions or distros or sometimes flavors. And distros

33
00:01:42.840 --> 00:01:45.280
<v Speaker 2>like a boon To and especially Linux Mint have really

34
00:01:45.319 --> 00:01:48.719
<v Speaker 2>made Linux well a practical user friendly option for the

35
00:01:48.760 --> 00:01:49.439
<v Speaker 2>desktop these.

36
00:01:49.400 --> 00:01:51.719
<v Speaker 1>Days, and the security side of things often comes up,

37
00:01:51.760 --> 00:01:54.959
<v Speaker 1>doesn't it. The source mentions fewer viruses, fewer intrusions compared

38
00:01:55.000 --> 00:01:56.159
<v Speaker 1>to Windows, it does.

39
00:01:56.079 --> 00:01:57.920
<v Speaker 2>Yeah, And what's interesting and the source touches on this

40
00:01:58.000 --> 00:02:00.159
<v Speaker 2>is the whole debate about why that is. Is it

41
00:02:00.239 --> 00:02:02.840
<v Speaker 2>just because fewer people use Linux on the desktop, so

42
00:02:02.920 --> 00:02:06.760
<v Speaker 2>it's like not worth the effort for malware riders less

43
00:02:06.760 --> 00:02:09.879
<v Speaker 2>of a target, or is it something fundamental about Linux's design,

44
00:02:10.000 --> 00:02:14.479
<v Speaker 2>you know, the permission system, how software is managed through repositories. Right,

45
00:02:14.520 --> 00:02:18.319
<v Speaker 2>Probably a bit of both, honestly, But the practical result

46
00:02:18.400 --> 00:02:22.159
<v Speaker 2>for you, the user, you're just way less likely to

47
00:02:22.280 --> 00:02:26.919
<v Speaker 2>run into nasty software than on Windows. That's generally true, and.

48
00:02:26.919 --> 00:02:30.120
<v Speaker 1>Men's popularity comes from making that switch easier right right

49
00:02:30.159 --> 00:02:32.199
<v Speaker 1>for people coming from Windows especially.

50
00:02:31.879 --> 00:02:35.479
<v Speaker 2>Exactly Min offers a few different versions based on different

51
00:02:35.520 --> 00:02:38.360
<v Speaker 2>desktop environments. That's the look and feel the interface you

52
00:02:38.360 --> 00:02:44.000
<v Speaker 2>actually use. There's Cinnamon may E kde x fice plus

53
00:02:44.039 --> 00:02:47.879
<v Speaker 2>one based directly on Debian, but the source and honestly,

54
00:02:47.960 --> 00:02:50.759
<v Speaker 2>most people focus on Cinnamon, it's kind of the default.

55
00:02:50.759 --> 00:02:52.719
<v Speaker 1>Why Cinnamon, It really hits a sweet.

56
00:02:52.439 --> 00:02:55.319
<v Speaker 2>Spot, you know, it feels familiar, comfortable, but it's still

57
00:02:55.319 --> 00:02:59.000
<v Speaker 2>got modern features. It's reasonably fast, easy to use. It's

58
00:02:59.039 --> 00:03:00.199
<v Speaker 2>just a great starting point.

59
00:03:00.680 --> 00:03:03.400
<v Speaker 1>And if you're trying something new, especially something run by

60
00:03:03.400 --> 00:03:06.319
<v Speaker 1>a community, knowing you can get help is pretty important.

61
00:03:06.360 --> 00:03:09.319
<v Speaker 2>Oh, definitely, that raises a key point. How good is

62
00:03:09.319 --> 00:03:12.639
<v Speaker 2>the support? And thankfully the Mint community is well, it's

63
00:03:12.680 --> 00:03:13.520
<v Speaker 2>a big plus.

64
00:03:13.639 --> 00:03:13.960
<v Speaker 1>Okay.

65
00:03:14.039 --> 00:03:17.000
<v Speaker 2>The source mentions the active forums and also real time

66
00:03:17.120 --> 00:03:20.159
<v Speaker 2>chat help through ir C. There's even a chat client

67
00:03:20.479 --> 00:03:23.280
<v Speaker 2>x chat included. Right away, knowing there are people out

68
00:03:23.280 --> 00:03:26.800
<v Speaker 2>there who can help, that's that's reassuring when you're starting out.

69
00:03:27.080 --> 00:03:29.039
<v Speaker 1>So let's say you're convinced you want to try it.

70
00:03:29.520 --> 00:03:32.360
<v Speaker 1>First step is getting it installed. The source walks through

71
00:03:32.360 --> 00:03:33.639
<v Speaker 1>making the installation media.

72
00:03:33.879 --> 00:03:37.360
<v Speaker 2>Right, you need something bootable, a USB stick basically, the

73
00:03:37.400 --> 00:03:39.680
<v Speaker 2>source mentions DVDs, but honestly.

74
00:03:39.400 --> 00:03:41.599
<v Speaker 1>Nobody has DVD drives anymore pretty.

75
00:03:41.360 --> 00:03:45.280
<v Speaker 2>Much, Yeah, especially on laptops or Max, so USB flash

76
00:03:45.400 --> 00:03:48.159
<v Speaker 2>drive is the way to go. Making one is usually straightforward,

77
00:03:48.199 --> 00:03:51.319
<v Speaker 2>with tools Mint provides or you know, other standard tools.

78
00:03:51.439 --> 00:03:54.120
<v Speaker 1>Okay, now here's something the source really emphasizes and it

79
00:03:54.199 --> 00:03:58.680
<v Speaker 1>sounds well, really interesting, planning your hard drive layout before installing,

80
00:03:59.199 --> 00:04:02.639
<v Speaker 1>specifically making a separate partition just for home.

81
00:04:03.039 --> 00:04:06.479
<v Speaker 2>Yes, this is one of those like key Linux things

82
00:04:07.000 --> 00:04:10.080
<v Speaker 2>the source nails. Think of home as your personal space.

83
00:04:10.439 --> 00:04:15.280
<v Speaker 2>All your documents, music pictures, downloads, and crucially all your

84
00:04:15.319 --> 00:04:19.600
<v Speaker 2>application settings, your customizations. They all live in Home. Everything

85
00:04:19.600 --> 00:04:24.120
<v Speaker 2>else the main operating system files that's on the root partition, which.

86
00:04:23.920 --> 00:04:27.319
<v Speaker 1>Is just at okay, so why separate them?

87
00:04:27.519 --> 00:04:29.839
<v Speaker 2>Huge benefit. If you need to reinstall the whole system

88
00:04:29.879 --> 00:04:33.319
<v Speaker 2>maybe something went wrong, or more likely you're upgrading to

89
00:04:33.720 --> 00:04:37.839
<v Speaker 2>a new major Mint version, you can tell the installer

90
00:04:37.920 --> 00:04:40.600
<v Speaker 2>to wipe and format the root partition, right, but leave

91
00:04:40.639 --> 00:04:43.560
<v Speaker 2>your home partition completely alone, untouched.

92
00:04:43.600 --> 00:04:46.000
<v Speaker 1>Wait, so all my stuff, my files, my settings. They

93
00:04:46.040 --> 00:04:49.000
<v Speaker 1>just stay there through a full reinstall exactly.

94
00:04:49.040 --> 00:04:51.480
<v Speaker 2>You just point the new install to your existing home,

95
00:04:51.560 --> 00:04:53.480
<v Speaker 2>tell it not to format it, and bam, a lot

96
00:04:53.480 --> 00:04:56.279
<v Speaker 2>of your environment is instantly back no manually backing up

97
00:04:56.319 --> 00:04:57.959
<v Speaker 2>and restoring tons of personal files.

98
00:04:58.040 --> 00:05:00.720
<v Speaker 1>This sounds like a massive time saver compared to like

99
00:05:00.759 --> 00:05:01.639
<v Speaker 1>the Windows way.

100
00:05:01.680 --> 00:05:04.759
<v Speaker 2>Oh it is. It makes reinstalling or upgrading way way smoother.

101
00:05:05.040 --> 00:05:08.480
<v Speaker 1>Okay. Another choice during installation encrypting your home Boulder.

102
00:05:08.680 --> 00:05:12.199
<v Speaker 2>Yeah, and this is that classic trade off security versus convenience.

103
00:05:12.639 --> 00:05:16.279
<v Speaker 2>How so encrypting home great. If your laptop gets stolen

104
00:05:16.480 --> 00:05:19.199
<v Speaker 2>someone pulls the drive, they can't read your files without

105
00:05:19.199 --> 00:05:21.120
<v Speaker 2>the password. Really strong protection.

106
00:05:21.279 --> 00:05:23.879
<v Speaker 1>Okay, sounds good. What's the downside?

107
00:05:24.040 --> 00:05:26.839
<v Speaker 2>The downside, and the source points this out clearly, is

108
00:05:26.879 --> 00:05:30.839
<v Speaker 2>that it makes reusing that same encrypted home partition across

109
00:05:30.879 --> 00:05:35.759
<v Speaker 2>a fresh reinstall really difficult, maybe impossible. The encryption keys

110
00:05:35.800 --> 00:05:37.600
<v Speaker 2>are tied to that specific installation.

111
00:05:37.800 --> 00:05:41.240
<v Speaker 1>Ah So if I encrypt and then reinstall later using

112
00:05:41.319 --> 00:05:42.839
<v Speaker 1>that separate home trick.

113
00:05:42.720 --> 00:05:45.600
<v Speaker 2>It probably won't work easily. You'd likely need to back

114
00:05:45.639 --> 00:05:48.399
<v Speaker 2>up the contents of the encrypted home first, then reinstall,

115
00:05:48.600 --> 00:05:51.160
<v Speaker 2>create a new unencrypted home or a new encrypted one.

116
00:05:51.560 --> 00:05:53.160
<v Speaker 2>And restore your files into it.

117
00:05:53.319 --> 00:05:57.279
<v Speaker 1>I see, so encrypt. If physical security is the top priority,

118
00:05:57.439 --> 00:06:00.959
<v Speaker 1>maybe skip it. If easier reinstallations are more important for you.

119
00:06:01.000 --> 00:06:04.040
<v Speaker 2>Pretty much depends on your risk assessment. Really, and don't forget.

120
00:06:04.040 --> 00:06:06.399
<v Speaker 2>The source reminds you you can always boot the USB

121
00:06:06.519 --> 00:06:07.120
<v Speaker 2>stick into.

122
00:06:07.000 --> 00:06:08.879
<v Speaker 1>The live environment first, right, test drive it.

123
00:06:09.120 --> 00:06:11.800
<v Speaker 2>Yeah, check your hardware works. Get a feel for Cinnamon

124
00:06:12.120 --> 00:06:15.000
<v Speaker 2>all before committing to install. Always a good idea.

125
00:06:15.439 --> 00:06:18.160
<v Speaker 1>Okay, let's assume Mint is up and running, or maybe

126
00:06:18.160 --> 00:06:21.560
<v Speaker 1>you're playing with that live version. You see the Cinnamon desktop.

127
00:06:22.120 --> 00:06:23.759
<v Speaker 1>What's the vibe they're going for here?

128
00:06:24.240 --> 00:06:28.120
<v Speaker 2>The source describes Cinnamon as trying to be well, full featured,

129
00:06:28.160 --> 00:06:31.759
<v Speaker 2>but also visually nice and just easy to get your

130
00:06:31.759 --> 00:06:35.680
<v Speaker 2>head around. Familiar, especially if you're coming from Windows. Less

131
00:06:35.720 --> 00:06:36.839
<v Speaker 2>of a steep learning curve.

132
00:06:36.879 --> 00:06:39.160
<v Speaker 1>For the basics, So, what are the main bits you

133
00:06:39.199 --> 00:06:40.040
<v Speaker 1>see on screen?

134
00:06:40.600 --> 00:06:43.560
<v Speaker 2>You've usually got a main menu button bottom left, maybe

135
00:06:43.600 --> 00:06:46.680
<v Speaker 2>like a start menu. To launch apps. There's a panel

136
00:06:46.959 --> 00:06:50.319
<v Speaker 2>usually along the bottom edge like a passbar, shows open windows,

137
00:06:50.399 --> 00:06:52.519
<v Speaker 2>lets you pin favorite apps for quick launching.

138
00:06:52.560 --> 00:06:53.319
<v Speaker 1>Standard stuff.

139
00:06:53.399 --> 00:06:57.600
<v Speaker 2>Yeah, and your usual window butters, minimize, maximize, clothes. All

140
00:06:57.639 --> 00:06:58.959
<v Speaker 2>pretty standard.

141
00:06:58.560 --> 00:07:01.439
<v Speaker 1>But the source highlights something maybe less standard, at least

142
00:07:01.480 --> 00:07:02.319
<v Speaker 1>coming from Windows.

143
00:07:02.519 --> 00:07:06.839
<v Speaker 2>Yeah, workspaces, ah workspaces, Yeah, virtual desktops. Essentially you have

144
00:07:06.920 --> 00:07:09.759
<v Speaker 2>multiple separate desktop screens and put different apps on each one.

145
00:07:10.040 --> 00:07:13.120
<v Speaker 2>Maybe all your chat and email on workspace one, your

146
00:07:13.120 --> 00:07:16.000
<v Speaker 2>web browser on workspace two, the document you're writing on

147
00:07:16.040 --> 00:07:20.000
<v Speaker 2>workspace three. It keeps things from getting super cluttered.

148
00:07:20.079 --> 00:07:20.920
<v Speaker 1>How do you manage them?

149
00:07:21.120 --> 00:07:23.959
<v Speaker 2>The source mentions expo mode Often you just flick your

150
00:07:24.000 --> 00:07:26.720
<v Speaker 2>mouse to the top left corner and it zooms out,

151
00:07:26.800 --> 00:07:29.680
<v Speaker 2>shows you all your workspaces as little thumbnails. You can

152
00:07:29.759 --> 00:07:33.120
<v Speaker 2>click to switch or even drag windows between them. Really

153
00:07:33.160 --> 00:07:36.000
<v Speaker 2>handy once you get used to it boost productivity for sure.

154
00:07:36.120 --> 00:07:38.800
<v Speaker 1>And Mint comes with some apps already installed, right, so

155
00:07:38.800 --> 00:07:40.000
<v Speaker 1>you're not starting from scratch.

156
00:07:40.120 --> 00:07:42.920
<v Speaker 2>Yeah. It bundles a decent starter set, things like Gimp

157
00:07:43.000 --> 00:07:45.279
<v Speaker 2>that's a really powerful image editor, kind of like a

158
00:07:45.279 --> 00:07:49.360
<v Speaker 2>free Photoshop alternative. Okay, simple Scan for scanning documents, Benshee

159
00:07:49.439 --> 00:07:52.439
<v Speaker 2>for managing and playing music. You know, covers the common

160
00:07:52.480 --> 00:07:54.680
<v Speaker 2>basis so you can get going right away.

161
00:07:54.759 --> 00:07:57.519
<v Speaker 1>And for tweaking settings you go to system settings. The

162
00:07:57.600 --> 00:08:00.800
<v Speaker 1>source says to switch it to advanced mode, right.

163
00:08:01.079 --> 00:08:03.800
<v Speaker 2>The default view is kind of simplified. Hide some options.

164
00:08:03.879 --> 00:08:06.279
<v Speaker 2>Advance Mode just shows you everything, all the panels for

165
00:08:06.399 --> 00:08:12.759
<v Speaker 2>changing themes, appearance, desktop icons, power management, and importantly, device drivers.

166
00:08:13.240 --> 00:08:17.879
<v Speaker 1>H drivers always potentially tricky. How does Mint handle those?

167
00:08:18.279 --> 00:08:21.399
<v Speaker 2>Generally, it's really good. Mint usually finds and uses open

168
00:08:21.480 --> 00:08:24.879
<v Speaker 2>source drivers for your hardware. Automatically works great most of

169
00:08:24.879 --> 00:08:28.560
<v Speaker 2>the time, but the source notes for some things, especially

170
00:08:28.600 --> 00:08:32.600
<v Speaker 2>graphics cards and VideA AMD, the proprietary drivers, the ones

171
00:08:32.600 --> 00:08:35.720
<v Speaker 2>made by the manufacturer, might give you better performance or

172
00:08:35.840 --> 00:08:36.679
<v Speaker 2>enable certain.

173
00:08:36.480 --> 00:08:38.000
<v Speaker 1>Features, so you can install those.

174
00:08:38.120 --> 00:08:41.200
<v Speaker 2>Yeah, there's usually a device driver's tool in the settings.

175
00:08:41.440 --> 00:08:44.960
<v Speaker 2>It'll scan your hardware and offer proprietary drivers if available.

176
00:08:45.399 --> 00:08:47.799
<v Speaker 2>The source kind of suggests sticking with the open source

177
00:08:47.840 --> 00:08:50.759
<v Speaker 2>ones unless you need the proprietary ones for something specific

178
00:08:51.200 --> 00:08:54.559
<v Speaker 2>like gaming performance or if something isn't working right. Open

179
00:08:54.600 --> 00:08:58.120
<v Speaker 2>sources generally preferred for transparency, but the option is there.

180
00:08:58.440 --> 00:09:01.559
<v Speaker 1>Okay, here's a little surprise from the source. Firefox in

181
00:09:01.759 --> 00:09:05.879
<v Speaker 1>Mint uses Yahoo as the default search engine, not Google.

182
00:09:05.960 --> 00:09:08.159
<v Speaker 2>Yeah, that catches some people off guard, but there's a

183
00:09:08.279 --> 00:09:12.279
<v Speaker 2>very practical reason actually, which is money. The source explains

184
00:09:12.279 --> 00:09:14.919
<v Speaker 2>that Mint gets a share of the advertising revenue generated

185
00:09:14.919 --> 00:09:18.200
<v Speaker 2>from searches made through that default Yahoo setting. In Firefox.

186
00:09:18.480 --> 00:09:19.919
<v Speaker 1>Uh so it helps fund the.

187
00:09:19.840 --> 00:09:25.279
<v Speaker 2>Project exactly, developing and maintaining an operating system, providing servers

188
00:09:25.279 --> 00:09:28.799
<v Speaker 2>for updates. It all costs money. This partnership is one

189
00:09:28.840 --> 00:09:30.240
<v Speaker 2>way they help fund the whole effort.

190
00:09:30.480 --> 00:09:32.759
<v Speaker 1>That's actually pretty clever. And I assume you can change

191
00:09:32.759 --> 00:09:34.840
<v Speaker 1>it easily if you prefer Google or a Duck dut

192
00:09:34.840 --> 00:09:35.399
<v Speaker 1>go or whatever.

193
00:09:35.519 --> 00:09:38.559
<v Speaker 2>Oh yeah, absolutely, the source shows you how. It's just

194
00:09:38.799 --> 00:09:42.200
<v Speaker 2>standard Firefox setting takes like two seconds to change. But yeah,

195
00:09:42.279 --> 00:09:44.879
<v Speaker 2>using the default is a small way to support Mint development.

196
00:09:45.000 --> 00:09:48.639
<v Speaker 1>Okay, so the desktop, the EUI, that's great for everyday stuff,

197
00:09:49.120 --> 00:09:52.279
<v Speaker 1>but the source really pushes the idea that to really

198
00:09:52.279 --> 00:09:55.000
<v Speaker 1>get Linux you need to get comfortable with the terminal.

199
00:09:55.080 --> 00:09:56.039
<v Speaker 1>The command line.

200
00:09:56.320 --> 00:09:58.720
<v Speaker 2>Absolutely can't argue with that. You can do most things

201
00:09:58.720 --> 00:10:01.559
<v Speaker 2>with the mouse these days, but the terminal it's faster

202
00:10:01.679 --> 00:10:05.320
<v Speaker 2>for some tasks, essential for others, especially administration or automation.

203
00:10:06.000 --> 00:10:08.799
<v Speaker 2>It's where the real power lies. The source starts with

204
00:10:08.840 --> 00:10:13.200
<v Speaker 2>the basics. You type a command, hit enter, stuff happens, and.

205
00:10:13.159 --> 00:10:15.440
<v Speaker 1>The first big hurdle is just moving around, yeah right,

206
00:10:15.559 --> 00:10:17.000
<v Speaker 1>finding your files exactly.

207
00:10:17.440 --> 00:10:22.279
<v Speaker 2>That's the CD command change directory. The source explains paths

208
00:10:22.360 --> 00:10:25.080
<v Speaker 2>really well you have absolute paths starting from the very

209
00:10:25.120 --> 00:10:27.919
<v Speaker 2>top the root root like home, your name, music okay,

210
00:10:28.159 --> 00:10:30.600
<v Speaker 2>and relative paths which depend on where you are now.

211
00:10:30.759 --> 00:10:32.559
<v Speaker 2>If you're in your home folder, you can just type

212
00:10:32.639 --> 00:10:35.519
<v Speaker 2>CD music to go into the music folder. It also

213
00:10:35.720 --> 00:10:40.840
<v Speaker 2>introduces those super useful shortcuts. Tilled always means your home directory,

214
00:10:41.159 --> 00:10:43.879
<v Speaker 2>ah andy means the current directory you're in, and dot

215
00:10:43.879 --> 00:10:47.519
<v Speaker 2>dot means the directory above the current one. Getting CD

216
00:10:47.720 --> 00:10:49.200
<v Speaker 2>down is fundamental.

217
00:10:49.440 --> 00:10:53.240
<v Speaker 1>The source also gives examples of managing files, like deleting.

218
00:10:52.799 --> 00:10:57.279
<v Speaker 2>Something YEP using RM for remove. The example RM on

219
00:10:57.399 --> 00:11:00.120
<v Speaker 2>document soold report dot txt shows how you can can

220
00:11:00.279 --> 00:11:03.080
<v Speaker 2>use that tilt or shortcut to easily delete a specific

221
00:11:03.120 --> 00:11:05.840
<v Speaker 2>file inside your documents folder, no matter where you currently

222
00:11:05.840 --> 00:11:06.600
<v Speaker 2>are in the terminal.

223
00:11:06.799 --> 00:11:08.960
<v Speaker 1>And if you just need to quickly edit a config

224
00:11:09.000 --> 00:11:12.960
<v Speaker 1>file or something simple without firing of a big graphical editor.

225
00:11:13.240 --> 00:11:16.440
<v Speaker 2>Nano is the recommendation in the source. It's a really simple,

226
00:11:16.639 --> 00:11:19.559
<v Speaker 2>straightforward text editor right there in the terminal. You just

227
00:11:19.600 --> 00:11:23.320
<v Speaker 2>type nanopath to thefile. Dot txt Easy to use shows

228
00:11:23.360 --> 00:11:25.759
<v Speaker 2>the basic commands at the bottom. Great for beginners.

229
00:11:26.000 --> 00:11:28.000
<v Speaker 1>What if you forget what a command does or what

230
00:11:28.080 --> 00:11:30.679
<v Speaker 1>options it has, like l's for listing files.

231
00:11:30.720 --> 00:11:34.120
<v Speaker 2>That's what man is for the manual pages. Type man

232
00:11:34.240 --> 00:11:37.679
<v Speaker 2>followed by the command name like man els, it brings

233
00:11:37.759 --> 00:11:40.759
<v Speaker 2>up the official documentation for that command explains what it does,

234
00:11:40.799 --> 00:11:44.120
<v Speaker 2>lists all the options, like danel for a detailed listing,

235
00:11:44.200 --> 00:11:46.559
<v Speaker 2>or a MACA to show hitten files. It's like having

236
00:11:46.600 --> 00:11:49.840
<v Speaker 2>a built in help system for everything. Incredibly useful.

237
00:11:49.879 --> 00:11:52.759
<v Speaker 1>The source also covers finding files using the command line

238
00:11:52.879 --> 00:11:54.240
<v Speaker 1>I don't know where something is right.

239
00:11:54.360 --> 00:11:57.559
<v Speaker 2>The fine command super powerful. You can search based on filename,

240
00:11:57.559 --> 00:12:01.200
<v Speaker 2>file type size. When it was less modified, lots of criteria.

241
00:12:01.360 --> 00:12:01.559
<v Speaker 1>Yeah.

242
00:12:01.600 --> 00:12:04.720
<v Speaker 2>The examples show things like find ashname iiimportant file dot

243
00:12:04.759 --> 00:12:07.399
<v Speaker 2>ADT to search the entire system for a file by

244
00:12:07.440 --> 00:12:07.879
<v Speaker 2>its name.

245
00:12:08.200 --> 00:12:09.600
<v Speaker 1>Okay, searching everywhere.

246
00:12:09.279 --> 00:12:11.399
<v Speaker 2>It could take a while, it could yeah, Or you

247
00:12:11.399 --> 00:12:13.399
<v Speaker 2>can narrow it down like a fine photos and dash

248
00:12:13.399 --> 00:12:15.879
<v Speaker 2>them TIMEGIC seven to find photos in your pictures folder.

249
00:12:16.000 --> 00:12:17.039
<v Speaker 2>Modified in the last week.

250
00:12:17.200 --> 00:12:20.039
<v Speaker 1>Very flexible and one last quick tip mentioned.

251
00:12:19.799 --> 00:12:22.279
<v Speaker 2>Was watch Yeah, watch is me. If you want to

252
00:12:22.360 --> 00:12:24.159
<v Speaker 2>run a command over and over and see how it's

253
00:12:24.200 --> 00:12:27.360
<v Speaker 2>output changes, maybe watch a log file grow or see

254
00:12:27.399 --> 00:12:29.679
<v Speaker 2>disk space change. You just type watch followed by the

255
00:12:29.679 --> 00:12:33.159
<v Speaker 2>command like watch DFH. It'll rerun it every couple seconds

256
00:12:33.200 --> 00:12:33.759
<v Speaker 2>by default.

257
00:12:33.840 --> 00:12:38.080
<v Speaker 1>Cool. Okay, So moving beyond terminal basics into actually managing

258
00:12:38.080 --> 00:12:43.399
<v Speaker 1>the system storage, software, users, security. Let's start with storage

259
00:12:43.600 --> 00:12:47.320
<v Speaker 1>external drives. USB sticks mostly automatic, right yeah?

260
00:12:47.480 --> 00:12:51.679
<v Speaker 2>For desktop use, plugging in a USB stick, Mince file manager,

261
00:12:51.799 --> 00:12:54.399
<v Speaker 2>Nemo usually just pops it up, mounts it automatically. You

262
00:12:54.399 --> 00:12:56.919
<v Speaker 2>see it, you use it. The source mentions using the

263
00:12:56.960 --> 00:12:59.679
<v Speaker 2>Little eject icon and Nemo before you unplug. Just to

264
00:12:59.679 --> 00:13:01.440
<v Speaker 2>be said, make sure all data is written.

265
00:13:01.639 --> 00:13:04.000
<v Speaker 1>But there are command line ways too for more control.

266
00:13:04.120 --> 00:13:06.759
<v Speaker 2>Definitely if you're dealing with internal drives or maybe something

267
00:13:06.799 --> 00:13:10.000
<v Speaker 2>is an auto mounting, the source introduces manual mounting commands

268
00:13:10.039 --> 00:13:13.320
<v Speaker 2>like pseudo mount and pseudomount. You often need to figure

269
00:13:13.360 --> 00:13:16.159
<v Speaker 2>out the device name first, using something like pseudofesca dash

270
00:13:16.320 --> 00:13:19.679
<v Speaker 2>L to list disks and partitions. It's more advanced, but

271
00:13:19.840 --> 00:13:20.960
<v Speaker 2>it's how it works underneath.

272
00:13:21.080 --> 00:13:24.399
<v Speaker 1>And what about drives you always want available, like maybe

273
00:13:24.399 --> 00:13:26.600
<v Speaker 1>a separate GATA drive you added. How do they get

274
00:13:26.600 --> 00:13:28.279
<v Speaker 1>mounted automatically when you boot up?

275
00:13:28.600 --> 00:13:32.200
<v Speaker 2>That's managed my configuration file called et cetera STAB. The

276
00:13:32.240 --> 00:13:34.960
<v Speaker 2>source explains this file tells the system okay, when you

277
00:13:35.000 --> 00:13:39.000
<v Speaker 2>start up, mount this partition onto this folder location. It

278
00:13:39.080 --> 00:13:44.559
<v Speaker 2>stresses using UUIDs in hef STAB ub wise unique identifiers

279
00:13:44.600 --> 00:13:47.919
<v Speaker 2>for each partition. Using the UID is more reliable than

280
00:13:48.000 --> 00:13:50.840
<v Speaker 2>using the device name like dev's doll one. Because device

281
00:13:50.919 --> 00:13:53.440
<v Speaker 2>names can sometimes change if you add or remove hardware.

282
00:13:54.080 --> 00:13:57.120
<v Speaker 2>The UUID always stays the same for that partition. Makes

283
00:13:57.159 --> 00:13:59.399
<v Speaker 2>boot up mounting much more robust if it.

284
00:13:59.440 --> 00:14:01.320
<v Speaker 1>Just starts filled up. How do you find out what's

285
00:14:01.320 --> 00:14:02.039
<v Speaker 1>eating the space?

286
00:14:02.320 --> 00:14:06.240
<v Speaker 2>The source recommends a great graphical tool disc usage analyzer.

287
00:14:06.360 --> 00:14:09.840
<v Speaker 2>The command is actually babop. It gives you this visual

288
00:14:09.879 --> 00:14:12.480
<v Speaker 2>breakdown like a sunburst chart or tree map, showing exactly

289
00:14:12.519 --> 00:14:14.960
<v Speaker 2>which folders are biggest. Makes it super easy to spot,

290
00:14:15.000 --> 00:14:18.120
<v Speaker 2>like a huge downloads folder or old virtual machines taking

291
00:14:18.200 --> 00:14:22.039
<v Speaker 2>up space, much quicker than poking around manually software management.

292
00:14:22.240 --> 00:14:24.200
<v Speaker 1>This is often a big shift for people coming from

293
00:14:24.200 --> 00:14:27.120
<v Speaker 1>Windows or Mac. Right, no more hunting for dot ex

294
00:14:27.279 --> 00:14:28.159
<v Speaker 1>files online.

295
00:14:28.240 --> 00:14:32.000
<v Speaker 2>It really is a different approach. Yeah, Linux generally uses

296
00:14:32.039 --> 00:14:34.519
<v Speaker 2>package managers. Think of it like an app store, but

297
00:14:34.600 --> 00:14:37.519
<v Speaker 2>for almost everything on your system, not just fancy apps.

298
00:14:38.000 --> 00:14:41.840
<v Speaker 2>Software comes in packages stored in online repositories, and the

299
00:14:41.840 --> 00:14:45.960
<v Speaker 2>package manager handles installing, updating, and removing them cleanly.

300
00:14:46.120 --> 00:14:48.720
<v Speaker 1>And MIN makes the czy with graphical tools totally.

301
00:14:48.840 --> 00:14:51.960
<v Speaker 2>There's the Mint Software Manager. It's very user friendly, lets

302
00:14:52.000 --> 00:14:55.759
<v Speaker 2>you browse categories, search, read descriptions, see reviews, installed with

303
00:14:55.799 --> 00:14:59.919
<v Speaker 2>one click, very straightforward. Then there's also Synaptic Package Manager,

304
00:15:00.039 --> 00:15:02.879
<v Speaker 2>which the source mentions it's a bit more powerful, maybe

305
00:15:02.879 --> 00:15:05.399
<v Speaker 2>a bit more intimidating at first, but gives you finer

306
00:15:05.399 --> 00:15:09.240
<v Speaker 2>control over packages and dependencies if you need it more

307
00:15:09.240 --> 00:15:11.200
<v Speaker 2>For advanced users, perhaps can you.

308
00:15:11.240 --> 00:15:15.320
<v Speaker 1>Get software that isn't in min's official repositories, like say

309
00:15:15.600 --> 00:15:16.720
<v Speaker 1>Google Chrome. Yep.

310
00:15:17.080 --> 00:15:20.120
<v Speaker 2>The source explains how you can add third party repositories

311
00:15:20.279 --> 00:15:24.559
<v Speaker 2>or PPAs personal package archives. For Chrome, you'd add Google's

312
00:15:24.600 --> 00:15:28.399
<v Speaker 2>official Linux repository to your system sources. Then Chrome just

313
00:15:28.440 --> 00:15:30.879
<v Speaker 2>shows up in the software manager like any other app,

314
00:15:31.039 --> 00:15:33.080
<v Speaker 2>and it gets updated automatically along with the rest of

315
00:15:33.080 --> 00:15:33.600
<v Speaker 2>your system.

316
00:15:33.919 --> 00:15:36.360
<v Speaker 1>But be careful adding random repositories.

317
00:15:36.720 --> 00:15:40.240
<v Speaker 2>Yeah, definitely stick to trusted sources like the official ones

318
00:15:40.240 --> 00:15:43.879
<v Speaker 2>from big companies or well known projects. Adding random ones

319
00:15:43.919 --> 00:15:47.240
<v Speaker 2>could potentially introduce instability or security risks.

320
00:15:47.360 --> 00:15:50.720
<v Speaker 1>Okay, users and permissions managing who can log in and

321
00:15:50.759 --> 00:15:52.080
<v Speaker 1>what they can do right.

322
00:15:52.559 --> 00:15:56.200
<v Speaker 2>Mint has a simple graphical users in Groups tool for

323
00:15:56.480 --> 00:15:59.159
<v Speaker 2>basic stuff, adding a new user account for someone else,

324
00:15:59.519 --> 00:16:02.759
<v Speaker 2>setting their password, deciding if they're an administrator or a

325
00:16:02.799 --> 00:16:03.960
<v Speaker 2>standard user.

326
00:16:03.799 --> 00:16:05.159
<v Speaker 1>And command line options.

327
00:16:05.279 --> 00:16:08.159
<v Speaker 2>Of course, the source introduces a doucer and a loser

328
00:16:08.200 --> 00:16:10.799
<v Speaker 2>for creating and deleting accounts, and if you just want

329
00:16:10.840 --> 00:16:13.039
<v Speaker 2>to change your own password, you can just type password

330
00:16:13.080 --> 00:16:16.320
<v Speaker 2>in the terminal. The source also mentions you can temporarily

331
00:16:16.440 --> 00:16:19.720
<v Speaker 2>lock an account password dasha l or unlock it password

332
00:16:19.799 --> 00:16:20.480
<v Speaker 2>you what.

333
00:16:20.480 --> 00:16:24.200
<v Speaker 1>About doing things that need admin rights, like installing software

334
00:16:24.240 --> 00:16:26.320
<v Speaker 1>system wide or editing system files.

335
00:16:26.639 --> 00:16:29.399
<v Speaker 2>That's where pseudo comes in. It's fundamental in Mint and

336
00:16:29.519 --> 00:16:32.639
<v Speaker 2>Ubuntu based systems. Instead of logging in as the all

337
00:16:32.679 --> 00:16:35.679
<v Speaker 2>powerful root user all the time, which is risky, you

338
00:16:35.799 --> 00:16:38.799
<v Speaker 2>just prefix a command that needs root privileges with Pseudo,

339
00:16:38.919 --> 00:16:42.440
<v Speaker 2>so like pseudo apped update exactly, it asks for your password,

340
00:16:42.480 --> 00:16:44.519
<v Speaker 2>and if you're allowed to use Pseudo, which the main

341
00:16:44.600 --> 00:16:47.919
<v Speaker 2>user created during installation usually is, it runs just that

342
00:16:47.960 --> 00:16:52.000
<v Speaker 2>one command is root. It's much safer. The source briefly

343
00:16:52.039 --> 00:16:55.000
<v Speaker 2>mentions the it's set pseudoor's file edited viav a Pseudo,

344
00:16:55.159 --> 00:16:57.799
<v Speaker 2>where you can configure who can use Pseudo and even

345
00:16:57.840 --> 00:17:01.440
<v Speaker 2>restrict them to only specific commands, but warns that editing

346
00:17:01.480 --> 00:17:03.480
<v Speaker 2>that file needs extreme care.

347
00:17:04.200 --> 00:17:07.839
<v Speaker 1>Okay. Now for something that often looks like hieroglyphics to newcomers, Yeah,

348
00:17:07.880 --> 00:17:11.359
<v Speaker 1>file permissions. When you type l'sh l and see things

349
00:17:11.480 --> 00:17:14.480
<v Speaker 1>like do wxr xr x, what does that mean?

350
00:17:14.720 --> 00:17:18.079
<v Speaker 2>Ah? Yes, the permission string. It looks scary, but it's logical.

351
00:17:18.160 --> 00:17:20.880
<v Speaker 2>The source broks it down nicely. First character D means

352
00:17:20.880 --> 00:17:23.720
<v Speaker 2>it's a directory, means it's a regular file. Then the

353
00:17:23.759 --> 00:17:27.119
<v Speaker 2>next nine characters are three groups of three dot rwx.

354
00:17:27.480 --> 00:17:29.640
<v Speaker 2>The first group is for the file's owner, usually the

355
00:17:29.680 --> 00:17:31.680
<v Speaker 2>person who created it. The second group is for the

356
00:17:31.680 --> 00:17:34.039
<v Speaker 2>group the file belongs to. The third group is for

357
00:17:34.079 --> 00:17:35.119
<v Speaker 2>everyone else on the system.

358
00:17:35.240 --> 00:17:39.279
<v Speaker 1>Okay, owner, group other, And rwx means read.

359
00:17:39.319 --> 00:17:43.519
<v Speaker 2>Write, execute, And this is the key thing. The source explains.

360
00:17:43.559 --> 00:17:45.799
<v Speaker 2>What they mean depends slightly on whether it's a file

361
00:17:45.920 --> 00:17:48.559
<v Speaker 2>or a directory. How So, for a file, dot R

362
00:17:48.680 --> 00:17:51.480
<v Speaker 2>means you can read its contents, W means you can

363
00:17:51.599 --> 00:17:54.039
<v Speaker 2>change or delete it. X means you can run it.

364
00:17:54.200 --> 00:17:56.720
<v Speaker 2>If it's a programm or script makes sense. For a directory,

365
00:17:56.759 --> 00:17:58.960
<v Speaker 2>dot R means you can list the files inside it.

366
00:17:59.400 --> 00:18:02.559
<v Speaker 2>W means you can create, delete, or rename files within

367
00:18:02.599 --> 00:18:05.519
<v Speaker 2>that directory. And X execute means you can enter that

368
00:18:05.559 --> 00:18:07.319
<v Speaker 2>directory like using CD to go into it.

369
00:18:07.480 --> 00:18:10.960
<v Speaker 1>Ah. Okay, So that grw xr dash xx.

370
00:18:10.680 --> 00:18:13.640
<v Speaker 2>Sample means it's a directory D The owner has read

371
00:18:13.720 --> 00:18:17.240
<v Speaker 2>right and execute rwx, the group has read and execute

372
00:18:17.480 --> 00:18:20.440
<v Speaker 2>RX but not right, and everyone else also has read

373
00:18:20.440 --> 00:18:22.359
<v Speaker 2>and execute RX but not right.

374
00:18:22.599 --> 00:18:25.599
<v Speaker 1>So others can list files inside and seedd into it,

375
00:18:25.680 --> 00:18:28.039
<v Speaker 1>but they can't add or delete files there exactly.

376
00:18:28.119 --> 00:18:31.200
<v Speaker 2>Understanding that distinction between file and directory of permissions is crucial.

377
00:18:31.559 --> 00:18:34.480
<v Speaker 1>The source also mentions numbers for permissions. Yeah, like seven

378
00:18:34.519 --> 00:18:35.000
<v Speaker 1>fifty five.

379
00:18:35.160 --> 00:18:37.720
<v Speaker 2>Yeah, that's a shorthand often used with the CHUM command

380
00:18:37.759 --> 00:18:40.920
<v Speaker 2>which changes permissions. Read is four, right is to execute

381
00:18:40.960 --> 00:18:42.799
<v Speaker 2>is one. You just add them up for each group, owner,

382
00:18:42.799 --> 00:18:45.759
<v Speaker 2>group other. So rx is four plus two plus one

383
00:18:45.759 --> 00:18:47.920
<v Speaker 2>of the seven. Rt of X is four plus zero

384
00:18:47.960 --> 00:18:50.559
<v Speaker 2>plus one s five, So r w x, r X,

385
00:18:50.759 --> 00:18:53.759
<v Speaker 2>r dash x becomes seven to fifty five. It's handy

386
00:18:53.799 --> 00:18:56.519
<v Speaker 2>for CHOM, but understanding the letters is more important conceptually.

387
00:18:56.839 --> 00:19:01.160
<v Speaker 1>Gotcha, okay. Shifting gears to networking Getting online usually pretty

388
00:19:01.160 --> 00:19:03.599
<v Speaker 1>easy with the GUI right wired or wireless?

389
00:19:03.680 --> 00:19:07.240
<v Speaker 2>Oh yeah, mostly straightforward. The network icon in the panel

390
00:19:07.359 --> 00:19:10.240
<v Speaker 2>usually lets you see available Wi Fi networks, click, enter

391
00:19:10.279 --> 00:19:13.680
<v Speaker 2>the password, and you're connected. Wired connections often just work

392
00:19:13.680 --> 00:19:16.079
<v Speaker 2>when you plug them in using DHCP to get an

393
00:19:16.079 --> 00:19:20.079
<v Speaker 2>address automatically. The source shows the network settings panel where

394
00:19:20.160 --> 00:19:20.960
<v Speaker 2>you manage all this.

395
00:19:21.440 --> 00:19:24.319
<v Speaker 1>What if you need a static IP address, like for

396
00:19:24.400 --> 00:19:26.279
<v Speaker 1>a server or something specific.

397
00:19:25.839 --> 00:19:28.480
<v Speaker 2>The graphical Network Settings lets you do that too. Instead

398
00:19:28.519 --> 00:19:31.799
<v Speaker 2>of automatic DHCP, you choose manual and then you can

399
00:19:31.839 --> 00:19:34.960
<v Speaker 2>type in the fixed IP address. The netmask gateway, DNS

400
00:19:34.960 --> 00:19:37.480
<v Speaker 2>servers all configurable through the guy.

401
00:19:37.720 --> 00:19:41.720
<v Speaker 1>Okay, what about accessing your Mint machine remotely or accessing

402
00:19:41.799 --> 00:19:42.839
<v Speaker 1>other machines from Mint?

403
00:19:42.960 --> 00:19:46.799
<v Speaker 2>Secure shell? SSH is the standard way for command line access.

404
00:19:47.319 --> 00:19:50.079
<v Speaker 2>The source notes that the SSH client to connect out

405
00:19:50.079 --> 00:19:52.960
<v Speaker 2>from Mint is usually installed by default. If you want

406
00:19:53.000 --> 00:19:55.799
<v Speaker 2>to allow SSH connections into your Mint machine, you need

407
00:19:55.839 --> 00:19:57.960
<v Speaker 2>to install the open server package, and.

408
00:19:57.920 --> 00:19:59.720
<v Speaker 1>The source recommends making it more secure.

409
00:20:00.000 --> 00:20:04.200
<v Speaker 2>Definitely edit the server configuration file et cetera. Shelog config

410
00:20:04.799 --> 00:20:07.400
<v Speaker 2>key things are to set permit root log in, no,

411
00:20:08.160 --> 00:20:11.000
<v Speaker 2>disallow logging in directly as route, and maybe change the

412
00:20:11.079 --> 00:20:14.039
<v Speaker 2>default port from twenty two to something else less obvious

413
00:20:14.200 --> 00:20:15.680
<v Speaker 2>to reduce automated scans.

414
00:20:16.160 --> 00:20:18.799
<v Speaker 1>What about sharing files on the local network like with

415
00:20:18.880 --> 00:20:19.759
<v Speaker 1>Windows machines.

416
00:20:20.279 --> 00:20:23.559
<v Speaker 2>For mixed networks with Windows or mac os, SAMA is

417
00:20:23.599 --> 00:20:26.960
<v Speaker 2>the way to go. It speaks the same SMBCIFS protocol

418
00:20:27.319 --> 00:20:30.079
<v Speaker 2>for Linux to Linux sharing. NFS is often simpler and

419
00:20:30.160 --> 00:20:33.039
<v Speaker 2>maybe a bit more efficient. The source mentions the config

420
00:20:33.119 --> 00:20:36.279
<v Speaker 2>files smb dot com for SAMA at sex sports for NFS,

421
00:20:36.559 --> 00:20:39.279
<v Speaker 2>hinting that setting up the server side requires some config

422
00:20:39.319 --> 00:20:42.200
<v Speaker 2>file editing, but connecting as a client is often easy

423
00:20:42.200 --> 00:20:44.079
<v Speaker 2>through the file manager security tools.

424
00:20:44.119 --> 00:20:47.160
<v Speaker 1>Let's talk firewall. Linux has one built in right iptables.

425
00:20:47.279 --> 00:20:50.720
<v Speaker 2>It does. Iptables is the underlying engine, very powerful, very flexible,

426
00:20:51.039 --> 00:20:53.160
<v Speaker 2>but as a source points out, the default policy on

427
00:20:53.200 --> 00:20:56.400
<v Speaker 2>many desktop distris, including Mint, often is just except to key,

428
00:20:56.480 --> 00:20:59.519
<v Speaker 2>meaning it's not actually blocking anything by default, and configuring

429
00:20:59.599 --> 00:21:03.000
<v Speaker 2>iptable manually using commands, well, it can be pretty complex.

430
00:21:03.079 --> 00:21:05.240
<v Speaker 1>So is there an easier way for desktop users?

431
00:21:05.559 --> 00:21:09.559
<v Speaker 2>Thankfully yes, The source recommends installing GOOF. It stands for

432
00:21:09.680 --> 00:21:14.160
<v Speaker 2>Graphical Uncomplicated Firewall. It's basically a user friendly front end

433
00:21:14.200 --> 00:21:14.920
<v Speaker 2>for iptables.

434
00:21:15.079 --> 00:21:15.799
<v Speaker 1>How does it work?

435
00:21:15.960 --> 00:21:18.359
<v Speaker 2>It lets you easily turn the firewall on or off,

436
00:21:18.480 --> 00:21:22.640
<v Speaker 2>set up basic profiles like home, office, public, and adds

437
00:21:22.680 --> 00:21:27.720
<v Speaker 2>simple rules like allow incoming SSH or deny incoming web

438
00:21:27.799 --> 00:21:31.119
<v Speaker 2>server access with just a few clicks makes basic firewall

439
00:21:31.160 --> 00:21:32.759
<v Speaker 2>management much much easier.

440
00:21:32.839 --> 00:21:36.680
<v Speaker 1>Okay, what about the idea that Linux doesn't get viruses?

441
00:21:37.079 --> 00:21:39.519
<v Speaker 1>The source touches on anti virus too, right.

442
00:21:39.440 --> 00:21:42.880
<v Speaker 2>That common claim it needs clarification is Linux and vulnerable. No,

443
00:21:43.160 --> 00:21:46.599
<v Speaker 2>but are widespread viruses targeting the Linux desktop common right now?

444
00:21:46.640 --> 00:21:47.079
<v Speaker 1>Not really?

445
00:21:47.119 --> 00:21:50.720
<v Speaker 2>Thankfully. However, a Linux machine, especially if it's acting as

446
00:21:50.720 --> 00:21:53.160
<v Speaker 2>a file server or you're sharing files with Windows users,

447
00:21:53.279 --> 00:21:56.480
<v Speaker 2>can still hold and spread Windows viruses. Your Linux system

448
00:21:56.480 --> 00:21:58.599
<v Speaker 2>won't get sick from them, but it could pass them on.

449
00:21:59.039 --> 00:22:02.200
<v Speaker 1>So an antivirus like ClamAV which the source mentioned.

450
00:22:02.160 --> 00:22:05.039
<v Speaker 2>Yeah, clamavvy is primarily useful on Linux as an on

451
00:22:05.119 --> 00:22:08.279
<v Speaker 2>demand scanner. You can use it to stand downloaded files

452
00:22:08.519 --> 00:22:12.000
<v Speaker 2>or scan a shared folder specifically looking for Windows malware

453
00:22:12.039 --> 00:22:14.480
<v Speaker 2>before you share those files or move them to a

454
00:22:14.519 --> 00:22:18.359
<v Speaker 2>Windows machine. It's not really about protecting Linux itself in

455
00:22:18.440 --> 00:22:20.599
<v Speaker 2>real time usually, gotcha.

456
00:22:20.680 --> 00:22:24.359
<v Speaker 1>The source also mentions mint nanny for simple website blocking.

457
00:22:24.920 --> 00:22:27.640
<v Speaker 2>Yeah, and open DNS is a more robust network level

458
00:22:27.680 --> 00:22:30.640
<v Speaker 2>filtering option if you want something more comprehensive than just

459
00:22:30.720 --> 00:22:32.200
<v Speaker 2>blocking a few sites locally.

460
00:22:32.359 --> 00:22:35.880
<v Speaker 1>And the absolute bedrock of security backups.

461
00:22:36.119 --> 00:22:39.559
<v Speaker 2>Yes, can't stress that enough. The source highlights Mint's own

462
00:22:39.599 --> 00:22:42.039
<v Speaker 2>backup tool. It can back up your personal files, your

463
00:22:42.039 --> 00:22:43.160
<v Speaker 2>home directory.

464
00:22:42.720 --> 00:22:44.720
<v Speaker 1>Contents, okay, standard stuff.

465
00:22:44.559 --> 00:22:46.839
<v Speaker 2>But crucially, it can also back up the list of

466
00:22:46.880 --> 00:22:48.440
<v Speaker 2>software packages you have installed.

467
00:22:48.599 --> 00:22:50.839
<v Speaker 1>Why is the list so important? We mentioned this briefly with.

468
00:22:50.799 --> 00:22:53.599
<v Speaker 2>Reinstalling exactly because when you do a fresh install for

469
00:22:53.680 --> 00:22:56.319
<v Speaker 2>a major upgrade, having that list backed up means you

470
00:22:56.359 --> 00:22:58.799
<v Speaker 2>can easily tell a new system, hey, install all the

471
00:22:58.799 --> 00:23:02.279
<v Speaker 2>stuff I had before. The backup tool helps automate restoring

472
00:23:02.279 --> 00:23:05.519
<v Speaker 2>those applications, saves a ton of time remembering and finding

473
00:23:05.599 --> 00:23:06.240
<v Speaker 2>everything again.

474
00:23:06.640 --> 00:23:09.920
<v Speaker 1>And just backing up to an external drive isn't always enough,

475
00:23:09.960 --> 00:23:12.640
<v Speaker 1>is it. The source recommends offside backups.

476
00:23:13.000 --> 00:23:16.119
<v Speaker 2>Right, A local backup is great against hard drive failure,

477
00:23:16.559 --> 00:23:20.000
<v Speaker 2>but what if there's a fire or theft your computer

478
00:23:20.079 --> 00:23:23.240
<v Speaker 2>and your backup drive could be gone. An offside backup

479
00:23:23.279 --> 00:23:26.720
<v Speaker 2>Storing copies of your important data somewhere else physically or

480
00:23:26.880 --> 00:23:29.960
<v Speaker 2>using a cloud backup service protects against that kind of disaster.

481
00:23:30.759 --> 00:23:33.799
<v Speaker 2>The source mentions services like spider Oak or crash Plan

482
00:23:33.920 --> 00:23:37.240
<v Speaker 2>as examples that have Linux clients and offer secure, encrypted

483
00:23:37.240 --> 00:23:41.680
<v Speaker 2>cloud storage essential for real peace of mind. For irreplaceable data.

484
00:23:41.759 --> 00:23:44.559
<v Speaker 1>Okay, let's dig into some more advanced techniques that source covers.

485
00:23:44.839 --> 00:23:46.680
<v Speaker 1>Command aliases. What are those?

486
00:23:47.000 --> 00:23:50.240
<v Speaker 2>Aliases? Are basically custom shortcuts for the terminal. If you

487
00:23:50.279 --> 00:23:52.839
<v Speaker 2>find yourself typing a really long command frequently, you can

488
00:23:52.880 --> 00:23:55.000
<v Speaker 2>create a short alias for it, like maybe you type

489
00:23:55.240 --> 00:23:57.960
<v Speaker 2>alias update pseudo apped up date and pseudo apped up

490
00:23:58.000 --> 00:24:01.440
<v Speaker 2>grade day. Then just update in the terminal runs that

491
00:24:01.559 --> 00:24:05.079
<v Speaker 2>whole sequence. The source shows how to define them temporarily

492
00:24:05.240 --> 00:24:06.920
<v Speaker 2>just for your current session, or how to make them

493
00:24:06.960 --> 00:24:09.240
<v Speaker 2>permanent by adding them to a file called bash rock

494
00:24:09.319 --> 00:24:12.119
<v Speaker 2>in your home directory. Little Time savers.

495
00:24:12.079 --> 00:24:14.920
<v Speaker 1>Managing programs that are currently running processes.

496
00:24:15.319 --> 00:24:18.039
<v Speaker 2>You can use the Graphical System Monitor tool. It looks

497
00:24:18.039 --> 00:24:21.400
<v Speaker 2>a bit like task Manager and Windows shows CPU memory,

498
00:24:21.519 --> 00:24:25.200
<v Speaker 2>network usage per application, lets you kill misbehaving.

499
00:24:24.680 --> 00:24:26.599
<v Speaker 1>Apps, and from the command line.

500
00:24:26.680 --> 00:24:29.000
<v Speaker 2>The classic tool is TOP. It gives you a live,

501
00:24:29.240 --> 00:24:33.599
<v Speaker 2>updating list of running processes, sorted by CPU usage by default.

502
00:24:34.119 --> 00:24:36.480
<v Speaker 2>The source mentions you can press keys within top to

503
00:24:36.559 --> 00:24:40.160
<v Speaker 2>change the sorting, like sorting my memory usage instead to

504
00:24:40.240 --> 00:24:44.000
<v Speaker 2>find what's hogging resources. It also introduces kill and kill

505
00:24:44.039 --> 00:24:47.680
<v Speaker 2>all to stop processes by ID or name, but yeah,

506
00:24:47.880 --> 00:24:51.000
<v Speaker 2>use with caution as the source advises force killing stuff

507
00:24:51.000 --> 00:24:51.759
<v Speaker 2>can lose data.

508
00:24:51.960 --> 00:24:55.039
<v Speaker 1>Now this sounds really powerful, maybe a bit complex. Automating

509
00:24:55.079 --> 00:24:56.160
<v Speaker 1>tasks with chron.

510
00:24:56.240 --> 00:24:59.640
<v Speaker 2>Hn Yeah, it's the standard Linux way to schedule commands

511
00:24:59.720 --> 00:25:02.599
<v Speaker 2>or screen to run automatically at specific times or intervals,

512
00:25:03.000 --> 00:25:05.720
<v Speaker 2>like run a backupscript every night at two am.

513
00:25:05.839 --> 00:25:06.720
<v Speaker 1>How do you set it up?

514
00:25:06.960 --> 00:25:10.039
<v Speaker 2>You usually edit your personal kron table using the command

515
00:25:10.160 --> 00:25:13.440
<v Speaker 2>kronte e. The source then dies into the syntax, which

516
00:25:13.440 --> 00:25:16.160
<v Speaker 2>can look a bit weird at first. It's five fields

517
00:25:16.160 --> 00:25:18.920
<v Speaker 2>for time, minute, hour, day of the month, month, day

518
00:25:18.960 --> 00:25:21.200
<v Speaker 2>of the week, followed by the command to run.

519
00:25:21.519 --> 00:25:23.839
<v Speaker 1>Okay, so stars and numbers right.

520
00:25:23.920 --> 00:25:27.119
<v Speaker 2>Oi means every so command means run command every single minute.

521
00:25:27.240 --> 00:25:29.559
<v Speaker 2>Zero three to one command means run command at three

522
00:25:29.720 --> 00:25:32.680
<v Speaker 2>zero am every Monday. The source gives examples to make

523
00:25:32.680 --> 00:25:36.359
<v Speaker 2>it clearer, and a key tip it gives always use

524
00:25:36.400 --> 00:25:39.119
<v Speaker 2>the full path to the command in your conteb like

525
00:25:39.359 --> 00:25:42.960
<v Speaker 2>surbanmyscript dot esh, not just MyScript dot esh to make

526
00:25:43.000 --> 00:25:44.119
<v Speaker 2>sure it runs reliably.

527
00:25:44.440 --> 00:25:47.440
<v Speaker 1>So kron is for scheduling. The source also mentions esh

528
00:25:47.440 --> 00:25:48.680
<v Speaker 1>scripting briefly.

529
00:25:48.559 --> 00:25:51.039
<v Speaker 2>Just the basics, like how to create a variable wineum

530
00:25:51.119 --> 00:25:53.559
<v Speaker 2>joe and use it echo my name and a simple

531
00:25:53.599 --> 00:25:56.559
<v Speaker 2>if in structure for making decisions in a script. Combine

532
00:25:56.599 --> 00:25:59.400
<v Speaker 2>scripting with KRON and you can automate some pretty complex

533
00:25:59.440 --> 00:26:03.119
<v Speaker 2>maintenance or reporting tasks. It's the next level of automation.

534
00:26:03.039 --> 00:26:06.119
<v Speaker 1>Monitoring system healthy. Right. We mentioned TOP for CPU usage,

535
00:26:06.240 --> 00:26:07.119
<v Speaker 1>What about temperature?

536
00:26:07.160 --> 00:26:09.599
<v Speaker 2>The sensor's command is usually the way you might need

537
00:26:09.640 --> 00:26:13.000
<v Speaker 2>to install it. LM sensors and run sensors detect once.

538
00:26:13.599 --> 00:26:16.559
<v Speaker 2>Then sensors will show you readings from temperature sensors, often

539
00:26:16.559 --> 00:26:19.400
<v Speaker 2>for the CPU course. The source explains how to read

540
00:26:19.440 --> 00:26:23.359
<v Speaker 2>the output showing current temp versus high critical thresholds. If

541
00:26:23.400 --> 00:26:26.440
<v Speaker 2>temps are consistently high, it suggests checking CP usage with

542
00:26:26.519 --> 00:26:29.799
<v Speaker 2>TOP first, or maybe looking for dust bunnies clogging fans

543
00:26:29.799 --> 00:26:31.599
<v Speaker 2>if it's high even when idle, and.

544
00:26:31.559 --> 00:26:34.200
<v Speaker 1>Getting reports automatically maybe emailed.

545
00:26:34.319 --> 00:26:37.119
<v Speaker 2>Yeah. The source suggests combining KRON with a command line

546
00:26:37.160 --> 00:26:39.799
<v Speaker 2>email tool like send email. You'd need to install and

547
00:26:39.839 --> 00:26:41.880
<v Speaker 2>configure it. You can have a CRON job run a

548
00:26:41.960 --> 00:26:46.000
<v Speaker 2>command say DFTH for DISC usage, redirect its output to

549
00:26:46.039 --> 00:26:49.960
<v Speaker 2>a file DFHH discusage not TXT, and then you send

550
00:26:50.039 --> 00:26:52.640
<v Speaker 2>email to mail that file to yourself automatically every day

551
00:26:52.720 --> 00:26:54.599
<v Speaker 2>or week. A good way to keep tabs on things

552
00:26:54.640 --> 00:26:55.519
<v Speaker 2>remotely right.

553
00:26:55.519 --> 00:26:59.359
<v Speaker 1>Inevitably, things sometimes go wrong. The source wraps up with troubleshooting.

554
00:26:59.519 --> 00:27:01.720
<v Speaker 2>What's real number one, the oldest trip in the book.

555
00:27:02.119 --> 00:27:05.039
<v Speaker 2>Just try restarting, read put the whole system, or maybe

556
00:27:05.079 --> 00:27:08.519
<v Speaker 2>just restart the specific service or application that's acting up.

557
00:27:08.759 --> 00:27:11.400
<v Speaker 2>You'd be surprised how often that fixes temporary glitches.

558
00:27:11.720 --> 00:27:12.839
<v Speaker 1>And if that doesn't cut it.

559
00:27:13.000 --> 00:27:17.440
<v Speaker 2>Google it seriously. The source emphasizes this, Copy the exact

560
00:27:17.519 --> 00:27:21.240
<v Speaker 2>error message, describe the symptoms, paste it into a search engine.

561
00:27:21.680 --> 00:27:23.720
<v Speaker 2>Nine times out of tens, someone else has hit the

562
00:27:23.720 --> 00:27:26.640
<v Speaker 2>same problem, and there's a forum post or blog entry

563
00:27:26.680 --> 00:27:27.079
<v Speaker 2>about it.

564
00:27:27.359 --> 00:27:28.599
<v Speaker 1>And when asking for help on.

565
00:27:28.640 --> 00:27:33.000
<v Speaker 2>Forums the specific The source stresses this, don't just say

566
00:27:33.079 --> 00:27:36.000
<v Speaker 2>it doesn't work. Say what you were trying to do,

567
00:27:36.160 --> 00:27:40.680
<v Speaker 2>what happened, Paste the exact error message, Mention your Mint version,

568
00:27:41.039 --> 00:27:44.759
<v Speaker 2>relevant hardware, and what you've already tried. Good details, get

569
00:27:44.799 --> 00:27:45.519
<v Speaker 2>good answers.

570
00:27:45.880 --> 00:27:49.000
<v Speaker 1>The source mentions a fallback mode for Cinnamon if graphics go.

571
00:27:49.039 --> 00:27:52.200
<v Speaker 2>Weird, Yeah, software rendering mode. If you're a graphics driver

572
00:27:52.279 --> 00:27:56.119
<v Speaker 2>crashes or isn't loading properly, Cinnamon might automatically fall back

573
00:27:56.160 --> 00:27:58.400
<v Speaker 2>to this mode. It'll look basic, maybe a bit slow.

574
00:27:58.480 --> 00:28:01.480
<v Speaker 2>No fancy effects, but it gives you a usable desktop,

575
00:28:01.559 --> 00:28:03.680
<v Speaker 2>so you can get into the settings and try the

576
00:28:03.680 --> 00:28:07.079
<v Speaker 2>device driver's tool to install or switch graphics drivers. It's

577
00:28:07.079 --> 00:28:07.640
<v Speaker 2>a lifesaver.

578
00:28:07.799 --> 00:28:11.599
<v Speaker 1>Sometimes boot problems can be scary. System won't even start up.

579
00:28:11.799 --> 00:28:15.559
<v Speaker 2>Yeah, those are stressful. The source covers common causes, like

580
00:28:15.640 --> 00:28:17.880
<v Speaker 2>maybe an error in that etceter s stab file we

581
00:28:17.960 --> 00:28:21.279
<v Speaker 2>talked about, often a wrong UUD preventing a crucial partition

582
00:28:21.319 --> 00:28:21.920
<v Speaker 2>from mounting.

583
00:28:22.119 --> 00:28:22.839
<v Speaker 1>How do you fix that?

584
00:28:22.920 --> 00:28:25.160
<v Speaker 2>If you can't boot, you have to boot from your

585
00:28:25.200 --> 00:28:29.519
<v Speaker 2>Mint installation USB stick again the live environment. From there

586
00:28:29.559 --> 00:28:32.880
<v Speaker 2>you can access the hard drive, find the correct UUIDs,

587
00:28:33.000 --> 00:28:37.039
<v Speaker 2>the source mentions using pseudobul kid, mount the broken systems partitions,

588
00:28:37.519 --> 00:28:40.279
<v Speaker 2>edit the ETCA stab file to fix the error, or

589
00:28:40.319 --> 00:28:43.480
<v Speaker 2>even reinstall the grub bootloader if that got messed up.

590
00:28:43.680 --> 00:28:45.720
<v Speaker 2>The live USB is your rescue tool.

591
00:28:45.920 --> 00:28:49.559
<v Speaker 1>Checking system logs is also key for diagnosing problems right Absolutely.

592
00:28:49.599 --> 00:28:53.000
<v Speaker 2>Logs record everything happening. The source points to important ones

593
00:28:53.039 --> 00:28:56.400
<v Speaker 2>like varlogof dot log for login attempts. Failed logins might

594
00:28:56.400 --> 00:29:00.400
<v Speaker 2>show up here varlogboot dot log for startup messages, and

595
00:29:00.680 --> 00:29:03.680
<v Speaker 2>varlog'slog for general system stuff. You can use cat to

596
00:29:03.759 --> 00:29:06.319
<v Speaker 2>view them, but GREB is essential for searching within them

597
00:29:06.359 --> 00:29:09.319
<v Speaker 2>for keywords like error failed or the name of the

598
00:29:09.359 --> 00:29:12.960
<v Speaker 2>program causing trouble. Digging through logs is a core troubleshooting skill.

599
00:29:13.039 --> 00:29:15.000
<v Speaker 1>Any other quick troubleshooting tips mentioned.

600
00:29:14.960 --> 00:29:18.680
<v Speaker 2>Basic network checks like if canfig or EPA to see

601
00:29:18.680 --> 00:29:22.599
<v Speaker 2>your IP address, and ping to test connectivity, and for gaming,

602
00:29:22.720 --> 00:29:26.640
<v Speaker 2>sometimes disabling desktop visual effects might slightly improve performance on

603
00:29:26.720 --> 00:29:29.839
<v Speaker 2>older hardware, though less of an issue now, and.

604
00:29:29.799 --> 00:29:32.200
<v Speaker 1>If you're really stuck back to the community yep.

605
00:29:32.400 --> 00:29:36.319
<v Speaker 2>The source reiterates Mint forums, related forums like a boontus

606
00:29:36.440 --> 00:29:40.359
<v Speaker 2>and the irc chat channels using x chat are great resources.

607
00:29:40.839 --> 00:29:44.359
<v Speaker 2>Describe the problem clearly, provide info, be patient, Help is

608
00:29:44.440 --> 00:29:45.119
<v Speaker 2>usually out there.

609
00:29:45.200 --> 00:29:48.640
<v Speaker 1>Okay. Finally, let's talk upgrades. Moving to a new major

610
00:29:48.759 --> 00:29:51.079
<v Speaker 1>version of Mint, like from Mint twenty one to Mint

611
00:29:51.119 --> 00:29:54.279
<v Speaker 1>twenty two. The source says there's no direct in place

612
00:29:54.400 --> 00:29:55.519
<v Speaker 1>upgrade that's correct.

613
00:29:55.599 --> 00:29:58.960
<v Speaker 2>Unlike Windows feature updates or macros upgrades, Mint doesn't typically

614
00:29:58.960 --> 00:30:01.119
<v Speaker 2>offer a way to just click a button and transform, say,

615
00:30:01.200 --> 00:30:04.240
<v Speaker 2>version twenty one into version twenty two while keeping everything running.

616
00:30:04.599 --> 00:30:07.039
<v Speaker 2>The recommended method is a fresh installation.

617
00:30:06.680 --> 00:30:07.720
<v Speaker 1>That sounds like a bit of a pain.

618
00:30:07.759 --> 00:30:11.279
<v Speaker 2>Honestly, it can seem like it. Yeah, the source acknowledges that,

619
00:30:11.720 --> 00:30:14.599
<v Speaker 2>but it also argues that clean installs often lead to

620
00:30:14.640 --> 00:30:17.319
<v Speaker 2>a more stable, cleaner system in the long run. In

621
00:30:17.400 --> 00:30:21.359
<v Speaker 2>place upgrades can sometimes bring old problems or weird configuration

622
00:30:21.519 --> 00:30:24.599
<v Speaker 2>conflicts along for the ride. A fresh start avoids that.

623
00:30:24.680 --> 00:30:27.359
<v Speaker 1>But this is where that separate home partition becomes the

624
00:30:27.400 --> 00:30:28.720
<v Speaker 1>hero again, right exactly.

625
00:30:28.799 --> 00:30:31.200
<v Speaker 2>This is the reason it's so highly recommended by the source.

626
00:30:31.519 --> 00:30:35.480
<v Speaker 2>The process is boot the installer for the new Mint version.

627
00:30:36.079 --> 00:30:39.279
<v Speaker 2>When you get to partitioning, choose the something else or

628
00:30:39.359 --> 00:30:43.279
<v Speaker 2>manual option, select your existing route partition and tell the

629
00:30:43.319 --> 00:30:45.440
<v Speaker 2>installer to format it and use it for the new

630
00:30:45.519 --> 00:30:46.200
<v Speaker 2>system route.

631
00:30:46.240 --> 00:30:47.960
<v Speaker 1>Okay, wipe the old OS right.

632
00:30:48.599 --> 00:30:51.480
<v Speaker 2>Then select your existing home partition, tell the installer to

633
00:30:51.559 --> 00:30:54.160
<v Speaker 2>use it as home, but crucially make sure the format

634
00:30:54.200 --> 00:30:55.599
<v Speaker 2>box is unchecked for Home.

635
00:30:56.640 --> 00:30:58.079
<v Speaker 1>Keep the home partition.

636
00:30:57.799 --> 00:31:01.440
<v Speaker 2>As is Precisely you finish the inte, you boot up

637
00:31:01.440 --> 00:31:05.119
<v Speaker 2>the new Mint version. It's a completely fresh operating system.

638
00:31:05.240 --> 00:31:10.160
<v Speaker 2>But poof all your documents, pictures, browser bookmarks, email settings,

639
00:31:10.200 --> 00:31:13.240
<v Speaker 2>application configurations from your old home are right there waiting

640
00:31:13.240 --> 00:31:13.519
<v Speaker 2>for you.

641
00:31:13.759 --> 00:31:16.559
<v Speaker 1>That makes the fresh install sound way less intimidating.

642
00:31:16.680 --> 00:31:19.839
<v Speaker 2>It really does then the last step is to use

643
00:31:19.880 --> 00:31:23.279
<v Speaker 2>that Mint backup tool we mentioned, restore from the backup

644
00:31:23.319 --> 00:31:26.799
<v Speaker 2>of your installed software list and let the package manager

645
00:31:26.880 --> 00:31:30.640
<v Speaker 2>reinstall all your favorite applications automatically onto the new system.

646
00:31:30.759 --> 00:31:32.559
<v Speaker 2>It's a very effective strategy.

647
00:31:32.720 --> 00:31:35.400
<v Speaker 1>The source also mentions LTS releases as a way to

648
00:31:35.440 --> 00:31:36.319
<v Speaker 1>do this less often.

649
00:31:36.400 --> 00:31:39.720
<v Speaker 2>Yeah, LTS stands for long Term Support. These versions come

650
00:31:39.759 --> 00:31:43.200
<v Speaker 2>out less frequently but are supported with security updates for longer,

651
00:31:43.240 --> 00:31:46.440
<v Speaker 2>typically three years for Mint these days, compared to maybe

652
00:31:46.680 --> 00:31:49.759
<v Speaker 2>nine months for the interim releases. If you stick with

653
00:31:49.839 --> 00:31:52.519
<v Speaker 2>LTS versions, you only need to do this fresh install,

654
00:31:52.640 --> 00:31:54.319
<v Speaker 2>keep home dance every three years or so.

655
00:31:54.799 --> 00:31:56.400
<v Speaker 1>What's the downside of LTS.

656
00:31:56.920 --> 00:32:00.000
<v Speaker 2>The main trade off is that the software in LTS version,

657
00:32:00.240 --> 00:32:03.960
<v Speaker 2>the kernel, applications libraries, tends to be a bit older,

658
00:32:04.119 --> 00:32:06.519
<v Speaker 2>less cutting edge than in the standard releases that come

659
00:32:06.559 --> 00:32:10.079
<v Speaker 2>out more often. So it's stability and longevity versus having

660
00:32:10.079 --> 00:32:13.000
<v Speaker 2>the absolute latest features. Depends on your priorities.

661
00:32:13.039 --> 00:32:15.960
<v Speaker 1>Wow. Okay, that really was a deep dive, drawing heavily

662
00:32:15.960 --> 00:32:18.119
<v Speaker 1>on that Listener source material. We covered a ton of ground.

663
00:32:18.240 --> 00:32:18.880
<v Speaker 2>We really did.

664
00:32:19.160 --> 00:32:23.880
<v Speaker 1>From the basics of why Linux, why meant through installation

665
00:32:24.039 --> 00:32:30.160
<v Speaker 1>planning that home trick is key exploring the Cinnamon desktop workspaces.

666
00:32:30.240 --> 00:32:35.000
<v Speaker 2>Getting hands on with the terminal CDLSNA manfind.

667
00:32:34.519 --> 00:32:41.880
<v Speaker 1>Right, then system management, storage, software packages, users, those tricky permissions, networking, SSH.

668
00:32:41.519 --> 00:32:46.720
<v Speaker 2>Security two, firewall with GUFF, the virus myth, clarified backups.

669
00:32:46.359 --> 00:32:50.759
<v Speaker 1>And even advanced stuff like aliases, cron for automation, troubleshooting logs,

670
00:32:51.039 --> 00:32:52.880
<v Speaker 1>and that whole reinstallation strategy.

671
00:32:52.960 --> 00:32:55.640
<v Speaker 2>It really shows the source provides a solid roadmap, you know,

672
00:32:55.720 --> 00:32:59.240
<v Speaker 2>from being a brand new user to understanding the fundamentals

673
00:32:59.240 --> 00:33:03.240
<v Speaker 2>of managing this effectively. It nicely bridges a gap between

674
00:33:03.240 --> 00:33:06.759
<v Speaker 2>the EASYGUI stuff and the power you get from the command.

675
00:33:06.519 --> 00:33:09.400
<v Speaker 1>Line, and it really underscores the control and flexibility you

676
00:33:09.480 --> 00:33:11.599
<v Speaker 1>get when you start to understand how things work under

677
00:33:11.599 --> 00:33:13.799
<v Speaker 1>the hood a bit more definitely. So what's the takeaway

678
00:33:13.799 --> 00:33:14.720
<v Speaker 1>for you listening to.

679
00:33:14.720 --> 00:33:17.519
<v Speaker 2>All this, Well, hopefully it's that you've got a clearer

680
00:33:17.559 --> 00:33:20.559
<v Speaker 2>picture based on this material of how to not just

681
00:33:20.680 --> 00:33:22.960
<v Speaker 2>use Mint, but how to manage it, customize it, and

682
00:33:23.039 --> 00:33:24.880
<v Speaker 2>fix things when they occasionally break.

683
00:33:25.039 --> 00:33:27.240
<v Speaker 1>So here's a final thought to chew one. Based on

684
00:33:27.319 --> 00:33:30.079
<v Speaker 1>everything we just discussed, what's one specific thing from this

685
00:33:30.480 --> 00:33:33.400
<v Speaker 1>deep dive that you might actually try out. Maybe fire

686
00:33:33.480 --> 00:33:36.240
<v Speaker 1>up a Mint Live USB if you haven't before. Will

687
00:33:36.240 --> 00:33:39.720
<v Speaker 1>you try navigating directories with cdn LS, use Man to

688
00:33:39.720 --> 00:33:42.599
<v Speaker 1>look up at command play with workspaces. Maybe try setting

689
00:33:42.640 --> 00:33:45.200
<v Speaker 1>a simple guff rule, or even just look up the

690
00:33:45.200 --> 00:33:49.000
<v Speaker 1>syntax for a basic crown job. Pick one thing good challenge.

691
00:33:49.039 --> 00:33:51.480
<v Speaker 1>We get massive thanks for providing the source material for this.

692
00:33:51.880 --> 00:33:55.519
<v Speaker 1>Keep exploring, keep learning Linux. Mint is a fantastic platform

693
00:33:55.559 --> 00:33:56.079
<v Speaker 1>to do that on