WEBVTT

1
00:00:00.160 --> 00:00:02.879
<v Speaker 1>Welcome to our deep dive. Today. We're going to be

2
00:00:02.919 --> 00:00:08.320
<v Speaker 1>looking at Linux system administration. We're cracking Open Practical Linux

3
00:00:08.320 --> 00:00:11.279
<v Speaker 1>System Administration by Kenneth Hess.

4
00:00:11.519 --> 00:00:14.119
<v Speaker 2>Oh yeah, and uh a classic.

5
00:00:14.160 --> 00:00:17.199
<v Speaker 1>It covers a lot. It really does everything from installation

6
00:00:17.399 --> 00:00:23.120
<v Speaker 1>and configuration to managing storage, securing your system, and even

7
00:00:23.160 --> 00:00:24.120
<v Speaker 1>some career advice.

8
00:00:24.359 --> 00:00:24.960
<v Speaker 2>Absolutely.

9
00:00:25.079 --> 00:00:25.280
<v Speaker 1>Yeah.

10
00:00:25.359 --> 00:00:27.719
<v Speaker 2>Yeah, it's a real soup to nuts kind of guide

11
00:00:27.800 --> 00:00:31.199
<v Speaker 2>for anyone, you know, if you want to truly master Linux.

12
00:00:31.239 --> 00:00:32.840
<v Speaker 1>Yeah, it sounds like you're ready to go beyond.

13
00:00:32.679 --> 00:00:34.159
<v Speaker 2>The basics here, Yeah, let's do it.

14
00:00:34.359 --> 00:00:38.000
<v Speaker 1>So let's start with those foundations installing Linux, getting comfortable

15
00:00:38.000 --> 00:00:38.240
<v Speaker 1>with the.

16
00:00:38.159 --> 00:00:40.679
<v Speaker 2>Command line, right into the command line. Yeah, the book

17
00:00:40.719 --> 00:00:43.159
<v Speaker 2>dives right in. And it's funny because the command line

18
00:00:43.200 --> 00:00:46.079
<v Speaker 2>it's not just for beginners. It's the cissedmin's control center.

19
00:00:46.280 --> 00:00:47.960
<v Speaker 2>It's how we get things done right.

20
00:00:47.840 --> 00:00:50.799
<v Speaker 1>Like LS for listing files. But I'm curious about those

21
00:00:50.840 --> 00:00:53.560
<v Speaker 1>hitter files. Oh yeah, that always seemed a bit mysterious.

22
00:00:53.640 --> 00:00:56.200
<v Speaker 2>They're kind of think of them as like the backstage

23
00:00:56.240 --> 00:00:59.000
<v Speaker 2>of your system. Okay, you know all those configuration files. Okay,

24
00:00:59.039 --> 00:01:02.399
<v Speaker 2>like boshiyamik which which customizes your shell, or dot esh

25
00:01:03.000 --> 00:01:07.959
<v Speaker 2>for managing secure connections. All those dot files and if

26
00:01:07.959 --> 00:01:12.439
<v Speaker 2>you want to see them, land AAATA is your backstage pass.

27
00:01:12.519 --> 00:01:15.159
<v Speaker 1>That's cool. So it's not just about finding those sneaky

28
00:01:15.200 --> 00:01:18.079
<v Speaker 1>dot files, but understanding their power.

29
00:01:19.200 --> 00:01:21.959
<v Speaker 2>They do a lot. Okay, and even something as simple

30
00:01:22.000 --> 00:01:24.640
<v Speaker 2>as shutting down rebooting, you got to do it right

31
00:01:24.799 --> 00:01:26.359
<v Speaker 2>really to avoid data corruption.

32
00:01:26.599 --> 00:01:27.079
<v Speaker 1>Interesting.

33
00:01:27.359 --> 00:01:30.319
<v Speaker 2>Yeah, the book covers all those essential details, all that

34
00:01:30.359 --> 00:01:30.879
<v Speaker 2>good stuff.

35
00:01:31.000 --> 00:01:34.879
<v Speaker 1>Let's talk about the root user, that ultimate power in.

36
00:01:34.840 --> 00:01:36.480
<v Speaker 2>Linux, the ultimate power.

37
00:01:36.560 --> 00:01:40.200
<v Speaker 1>The book stresses using pseudo wisely pseudo.

38
00:01:40.359 --> 00:01:43.879
<v Speaker 2>Yeah, it's like having a scalpel or chainsaw in surgery.

39
00:01:44.599 --> 00:01:48.000
<v Speaker 2>Like logging in directly as root. That's like wielding that chainsaw.

40
00:01:48.159 --> 00:01:50.599
<v Speaker 2>You might get the job done, but you're going to

41
00:01:50.640 --> 00:01:52.840
<v Speaker 2>cause a lot of collateral damage. Right, It's like you're

42
00:01:52.920 --> 00:01:54.640
<v Speaker 2>using the scalpel precisely when needed.

