►
Description
A show that features the people and technology that make Red Hat® Enterprise Linux® into the world’s leading enterprise Linux platform.
This episode we'll be talking with Bob Davis about RHEL Workstation
A
A
A
B
Go
good
morning,
good
afternoon,
good
evening,
welcome
to
another
episode
of
red
hat
enterprise.
Linux
presents,
I
am
chris
short
executive
producer
of
open
shift
tv.
I
am
joined
by
some
of
my
favorite
red
hatters,
scott
mcbryan
and
bob
davis.
Today
we
are
going
to
be
talking
about
rel
workstation,
which
I
think
is
awesome,
because
I've
used
it
before
and
it's
intended
capacity
and
have
had
great
success
with
it
in
a
previous
life.
So
scott,
how
you
doing
today,
buddy.
C
D
D
I've
been
with
red
hat
for
four
and
a
half
years,
or
so
working
in
various
capacities
and
product
management,
and
now
I
run
the
rel
workstation
offering.
D
So
I
think
a
lot
about
how
the
people
who
actually
sit
at
keyboards
and
in
front
of
monitors
or
with
their
cintiq
tablets
and
and
stylus,
is
how
everybody
uses
rowell
workstation
to
to
do
the
things
that
they
do.
C
D
Well,
rel,
is
you
know,
rel
is
lots
of
things
to
do
to
different
people.
Workstation
is
like
I
said:
it's
that's
something
that
people
actually
interact
with,
so
I
tend
to
look
at
workstation
as
that
confluence
point
between
human
creativity
and
high
performance
computing
power.
D
So
you
know
it
is
where
the
a
digital
artist
can
bring
their
character
to
life.
D
Using
you
know
all
the
the
wonderful
software
that
that
people
build
for
rel
to
make
3d
animations
or
it's
where
engineers
work,
to
make
the
cars
that
we
drive
safer
or
where
scientists
sit
and
analyze
data
that
comes
off
of
supercomputers
to
develop
medicines
or
understand
some.
You
know
fundamental
aspects
of
the
universe,
yeah,
it's
it's!
Where
the
you
know
some
magical
things
happen
in
front
of
these
screens,
so
it's
really
really
fun.
To
talk
to
my
customers
about
it.
B
I
bet
I
mean
some
of
the
to
give
you
some
examples
right
like
looking
at
large,
you
know
imagery
data
sets
is
some
of
my
use
cases
from
my
past.
Some
civil
engineering
use
cases
right
versus
dams,
that
kind
of
thing,
and
then
I
think
most
interesting.
D
It's
it.
People
are
doing
really
really
wonderful
things,
and
I
love
that
the
I
love
the
human
component
to
it,
because
so
much
of
the
time
you
think
about
rel.
As
you
know,
the
operating
system
that
makes
all
the
internet
work
and
it's
you
know
it's
it's
sitting
in
those
cold,
loud
rooms
that
have
you
know
so
a
whole
bunch
of
power
running
into
it.
But
nobody
ever
sees
it.
Nobody
ever
touches
it,
but
this
is
you
know
this
is
where.
D
Yeah
and
in
fact,
that
really
that
change
happened
so
there
used
to
be
what
we
refer
to
as
content
differences.
So
there
were
packages
that
were
included
in
server
that
are
not
included
in
rel
workstation
and
vice
versa.
You
don't
need
the
the
you
know,
a
massive
list
of
fonts,
for
example,
in
a
server
generally
speaking,
that
you
would
need
in
a
workstation
you
don't.
D
You
know
there
were
limitations
around
what
you
could
do
as
far
as
using
a
workstation
as
a
hypervisor
or
for
you
know,
doing
anything
with
containers,
but
but
with
the
with
the
launch
of
rail,
eight
we
shifted
over
to
a
flat
content
set
so
that
the
the
content
that
you
get
in
the
server
is
the
same
as
what
you
have
in
a
workstation
which
is
fantastic,
because
what
it
allows
say,
a
software
developer
to
do
is
build,
build
and
test
software
in
an
environment
that
they
know
is
going
to
mirror
what
the
production
run
or
what
the
production
environment
is
going
to
be.
D
D
You
know
it's
the
same,
for
you
know,
let's
say
you're
doing
a
you
know:
3d
visual
effects,
work
on
your
on
your
workstation
and
then
you
ship
it
off
to
the
render
farm
to
be
composited
with
all
the
lighting
and
the
environments
and
everything
else
that
has
to
happen
to
actually
make
a
frame
of
of
a
you
know,
a
movie
again
having
everything
be
the
same,
in
your
design
and
and
in
your
design
environment.
D
As
your
render
environment
isn't
is
important,
so
you
know
flattening
that
out
has
made
a
diff
a
a
good
difference
for
us.
It
makes
the
when
it
comes
to
like
what
what
version
should
I
buy.
You
can
actually
look
at
now.
D
What
am
I
using
it
for,
instead
of
what
packages
do
I
need
to
make
sure
are
there,
which
is
you
know,
just
a
more.
D
Customer
friendly,
I
guess
you
could
say
a
way
of
way
of
looking
at
things.
It's
like
are
people
touching
it
or
not.
B
So
scott
there's
a
question
in
chat
is
rel
for
devs
valid
for
one
year
or
is
it
just
valid
forever
kind
of
thing?
I'm
a
little
confused.
D
The
individual
so
fortunately.
B
D
I
was
the
rel
experience
product
management
person
in
in
the
developer
business
unit,
so
that
subscription
is
a
one-year
subscription
that
just
on
an
annual
basis
when
you
find
out
that
it's
expired
now,
nothing
stops
right
like
it's,
not
you're,
not
gonna,
try
to
like
boot
rel
one
day
and
it's
gonna
be
like
your
subscription
expired
goodbye
insert
coin
here
it
doesn't
that
doesn't
happen,
you
just
need
to
go
in
and
you
just
need
to
go
in
and
like
check
that
everything's
still
the
same
and
re-agree
to
the
terms
and
conditions
for
another
year.
D
The
snag
is
that
you
cannot
do
that.
Preemptively
and
usually
what
you
have
to
do
is
like
try
to
download
something.
So
if
you
download,
download
download
the
most
recent
version
of
rel
and-
and
it
will
ask
you
it'll-
ask
you
for
the
resubscription.
A
C
And
then,
if
you
log
on
to
the
red
hat
customer
portal,
which
is
access.redhat.com
in
the
subscriptions
field,
that
will
be
listed
and
you'll
have
the
date
on
which
it
needs
to
be
renewed
and
there'll,
be
warnings
there
too,
when
it's
about
to
expire.
So,
but
it's
bob
mentioned
like
well,
does
stuff
working.
What
ends
up
happening
is
your
machine's
access
to
the
content.
Development
network
won't
authenticate
until
you
react
your
subscription
and
that
the
machine's
still
registered,
and
then
it's
authorized
to
download
content
again.
C
Oh,
but
back
to
our
earlier
thing,
so
bob
one
of
the
things
I
found
most
irritating
when
I
was
a
systems
administrator
was
like
a
lot
of
times
the
packages
between
workstation
and
server
were
they
were
all
there
with
one
or
two
very
small
exceptions,
but
it's
like
in
the
raw
for
server
distro.
C
We
packaged
some
things
up
as
like:
optional
rpms,
which
were
libreoffice
and
and
those
more
desktop
e
apps,
whereas
in
the
workstation
those
were
part
of
the
standard
workstation
channel,
and
then
you
have
to
find
the
server
supplementary
channel
to
get
some
of
the
server
side
applications
because
of
course,
we
read
out
like
somebody
on
a
workstation
would
never
need
a
dhcp
server,
and
then
we
find
out
that
there's
that
one
guy
that
needs
a
dhcp
server
and
we
have
to
deal
with
it.
Oh.
D
D
D
We
were
doing
something
that
made
sense
to
us
from
where
we
sit,
but
it
added
complexity
for
enough
customers
that
you
know
our
our
effort
to
make
things
more
streamlined
actually
turned
out
to
be
injecting
pain
for
some.
For
us,
you
know,
even
if
it's
a
small
subset
of
customers
right,
it's
you
know
like
why?
Don't
we
just
make
it
the
same
everywhere?
D
So
from
a
from
a
sysadmin
perspective,
a
real
machine
is
a
real
machine
as
a
realm
machine,
and
you
don't
have
to
you
know,
have
some
these
crazy
run
books
to
figure
out
how
to
how
to
do
an
update
on
something.
D
C
D
Desktop
was
a
so
desktop
in
some
ways
was
redundant
and
when
we
were
looking
at
the
ways
it
was
being
used
most
frequently,
it
was
almost
more
like
a
an
edge
device
or
or
what
we
would
refer
to
now
as
a
distributed
computing
device.
So
this
would
be
like
a
like
a
point
of
sale
station.
You
know,
like
a
you,
know,
a
cash
register
or
some
kind
of
a
a
kiosk
kind
of
use
case,
but
it
was
not
optimized
necessarily
for
those
particular
things.
D
So
you
know
there
are.
There
are
problems
that
are
unique
to
edge
use
cases
that
we
weren't
necessarily
accommodating
in
the
product
development
of
for
for
desktop.
D
So
what
we've
done
is,
I
think
we
you
know
we
eliminated
desktop,
we're
now,
focusing
in
on
the
workstation
experience,
which
you
know
as
we've
described.
Isn't
it's
not
that
point
of
sale
thing
it's
that
scientific
animators
engineering.
D
D
That's
where
you
know
using
edge
types
of
installations
are,
are
going
to
work
better
for
our
customers.
Nice.
C
So
are
there
like
specific
things,
somebody
should
look
for
when
deciding
whether
they
should
use
workstation
or
server
or
some
other
type
of
role.
D
Well,
the
biggest
one
is
going
to
be
the
use
case,
so
you
know
think
about.
Where
is
it
going
to
run,
meaning
what
kind
of
hardware
is
going
to
run
on
what
kind
of
environment
is
it
going
to
be
in
and
what
kinds
of
things
are
an
end
user
going
to
be
doing
with
it?
So
you
know
typically
when
for
workstations
it
it
it's
going
to
imply
that
this
is
going
to
be
a
heavy
graphical
use.
D
It's
going
to
be
a
well,
it's
always
a
single
user
environment
right
just
by
by
definition,
it's
a
single
user
environment
where
you're
going
to
have
typically
a
very
like
a
beefy
kind
of
workstation,
which
is
you
know,
so
you
know
probably
two
processors,
very
expensive
type
of
professional-grade
graphics
cards,
very
high
power.
D
It's
going
to
have
multiple
screens
or
large
screens
the
input
devices.
Will
you
know
a
lot
of
the
ones
that
I'm
seeing
typically
include
like
the
the
large
professional
grade,
wacom
tablets
for
salt,
for
a
lot
of
use?
Cases
for
other
ones
say
you
know
using
it
for
a
you
know,
a
scientific
analysis,
type
of
use
case.
D
It
won't
have
that
but
gpu
heavy
workloads
designed
for
an
individual
to
sit
and
work
at
a
screen
with
a
you
know,
mouse
and
keyboard
versus
a
server
is,
you
know,
obviously
going
to
be
something
that's
nine
times
most
of
the
time
it's
going
to
be
running
headless,
so
it's
not
going
to
have
it's
not
going
to
have
any
gui
components,
necessarily
it'll
it'll
be
in
a
data
center.
D
We
also
do
have
use
cases
where
people
are
running
workstations
in
data
centers
with
individuals
remoting
in
using
some
type
of
you
know
a
vdi
kind
of
setup,
oh
yeah,
which
is
an
interesting
option
for
it's
an
interesting
option
for
customers
that
have
a
workstation
dedicated
to
particular
computational
types
of
analyses.
D
Where
you
know
the
the
data
and
the
the
data
that
they're
using
needs
to
be
kept
protected.
So
they
don't
want
it
necessary.
They
don't
want,
they
don't
want
it
outside
of
a
they,
don't
want
it
outside
of
the
data
center,
but
they
need
people
in
remote
areas
to
be
able
to
access
it
even
or
you
know,
from
remote
offices
or
or
now,
even
with
coronavirus.
D
A
B
Yeah
actually
like
not
rdp,
but
yeah
vncm
through
a
vpn
kind
of
deal,
and
I
use
it
like
a
vdi
kind
of
deal,
but
I'm
just
actually
sitting
at
home
and
it's
like
if
someone
walked
by,
they
would
see
stuff
going
on.
My.
D
Solutions
you
know
such
as
a
nice,
dcv
or
teradici,
that
that
are
being
used
in
conjunction
with
high-powered
workstations,
where
you
know
very
low
latency,
yes,
response
times
on
key
presses
or
or
stylus
input
is
required,
and
it's
funny
because
they,
you
know
they
refer
to
it
in
terms
of
like
frames
per
second.
So
when
you
hear
when
you
hear
them
talking
about
these
input
responses,
it's
like
oh
okay,
so
we're
talking
about
like
high-powered
gaming
tech
is
now
is
turning
into
high-powered
workstation
tech
right.
B
Yeah,
it's
like
the
same
stuff
you
would
use
for
bitcoin
mining.
You
would
find
in
a
workstation
these
days
right
like
not
that
I
would
recommend
drill
for
bitcoin
money.
No,
please
don't
save
the
environment.
Folks,
anyways.
D
So
yeah,
you
know,
you
know
like
which
one
to
choose
is
going
to
be
really
dependent
on.
You
know
is
this:
is
this
a
server
cluster?
That's
serving
up
an
application
for
remote
use.
You
know
that
could
be
or
is
it
you
know
we
have
hpc
high
performance.
Compute,
which
is
you
know,
depends
on
a
massively
parallel
computational
model
where
you've
got
thousands
or
tens
of
thousands
of
individual
nodes
working
simultaneously.
D
You
know
you
buy
server
for
for
the
application
that
it's
running
or
for
the
you
know,
for
the
final
application.
As
it's
being
run,
you
can
buy
workstations
or
use
the
developer
subscriptions
for
and
workstation
with
that
with.
You
know
for
your
software
developers
to
be
building
on
the
same
platform
that
you're
deploying
to
or
you
use
a
workstation
in
conjunction
with
your
hpc.
B
B
Got
three
of
the
top
five
yeah
like
it's
there's
like
and
the
most
recent
ones
are
using
rail,
which
is
cool
right
like
it's
not
like
some.
You
know
some
old
hpc
system.
Like
you
know
it's
national
laboratories,
which
we've
got
one
japan,
I
think,
has
one
yep
yeah
they're
all
over
the
planet,
but
yeah.
D
The
one
in
japan
is
unique
in
that
it
also
runs
on
arm.
B
A
C
So
bob
what
are
some
of
the?
What
are
some
of
the
developments
that
you're
working
on
to
pull
into
the
workstation
experience?
D
D
Obviously,
it's
a
it's
largely
iterative.
A
lot
of
the
things
that
we
that
we
work
on
are
driven
by
specific
customer
requests
that
come
about
as
the
nature
of
work
changes
or
the
things
are
the
problems
that
we
need
to
solve
change.
D
So
you
know
I
don't
have
any
major
breakthroughs
to
report,
but
you
know
things
like
support
for
hdr
monitors
as
an
example,
you
know
that's
the
kind
of
thing
that
we
would
be
working
on
as
they
become
more
and
more
important
for,
for
our
end,
users.
D
Continuing
to
align
the
the
packages
that
we
ship
as
part
of
workstation
with
different
standards
organizations
so
that
you
know
it's
like
we
have
different.
D
There
are
different
standards
organizations
that
drive
like
reference
platforms
that
whole
communities
of
software
development
companies
depend
on
so
making
sure
that
the
the
pla,
the
operating
system
platform
that
we
deliver
is
going
to
work
with
the
various
software
packages
that
people
depend
on
is
one
of
the
things
that
we
do
by
have
continuing
to
have
ongoing
conversations
with
those
with
those
reference
platform
organizations
and
a
lot,
as
well
as
with
the
different
software
vendors
and
different
hardware.
Vendors,
to
make
sure
that
everything
works
together.
D
So
you
don't
have
to
you
know,
have
six
different
systems
to
run
six
different
software
solutions,
because
they're
all
set
ups
just
slightly
differently.
D
So
you
know
a
lot
of
it
is
just
making
sure
that
the
end
result
is
simpler.
I
think
that
you
know
one
of
the
big
things
that
I
think
is
important
when
it
comes
to
simplicity
and
flexibility
is
actually
a
flat
pack
so
flat
pack,
if
you're
not
aware,
is
it's
similar
to
a
container
based,
it's
a
contain.
Basically,
it
is
a
container
that
our
flat
packs
are
our
oci
compliant
containers
that
you
ship
a
desktop
application
in
the
difference.
D
So
it
enables
a
great
deal
of
flexibility,
because
if
you,
if
you
look
at
a
lot
of
the
professional
grade
packages,
a
lot
of
the
support
forums
are
constantly
is,
if
you
do,
quick
searches.
You'll
find
a
lot
of
questions
about.
How
do
I
even
get
this
installed,
and
what
tweaks
do
I
need
to
make
here?
What
tweaks
do
I
need
to
make
there
if
it's
running
in
a
container,
you
get
the
application,
along
with
all
of
the
dependencies
and
all
the
configurations
that
need
to
be
there.
A
D
Mac
is
exciting
flat.
Pack,
I
think,
is
going
to
be
something
that
will
it
will
make
you
know,
as
we
commit
more
fully
to
flat
pack.
You
know
by
providing
flat
pack
options
for
various
applications
that
we
ship
along
with
rel,
and
then
you
know
trying
to
do
what
we
can
to
provide
assistance
to
software
vendors
who
want
to
also
ship
this
flat
pack.
D
D
It
makes
it
a
whole
lot
easier
for
them.
Is
you
know,
and
then
for
all
the
for
all
those
organizations
that
are
using?
You
know
in-house
built,
bespoke
applications
who
just
want
an
easy
way
of
distributing
internal.
You
know
distributing
the
app
internally
without
incurring
a
massive
support
load
just
to
get
the
things
installed.
D
You
know
it's
so
much
better,
it's
so
much
better
as
a
workstation
product
management,
you
have
to
kind
of
be
passionate
about
the
end
user
experience
exactly,
and
you
know
if
I
can
make
if
I
can
do
something
that
helps
an
artist,
an
engineer,
a
scientist
get
into
that
mental
flow
state
where
suddenly
they
realize
that
they're
starving,
because
it's
three
o'clock
in
the
afternoon
and
they
forgot
to
eat
lunch
because
they
were
in
the
zone
and
they
were
doing
the
best
work
that
they've
done
all
week
or
all
month
and
they
or
they,
cracked
that
huge
problem
and
they're
just
so
excited
that
they
lost
track
of
time.
D
B
Yeah
and
and
to
be
honest,
the
fedora
box
sitting
just
over
my
shoulder
there,
it's
filled
with
everything's,
pretty
much
installed
through
flat
pack.
At
this
point
right.
A
B
C
So
we're
where
we're
starting,
I
think,
to
enterprise
up
that
that
technology
right
so
flat,
pack's,
really
good
in
that
it
solves
some
problems,
like
somebody
upgraded
image,
magic
on
your
box
and
now
your
app
doesn't
work
anymore
because
it
required
the
image,
magic
library.
But
now
it's
been
updated
and
the
api
is
different,
and
so
you
could
take
with
your
flat
pack
those
key
libraries
and
include
them
in
your
flat
back
so
they're
stationary
right
and
the
operating
system.
C
C
A
D
So
like,
if
you
look
at
our,
if
you
look
at
the
red
hat
container
catalog,
you
see
that
they
have
freshness
grades,
all
the
containers
have
freshness
grades
and
you
can
look
and
see
what
you
know.
What's
you
know,
has
a
cve
been
addressed?
What's
the
latest
version?
When
was
the
last
time
it
was
touched?
D
These
are
all
like.
A
lot
of
this
stuff
happens
automatically
and
what's
really
cool
about
our
container
images.
Is
that
if
you
say
you
know
you
grab
say
a
node.js
base
image,
it
has
other
libraries
besides
just
node.js
in
it.
D
Well,
if
there's
a
cve
that
was
in
anything
anything
that's
in
that
container
image,
that
container
image
gets
updated
and
it's
not
just
looking
for
no
js
updates.
So
you
don't
wind
up
in
a
situation
where
you
know
your,
where
you
have
are
using
this
node.js
base
image,
but
only
node.js
gets
updated.
D
So
what
we
need
to
do
in
our
in
our
efforts
with
making
you
know
every
time
we
adopt
a
new
technology,
making
it
enterprise
grade
is
a
big
part
of
the
value
that
red
hat
adds.
D
D
I
want
to
make
sure
that
the
expectations
that
you
have
for
what
a
red
hat
product
means
are
met,
and
that
means
you
know
that
things
like
automatically
updating
the
the
flat
pack
containers
when
there's
when
there's
a
problem
in
any
component
in
the
you
know
in
the
container
itself,
cve
or
otherwise,.
D
You
know
that
those
things
always
get
updated
on
time,
making
sure
that
you
know
whatever
you
use
for
what
you
know
the
tools
that
we
shipped
for
management
today
we'll
be
able
to
manage
that
in
a
in
a
way
that
is
expected
by
seasoned
users.
D
So
you
know
that's
that's
a
great
point.
Scott,
that's
you
know
like
flat
pack
in
the
wild
today
and
fedora
is,
is
great
and
it
provides
a
you
know
like
it's
really
easy
to
see
the
benefit
of
flat
pack
when
you
use
it
in
fedora.
Now
we
need
to
take
that
and
and
how
to
you
know
and
make
it
enterprise
grade
and
in
line
with
what
a
a
rel
administrator
would
expect.
C
And
the
the
parallel
with
the
red
hat
container
catalog,
I
think,
is
a
really
good
one
because,
like
we
do
automatic
rebuilds
of
those
containers
every
six
weeks
by
default
and
if
there's
a
you
know
critical
or
important
cbe
opened
against
any
component
and
by
the
way
we
track
all
the
components.
You
can
look
at
it
in
the
container
catalog
of
what
actually
went
in
there
to
build
that
container.
C
It's
a
rebuild
all
the
way
across
all
of
the
assets
that
are
affected
by
that
that
package
change
so
like
we've
done
it
with
other
technologies,
and
hopefully
we
we
will
continue
to
carry
on
and
do
that
in
newer
technologies
as
well.
C
That's
the
goal
so
bob!
What's
what's
one
thing
you
see,
people
do
with
rel
all
the
time
that
you
wish
they
would
either
not
do
or
do
differently.
I
love
this
question.
D
What
do
they
do?
Write
star
wars
fan
picture-
I
don't
know
I'm
kidding.
Of
course
I
love
your
star
wars,
fans
fiction,
the.
What
do
they
do
with
rel.
B
D
Trying
to
bag
on
apple-
and
I
and
I
love
apple
and
I
don't
know,
use
a
use
rel
and
not
tell
us
what
they
don't
like
or
do
like
one
of
my
whenever
I
get
I
get
called
into
you
know,
customer
calls,
and
sometimes
it's
just
a
you
know
it's
like
it's
part
of
a
various
different
kinds
of
engagements.
Sometimes
it's
you
know
this
customer
is
angry
and
they
want
somebody
to
talk
to
or
sometimes
it's
hey.
D
Can
you
explain
why
customers
should
use
this
instead
of
this,
but
one
of
my
favorite
things
and
and
I'm
very
open
with
every
customer
that
I've
ever
spoken
to
is
getting
the
bad
feedback.
D
So
I
guess
one
of
the
things
that
I
don't
like
is
when
people
use
something
they're
not
happy
with
it,
and
they
don't
tell
me
why
ooh
good
point,
because
you
know
in
fact,
early
earlier
today
I
was
I
was
on
a
phone
call
with
a
customer,
and
I
was
very
explicit
about
saying
that
I
want
to
know
every
problem
that
you
have,
because
if
I
don't
know,
I
can't
fix
it
and
it's
my
goal
to
make
rel
workstation
better
all
the
time.
D
I
want
your
users
to
ask
for
rel
workstation,
because
that
tells
me
I've
done
my
job
right,
but
I
can't
do
it
if
people
don't
tell
me
what's
wrong.
D
Yeah
and-
and
you
know
it's-
some
people
are
really
not
shy
about
giving
me
bad
news
all
the
time,
which
is
thank
you,
sir
yeah,
and
but
it's
but
the
and
that's
great,
but
the
danger
there
is
that
I
you
know
I
have
to
get
other
end
users
and
an
organization's
input.
D
D
I
would
much
rather
you
know
make
sure
that
it
is
suitable
for
lots
of
different
things,
because
you
know
I
love
seeing
the
kinds
of
I
love,
seeing
the
things
that
everybody
makes
with
a
withdrawal
workstation.
C
Sounds
good
awesome,
so
chris
I
I
saw
that
there's
some
like
chatter
in
the
in
the
chat,
anything
we
should
more
largely
engage
with,
or
should
we
pivot
in
to.
B
D
B
I
can't
see
them
so,
okay,
right,
like
that's
what
I
mean
like,
let's
get
bob's
answer
on
this.
If
he
wants
to
the
point
of
bsd
users
argument
is
that
they
have
a
different
development
model
than
linux,
and
I
realize
that
the
bsd
argument
is
true.
What
do
you
think
about
this?
From
the
point
of
information
security
me
being
on
me?
Not
knowing.
A
A
B
B
B
C
Yeah,
let's
continue
forward
all
right,
so
I
wanted
to
pivot.
Actually,
let
me
share
my
screen
here
to
tell
folks
that
we're
doing
something
a
little
bit
different
with
our
relabs.
C
C
Configuring
network
interfaces,
one
is
about
the
network,
manager,
command
line,
interface
or
nmcli,
and
then
like
there's
this
one
on
file
permissions.
That
goes
into
like
what
are
file
permissions
and
that
manipulating
the
mod.
C
C
Managing
user
and
group
accounts
so
creating
users
create
that
shared
and
adding
users
to
it.
Now
I
know
that
the
content
author
on
this
is
jared
anderson
and
he's
working
on
one
on
installing
software.
C
That,
I
think,
is
actually
was
it
already
published.
Let's
see,
oh
there,
it
is
installing
software,
so
it's
like
some
basics
on
yum
and
rpm,
and
then
there's
another
one
that
he
and
I
were
talking
about
today
on
process
and
service
management.
C
C
So
I
just
want
to
give
a
shout
out
to
jared
the
other
thing
that
we've
done
recently
down
at
the
very
very
bottom.
Is
I've
created
an
open
lab
yeah
which
is
yeah?
Essentially
it's
like
hey
here's
a
box
and
you
can
do
things
so.
B
How
long
does
it
last
because
we
have
the
same?
We
have
a
similar
thing
in
in
the
the
openshift
playground
yeah.
We
call
it
and
it's
like
60
minutes.
It's
not
very
long.
C
And
I
think
ours
is
30
minutes;
okay,
it's
between
30
and
60
minutes
yeah,
but
like
if
you're
just
trying
to
do
something
simple.
I
think
it's
perfectly
adequate.
You
just
want
to
install
a
package
or
you
want
to
test.
D
C
So
there's
there's
all
different
kinds
of
things
that
you
can
do
with
it,
if
you
so
choose
and
eventually
it'll
get
provisioned
and
we
can
see
the
the
command
line
also
it
it
is
installed
with
the
web
console
right,
which
is
providing
a
cockpit
project.
Yep.
C
So
if
you
hit
this
guy
and
say
that
you
want
to
view
ports,
I
think
it's
99
db.
B
C
Right
so
you
can
like
log
in
to
to
the
web
console
and
do
graphical
based
administration
if
you've
not
seen
that
before
or
you
want
to
try
something
out.
What's.
B
B
C
I
think
web
console
gets
kind
of
a
bad
rap,
especially
amongst
experienced
users,
because
they
think
of
it
as
graphical
and
graphical
is
for
noobs
right
and
in
reality,
like
there's
a
lot
of
things
that
web
console
offers.
That.
C
It
makes
your
life
better,
even
if
you're
experienced
like,
for
example,
one
one
of
my
co-workers
uses
the
storage
plug-in
all
the
time
for
managing
his
logical
volumes
and
he's
like
it's
not
a
matter
of
capability
like
he
could
run
vgs
and
look
at
the
blind
groups
and
do
an
lv
extend
and
mistyped
the
size
and
have
to
go
back
and
fix
it
again
and
grow
the
file
system,
and
you
know,
there's
like
this
whole
procedure
for
doing
it,
he's
capable
of
doing
that.
C
C
B
As
somebody
that
rarely
resizes
a
volume,
I
have
to
go,
look
up
the
commands
every
time
right,
like
I
know,
there's
a
series.
I
know
how
to
do
that.
I've
been
certified
in
doing
it,
but
I
don't
remember
all
the
time
if
I
can
go
and
just
slide
something
as
opposed
to
running
20
commands
or
10
commands
or
five
commands,
even
that's
way
easier
for
me.
I
feel
like
and
yeah
saves
me
more
time,
which
is
what
I'm
all
about.
C
C
Oh,
I
need
to
install
it,
but
it'll
show
you
like
performance
metrics
of
the
box
or
in
the
containers
plug-in
for
it.
You
can
actually
like
download,
run,
manage
running
containers
on
the
box.
It's
actually
really
slick
web-based
interface
into
podman.
Essentially,
they've
also
done
a
lot
of
extension
of
the
cockpit
machines
plug-in,
so
it's
much
more
on
par
with
vert
manager,
which
was
our
classic
utility
for
managing
virtual
machines
on
the
on
a
host
on
a
rail
host.
C
And
then
also
more
recently
under
software
updates,
so
it
used
to
be
that
anytime,
you
did
an
install
of
updates,
it
would
just
say:
oh,
you
should
reboot
the
machine,
no
matter
what
it
was
like.
I
installed
an
apache
update,
oh
reboot,
machine
yeah.
No,
no
now
it'll
actually
be
like
you
should
restart
these
services
or
if
there
is
one
like
a
kernel,
that'll
go.
You
should
reboot
the
machine
right
to
get
this
fully
effect,
but
yeah.
So
if
you've
not
seen.
B
B
B
A
C
Well,
it
captures
a
ton
of
system
data
and
I
know
that
we've
been
a
bit
bumpy
in
our
grafana
integration
with
it
but
again
with
a4.
I
think
we've
closed
that
gap
even
further
and
made
it
easier
to
build
grafana
dashboards
to
be
based
off
of
the
performance
co-pilot
data
yeah.
So
so,
if
you
look
at
it,
you
know
two
years
ago,
you're
like
wow
wish
it
was
easier.
Well,
you
should
look
at
it
again
because
mike
could
be
easier.
A
B
Which
also
has
cockpit
installed
as
it's,
you
know
kind
of
upstream
of
red
hat
and
it
has
multiple
nics
and
I
have
those
next
assigned
to
do
different
things.
So
I
can
actually
like
look
at
utilization
to
kind
of
get
an
idea
of.
Are
you
doing
the
thing
right
or
not?
B
Are
you
load
balancing
services
correctly,
that
kind
of
thing
it's
very
nice
to
be
able
to
see
kind
of
traffic
utilization
live.
You
know.
B
C
So
you're,
looking
at
like
network
io
or
disk
io.
B
Right
exactly
network
io,
especially
in
and
out
because
you
know
I
am
on
a
quote,
unlimited
connection,
but
sometimes
that
unlimited
connection
seems
to
favor
some
services
more
than
others.
So
it's
just
interesting
to
see
what
happens
when.
C
B
Right
yeah,
it's
just
one
of
those
things
where
it's
like.
Are
you
able
to
download
these?
You
know
new
updates
in
a
speedy
fashion.
What's
going
on
here
and
then
you
know
test
and
find
out.
Oh
some
reason,
I'm
being
rate
limited.
B
A
C
B
Yeah
account
management
too
right
like
if
I
need
to
add
a
friend,
you
know
that's
here
under
accounts
yeah,
it's
it's
easier
to
kind
of.
I
know,
that's
the
one
thing
that
I
feel
like
active
directory
does
kind
of
get
right.
You
know
showing
you
hey,
this
user
is
part
of
all
these
groups
and
that
kind
of
thing
right,
like
you,
click
on
a
user,
you
get
all
the
data.
B
C
They
have
ad
for
unix
services,
and
especially
essentially,
what
they
do
is
provide
the
normal
unixy
things
like
gizma
and
uid
groups
in
a
format
that
xboxes
can
consume.
C
Red
hat
has
identity
manager
which
is
based
off
the
free
ipa
project,
and
it
can
do
active
directory
integration
or
it
can
manage
user
accounts
and
there's
like
a
really
sophisticated
web
ui
for
working
with
that.
If
you've
not
seen
before,
but.
C
Bob
any
any
parting
words
of
wisdom
before
we
close
up
the
show
drop
one
on
me,
I
like
putting
him
on
the
spot.
D
D
But
seriously,
if
you
are
using
rel,
workstation
or
bell
period
right
in
your
work
or
you
know
in
any
capacity
product
managers
want
to
know
what
you
don't
like.
You
will
not
hurt
our
feelings
right.
We
work
with
people
like
scott
we're
like
made
of
callous
now,
so
please,
please,
please.
We
want
to
know
what
your
what
you
would
love
to
have
us
improve.
You
know,
even
if
it
seems
like
crazy,
you
know,
like
you
know.
D
What
would
be
great
is
if
you
replaced
package
some
critical
like
let's
say
you
wanted
us
to
replace
gnome
with
with
a
different
desktop
environment.
D
You
know
what
we'll
make
sure
that
never
happens,
keeping
your
mouth
shut
right
and
that's
true.
For
anything.
You
know,
red
hat
is
deeply
engaged
in
a
lot
of
upstream
environments
or
upstream
projects.
So
if
there's
a
major
change
that
needs
to
happen
and
it
fits
along
with
that
particular
use
and
a
particular
project,
you
know-
and
you
tell
us
we
can-
you
know
we
can
consider
it.
D
We
can
talk
about
what
what
that
would
look
like
and
we
can
think
about
what
we
can
do
to
make
changes
that
would
make
rel
and
make
working
with
rel
better.
That's
why
we're
here.
So
please
tell
us
all
the
things
that
you
love
as
and
the
things
that
you
don't
love
so
much.
A
B
D
I
miss
I
miss
having
these
kinds
of
conversations
face
to
face
at
like
at
summit.
Nothing
feels
better
than
getting
on
an
airplane
with
a
voice.
That's
just
trashed.
At
the
end
of
four
days
of
talking
to
thousands
of
people.
B
It's
a
different
kind
of
feel
good.
It
is
all
right
awesome.
Thank
you
all
for
joining
us
today,
catch
us
in
what
two
weeks,
scott
yeah,
I
think
so
yep
and
we'll
be
back
with
more
of
your
rel
content
for
your
real
ears,
so
sign
off
for
now.
Thank
you.
Stay
safe
out.
There.