►
From YouTube: Red Hat Enterprise Linux Presents (E02): Enable SysAdmin, a Community for Linux Administrators
Description
A show that features the people and technology that make Red Hat Enterprise Linux into the the world’s leading enterprise Linux platform.
https://openshift.tv
A
Good
morning,
good
afternoon,
good
evening,
wherever
you're
hailing
from
welcome
to
another
episode
of
red
hat
enterprise,
linux
presents
here
on
openshift
tv,
I
am
chris
short
executive
producer
of
openshift
tv
today,
I
am
joined
by
the
wonderful
and
always
brilliant
scott
mcbryan
who's
brought
a
special
guest
with
him
scott.
Would
you
like
to
introduce
yourself
and
then
introduce
your
guest?
Maybe.
B
Sure
so
challenge
accepted
on
the
brilliance.
Maybe
I
will
not
introduce
this
guest
with
the
wrong
title
or
you
know
what
have
you
so
for
those
of
you
who
haven't
seen
it
before?
This
is
the
second
episode
of
red
hat
enterprise.
Linux
presents
our
guest.
Today
is
ken
hess,
who
is
an
author
and
editor
for
the
enable
sysadmin
community
which,
if
you've
not
seen
it,
is
redhat.com
and
yeah?
B
We
will
be
talking
with
ken
about
said
site
and
contributions
and
if
you've
not
seen
the
format
before
we
do
a
little
bit
of
interview
for
about
20
or
30
minutes,
and
then
we
transition
into
some
practical,
hands-on
demo.
So
I'm
thinking
I'll
take
some
inspiration
from
ken's
couple
of
articles
on
10,
most
essential
linux
commands
and
kind
of
parlay
that
into
10
essentials,
admin,
linux
commands
and
we'll
talk
about
them.
So
without
further
ado,
ken
watch
tell
us
a
little
bit
about
you.
C
Oh
gosh,
what
can
I
say?
I've
worked
with
red
hat
linux
for
25-ish
years
and
I
think
ever
since
red
hat
linux
4.0,
I
started
the
local
linux
users
group
here
in
tulsa
oklahoma
back
in
96,
and
let's
see
what
else,
I'm
a
community
manager
for
enable
sys
admin
and
have
done
tons
of
technology
writing
technology
journalism
and
also
I've
been
assist
admin
for
that
25-ish
years.
A
B
Five
two
was
pretty
good.
I
was
like
somewhere
in
the
fours,
but
yeah.
I
actually
several
years
ago,
was
working
in
professional
services
and
was
at
a
at
a
customer
site,
and
I
found
a
red
hat
linux
7.2
box,
not
rel72,
a
red
hat
linux
7.2
and
I
went
to
the
to
the
manager
of
the
team
that
I
was
supplementing
and
I
was
like
hey.
I
just
found
this
thing
and
he's
like
really:
click
click.
Click,
click,
click,
it's
not
in
the
inventory
anymore
find
it.
Now.
B
So
again,
I've
actually
got
my
enable
sysadmin
tumbler
right
here
that
no
one
can
read,
because
it's
too
small,
but
I
wanted
to
to
ask
you
so
there's
a
lot
of
great
linux
content.
I
know
that
talking
with
jason
hibbitz
who's,
another
editor
over
there
that
you
guys
try
to
keep
it
less
red
hat
and
more
linux.
So
there's
stuff.
That
applies
to
a
bunch
of
different
linuxes,
not
just
red
hat
histories.
C
Well,
our
official
start
date
was
june,
1st
of
2019,
which
has
been
just
maybe
a
year,
and
a
half
ish
where
I
would
like
to
see
it
go,
is
for
it
to
be
kind
of
a
technology
watering
hole
for
system,
administrators,
linux
system,
administrators
and
those
who
are
transitioning
to
linux,
and
I
hope
to
have
a
lot
more
introductory
content
and
a
lot
more
content.
That
draws
those
new
people
in,
like
I
say,
from
windows
or
mac,
or
you
know,
maybe
from
a
non-technology
role.
C
C
B
C
Well,
I
really
like
beginner
type
content.
You
know
introductory
material
intro
to
ansible
intro
to
the
linux
file
systems
intro
to
linux.
Networking
you
know
anything,
that's
new
for
someone
coming
into
the
field,
either
as
a
junior
sysadmin
or
from
windows
or
mac
or
whatever
introductory
content,
is
always
welcome,
but
the
thing
that
really
does
very
well
on
our
site.
Besides
the
how
to
type
stuff
believe
it
or
not,
is
career
articles.
C
We
have
a
few
career
articles
that
have
done
very,
very
well
like
not
not
from
the
standpoint
of
you
know:
there's
10
000
jobs
available
in
system
administration,
but
from
the
viewpoint
of
this
is
my
story.
This
is
how
I
got
in
to
linux
system
administration,
I've
written
mine,
tyler,
kerrigan
who's,
another
one
of
the
editors
and
community
managers
has
written
his
and
we've
had
some
of
the
community
members
as
well
write
those
and
they
always
do
very
well
because
you
know,
even
though.
D
B
C
C
You
had
all
these
weird
serial
interfaces
and
things-
and
you
know
over
time,
chemistry
became
less
and
less
palatable
and
computers
became
more
and
more
palatable.
So
I
basically
just
transitioned
about
the
time.
Oh,
that
novell
was
big.
I
got
certified
in
novell
and
you
know
which
was
actually
unix-based
and
then
you
know
we
transitioned
to
banyan
networks,
which
was
unix-based,
and
you
know
I
guess
kind
of
the
rest
is
history.
A
I
was
working
in
a
warehouse
and
one
of
the
big
projects
that
summer
this
is
the
summer
I
went
from
turning
14
to
15
was
barcoding
everything
right
like
every
rack
in
the
warehouse,
every
position
everything
had
to
have
a
barcode
and
they
would
all
correspond
and
that
whole
system
would
make
all
of
our
you
know.
Packing
and
shipping
operations
faster,
made
total
sense
right.
D
A
A
B
B
So
can
I
getting
back
to
enable
seven
content?
Sorry,
I
took
us
down
down
a
sidebar
a
little
bit
memory
lane.
So
one
of
the
things
that
I
like
about
a
naples
admin
is
that
you
guys
have
attracted
some
really
interesting
authors
like
dan
walsh,
who
is
notably
of
s.
Excuse
me
essie,
linux
fame,
but
now
he
does
a
lot
of
content
on
containers.
B
C
Well,
we're
looking
for
people
with
you
know
a
good
deal
of
experience
as
a
sis
admin,
although
I
say
a
lot
of
experience,
we
accept
articles
from
people
at
all
levels.
Of
course
you
know
glad
to
have
anybody
from
you
know
the
rankest
beginner
to
the
saltiest
old
guy.
With
the
you
know,
the
keyboard
on
his
lap,
but
the
kind
of
content
we're
seeking
is
like
I
said
before.
You
know
we're
really
looking
for
how
to's
you
know,
one
simple
concept
per
article.
C
You
know,
for
example,
to
do
something
with
ansible.
You
know,
deliver
a
config
file
with
ansible,
that's
a
good
one.
I
love
ansible
myself.
It's
it's
a
great
opportunity
to
automate
some
of
your
environment,
especially
if
you
have
a
lot
of
servers
like
I
always
have
had
you
know
when
you
have
400
servers
in
a
single
data
center.
C
C
I
haven't
done
any
instagramming,
yet
I
still
am
a
little
gun
shy
of
that
one.
But
you
know
we
we
keep
the
word
out
pretty
well.
We
also
contact
internal
people
in
red
hat
and
you
don't
have
to
work
for
red
hat,
to
write
for
naval
sysadmin.
We
encourage
anyone
who
wants
to
write
for
us
to
do
so,
and
you
know
we
help
people
along.
We
have
copy
editors,
we
have
two
copy
editors.
We
have
four
of
us
internal
editors,
so
you
know
the
the
content
will
get
looked
at
for
sure.
C
C
B
C
You
could
go
on
to
our
site,
redhat.com
sysadmin,
slash,
join
dash
community
and
fill
out
the
form,
and
it's
only
used
for
internal
purposes.
Only
we
don't
sell
it
or
give
it
to
anybody
else,
even
in
the
rest
of
the
organization.
We
only
use
it
for
us-
and
I
fill
in
that
form,
which
has
some
details
about
yourself
and
that's
one
way
of
getting
in
the
other
way
is
just
send
us
an
email
to
enable
dash.
Sysadmin
redhat.com
tell
us
about
yourself
what
you
want
to
write
about.
C
You
know,
take
one
of
those
titles
or
ideas
and
make
up
your
own
or
if
you
work
with
something
you
can
write
an
article
about
it
or
at
least
pitch
the
article
to
us
and
we'll
see
if
it
works.
But
we're
really,
I
think,
as
you
said
at
the
very
beginning,
we're
red
hat
oriented,
but
we're
really
kind
of
generic
linux
as
well.
C
B
D
C
It's
probably
not
something
I
want
you
to
do,
and
I've
seen
people
do
it
in
enterprises
and
it's
you
know
you
can
secure
it,
but
it's
a
major
security
hole
and
I'd
rather
see
people
not
do
that
and
it's
okay
on,
of
course,
desktop
systems
or
virtual
machines.
You
know
that
you
protect,
but
that's
one
thing
I
don't
like
when
people
do.
The
other
thing
I
don't
like
to
see
people
do
is
when
something
goes
wrong
with
the
system.
C
Instead
of
fixing
it
they
just
blow
it
away,
and
that's
that's
really
something
that's
occurred
with
high
frequency
on
virtual
machines
and
containers.
They
think
oh
well,
this
is
it's
expendable.
It's
like
wait,
a
minute.
That's
a
production
system.
You
can't
just
blow
it
away.
You
know
you
can't
just
re-image
this
system
at
will.
C
C
B
Well,
I
know
that
a
lot
of
the
deployment
methodologies
we're
using
now
have
skewed
towards
the
cattle
mentality.
Like
you
know,
when
you
see
a
field
full
of
cows,
it's
like
they
don't
have
names
right.
They
have
little
like
ear
tags
with
a
number
or
something
and
when
one
of
them
gets
sick,
you
you
don't,
you
know,
go
over
and
soothe
it
and
you
know
talk
about
poor
messy.
Well,
you.
C
Know
that's
an
interesting
point
because,
a
long
time
ago
we
used
to
name
our
servers
like
cartoon
names
and
and
fun
names.
You
know
like
snuffy
and
sparky,
and
you
know
whatever
you
know
and
we
would
have
themes
run
through
an
entire
data
center,
where
we
would
have
all
like
calvin
and
hobbes
names,
or
you
know,
whatever
cartoon
characters,
I
think
there
was
a
wren
and
stimpy
at
one
time.
You
know,
but
then,
when
I
don't
know
when
bigger
corporate
stuff
came
down,
they
made
us
change.
The
names
to
it
was
like
location
function.
C
Number
like
told
db001
meant
that
it
was
a
in
the
tulsa
data
center.
It
was
a
database
server
and
it
was
the
first
one.
It's
like
no
man,
I
don't.
I
don't
know
the
personality
of
that
server.
You
know
it
needs
to
be
a
pet.
I
need
to
know
that
snuffy
has
an
issue
with
its
hba
card.
I
don't
you
know
if
you
say
so
ken
how
about
that
tall
db001.
C
I
don't
know
what
that
is,
but
if
you
said
snuffy
or
sparky
or
wren
or
stimpy,
I
would
know
exactly
what
system
you're
talking
about.
I
could
tell
you
where
it
is
in
the
rack,
but
tall
db001,
no
clue
so
yeah.
I
get
that
mentality
and
I
I
like
pets
versus
cattle.
In
fact,
what
a
great
article
that
would
be
chris
short.
A
It's
it's
already
been
written
right
like
there's,
there's,
there's
so
many
articles
about
how
we
should
treat
infrastructure
more
ephemerally
and
declaratively
right
so
that
we
can
just
state.
This
is
what
I
want
and
if
something
falls
out
of
state
put
it
back
for
whatever
reason,
stability,
security,
so
for
so
on
right,
like
the
whole
idea
of
open
shift.
Is
that
like?
If
I
say
this
deployment
has
17
pods,
it's
always
going
to
have
17
pods.
A
B
Let
me
spin
one
up
for
an
hour
and
then
I'll
kill
it
off
like
the
magnitude
that
we
operate
at
and
the
scale
at
which
we
operate
at
is
different
and
there
there
are
still
a
lot
of
instances
out
there.
Where
you
know
you
have
this
lovingly
crafted
artisanal
system
that
you've
created
for
a
bespoke
purpose
right,
but
how
many
of
those
can
one
person
make.
A
A
It
did
not
work
with
the
scale
that
they
were
trying
to
go
right.
So
lots
of
vulnerabilities
lots
of
you
know:
mistakes,
misconfigurations
and
consistencies
right,
like
great
you've,
got
a
naming
scheme,
but,
like
none
of
these
systems
are
the
same.
So
that's
where
things
like
ansible
come
along
and
kind
of
save
you
and
keep
things
consistent,
and
you
know
you
continuously
run
those
ansible
playbooks
against
your
systems
so
that
they
are
the
right
version
consistently
configured
and
you
know
so
forth
so
on.
You
can't
just
run
it
once
it's
supposed
to
be
that
impotent.
A
B
Yeah-
and
I
I
think
that
I
probably
operate
at
that
that
scale
now,
where
I
don't
care
as
much
about
boxes
and
where
honestly
fixing
them
takes
longer
than
it
does
to
blow
it
away
and
make
a
new
one,
but
at
the
same
time
like
there's
a
lot
of
customers.
I
know
sorry,
ken
there's
a
lot
of
customers
like
if
you
look
at
maybe
somebody
who
has
a
an
embedded
linux
running
their
mri
machine
right.
C
A
Yes,
it
was
a
linux
box,
but
it
was
like
a
controller
arm
to
move
the
silicon
chip
from
this
piece
of
equipment
to
this
piece
of
equipment,
but
it
still
needed
patches
right,
like
it
was
running,
rel
or
whatever.
Right
like
it
still
needed
to
be
patched
still
needed
to
be
maintained,
but
it
was
not
on
the
network.
A
C
B
A
So
yeah
there's
a
lot
of,
and
you
know
we
see
a
lot
of
that
in
in
government
where
there's
right,
like
no
internet
connectivity,
kind
of
thing
or
no
even
like
you
know,
network
connectivity
to
other
networks.
There's
like
silos
of
networking
and
like
the
idea
of
treating
those
whole
networks
as
ephemeral
is
impossible
right,
like
there's
always
going
to
be
those
bespoke
systems
on
those
networks
that
need
those
kinds
of
hands
on.
A
B
B
A
Yeah,
I've
always
been
a
fan
of
if
the
rpm
doesn't
exist.
For
me,
I
need
to
build
it
and
serve
it
myself.
Right,
like
I
had
to
do
that
with
aj
proxy
at
one
point
where
I
think
rel
pulled
it
and
put
it
in
a
different
repo
at
some
point
because
of
some
licensing
issue
and
like
it's
like
okay,
I
can
rpm
build
this.
There's
the
spec
file
and
you
know
the
source
code
done.
A
So
you
need
to
make
sure
you
know
what
kind
of
code
you're
running
on
your
systems,
which
goes
back
to
ken's
point
right,
like
don't
put
you
know,
gui's,
on
servers
right
like
it's
just
another
layer
that
you
have
to
secure
right,
like
keep
things
simple,
that's
always
kind
of
my
mantra
is
keep
things
as
simple
as
possible,
and
you
know
ansible
kind
of
helps
with
that.
You
know.
Operators
in
the
kubernetes
world
helps
with
that.
There's
a
lot
of
tooling
out
there
that
helps.
You
maintain
simplicity,
while
achieving
complexity.
C
Oh
gosh,
I
guess
there's
two
early
on
things.
The
first
one
was,
I'm
sure
you
remember
when
you
got
a
new
linux
installation.
The
first
thing
you
had
to
do
was
recompile
the
kernel,
and
that
was
that
was
pretty
tough
because
it
took
hours
to
go
through
that
question
there.
You
know
the
xf
config
or
whatever
it
was,
and
I
mean
it
just
took
a
long
time
to
get
it
right
to
get
all
your
peripherals
operational
and
the
other
thing
that
was
really
hard
was
getting
a
gui
to
work.
C
You
know,
because
you
had
to
go
to
the
xf,
86
config
and
answer
the
questions
and
change
your
refresh
rate
and
you
could
damage
your
monitor
or
your
video
card.
If
you
use
the
wrong
one,
that
was
kind
of
a
pain.
So
I
guess
those
two.
You
know
linux
has
never
been
particularly
hard
to
install
or
to
use,
but
getting
certain
things
to
work
they
used
to
be
hard.
I
mean
I
haven't
compiled
a
colonel
in
more
than
15
years,
probably
so,.
C
C
And
I
haven't
worried
about
graphical
interfaces
because
now,
if
you
want
a
graphical
interface,
you
do
it
on
install
or
you
can
just
download
the
you
know
you
do
group
install.
You
know
you
get
a
desktop
environment,
but
man
it
used
to
be
really
tough.
So
those
were
the
those
were
the
practical,
tough
things.
I
think
one
of
the
more
obscure
problems
I
had
with
linux
early
on
was
not
getting
involved
in
the
os
wars.
C
You
know,
because
all
the
nerds
of
course,
especially
when
I
started
the
linux
users
group
here
locally,
you
know
like
well.
Linux
is
way
more
stable
than
windows.
You
know
and
they
use
that
voice
too,
and
you
know
it
was
all
over
by
because
I
always
had
to
work
in
both
worlds.
I've
always
had
to
work
with
windows,
and
you
know
commercial,
unices
and
linux,
and
even
a
funny
story
about
things
being
difficult.
C
When
I
was
at
worldcom-
and
this
was
in
96-
I
believe
I
installed
a
linux
system
on
the
network
for
the
the
help
desk
and
the
desktop
support
guys
to
use-
and
I
was
told
by
one
of
the
gurus
of
the
group-
called
pc
support
and
came
over
one
day
and
goes:
do
you
have
a
linux
system
over
here?
I
go
yeah
and
he
goes.
You
need
to
take
that
linux
system
off
the
network.
Linux
is
not
an
approved
operating
system.
C
B
Yeah,
well,
I
think
one
of
the
more
challenging
things
to
learn
is
is
troubleshooting
mostly
because
I
a
co-worker
at
a
previous
position,
described
it
to
me
best.
He
said
in
order
to
troubleshoot
a
thing
you
need
to
know
every
layer
of
that
thing
and
how
they
interact
with
each
other
so
like,
if
you're
talking
about
troubleshooting
network
problem.
Well,
you
need
to
know
the
physical
layer,
at
least
to
some
extent
you
know
the
ip
layer.
You
need
the
protocol
layer.
B
A
Think
about
the
you
know:
application
layer,
all
the
different
languages
that
are
out
there
now
and
everything
in
between
right,
like
there's
so
much
to
the
osi
model
that
having
to
like
learning
it
is,
has
helped
me
troubleshoot
things
so
much
more
than
I
think
a
lot
of
my
peers,
because
they
didn't
understand
that
some
of
those
layers
actually
existed
and
they
had
to
go.
They
were
in
charge
of
touching
them.
Yeah
like
you
actually
have
to
go,
configure
the
right
dns
to
use
internal
dns.
A
B
A
B
A
A
A
B
B
B
Accepted
so
ken
you
were
talking
earlier
about
ansible,
I
don't
know
if
you've
seen
the
hey
that
works,
pretty
good.
If
you
see
the
lab.redhat.com
site
recently,
but
down
here
somewhere
there,
it
is.
We
I've
been
working
with
my
peers
on
the
ansible
team
and
they've,
put
together
a
couple
of
ansible
labs
for
kind
of
basic,
getting
started
with
ansible,
my
first
playbook
type
stuff.
A
It's
pretty
easy
yeah.
I
just
dropped
it
in
chat
for
everybody,
so
yeah,
but
there's
tons
of
content
there,
and
then
there
is
even
there's
more
stuff
out
there
for
every
product.
Right,
like
I
feel
like
every
like
red
hat,
has
one
openshift
has
one
I
feel
like
ansible
has
stuff
there
on
their
website
as
well.
So
just
look
around
there's
plenty
of
content
out
there,
folks
to
learn
and.
D
B
B
A
B
A
A
So
it's
updating
based
off
in
this
view,
activity
right,
like
any
kind
of
usage
cpu-wise.
I
believe,
I
think,
is
the
default
view,
but
you
can
actually
change
that
into
anything
from
and
there's
there's
more
things
that
you
can
display
here
as
well.
So
there's
any
amount
of
customization
you
can
do
to
top.
That
will
allow
you
to
do
to
see
exactly
what
you
need
in
a
pretty
friendly
and
easy
to
use
interface,
yeah
and
again.
C
C
You
have
a
process
table
that
that
dynamically
updates.
You
can
change
it
from
this
default.
Cpu-Oriented.
Look
to
a
memory.
You
know,
there's
like
chris
was
saying
you
can
change
it,
a
dozen
different
ways,
but
it's
a
it's
a
real-time
look
at
what's
going
on
in
your
system.
If
you
feel
like
you,
have
a
a
problem,
it's
one
of
the
first
things
I
always
do
is
go
into
top
and
see
you
know.
What's
what's
burning
my
cpu?
What's
burning
my
memory,
do
I
have
a
performance
problem?
Do
I
have
something?
B
Yeah
and
that's
how
I
use
it
too:
it's
like
system
experiencing
problem
first
thing,
pull
up
top
and
kind
of
get
a
general
read
of
what's
going
on.
Chris
was
correct
that
it
sorts
based
off
of
percentage
of
cp
utilization
first
and
then
secondarily,
sorts
on
percentage
of
memory,
that's
being
consumed,
but
there's
a
whole
bunch
of
commands
that
you
can
call
here,
inside
of
top
to
re-shuffle
things,
to
sort
it
on
different
columns
or
add
columns
of
data.
B
I
think
it's
five
seconds
and
we'll
reorganize
based
off
that
topmost,
topmost,
cpu
utilization,
the
place
where
I've
used
it
the
most
recently
web
browsers,
because
every
tab
now
has
like
javascript
and
other
stuff
that
runs
in
it
and
so
it'll
show
up
in
the
command
side
as
web
content.
And
it's
like
and
you'll
see
that
it's
like
using
some
just
abhorrent
amount
of
memory
or
cpu
and
and
that's
probably
what's
causing
your
slowdown.
B
So
this
is
also
reported
in
the
uptime
command
and
what
it's
showing
you
is
the
1,
5
and
15
minute
cpu
run
queue
average
depths,
that's
been
logged,
like
not
logged,
like
I'm
logging
messages,
but
logged,
as
in
like
the
mathematical
function,
logarithm
to
kind
of
smooth
out
any
spikes
during
those
1,
5
and
15
minute
periods
and
people
will
often,
in
my
experience,
pull
that
out
and
be
like
what
it's
it's
30
cpu's,
so
busy
and
it's
like.
Well,
that's
probably
not
true.
B
It
may
be
like
there's
30
things
out
there
on
the
run
queue
and
that's
why
you're
getting
that
data
there.
But
generally
my
experience
is
if
your
load
average
is
increasing.
You
probably
have
an
I
o
problem
because,
as
things
are
waiting
for,
I
o
to
be
retrieved
they're
still
on
the
cpu
run
queue
because
they're
just
waiting
for
that.
I
o
to
come
back
and
it
periodically
gets
checked
and
that's
been
my
my
experience.
It's
not
always
the
case,
but
sometimes.
D
A
B
All
right
to
get
out
of
top
you
hit
q
to
quit.
I
think
control
c
probably
also
works
there,
but
it's
native
native
command,
because
there's
like
I
was
surprised
at
how
many
internal
to
top
commands
there
are
it's.
It's
a
stupid
amount
anyway.
So
that
gets
you
back
my
next
top
10
system
command.
I
use
a
lot.
I
bet
I
need
to
install
it.
B
B
B
Yeah,
it's
now
that
we're
all
working
from
home-
it's
even
more
better
because
you
know
you'll
get
like
your
video
conferences,
blinking
out
or
you're
having
you
know
stuff,
and
it
could
be
that
somebody
else
in
your
network
is
sucking
up
all
your
bandwidth
right.
You've
got
kids
at
home
and
they're
all
streaming
and
on
pads
and
whatever
else,
but
it
might
be
that
your
isp
is
doing
something
janky
and
so
mtr
here
helps
with
that
and
what
it's
doing
is
it's
sending
out
a
series
of
trace
routes
and
then
reporting
on
it?
B
So
we
can
see
here
that,
for
example,
nope
this
guy,
he
seems
to
be
losing
packets.
In
reality,
I
think
he's
refusing
the
expired
icmp
packets.
That
traceroute
sends
because
clearly,
I'm
getting
good
throughput
on
my
video
stream
and
whatnot,
and
so
there
are
some
that
will
kind
of
misnomer,
but
the
other
nice
thing
is
if
it's
actually
dropping
packets,
it'll
bold,
the
box,
that's
dropping
the
packet.
B
So
it's
easy
to
pick
out
of
your
output,
and
so
I
use
this
a
lot
at
another
work
or
another
portion
of
my
job,
where
I
do
some
network
administration
and
all
the
non-technical
users
will
come
up
and
be
like
hey.
The
wi-fi
is
down
it's
like
well,
no,
actually,
the
wi-fi
is
just
fine,
because
that's
the
part
I
control
we're
all
good,
but
it'll
be
like
the
the
isp
is
doing
maintenance
on
a
saturday
and
that
they're,
like
taking
boxes
down
and
jacking
up
routes
and
a
whole
bunch
of
other
stuff.
A
B
This
box
is
causing
a
problem
and
he'd
pull
it
up
and
be
like
oh
yeah,
you're
right,
we
hadn't
even
been
alerted
to
that.
Let
me
go
handle
that
right
now
for
you,
it's
like,
I
was
the
canary
in
the
coal
mine
for
for
the
network
infrastructure,
but
anyway,
so
mtr
is
like
one
of
my
favorites
trace
routes
like
okay,
but
mtr
like
cranks
it
up
to
the
next
level,
one
of
the
others
that
I
think
is
really
handy.
That
has
fallen
out
of
vogue.
B
B
B
This
so
as
we're
building
packages,
the
maintainer
of
the
package,
at
least
at
red
hat,
puts
in
a
change
log.
That
tells
you
what
has
changed
between
the
different
versions
and
so
more
specifically
here.
These
are
bugzilla
bug
id
numbers
that
go
along
with
the
thing.
That's
been
changed
in
this
version.
They
also
log
cves
here.
So,
if
you
are
ever
asked
by
a
by
an
auditor,
has
the
cve
been
fixed?
D
B
Somebody
was
asking
me
about
this
release
value
because
in
rel,
the
release
value
on
packages,
kind
of
varies
from
subsystem,
t
to
subsystem
team
so
like
here
they're
using
dash
three
dot
el8
and
some
of
them
you'll
see
like
dash
three
dot.
El
eight
underscore
two
right
or
on
the
kernel,
and
they
use
something
a
little
bit
different.
A
B
I
think
it's
fell
out
all
right,
so
this
one
has
been
unpatched
but,
as
we
apply
kernel
updates,
there
will
be
like
additional
dot
numbers
that
go
in
here
and
basically,
like
every
subsystem
team
chooses
the
version
extension
that
makes
sense
for
them
to
track
the
changes
that
they're
doing
to
it.
So
some
you'll
see
use
just
siri
serially
right
dash,
1-2-3,
all
the
way
up.
Some
will
use
the
you
know
additional
fields
like
the
kernel,
because
it's
a
very
complex
piece
of
software.
D
B
And
then
others,
just
like
you,
know,
kind
of
choose
other
things
that
they
use.
You
could
find
like
somebody
could
use
abc
as
their
extroversion
number
there,
but
that's
specified
by
the
person
building
the
rpm
and
it's
kind
of
their
version
that
keeps
track
of
it
anyway.
So
I
was
trying
to
convince
someone
that
they
should
not
pay
attention
to
extroversion
numbers
because
they
would
just
drive
themselves.
B
A
B
Yeah,
so
these
actually
get
set
automatically
when
you
log
in
through
your
bash
profiles
or
bash
rc.
Actually
bash
rc
is
not
bash
profiles
and
for
root.
You
can
see
that
we
do
some
things
like
when
I
call
copy
as
root
it
really
calls
copy
minus.
I,
because
if
I
my
copy's,
going
to
overwrite
something
it'll,
ask
me
first
or
same
thing
to
remove.
A
A
So
like,
oh
yeah,
I
just
downloaded
something
it'll
be
right
there
at
the
end
of
the
line,
so
like
lla
does
the
dash
la,
but
if
I
just
do
ls
alert
this
is
my
alias
all
one
word,
so
I
just
shortened
it
to
lart
the
other
day
and
it's
because
that's
not
actually
a
valid
command
anywhere.
I
don't
think
so.
The
the
the
larp
command
that
you
see
me
run
sometimes
on
my
mac,
because
that's
my
main
driver
right
like
that
doesn't
exist.
A
It
doesn't
exist
on
other
boxes
that
I
log
into
throughout
the
day.
So
yeah
I've
come
to
just
start
typing
it
back
in
again
and
and
kind
of
walked
away
from
the
alias
a
little
bit
just
because
I'm
too
lazy
to
maintain
the
aliases
across
multiple
boxes.
Even
though
I
have
like
ansible
right
here
at
my
disposal.
B
Yeah,
I
used
to
use
it
a
lot,
for
we
would
move
the
port
of
ssh
to
other
things
besides
22
and
so
like
every
scp
command,
every
ssh
command.
You
had
to
specify
the
port
and,
of
course,
with
ssh,
it's
a
lowercase
p
and
with
scp
it's
an
uppercase
pe,
of
course,
which
is
like
more
irritating.
So
I
would
use
aliases
to
to
kind
of
just
stub
in
those.
B
A
B
B
B
B
B
A
D
A
B
A
B
B
A
B
B
So
I'm
just
going
to
do
my
cell,
because
that's
that
won't
cause
any
problems,
but
essentially
what
it's
doing
is
it's
scanning
that
target
host
or
ip
address
and
connecting
to
the
first
65
535
ports
on
it
to
see?
If
there's
something
running,
so
we
can
see
that
this
one
has
the
cockpit
port,
open
and
ssh
port
open
the
reason
that
places
will
not
allow
you
to
run.
It
will
be
very
angry
if
you
run
it
is,
if
you
run
it
across
the
network.
A
B
There's
also
a
oh
I've
not
done
it
in
forever.
I'd
have
to
look
at
the
syntax,
but
you
can
basically
like
write
a
tcp
connection,
basically
make
an
individual
tcp
connection
to
a
port
and
then
tell
it
to
time
out
after
a
little
bit
if
it's
not
able
to
make
the
connection.
So,
if
you're
looking
for
a
specific
port,
that's
probably
the
better
route
to
go.
Yes
because
then
you're
sending
a
single
connection.
B
C
Oh
yeah,
okay,
so
we've
got
really
two
levels
so
far
and
we're
going
to
add
more.
But
really
we
have
two
levels
right
now
of
authors,
I
guess
accolades
or
whatever
you
want
to
call
them.
The
first
one
is
called
run
level
three
club
and
what
that
is
is
when
you
publish
three
articles,
you
become
a
member
of
the
run
level
three
club
and
that
has
certain
perks
and
things
that
go
with
it.
But
the
seduers
level
and
you'll
see
that
on
articles
you'll
see
next
to
an
author's
name,
they'll
say
sedur.
C
C
You
get
to
get
involved
with
our
conference
calls.
There's
a
seducer
conference
call
where
we
discuss
directions
for
the
site.
We
discuss
calls
for
papers,
we
discuss
all
kinds
of
topics
and
we
let
you
guys,
talk
and
discuss
whatever
you
want
to
talk
about.
So
those
are
the
two
levels
right
now,
but
I
just
wanted
to
clear
that
up,
because
we
were
talking
about
the
seducers.
B
A
A
C
It's
incredible,
I
mean
a
lot
of
people.
Are
you
know
reluctant
to
write
or
whatever,
but
honestly
it's
one
of
the
best
things
you
can
do
for
your
career,
because
every
time
you
see
a
job
description,
it'll
say
must
be
an
effective
communicator,
written
and
verbal.
Well,
you
can
prove
it
if
you
point
to
articles
that
you've
written.
A
C
A
B
A
A
And
thank
you
everyone
out
there
that
tuned
in
to
watch.
I
I
I
think
my
g
chat
was
a
little
noisy
earlier.
Maybe
I'm
not
sure
who
that
was,
but
it
was
either
me
or
scott.
I
blame
myself
because
I'm
the
producer
and
that's
what
I
do
it
could
have
been
back
on
the
streaming
box
too.
I
don't
think
so,
though,
but
yeah
unless
unless
well,
google
has
done
weird
stuff
and
chrome
is
open,
so
I
don't
think
I
have
gmail
but
anyways.
Thank
you
all
for
tuning
in.
A
We
will
catch
you
all
tomorrow.
We
have
a.
I
have
a
lot
of
meetings
in
the
morning.
Oh
that's
not
fun,
but
at
11
we
have
the
in
the
clouds
with
red
hat
leadership.
Satish
will
be
joining
us
from
our
managed
services.
So
with
ibm's
recent
managed
services
move
and
our
kind
of
you
know
managed
services
thing
we'll
see,
we'll
have
a
little
discussion
about
all
that
yeah,
so
it'll
be
fun,
so
please
tune
in
first
showing
is
11
a.m.