43
00:01:54.719 --> 00:01:57.480
<v Speaker 1>Okay, So, but isn't pseudo still risky if you don't

44
00:01:57.480 --> 00:01:58.439
<v Speaker 1>know the commands are running.

45
00:02:00.200 --> 00:02:01.120
<v Speaker 2>That's a great point.

46
00:02:01.560 --> 00:02:04.120
<v Speaker 1>Like you could accidentally wipe out important system files.

47
00:02:04.239 --> 00:02:06.200
<v Speaker 2>That's a really good point. That's why the book really

48
00:02:06.200 --> 00:02:11.960
<v Speaker 2>emphasises understanding each command before you so do it blindly.

49
00:02:12.080 --> 00:02:13.919
<v Speaker 2>Using pseudo can lead to disaster.

50
00:02:14.159 --> 00:02:17.759
<v Speaker 1>So knowledge is power. Knowledge is power and pseudo amplifies it.

51
00:02:17.759 --> 00:02:20.159
<v Speaker 2>It really does better or worse? Yeah, for better or

52
00:02:20.159 --> 00:02:20.479
<v Speaker 2>for worse.

53
00:02:20.520 --> 00:02:23.759
<v Speaker 1>Now, the book also dives into file permissions with.

54
00:02:24.120 --> 00:02:27.840
<v Speaker 2>Oh yeah, shmode. This is about controlling who can access what.

55
00:02:28.240 --> 00:02:32.400
<v Speaker 2>You can use numbers or symbolic modes to set read, write,

56
00:02:33.039 --> 00:02:37.199
<v Speaker 2>and execute permissions for the owner, the group, and everyone else.

57
00:02:37.280 --> 00:02:39.960
<v Speaker 2>It's like setting the locks on your data's doors.

58
00:02:40.599 --> 00:02:43.039
<v Speaker 1>Okay, I'm starting to see the analogy here. Yeah, what

59
00:02:43.159 --> 00:02:45.840
<v Speaker 1>about mask? That one always seemed a bit confusing to

60
00:02:45.919 --> 00:02:46.840
<v Speaker 1>Now mask.

61
00:02:47.039 --> 00:02:51.280
<v Speaker 2>Think of it as the default security template for new files.

62
00:02:51.400 --> 00:02:53.439
<v Speaker 2>Yeah you know. Let's say you want every new file

63
00:02:53.520 --> 00:02:58.599
<v Speaker 2>you create to be private by default, you'd set a

64
00:02:58.680 --> 00:03:02.120
<v Speaker 2>mask that prevents others from reading or writing to it.

65
00:03:02.120 --> 00:03:05.159
<v Speaker 2>It's like setting the baseline security level for your whole system.

66
00:03:05.400 --> 00:03:09.520
<v Speaker 1>So it's not about individual file permissions, but setting the

67
00:03:09.560 --> 00:03:11.599
<v Speaker 1>starting point for all new files.

68
00:03:11.639 --> 00:03:13.840
<v Speaker 2>We got it. It saves you from having to manually

69
00:03:13.879 --> 00:03:16.159
<v Speaker 2>set permissions every time you create a new file.

70
00:03:17.360 --> 00:03:21.319
<v Speaker 1>Now's shift gears to something a bit more fun. Customizing

71
00:03:21.360 --> 00:03:24.759
<v Speaker 1>your shell prompt. Oh yeah, who doesn't love a bit

72
00:03:24.800 --> 00:03:25.840
<v Speaker 1>of personalization.

73
00:03:26.199 --> 00:03:29.400
<v Speaker 2>It's all about making your command line workspace ye feel

74
00:03:29.400 --> 00:03:33.240
<v Speaker 2>like your own Yeah, You can use escape characters to

75
00:03:33.360 --> 00:03:37.400
<v Speaker 2>add things like your username, host name, even the current

76
00:03:37.439 --> 00:03:40.080
<v Speaker 2>time to your prompt. Oh wow, the book gives you

77
00:03:40.120 --> 00:03:41.879
<v Speaker 2>some cool examples to get you started.

78
00:03:42.159 --> 00:03:47.439
<v Speaker 1>Speaking of personalization, what about user account management? Creating, modifying,

79
00:03:47.560 --> 00:03:48.759
<v Speaker 1>deleting that kind of thing.

80
00:03:48.919 --> 00:03:52.840
<v Speaker 2>User account management, it's crucial for any multi user system.

81
00:03:53.199 --> 00:03:57.039
<v Speaker 2>The book covers it all, adding new users, managing passwords

82
00:03:57.039 --> 00:04:00.400
<v Speaker 2>and groups. And let's not forget about password security.

83
00:04:00.159 --> 00:04:03.199
<v Speaker 1>Right Strong passwords are the first line of defense. A

84
00:04:03.199 --> 00:04:05.639
<v Speaker 1>book mentions using the change command, what's that all about?

