WEBVTT

1
00:00:02.050 --> 00:00:09.050
Open the Linux endpoint terminal to run commands inside your simulated lab.

2
00:00:09.300 --> 00:00:16.800
These examples use supported simulated shell features, not programs on your own computer.

3
00:00:20.750 --> 00:00:27.750
Create a short Bash script, then inspect its contents before running it.

4
00:00:29.150 --> 00:00:35.650
Run the script to report this endpoint’s real simulated interface state.

5
00:00:36.200 --> 00:00:43.700
A missing command reports an error; it does not become a successful result.

6
00:00:50.350 --> 00:00:57.350
Create a small Python script that reads and writes a device file.

7
00:00:59.250 --> 00:01:06.250
Run it with Python, then inspect the resulting file from the shell.

8
00:01:08.500 --> 00:01:16.500
A missing input file reports a clear error while the existing output remains intact.

9
00:01:22.100 --> 00:01:30.600
Use a supported Python subprocess call to inspect the same network state as the shell.

10
00:01:30.900 --> 00:01:38.400
This is a bounded Python environment, not an arbitrary package or host runtime.

11
00:01:43.500 --> 00:01:50.000
Open the Windows endpoint terminal and prepare a small PowerShell report.

12
00:01:50.600 --> 00:01:55.600
Inspect the report before running it with PowerShell.

13
00:01:56.750 --> 00:02:02.750
Compare its network information with the endpoint’s normal command output.

14
00:02:04.350 --> 00:02:10.850
A missing PowerShell script is reported without replacing the valid report.

15
00:02:10.950 --> 00:02:18.450
Keep scripts small, inspect their results, and save the lab separately when needed.