►
Description
A show that features the people and technology that make Red Hat® Enterprise Linux® into the world’s leading enterprise Linux platform.
A
A
B
B
B
A
A
A
A
A
All
right,
so,
let's
see
I
mean
I'll
just
do
home
home-
is
where
all
your
users
live.
Essentially
right
like
they
will
work
inside
home,
their
home
directory
is
theirs
like
unless
you're
root
on
a
system,
one
user
can't
look
at
another
user's
directory
by
default,
at
least
so
it's
kind
of
like
your
private
playground
to
do
whatever
you
need
to
do
in
you'll,
see,
interestingly
enough
root
does
not
live
under
home.
It
lives
under
root.
We'll
talk
about
that
later,
but
you
know
your.
A
B
A
A
A
B
B
Yes,
but
they're,
both
first
shared
libraries
and
the
difference
between
them
is
that
you
know
once
upon
a
time
we
were
compiled
with
32-bit,
binaries
and
libraries
and
then
at
some
point
we
started
supporting
64-bit
stuff,
so
lib64
was
created
to
hold
those
and
now
we've
kind
of
coalesced
them
back
together
again.
But
I'll
talk
about
that
coalescing
in
a
bit,
so
lib
and
lib64
are
for
shared
libraries.
B
A
But
anyways
mount
is
the
you
know,
defecto
point
for
mounting
file
systems
of
another
variety
right.
So
you
know,
if
you
have
your
iscsi
network,
this
would
get
mounted
here
as
a
subdirectory
underneath
mount.
You
know
your
nfs
shares
would
get
mounted
for
system
use
in
the
mount
directory
and
notice.
B
B
A
A
B
So
I
I
mentioned
that
there
was
a
newer
place
that
noam
was
using
for
file
system,
removable,
media
stuff
and
that's
under
run.
These
are
four
mount
points
that
people
need
during
the
run
time
of
an
application.
So
when
you
plug
a
usb
thumbstick
into
gnome,
that's
running
it's
running
application.
It's
like!
Oh!
I
need
to
make
a
mount
point
to
mount
this
usb.
Stick
that
just
got
plugged
in
for
my
user,
so
I
can
run
the
files
application,
so
it
creates
this
subdirectory
to
run
and
then
attaches
that
device
at
that
location.
A
A
That
was
because,
on
spinning
media
spinning
rust,
as
I
like
to
call
it
nowadays,
it
would
be
faster
access
times.
So
now,
with
ssds
nvme
drives
like
the
access
time
is
consistent
across
the
entire
storage
device.
So
it
doesn't
really
matter
as
much,
but
boot
is
where
the
inet
system
lives
well,
not
all
of
it,
but
some
of
it
and
like
how
linux
starts
on
your
system
that
lives
here.
The
kernel
like
lives
here
and
everything
gets
loaded
at
startup
from
boot.
B
B
A
A
B
But
what
has
happened
over
time
is
it's
become
the
place
where
we
put
configuration
files
because,
like
you,
put
your
binaries
in
the
bin
directory
and
you
put
other
files
in
other
directories
and
then
I
was
like
well,
I
need
this
config
file.
Where
does
that
go
yeah
I'll,
put
it
in
the
center
directory
and
over
time
that
just
became
the
place
where
all
the
configuration
files
went.
A
A
Is
you
get
like
like
opt-ben
and
doc
and
stuff
are
usually
in
there,
but
then
you
get
opt
package
bin
and
people
get
confused.
Sometimes
right,
like
let's
say
my
package,
is
you
know
a
go
binary
and
that's
not
where
the
go
binary
goes
right,
like
opt
is
for
specifically
stuff
you're
deploying
right,
like
it's,
not
necessarily
the
de
facto
place
where
stuff
gets
installed,
which
is
kind
of
confusing
to
people.
But
if
you
look
at
the
page
for
op,
there's
some
very
specific,
oh
there's
a
question
in
here.
A
B
So
there
are
still
some
packages
that
will
do
that.
Like
a
lot
of
the
add-on
software,
you
get
from
ibm
or
oracle,
for
example,
with
their
database
suite
yeah
they'll,
put
it
down
under
opt-in,
so
there'll
be
a
directory
in
opt.
That
says,
like
you
know,
name
of
software
and
then
underneath
of
that
will
be
bin
lib.
You
know
yadda
yadda
for
the
software
that
goes
along
with
that.
A
B
But
a
lot
of
stuff
like
if
you
install
software
off
of
the
extra
packages
for
enterprise
linux
repository,
for
example,
it's
not
going
to
put
it
knobbed,
no,
it's
going
to
put
it
in
bin
or
lib
or
you
know,
wherever
else
it.
It
goes
into
the
file
system,
directory
structure
and
that's
kind
of
just
the
way
it
is
yeah.
So
and
there's
not
a
one
good
approach
like
you
know,.
B
B
A
B
I'm
taking
root,
so
this
is
the
root
user
accounts
home
directory.
We
don't
put
it
in
slash
home
because,
as
chris
pointed
out
earlier,
it's
flagged
as
optional
also
a
lot
of
times.
It's
set
up
as
a
separate
file
system,
so
it
goes
to
like
different
storage
yeah
and
if
your
system
was
having
problems
and
for
whatever
reason
that
storage
wasn't
available
when
you
log
in
as
root,
you
still
need
to
maybe
have
access
to
your
own
stuff.
B
So
slash
root
goes
as
part
of
the
slash
file
system
and
goes
on
the
storage
of
the
slash
file
system.
Other
unix's
will
actually
not
put
this
out
there.
So
when
you
log
in
as
root
on
solaris,
for
example,
you
get
dropped
into
slash
as
your
home
directory,
which
means
when
you
download
a
file
or
your
desktop,
wants
to
create
things
like
downloads
and
pictures
or
whatever
it
puts
to
the
topmost
directory,
because
that's
your
home
directory
for
root,
so
things
got
kind
of
cluttered
at
that
top
level.
A
And-
and
this
is
an
interest
like
as
we're
going
through
these
I'm
pulling
up
the
docs-
this
is
an
interesting
footnote
on
root.
We
recommend
against
the
root
account
you
we
recommend
against
using
the
root
account
for
tasks
that
can
be
performed
as
an
unprivileged
user,
what
a
great
idea
and
that
it
be
used
solely
for
system
administration.
A
What
does
this
mean
to
me?
I
read
this
as
root.
Is
cli
only
don't
install
a
gui
as
root
right
and
have
mail
and
all
kinds
of
other
stuff
living
under
this
directory,
because
it
is
going
to
be
a
necessary
thing
for
when
stuff
goes
bump
in
the
night?
You
want
that
to
be
there
right
and
only
really
important
things
should
just
live
in
root
for
system
administration.
I
mean
but
fair.
B
It
but
there's
a
lot
of
like
workstations
that
people
own
and
I
could
see
them
maybe
using
root
on
that,
but
again
for
system
administration
stuff.
I
think
you
typically
will
operate
on
those
boxes
as
a
regular
user
for
a
whole
host
of
reasons,
not
just
security
and
file
ownership
and
a
variety
of
other
things.
A
No,
we
have
a
comment,
slash
question
from
rapscallion
reeves,
our
friend,
and
we
now
be.
We
might
not
be
able
to
answer
this
because
I
don't
know
the
answer.
Maybe
you
just
got,
why
are
bsd
and
linux's
file
trees
so
similar,
but
so
different?
I
don't
get
why
bsd
has
user
local
bin
and
user
local
etsy,
for
example,.
B
I
think
it
ties
to
the
history
of
how
we
got
here
right.
So
once
upon
a
time
there
were
two
large
unix
distributions,
berkeley
and
system
five
and
as
they
matured
and
they
wanted
to
woo
users
from
one
to
the
other
or
back
again
they
had
to
build
up
this
kind
of
cross-populated
directory
structure
horribleness
so
like.
B
If
you
were
a
a
berkeley
person
right,
because
you
started
on
solaris
when
it
was
solaris
four
dot,
something
something,
and
then
your
company
decided
that
you
were
going
to
be
an
hp,
ux
shop
which
was
system
five.
So
you
log
into
your
first
hp
x,
machine
you're
like
where
is
everything
so
hp,
ux
or
aix?
For
that
matter
too,
from
ibm,
they
started
to
create
these
kind
of
additional
directories
to
make
it
more
comfortable
for
people
coming
from
berkeley
and
then
sun
was
like.
B
And
so
when
you
look
at
the
commercial
unix's,
I
think
a
lot
of
them
end
up
cross-populating
between
the
berkeley
and
system.
Five
standards
and
then
linux
comes
along
and
it's
the
same
deal.
They
have
to
appeal
to
people
who
maybe
were
used
to
working
in
a
variety
of
unixes,
so
they
created
this
much
more
amalgam
of
directory
structures,
but
bsd
is
still
a
legitimate
unix
distribution
with
a
couple
of
different
flavors
and
they've
stayed
pretty
true
to
their
their
file
system
hierarchy,
standard
that
they
minted
back
in
the
day.
And
so
that's.
A
A
B
So
you
know
you
have
to
make
sure
that
that
stuff
is
rock
solid
like
somebody
was
just
recently
was
asking
me
about
file
system
driver
for
linux,
and
we
do
not
ship
that
as
part
of
route.
You
can
get
it
in
places
like.
I
think
people
may
have
it
yeah,
so
you
can
get
a
module
and
it'll
plug
into
your
kernel
and
stuff.
A
A
We
like
to
make
sure
your
data
is
as
stable
and
intact
as
possible
as
we're
going
about
making
your
operating
systems
so
yeah
I
mean
there's,
there's
a
lot
of
work
being
done
in
butter.
Fs
fedora
is
using
butter
fs,
I'm
using
that
screen
right
there,
I'm
using
butter
fs.
I
don't
have
anything
of
significance
that
I
cannot
replace
easily
on
that
box,
for
example,
though,
as
a
result.
B
Yeah
yeah,
so
I
know
that
our
product
manager
for
file
system
stuff
is
continued
to
keep
an
eye
on
rfs.
So
I
I
don't
remember
if
we
put
it
into
centos
stream,
nine
centos
stream.
Nine
was
had
their
first
build
just
like
a
week
ago,
and
that
should
be
a
pretty
good
representation
of
what
we
expect
to
land
in
in
rel
next
year.
B
B
A
A
It
definitely
was,
and
it
came
from
the
need
to
have
like
back
in
the
day
you
partition
the
hell
out
of
disks.
Nowadays,
you
might
not
so
much,
it
might
be
one
or
two
partitions
right,
so
you
would
want
s-bend
to
be
in
a
similarly
fast.
You
know:
file
system,
slash
space
on
disk
as
boot
was
right,
because
you're
gonna
need
fsck
at
boot.
Time.
Sometimes
right
so
like
there
was
that
for
a
little
bit
and
people
kind
of
went
away
from
that,
as
this
got
faster.
B
So
like
partitioning
disks,
yeah
exactly
and
like
way
way
back,
we
could
do
things
like
change
the
permissions
on
it,
so
that
people
couldn't
access
them,
but
we
also
for
regular
users.
Don't
include
the
s-pen
directories
on
their
path,
so
when
they're
looking
for
commands,
they
probably
won't
find
these
with
things
like
tab
completion
because
they're,
not
system
administrators,
they
don't
get
the
aspen
directory
and
then
over
time
we
we
figured
out
that
that
wasn't
a
great
plan,
because
people
would
still
add
it
to
their
path
and
find
it
anyway.
A
B
B
And
they
point
to
their
user
counterparts,
so
this
is
a
functionality
of
combining
the
linux
file
system
hierarchy,
standard
out
of
berkeley
and
system
five.
So
in
berkeley
they
put
all
of
the
bin
lib
s
bin
at
the
top
level
root
directory,
whereas
in
system
5's
directory
file
system
hierarchy
standard,
they
put
it
under
user
for
unix
system
resources
and
then
it
became
like
well
as
time
went
on
and
we
started
to
cross
populate
between
those
two
directory
structures.
B
B
We
just
went
ahead
and
merged
them
together
and
created
these
sim
links.
So
in
reality
everything
in
rel
goes
into
user
and
then,
if
your
package,
when
you're
you
know
installing
an
rpm
or
whatever
says,
slash
bin,
that's
fine.
It
just
follows
the
sim
link
and
puts
it
in
user
bin.
So
yeah
we
created
those
sim
links
to
still
maintain
that
compatibility.
A
And
I
missed
this
question
from
rapscallion
reeves.
One
thing
I
still
don't
understand
about
fedora,
34
and
butterfs,
since
compression
is
enabled
by
default.
If
you
check
the
encryption
box
during
f34
install
will
that
mess
you
up?
How
can
butter
fs
encrypt
compress
encrypted
data?
Let's
and
let's
not
conflate
compression
and
encryption
right,
they
are
vastly
different
things.
An
encryption
algorithm
masks.
A
B
A
B
B
A
B
A
B
Yeah
and
if
you're
interested
in
things
like
compression
and
saving
space,
you
may
also
be
interested
in
taking
a
look
at
vdo,
which
is
the
virtual
data.
Optimizer
that
comes
with
rel,
essentially
uses
data
deduplication,
yes
to
right
to
not
store
the
same
bits
on
disk
multiple
times,
but
all
right.
So
I
think
it's
my
turn.
Srv
is
one
that
we
don't
really
use
in
rel,
but
like
debian
distros
use
a
lot.
A
A
A
Okay,
temp
is
almost
exactly
what
you
think
it's
for.
It
is
for
temporary
files,
but
the
different
temp
has
a
relative
in
var
temp,
which
will
actually
purge
itself
on
boot.
So
if
you're
putting
files
in
temp,
they
will
last
through
a
reboot
where
var
temp
they
may
or
may
not,
depending
upon
the
os.
A
And
I
use
temp
for,
like
literally
the
output
of
scripts,
that
I'm
running
as
like
a
diagnostic
type
thing
or
if
I'm
running
an
ansible
playbook,
and
I
need
to
actually
write
a
file
to
disk
and
then
I
know
I'm
going
to
get
rid
of
it
later.
Temp
is
where
I
do
it
right,
so
anything
that
I
know
I'm
going
to
have
to
have
some
output
that
has
to
land
on
disk,
and
then
I
want
to
erase
it
later.
That's
what
temp
is
for.
B
B
B
A
Var
is
one
of
my
favorite
directories
because
there's
so
much
going
on
right,
like
you
know,
var,
logs
var
cash
var
crash
var,
lib
var,
lock,
like
everything
kind
of
like
running
on
the
system,
is
under,
like
the
outputs
of
that
is
all
under
var
right.
So,
if
you're
looking
for
logs
somewhere
go
look
in
var
logs,
if
you're
looking
for
lock
files
that
you're
trying
to
get
rid
of
go
looking
for
lock,
but
the
the
the
purpose
of
like
var
itself,
it
contains
variable
data
files.
That's
literally
why
it's
called
var.
A
This
includes,
like
spool
directories,
so
print
jobs,
emails
things
like
that
administrative
logging,
data,
transient
files,
temporary
files.
One
thing
to
point
out
is
that,
like
some
things,
living
in
var
aren't
shareable
right
across
systems.
So
just
keep
that
in
mind.
Right,
like
you,
don't
want
to
mount
var
log
to
the
same
thing
on
every
system,
unless
you
have
a
way
to
take
care
of
that
output.
A
B
B
A
A
A
B
A
A
A
A
A
A
A
B
So
it
depends
on
what
you're
trying
to
share
right.
If
you
were
trying
like
back
in
the
day,
we
would
do
things
like
nfs
share
our
user
directory,
because
we
would
install
matlab
on
a
server
and
we
want
other
client
boxes
to
be
able
to
mount
and
execute
it
locally,
and
so
we
we
share
user
as
an
nfs
share.
B
B
B
A
A
A
A
B
B
A
A
B
A
I
guess,
instead
of
christian
hernandez
so
andrew
says
I
probably
unfairly
shy
away
from
butter
fs
as
a
result
of
the
now
quite
old
data
corruption
bugs
I
stopped
paying
attention
to
it
back
then,
but
I
understand
there's
quite
a
few
commercial
products
using
it
now,
including
synology.
He
thinks
that's
interesting
to
learn.
If
that's
the
case,
if
your
synology
box
is
running
butter
fs,
let
me
know.
A
A
B
B
And
xfs,
like
it's
ridiculous,
amounts
that
I
would
challenge
someone
to
actually
achieve.
It's
like
millions
of
files
in
that
in
a
single
directory
level,
and
I
can
retrieve
it,
but
because
it's
better
at
looking
up
and
retrieving
those
tiny
large
amounts
of
files,
that's
kind
of
what
sweet
spot.
Oh.
B
B
So
you
want
to
make
sure
that
you
are
running
the
same
kernel
module
that
you
have
on
your
running
kernel,
and
so,
whenever
this
provisions
you'll
see
that
very
first
command
here
is
the
yum
install
and
it
has
a
video
version
and
I
actually
specify
the
version
in
the
command
and
the
kvdo
kmod
also
has
a
version
that
I
specify
because
it
all
has
to
match
the
currently
running
kernel
right.
So
if
I
do
a
umay
r.
A
A
A
I
thought
we
were
gonna,
call
it
a
day
yeah.
I
hope
this
was
educational
for
folks
right
like
if
you
have
any
questions,
feel
free
to
reach
out
to
me
short
at
redhat.com
or
chrisshort
on
twitter,
and
you
know
we're
very
happy
to
have
you
here
for
this
episode
and
we
look
forward
to
seeing
you
tomorrow
at
9.
00
a.m.
To
talk
about
same
show,
different
name,
the
data
services
office
hour.