85
00:04:05.800 --> 00:04:09.759
<v Speaker 2>Change? Yeah, this let's unforce password aging policies. You can

86
00:04:09.840 --> 00:04:13.680
<v Speaker 2>set how often users have to change their passwords and

87
00:04:13.800 --> 00:04:15.840
<v Speaker 2>even prevent them from reusing old ones.

88
00:04:15.919 --> 00:04:16.600
<v Speaker 1>Oh it's good.

89
00:04:17.079 --> 00:04:20.199
<v Speaker 2>It's a key tool for keeping those pesky hackers out.

90
00:04:20.519 --> 00:04:23.480
<v Speaker 1>So it's like a password expiration date, forcing people to

91
00:04:23.600 --> 00:04:24.360
<v Speaker 1>keep things.

92
00:04:24.120 --> 00:04:25.319
<v Speaker 2>Fresh, keep it fresh.

93
00:04:25.519 --> 00:04:28.079
<v Speaker 1>Makes sense. But speaking of keeping things secure, let's move

94
00:04:28.120 --> 00:04:31.720
<v Speaker 1>on to the big one, networking and security, the big one.

95
00:04:32.079 --> 00:04:37.079
<v Speaker 1>What's the book's approach to keeping a networked Linux system safe?

96
00:04:37.240 --> 00:04:41.879
<v Speaker 2>I think it all starts with minimizing the attack surface. Okay,

97
00:04:42.040 --> 00:04:45.639
<v Speaker 2>like closing off unnecessary ports. You know, think of your

98
00:04:45.680 --> 00:04:48.839
<v Speaker 2>system as a castle. With multiple gates, you only want

99
00:04:48.839 --> 00:04:50.240
<v Speaker 2>to leave the essential ones open.

100
00:04:50.399 --> 00:04:52.879
<v Speaker 1>I like that castle analogy, So it's about making it

101
00:04:52.920 --> 00:04:55.399
<v Speaker 1>as hard as possible for attackers to find a way in.

102
00:04:55.560 --> 00:04:56.120
<v Speaker 2>Absolutely.

103
00:04:56.279 --> 00:04:56.639
<v Speaker 1>Yeah.

104
00:04:56.680 --> 00:05:00.000
<v Speaker 2>And the book dies into securing SSH, which is really

105
00:05:00.360 --> 00:05:03.560
<v Speaker 2>the gateway to your system, covers tools like TCP wrappers

106
00:05:03.560 --> 00:05:07.199
<v Speaker 2>and firewalls. Okay, you know, acting as extra layers of

107
00:05:07.240 --> 00:05:09.360
<v Speaker 2>defense on those castle walls.

108
00:05:09.040 --> 00:05:12.120
<v Speaker 1>So you're not just locking the doors, but reinforcing the

109
00:05:12.160 --> 00:05:15.560
<v Speaker 1>walls and setting up guard towers exactly. Okay, let's get

110
00:05:15.560 --> 00:05:18.759
<v Speaker 1>into something that's always a bit daunting, storage administration.

111
00:05:19.360 --> 00:05:19.879
<v Speaker 2>Oh yeah.

112
00:05:20.000 --> 00:05:25.399
<v Speaker 1>The book mentions disc partitions, file systems, and even something

113
00:05:25.439 --> 00:05:27.160
<v Speaker 1>called logical volumes.

114
00:05:27.360 --> 00:05:31.519
<v Speaker 2>Logical volumes that give you amazing flexibility with storage management. Okay,

115
00:05:31.680 --> 00:05:36.439
<v Speaker 2>imagine you have a database that's growing rapidly. With LVM,

116
00:05:36.560 --> 00:05:40.240
<v Speaker 2>you can resize that storage on the fly without taking

117
00:05:40.319 --> 00:05:44.560
<v Speaker 2>the system down, unlike traditional partitions. Wow, it's a real

118
00:05:44.600 --> 00:05:45.199
<v Speaker 2>game changer.

119
00:05:45.279 --> 00:05:47.959
<v Speaker 1>Okay, that makes logical volume sound way more exciting than

120
00:05:48.000 --> 00:05:48.360
<v Speaker 1>I thought.

121
00:05:48.680 --> 00:05:49.399
<v Speaker 2>Oh yeah, they are.

122
00:05:49.519 --> 00:05:52.399
<v Speaker 1>So they're like dynamic containers for your storage space.

123
00:05:52.439 --> 00:05:52.879
<v Speaker 2>You got it.

124
00:05:52.920 --> 00:05:53.160
<v Speaker 1>Cool.

125
00:05:53.240 --> 00:05:57.639
<v Speaker 2>You can resize them, take snapshots, even combine multiple physical

126
00:05:57.680 --> 00:06:01.920
<v Speaker 2>discs into one logical volume. Oh wow, it's amazing.

127
00:06:02.000 --> 00:06:05.399
<v Speaker 1>So it's like taking lego blocks and building whatever storage

128
00:06:05.399 --> 00:06:06.279
<v Speaker 1>structure you need.

129
00:06:06.519 --> 00:06:08.000
<v Speaker 2>Yeah, exactly, pretty cool.

130
00:06:08.120 --> 00:06:12.600
<v Speaker 1>The book also mentions decommissioning a system and securely wiping discs.

131
00:06:12.639 --> 00:06:13.879
<v Speaker 1>Why is that so crucial?

132
00:06:13.959 --> 00:06:16.240
<v Speaker 2>Imagine if someone got a hold of your old server

133
00:06:16.839 --> 00:06:20.240
<v Speaker 2>and was able to recover sensitive client information, it would

134
00:06:20.279 --> 00:06:21.000
<v Speaker 2>be a disaster.

135
00:06:21.279 --> 00:06:21.720
<v Speaker 1>Yeah.

136
00:06:21.800 --> 00:06:26.240
<v Speaker 2>Securely wiping a disc goes beyond just formatting it, you know,

137
00:06:26.800 --> 00:06:30.040
<v Speaker 2>It ensures that the deity is truly unrecoverable. The book

138
00:06:30.040 --> 00:06:33.839
<v Speaker 2>outlines a multi step process to do this safely.

139
00:06:34.639 --> 00:06:37.000
<v Speaker 1>Makes sense. You wouldn't want to leave any digital skeletons

140
00:06:37.000 --> 00:06:40.879
<v Speaker 1>in the closet, definitely not Well, we've covered a lot

141
00:06:40.879 --> 00:06:44.000
<v Speaker 1>of ground already, from the basics of the command line

142
00:06:44.000 --> 00:06:46.519
<v Speaker 1>to the intricacies of storage and security.

143
00:06:46.720 --> 00:06:48.519
<v Speaker 2>Yeah we've been busy, Yeah.

144
00:06:48.240 --> 00:06:52.920
<v Speaker 1>We have, but a truly masterful Linux Syssigmund. They go

145
00:06:53.000 --> 00:06:54.199
<v Speaker 1>beyond just set up.

146
00:06:54.319 --> 00:06:57.399
<v Speaker 2>You know, right, keeping those servers humming along smoothly. It's

147
00:06:57.439 --> 00:07:01.040
<v Speaker 2>not always glamorous, but it's crucial for avoiding those late

148
00:07:01.160 --> 00:07:02.319
<v Speaker 2>night troubleshooting sessions.

149
00:07:02.360 --> 00:07:04.040
<v Speaker 1>It really is. It's like taking care of your car,

150
00:07:04.399 --> 00:07:08.199
<v Speaker 1>you know, regular checkups and maintenance prevent those major breakdowns.

151
00:07:08.279 --> 00:07:11.480
<v Speaker 2>So what are some of the key things that assisted

152
00:07:11.519 --> 00:07:12.480
<v Speaker 2>men should keep an eye on?

153
00:07:12.680 --> 00:07:15.319
<v Speaker 1>Disk space is a big one. Okay, servers can become

154
00:07:15.360 --> 00:07:17.680
<v Speaker 1>digital hoarders if you're not caring.

155
00:07:17.759 --> 00:07:21.240
<v Speaker 2>That's the book recommends using tools like do, which lets

156
00:07:21.279 --> 00:07:25.560
<v Speaker 2>you analyze disc usage and find those space hogging files

157
00:07:25.560 --> 00:07:28.800
<v Speaker 2>and directories like a spring cleaning for your server makes sense.

158
00:07:28.800 --> 00:07:30.680
<v Speaker 1>You don't want your server turning into that one junk

159
00:07:30.759 --> 00:07:32.199
<v Speaker 1>drawer everyone has in their kitchen.

160
00:07:32.319 --> 00:07:32.839
<v Speaker 2>Exactly.

161
00:07:33.120 --> 00:07:36.160
<v Speaker 1>What about system updates? I know those are crucial for security.

162
00:07:36.439 --> 00:07:39.920
<v Speaker 2>Absolutely. Updates are like patching those holes in your castle walls.

163
00:07:40.519 --> 00:07:45.519
<v Speaker 2>The book covers different package managers like RPM, DNF, and APT.

164
00:07:46.120 --> 00:07:48.639
<v Speaker 2>They each have their quarks, but they all share the

165
00:07:48.680 --> 00:07:52.480
<v Speaker 2>goal of keeping your system up to date and protected.

166
00:07:52.680 --> 00:07:55.519
<v Speaker 1>It's amazing how many different tools and approaches there are

167
00:07:55.920 --> 00:07:56.839
<v Speaker 1>in the Linux world.

168
00:07:57.199 --> 00:07:57.800
<v Speaker 2>It really is.

169
00:07:58.079 --> 00:08:03.040
<v Speaker 1>Speaking of tools, I've always been fascinated by scripting and automation.

170
00:08:03.639 --> 00:08:06.000
<v Speaker 1>It's like having your own army of digital helpers.

171
00:08:06.079 --> 00:08:07.560
<v Speaker 2>That's a great way to put it. You're getting it.

172
00:08:07.680 --> 00:08:11.680
<v Speaker 2>So the book introduces shell scripting, which is basically like

173
00:08:11.920 --> 00:08:14.680
<v Speaker 2>writing instructions for your system to follow okay, and then

174
00:08:14.720 --> 00:08:17.240
<v Speaker 2>there's a kron the task scheduler. It's like setting an

175
00:08:17.240 --> 00:08:20.800
<v Speaker 2>alarm clock for your scripts to run at specific times,

176
00:08:21.040 --> 00:08:21.360
<v Speaker 2>so you.

177
00:08:21.319 --> 00:08:25.480
<v Speaker 1>Can automate things like backups or system checks exactly.

178
00:08:25.560 --> 00:08:28.839
<v Speaker 2>The book even provides a simple backup script example that

179
00:08:28.920 --> 00:08:30.439
<v Speaker 2>you can adapt for your own needs.

180
00:08:30.560 --> 00:08:34.639
<v Speaker 1>A backup script. Every cisadmin's best friend. Absolutely, It's like

181
00:08:34.679 --> 00:08:36.679
<v Speaker 1>having an insurance policy for your data.

182
00:08:37.000 --> 00:08:38.000
<v Speaker 2>I like that analogy.

183
00:08:38.519 --> 00:08:41.919
<v Speaker 1>Speaking of insurance, the book also stresses the importance of

184
00:08:42.000 --> 00:08:46.600
<v Speaker 1>time synchronization using NTP and the Krony utility. If your

185
00:08:46.600 --> 00:08:50.759
<v Speaker 1>server's clock is off, those scheduled tasks won't run as expected.

186
00:08:50.919 --> 00:08:51.440
<v Speaker 2>Exact right.

187
00:08:51.519 --> 00:08:53.480
<v Speaker 1>You don't want your backups happening at the wrong time

188
00:08:53.600 --> 00:08:56.639
<v Speaker 1>or your log files getting messed up. Time is critical

189
00:08:56.679 --> 00:08:59.279
<v Speaker 1>in the digital world, it really is. But let's not

190
00:08:59.399 --> 00:09:01.559
<v Speaker 1>forget about those Windows users out there.

191
00:09:01.639 --> 00:09:03.080
<v Speaker 2>Oh yeah, those Windows users.

192
00:09:03.120 --> 00:09:08.200
<v Speaker 1>How does the book address interoperability between Linux and Windows systems.

193
00:09:08.279 --> 00:09:10.919
<v Speaker 2>That's where Samba comes in. It's like building a bridge

194
00:09:11.600 --> 00:09:14.399
<v Speaker 2>between those two kingdoms, allowing you to share files and

195
00:09:14.440 --> 00:09:15.440
<v Speaker 2>printers seamlessly.

196
00:09:15.639 --> 00:09:19.120
<v Speaker 1>So no more that sneakernet stuff, copying files to a

197
00:09:19.200 --> 00:09:21.720
<v Speaker 1>USB drive and walking it over to the Windows machine.

198
00:09:21.759 --> 00:09:26.919
<v Speaker 2>Exactly. Samba lets you share folders directly, making collaboration a breeze.

199
00:09:26.960 --> 00:09:27.519
<v Speaker 1>That's great.

200
00:09:27.559 --> 00:09:31.960
<v Speaker 2>The book explains how to configure shares, manage permissions, and

201
00:09:32.039 --> 00:09:34.600
<v Speaker 2>even use the ELM hosts file for name resolution.

202
00:09:35.159 --> 00:09:35.559
<v Speaker 1>Cool.

203
00:09:35.679 --> 00:09:39.080
<v Speaker 2>You know it's like setting up a diplomatic channel between.

204
00:09:38.759 --> 00:09:41.799
<v Speaker 1>The two worlds diplomacy. I love it. Okay. Let's face it.

205
00:09:41.840 --> 00:09:44.720
<v Speaker 1>Even with the best maintenance and security, things can still

206
00:09:44.759 --> 00:09:50.360
<v Speaker 1>go wrong. Systems crash, applications, misbehave, hardware fails. How does

207
00:09:50.360 --> 00:09:53.639
<v Speaker 1>the book equip you to handle those troubleshooting moments?

208
00:09:53.879 --> 00:09:56.600
<v Speaker 2>You know it starts with understanding your system inside and out.

209
00:09:56.679 --> 00:09:57.039
<v Speaker 1>Okay.

210
00:09:57.240 --> 00:10:02.279
<v Speaker 2>The book encourages a methodical approach to troubleshooting. First, yeah,

211
00:10:02.399 --> 00:10:05.120
<v Speaker 2>check the system logs. They often contain clues about what

212
00:10:05.200 --> 00:10:08.360
<v Speaker 2>went wrong. Okay. The DMAZ command is your friend. Here

213
00:10:08.639 --> 00:10:11.679
<v Speaker 2>it shows you kernel messages that can help pinpoint the issue.

214
00:10:11.720 --> 00:10:14.519
<v Speaker 1>So DEMAS is like the detective's magnifying glass for the

215
00:10:14.559 --> 00:10:15.200
<v Speaker 1>Linux kernel.

216
00:10:15.279 --> 00:10:15.679
<v Speaker 2>Exactly.

217
00:10:15.759 --> 00:10:16.320
<v Speaker 1>That's cool.

218
00:10:16.440 --> 00:10:19.879
<v Speaker 2>The book also provides tips for filtering through those logs

219
00:10:20.080 --> 00:10:23.840
<v Speaker 2>so you're not overwhelmed with information. And then there's application logs,

220
00:10:24.480 --> 00:10:28.200
<v Speaker 2>which can reveal problems specific to certain software. You know,

221
00:10:28.320 --> 00:10:31.799
<v Speaker 2>it's all about gathering evidence to solve the mystery.

222
00:10:32.480 --> 00:10:35.679
<v Speaker 1>I like the detective analogy. But what about those times

223
00:10:35.720 --> 00:10:38.720
<v Speaker 1>when a simple reboot doesn't fix things? What if the

224
00:10:38.759 --> 00:10:41.039
<v Speaker 1>problem is more serious, like a hardware failure.

225
00:10:41.519 --> 00:10:46.159
<v Speaker 2>The book covers basic hardware diagnostics okay, helping you identify

226
00:10:46.240 --> 00:10:50.240
<v Speaker 2>faulty components like RAM or hard drives. It's like running

227
00:10:50.240 --> 00:10:53.159
<v Speaker 2>a health check on your server's physical body.

228
00:10:53.320 --> 00:10:53.679
<v Speaker 1>Okay.

229
00:10:54.279 --> 00:10:57.960
<v Speaker 2>And when it comes to persistent software problems, sometimes the

230
00:10:57.960 --> 00:11:01.080
<v Speaker 2>best solution is the remove and re install strategy.

231
00:11:01.159 --> 00:11:04.080
<v Speaker 1>It's like hitting the reset button, giving the application a

232
00:11:04.120 --> 00:11:04.639
<v Speaker 1>fresh start.

233
00:11:04.840 --> 00:11:05.159
<v Speaker 2>Exactly.

234
00:11:05.240 --> 00:11:07.679
<v Speaker 1>Imagine that's a last resort after you've exhausted all other

235
00:11:07.720 --> 00:11:08.519
<v Speaker 1>options exactly.

236
00:11:08.519 --> 00:11:12.840
<v Speaker 2>Troubleshooting is about being patient and methodical. The book emphasizes

237
00:11:12.960 --> 00:11:17.399
<v Speaker 2>understanding the problem before jumping to solutions. Okay, sometimes the

238
00:11:17.440 --> 00:11:18.679
<v Speaker 2>simplest fix is the right one.

239
00:11:18.799 --> 00:11:21.440
<v Speaker 1>Okay. I'm starting to feel more confident about handling those

240
00:11:21.440 --> 00:11:25.279
<v Speaker 1>inevitable troubleshooting moments. But security is such a huge topic.

241
00:11:25.399 --> 00:11:27.840
<v Speaker 1>I feel like we've only scratched the surface. Yeah, what

242
00:11:27.960 --> 00:11:31.519
<v Speaker 1>are some of the more advanced security measures covered in

243
00:11:31.519 --> 00:11:31.799
<v Speaker 1>the book.

244
00:11:31.919 --> 00:11:35.919
<v Speaker 2>Well, the book advocates for a layered security approach. It

245
00:11:35.960 --> 00:11:41.879
<v Speaker 2>introduces the concept of a security Technical Implementation Guide or STIG.

246
00:11:42.399 --> 00:11:46.399
<v Speaker 1>STIG that sounds serious, it is, What exactly does it involve.

247
00:11:46.480 --> 00:11:49.919
<v Speaker 2>It's basically a set of security guidelines and best practices

248
00:11:50.519 --> 00:11:53.320
<v Speaker 2>for hardening your system. Think of it as a blueprint

249
00:11:53.679 --> 00:11:57.200
<v Speaker 2>for building a fortress around your system. The book provides

250
00:11:57.240 --> 00:12:01.639
<v Speaker 2>examples of STIG controls and how to implement them, focusing

251
00:12:01.679 --> 00:12:04.919
<v Speaker 2>on high severity items. You're essentially locking down every possible

252
00:12:05.080 --> 00:12:08.519
<v Speaker 2>entry point and making it much harder for attackers to

253
00:12:08.559 --> 00:12:08.840
<v Speaker 2>get in.

254
00:12:09.080 --> 00:12:12.240
<v Speaker 1>So it's about going above and beyond the basic security

255
00:12:12.240 --> 00:12:16.159
<v Speaker 1>measures like strong passwords and firewalls exactly. You're creating a

256
00:12:16.240 --> 00:12:18.240
<v Speaker 1>multi layered defense system.

257
00:12:17.960 --> 00:12:21.279
<v Speaker 2>You got it, and to detect any intruders who managed

258
00:12:21.279 --> 00:12:25.000
<v Speaker 2>to slip through the cracks. The book dives into intrusion

259
00:12:25.080 --> 00:12:29.559
<v Speaker 2>detection techniques okay. It covers things like port scans, which

260
00:12:29.600 --> 00:12:32.480
<v Speaker 2>can reveal open ports that might be vulnerable.

261
00:12:32.559 --> 00:12:37.000
<v Speaker 1>So you're actively scanning for suspicious activity like a security

262
00:12:37.000 --> 00:12:39.200
<v Speaker 1>guard patrolling the perimeter.

263
00:12:38.960 --> 00:12:42.200
<v Speaker 2>Exactly, and to monitor for any changes within the system.

264
00:12:42.960 --> 00:12:46.159
<v Speaker 2>The book introduces the AID tool. Okay, it's like a

265
00:12:46.159 --> 00:12:48.919
<v Speaker 2>trip wire system that alerts you if any files are

266
00:12:48.960 --> 00:12:50.919
<v Speaker 2>modified unexpectedly.

267
00:12:50.279 --> 00:12:53.080
<v Speaker 1>So you're not just protecting the perimeter, but you're also

268
00:12:53.200 --> 00:12:55.559
<v Speaker 1>monitoring the inside for any signs of trouble. It's like

269
00:12:55.600 --> 00:12:58.159
<v Speaker 1>a comprehensive security system for your server.

270
00:12:58.559 --> 00:12:59.200
<v Speaker 2>Absolutely.

271
00:12:59.320 --> 00:12:59.519
<v Speaker 1>Yeah.

272
00:12:59.639 --> 00:13:02.799
<v Speaker 2>Boomphasizes that security is an ongoing process. It's not a

273
00:13:02.799 --> 00:13:05.919
<v Speaker 2>one time setup, you know. It's about staying vigilant and

274
00:13:05.960 --> 00:13:09.240
<v Speaker 2>proactive in a world of ever evolving threats. Yeah, and

275
00:13:09.279 --> 00:13:12.720
<v Speaker 2>speaking of evolving, let's shift our focus to the human

276
00:13:12.799 --> 00:13:14.320
<v Speaker 2>side of things, the human side of things.

277
00:13:14.559 --> 00:13:17.240
<v Speaker 1>We've covered a lot of technical ground, but as you said,

278
00:13:17.240 --> 00:13:20.200
<v Speaker 1>as sissmin is more than just a collection of technical skills.

279
00:13:20.679 --> 00:13:24.600
<v Speaker 1>This book also delves into the career aspects, which is

280
00:13:24.600 --> 00:13:25.720
<v Speaker 1>something I'm really interested in.

281
00:13:25.799 --> 00:13:30.200
<v Speaker 2>Oh yeah, it's often overlooked, but building a successful cissismin

282
00:13:30.320 --> 00:13:34.799
<v Speaker 2>career requires more than just knowing your way around a server.

283
00:13:35.120 --> 00:13:37.639
<v Speaker 1>So let's talk about certifications. Are they really a make

284
00:13:37.720 --> 00:13:39.679
<v Speaker 1>or break factor in the sissigmin world?

285
00:13:40.120 --> 00:13:43.720
<v Speaker 2>You know? The book offers a balanced perspective. Some certifications

286
00:13:43.720 --> 00:13:48.559
<v Speaker 2>have become more about memorizing answers than demonstrating real world skills,

287
00:13:49.320 --> 00:13:52.679
<v Speaker 2>but others, like the CISSP, they carry a lot of weight.

288
00:13:52.919 --> 00:13:56.559
<v Speaker 2>It shows potential employers that you're serious about security.

289
00:13:56.759 --> 00:13:59.559
<v Speaker 1>So it's about choosing certifications that align with your goals

290
00:14:00.120 --> 00:14:01.919
<v Speaker 1>and have real credibility in the industry.

291
00:14:02.000 --> 00:14:04.679
<v Speaker 2>Exactly, But certifications are just one piece of the puzzle.

292
00:14:05.039 --> 00:14:09.200
<v Speaker 2>The book really emphasizes continuous learning. Technology changes so fast

293
00:14:09.639 --> 00:14:13.240
<v Speaker 2>a good sissedmin is always picking up new skills, whether

294
00:14:13.279 --> 00:14:16.200
<v Speaker 2>it's through formal training or independent study.

295
00:14:16.399 --> 00:14:19.399
<v Speaker 1>I love that the author shares a story about how

296
00:14:19.480 --> 00:14:22.960
<v Speaker 1>he solved a tricky problem for a client using something

297
00:14:23.000 --> 00:14:26.679
<v Speaker 1>he learned through independent study. Yeah, it shows initiative and

298
00:14:26.720 --> 00:14:28.480
<v Speaker 1>a willingness to go the extra mile.

299
00:14:28.600 --> 00:14:31.480
<v Speaker 2>Absolutely, that's what sets a great sissegment apart, is that

300
00:14:31.600 --> 00:14:34.440
<v Speaker 2>drive to keep learning and pushing your boundaries.

301
00:14:34.480 --> 00:14:36.679
<v Speaker 1>The book also gets into the nitty gritty of the

302
00:14:36.759 --> 00:14:42.039
<v Speaker 1>job market, navigating online job boards, the importance of professional networking,

303
00:14:42.679 --> 00:14:45.080
<v Speaker 1>and even the rise of remote work. It feels very

304
00:14:45.120 --> 00:14:46.600
<v Speaker 1>relevant to today's landscape.

305
00:14:46.639 --> 00:14:50.840
<v Speaker 2>Absolutely offer some really solid advice for standing out in

306
00:14:50.879 --> 00:14:56.120
<v Speaker 2>a crowded field. Crafting a strong LinkedIn profile, showcasing your skills,

307
00:14:56.720 --> 00:15:00.440
<v Speaker 2>networking with other professionals can make a huge difference, not just.

308
00:15:00.360 --> 00:15:03.519
<v Speaker 1>About what you know, but also who you know and

309
00:15:03.559 --> 00:15:04.679
<v Speaker 1>how you present yourself.

310
00:15:04.720 --> 00:15:05.519
<v Speaker 2>It's all part of it.

311
00:15:05.600 --> 00:15:08.559
<v Speaker 1>And for those considering the entrepreneurial path, the book even

312
00:15:08.600 --> 00:15:12.240
<v Speaker 1>explores starting your own business, from managing clients to potentially

313
00:15:12.279 --> 00:15:13.200
<v Speaker 1>building a team.

314
00:15:13.320 --> 00:15:16.759
<v Speaker 2>Yeah, it's like a roadmap for different career trajectories within

315
00:15:16.799 --> 00:15:20.240
<v Speaker 2>the cisiman world. You know, you can specialize, go freelance, cloud,

316
00:15:20.279 --> 00:15:22.480
<v Speaker 2>the corporate ladder. There's so many options there, really are.

317
00:15:22.600 --> 00:15:25.879
<v Speaker 2>The key takeaway is that assisment career is a journey,

318
00:15:25.919 --> 00:15:26.799
<v Speaker 2>not a destination.

319
00:15:27.279 --> 00:15:27.480
<v Speaker 1>Right.

320
00:15:27.519 --> 00:15:30.679
<v Speaker 2>There's always new things to learn, new challenges to tackle,

321
00:15:31.159 --> 00:15:32.159
<v Speaker 2>new ways to grow.

322
00:15:32.799 --> 00:15:35.919
<v Speaker 1>So, as we wrap up this deep dive, what's the

323
00:15:35.960 --> 00:15:39.360
<v Speaker 1>one piece of advice from the book that really resonates

324
00:15:39.360 --> 00:15:39.600
<v Speaker 1>with you?

325
00:15:40.000 --> 00:15:43.919
<v Speaker 2>For me, it's that combination of continuous learning and a

326
00:15:43.960 --> 00:15:48.240
<v Speaker 2>security first mindset. Okay, technology never stands still, and neither

327
00:15:48.240 --> 00:15:52.399
<v Speaker 2>should assistiment. Every decision you make, from installing software to

328
00:15:52.440 --> 00:15:55.600
<v Speaker 2>configuring a firewall should be made with security in mind.

329
00:15:56.000 --> 00:15:59.120
<v Speaker 2>A secure system is a stable system, and that's what

330
00:15:59.159 --> 00:15:59.799
<v Speaker 2>we all strive for.

331
00:16:00.159 --> 00:16:04.000
<v Speaker 1>Well said, it seems like Practical Linux System Administration is

332
00:16:04.080 --> 00:16:06.240
<v Speaker 1>much more than just a technical manual. It's a guide

333
00:16:06.320 --> 00:16:09.679
<v Speaker 1>to navigating the ever evolving world of Linux and building

334
00:16:09.679 --> 00:16:10.960
<v Speaker 1>a fulfilling career in the.

335
00:16:10.919 --> 00:16:12.039
<v Speaker 2>Process it really is.

336
00:16:12.279 --> 00:16:14.559
<v Speaker 1>I know I will into all our listeners out there,

337
00:16:14.879 --> 00:16:18.399
<v Speaker 1>whether you're just starting out or you're a Seasons to Sadman,

338
00:16:18.960 --> 00:16:23.039
<v Speaker 1>Remember that learning never stops. Embrace those challenges, stay curious,

339
00:16:23.320 --> 00:16:24.639
<v Speaker 1>and keep those servers humming.