►
From YouTube: CentOS Automotive SIG - June 1, 2022
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
All
right:
well,
let's
go
ahead
and
type
in
so
good
morning
afternoon
evening,
everyone
and
welcome
to
the
centos
automotive
sig
monthly
meeting.
This
is
the
monthly
call
that
we
record
that
we
get
together
and
talk
about
the
technical
status
of
the
project
and
find
out
all
the
different
stuff
that's
going
on.
I
have
a
very
brief
agenda,
which
is
out
of
date,
because
this
is
the
agenda
from
last
month.
A
B
Sure
so,
just
the
g4
nicely
put
at
the
top
the
reminder
to
where
things
live.
So
you
can
find
the
code
on
class
gitlab.com.
You
have
a
number
of
repositories
there
you
can
browse
everything
that
is
under
source
will
have
sources.
Everything
on
the
rpms
will
help
the
sources
to
build
the
rpm,
so
spec
file
patches
you'll,
have
the
sample
images.
You
also
have
to
talk
repo,
the
documentation
which
you
can
see
live
at
six.center.org
motif.
B
It
contains
a
number
of
informations
about
what
the
sig
produces,
how
you
build
raspberry,
pi
images,
how
you
build
customize,
how
you
can
customize
your
images,
how
you
can
contribute
to
the
to
the
seek
from
an
rpm
point
of
view.
Where
do
you,
whether
you
contribute
rpms,
depending
on
where
you
want
things
to
go?
B
So
there
are
a
few
things
we've
looked
at
recently
and
I'm
going
to
take
them
in
reverse
order.
From
what
jfro
put
in
there,
we
looked
at
using
usb
get
jet
configuring,
the
raspberry
pi
to
be
usb
gadget
so
usb
catch.
It
is
something
in
the
linux
kernels
that
allows
a
device
plugged
via
usb
cable
to
appear
to
the
to.
You
know
the
laptop
that
is
connected
to
as
if
it
was
a
network
device.
B
So
it
you
basically,
the
idea
is
that
you,
you
have
a
raspberry
pi
image,
you
flash
it
onto
an
sd
card.
You
plug
that
sd
card
into
your
s3
pi.
You
power,
the
raspberry
pi
via
usb
c
cable
to
your
laptop
and
the
raspberry
pi
boots,
and
there
is
a
network
created
between
the
laptop
and
your
raspberry
pi
and
you
can
ssh
into
the
raspberry
pi
while
it
is
not
plugged
in
anything
other
than
the
usbc
cable
to
your
laptop.
So
it's
not
connected
to
the
network.
B
So
imagine
if
you're
in
a
in
a
very
restrained
network
environment
from
you
know
from
your
company
or
you
just
don't
want
you
know,
just
don't
try
you
just
don't
trust
the
raspberry
pi
to
be
plugged
to
your
network
on
geras.
Maybe
you
just
don't
have
the
the
network
there,
so
you
that's
an
easy
way
where
you
could
ssh
into
the
raspberry
pi
over
the
usb
over
the
usb
cable
and
get
it
to
work
nice
and
easy.
B
So
this
was
this
is
something
we
have
worked
on.
We
have
made
it
working
on
linux.
We
have
made
it
working
on
windows
and
both
of
these
are
in
the
documentation
that
gfro
linked
to
earlier
there
are.
There
are
a
few
pages
that
we've
been
pointed
are
not
available
in
the
documentation,
but
if
you
go
to
the
building
page
at
the
very
bottom,
you
have
a
number
of
extra
resources.
B
Things
like
the
deluxe
encryption,
so
yeah
building
images,
and
then
you
scroll
to
the
bottom.
There.
B
There
you
have
additional
resources
so
like
how
do
you,
how
do
you
use
our
s3,
or
do
you
update
on
os3?
How
do.
B
Or
you
can
customize
your
own
noise
field
images,
your
templates,
how
you
can
embed
containers
into
the
image
how
you
can
encrypt
that
image
and
get
to
that?
And
then
you
have
here.
B
Via
you,
as
a
usb
gadget,
we
are
not
quite
there
yet,
but
we
have
everything
in
place,
but
we're
not.
B
We
don't
have
the
final
piece
missing
here
to
actually
make
these
images
available
so
that
you,
you
can
directly
grab
an
image
from
osd.6.centos.org
and
you
know
download
that
image
flash
it
onto
the
sd
card
and
and
get
it
as
a
usb
gadget
there.
It's
we
it's
almost
ready.
We
just
need
to
figure
out
to
find
a
mechanism
to
build
these
images
and
make.
D
B
Available,
so
it's
soon
to
come,
but
not
there
yet
so
that's!
That
was
the
first
point.
The
second
one
is
the
I'm
actually
going,
I'm
going
to
skip
the
linux
film
I'll
come
back
to
it
afterwards,
I'm
just
going
to
mention
the
lux
encrypting
images
with
vlogs,
because
I've
mentioned
it
just
a
few
seconds
ago.
It's
part
of
the
same
at
the
bottom
of
the
building
images
documentation.
You
have
an
old
page
about.
B
Encrypt
your
system,
using
lux
directly
for
the
image
you're
building
with
build
coming
back
to
the
links
firmware.
The
linux
firmware
is
a
pretty
big
package.
Rpm
package,
it's
about
200,
meg
of
binary
blobs
for
all
sorts
of
boards,
which
is
rare,
which
is
of
you,
know,
high
interest
for
a
generic
purpose
operating
system
such
as
braille
or
federer,
or
center
stream.
But
in
our
case
we
are
targeting
a
much
smaller
set
of
devices,
so
we
don't
actually
need
to
have
holder
firmwares
that
are
contained
in
the
linux
firmware.
B
So
as
a
proof
of
concept,
we
reduced
the
size
of
the
linux
firmware
and
we
created
a
linear,
extremely
automative
rpm,
that
is
in
the
automotive
c
repository,
and
currently
it
basically
only
contains
the
raspberry
pi
firmware
and
maybe
a
few
others
or
depending
dependent
one.
B
But
the
idea
is
yeah
just
to
reduce
the
the
size
of
the
image
as
well
as
the
need
of.
We
don't
need
to
have
a
lot
of
firmwares
if
we
only
care
about
few
parts,
and
the
last
point
is
the
the
first
one
on
the
list
here
is
that
we,
with
the
ship
shortage
and
the
increase
in
cost
of
simple
device
such
as
a
raspberry
pi.
Just
to
give
you
an
idea.
In
france,
the
price
of
raspberry
pi
has
about
doubled.
B
In
a
year
we
went
from
about
100
to
150
euros
to
between
two
and
three
hundred
euros,
four
bought
with
a
case-
and
you
know
sd
card
provided
fun
for
the
cpu
and
other
kind
of
things.
That
is
a
lot,
but
it
is
also
bringing
an
interesting
an
interesting
conversation,
because
that
makes
secondhand
android
devices
a
lot
closer
in
price
to
the
raspberry
pi.
I
bought
an
s9
from
sax
on
the
samsung
galaxy
s9
from
2020,
so
it's
two
years
old
phone.
B
It
has
128
of
category
a
gig
of
memory
of
disk,
sorry,
128,
gig
of
disk
and
raspberry
pi.
You
you
can
have
128
gigs
of
disk.
You
can
even
have
off
more
than
that
in
microsd
cards,
but
the
micro
sd
cards
with
sono
are
pretty
fragile.
So
you
have
better
storage
or
more
reliable
storage.
B
B
B
So
it's
that
that's
what
brought
us
to
look
at
the
android
devices
a
as.
C
B
Mechanism
to
you
know,
have
access
to
an
af64
system,
so
I
have
used
the
work
that
terry
curtin,
who
is
in
the
call
as
as
done
and
as
you
know,
he
opened
the
past
to
to
this
investigation
and
we
looked
at
what
it
would
take
to
to
build.
B
So
eric
made
it
easy
for
anyone
to
have
p
roots,
which
is
the
unprivileged
equivalence
of
a
sketch
route,
so
see
it
roots.
You
can
run.
Let's
see
you
can
have
a
linux
fruit
in
an
android
device.
If
you
root
the
phone,
you'll
have
a
linux
period.
If
you
do
not
root
the
phone
and
the
recommended
way
is
not
to
root
your
phone,
because
if
you
do
root
it
android
will
reset
itself
from
scratch,
because
something
or
someone
has
tempered
with
the
phone.
B
So
I'm
going
to
erase
all
the
data
on
the
phone,
but
also
a
number
of
applications
are,
are
going
to
refuse
to
work
because
something
has
tempered
with
the
funnel.
B
So
we
we've
been
looking
at
period
overseert
and
so
eric
has
made
it
easy
to
to
get
a
federer
federal
environment
in
using
periods
using
termix
on
android
devices.
It's
it
is
interesting.
It
is
an
interesting
angle
to
look
at.
B
We
are
able
to
compile
software,
we
were
able
to
compile
things
like
the
time
package.
You
know
we
just
took
the
time
sources
and
we
are
able
to
configure
and
make
make
install
with
that
problem.
We
have
run
into
two
issues.
One
of
them
is,
we
are
not
able
to
build
rpms
directly,
and
this
is
weird.
Basically,
when
you
do
rp,
I
took
the
source
rpm
from
you
know
from
koji.
B
I
don't
need
them
into
the
phone,
I
do
rpm
build
rebuild
and
it
it
builds,
and
it
fails
at
the
very
last
step
which
is
creating
writing
on
disk
the
rto,
the
actual
rpm
binary
file.
I
got
things
like
the
the
debug
source
profile,
for
I
also
looked
at
the
x-pac
package,
which
is
one
I
was
using
as
a
test
package
in
another
project,
and
this
one
has
a
package
that
is
a
static,
rpm
static,
sub
package
and
that
sub
package
was
written
fine
on
disk,
but
the
expect
rpm
the
time
rpm.
D
B
Font,
so
we
are
not
quite
sure
what's
going
on
here.
Our
our
inch
is
that
there
is
something
in
the
android
kernel
that
prevents
it.
B
Maybe
it's
something
in
the
s900
that
I
have
or
ds9
device
that
I
have
maybe
something
specific
to
android,
we're
not
quite
sure
there,
and
it's
it's
a
little
bit
one
of
these
case
where
we
want
to
go
to
the
bottom
of
it
because
we're
curious
about
it.
But
on
the
other
side,
if,
if
fitting,
you
know
what
are
what
are
our
chances?
B
If
we
find
the
issues,
if
we
can
fix
the
issue,
what
are
our
things?
What
are
our
chances
that
we
can
contribute
that
fix
to
android
that
we
can
get
that
fixed
deployed
on
phone
sync,
including
all
the
phones
who
are
now
two
years
old,
it's
fairly
low,
so
we
may
investigate
it.
B
Unfortunately,
when
we
build
images
using
waste
build
at
one
point,
we
are
building
a
file
system
when
we
need
to
mount
that
file
system
and
that
one
command
needs
admin.
Access
on
the
device
and
keyword
does
not
have
full
admin
access,
and
so
the
period
actually
does
not
implement
the
mount
system
call.
So
we
are
not
able
to
build
rpms
and
we
are
not
able
to
build
images
on
the
android
device.
B
C
B
Yeah,
we
have
also
looked
at
being
able
to
have
image
manifest
hosted
outside
of
the
the
sample
image
repo.
So
you
can
point
when
you
do
when
you
do
your
make
command,
you
can
actually
say
well
my
manifest
my
folders
with
the
the
manifest
image
are
somewhere
else,
that's
handy
for
if
you
want
to
customize
things
on
your
side,
sample
image,
some
of
the
sample
image
are
already
available
in
auto
isd.center.org.
B
B
And
if
especially
the
gadget,
one
is
not
there
yet.
Also
like
the
neptune
one,
I
believe
it's
not
there
yet.
So
we
also
don't
have
a
nice
image
with
a
you
know,
with
a
nice
graphical
interface
that
people
can
download
and
that's
working
progress.
So
it's
it's
there
and
that's
and
the
idea
is
to
have
this
image
being
generated
by
the
civ
pipeline.
So
it's
a
part
of
the
ci
pipeline
which
includes
the
test
path
line.
B
So
that's
that's
about
it
and
I
think
I've
covered
everything
else
in
this
slide.
In
my
previous
chat,
that
was
a
long
rant.
If
you
have
any
questions
anything
I've
said
wrong.
Please.
A
Does
anybody
have
any
questions
or
any
any
comments
on
all
of
that.
F
Now
it
all
looks
great,
I
think,
there's
we
certainly
have.
We
have
left
no
stone
unturned
in
looking
at
ways
that
people
who
don't
necessarily
have
access
to
server
class
hardware
can
can
still
do
some
meaningful
development
on
arm.
So
I
think
it's
really
cool.
A
B
The
android
devices,
but
I
have
very
very
little
hope,
is
a:
could
we,
by
any
chance
to
run
an
actual
virtual
image
on
an
android
on
an
android
device
which
may
solve
some
of
the
permission
issue
that
we
are
that
we're
having
with
the
periods
we
have
yeah
low
hopes
on
that
things
like
dev
kvm
are
not
available
on
the
devices
even
running
the
qmuk
qmu
ar64
on
the
p
root
gives
you
a
permission,
design
error,
so
it
I'm
just
starting
to
look
into
that.
A
E
Firmware
that
is,
that
is
blocking
you,
so
eric
has
also
access
to
other
hardware.
You
know.
B
E
D
C
D
F
Yeah,
I
think,
the
only
other
that,
as
you
are
encountering
these
issues,
pierre
and
eric
I'm
struck
by.
If
we
look
at
what
yocto
does
in
order
to
be
able
to
do
all
of
the
things
it
does
for
image,
building
as
an
unprivileged
user,
they're
they're
all
related
to
the
same
stumbles
that
we're
seeing
when
trying
to
use
p
root.
Essentially
so.
F
F
Like
yokto
generates
image
files
without
ever
having
the
ability
to
do
loop,
loopback
mouse
doesn't
have
root,
so
it
doesn't
do
loopback
mounts
and
we,
if
you
peel
back
the
onion
on
that,
you
discover
that
it
does
that
by
spoofing
the
ownership
of
files
on
the
file
system
and
then
taking
advantage
of
the
fact
that
make
fs
commands
can
be
run
in
non-privileged
mode
if
they're
targeted
at
a
file,
and
they
can
be
pointed
at
a
directory
to
populate
the
file
system.
So
that's
an
interesting
one.
F
Image
builder
takes
advantage
of
the
kernel,
uses
the
kernel's
knowledge
of
the
file
system
to
populate
the
file
system.
The
octo
uses
user
space
tools.
That
can
accomplish
the
same
thing.
So,
but
again
at
that
point,
and
the
other
interesting
thing
about
image
building
is
if
you're,
if
you've
got
something
you
can
flash
an
image
on
to.
Why
aren't
you
using
that
to
do
your
development
so
perhaps
because
you
only
have
one
of
them
and
you
can't
build
the
image
and
then
flash
it
etc.
So
that's
interesting
stuff.
B
B
So
the
there
is
a
team
in
in
reddit
that
has
looked
at
the
the
chromebook.
Let
us
look
at
the
chromebook
with
some
success.
Eric
is
saying:
hey
kiss
has
placed
another
from
from
books
three
months
ago
and
is
still
waiting
on
the
list.
I
have
placed
another
for
m1
and
I
got
three
months
ago
and
I
got
the
tracking
number
for
the
order
earlier
today.
B
B
F
No,
it
works
it.
It
has
hyper
v.
I
I
mean
I
feel
with
both,
in
both
cases
we're
kind
of
dishonoring
the
primary
use
case
for
these
things
and
just
using
them
as
virtual
machine
hosts,
but
they
do
work
so
they're
available,
there's
also
a
there's,
a
thinkpad
that
does
windows
for
arm.
That's
supposed
to
be
coming
out.
It
was
supposed
to
come
out.
Last
month
it's
apparently
been
delayed,
but
that's
very
closely
related
to
some
of
the
hardware.
We're
looking
at
the
thinkpad
x13s
is
another
windows
for
arm.
F
D
F
A
A
Not
exactly
just
world
weary,
I
guess
yes,
there
are
also
a
number
of
other
boards
that
that
are
out
so
that
they're
they're,
basically
have
already
been
manufactured,
were
manufactured
prior
to
the
chip
shortage,
the
ones
that
I'm
thinking
of
are
the
some
of
the
ones
from
99
boards.
A
The
beagle
board,
in
particular
like
the
the
there's,
a
small
pocket
beagle
that
has
been
made
in
large
quantity
and
it
uses
it
uses
a
ti
chip.
But
it
is
an
arm
processor.
It
actually
has
a
built-in
dsp.
F
Thing
is
even
raspberry
pies
that
were
manufactured
before
the
chip
shortage,
the
the
secondary
market
for
a
lot
of
these
things
has
gone
up
because
they're
so
much
harder
to
find.
The
other
challenge
I
think
we
face
is
that
our
like
hard
as
it
is
to
believe,
like
less
than
four
gigs,
is
a
fairly
constrained
environment
for
the
type
of
rpms
and
whatnot
that
we
build.
I
think
a
lot
of
it
comes
down
to
that's
roughly
the
size
of
our
own
builders,
for
things
in
fedora
yeah
and
in
rel.
F
So
a
you
know,
beaglebone
the
beagleboards
that
I'm
aware
of,
I
think
many
of
those
have
less
than
oh.
You
know
less
than
a
gigabyte
of
memory.
Some
of
them
are
are
512
mags.
Some
of
them
are
cake,
whereas
the
pie-
and
these
things
like
the
surface
and
the
m1,
have
a
reasonable
amount
of
memory
right.
That's
the
main
concern.
A
I
thought
the
pocket
beagle
had
oh
you're
right.
It
only
has
half
a
it
actually
has
512
megs
of
ddr3.
So
it's
a
a
very
underpowered
chip,
a
very
forgetful
machine,
a
very
forgetful
little
two
little
homer.
Let's
see
a
lot
of
swapping
what's
going
on
yeah,
which
is
not
it's
funny
that
was
state
of
the
art
a
few
years
ago,.
A
A
X13S
is
the
one
I'm
actually
looking
x13s
right,
because
I'm
looking
at
this
regular
x13
currently
has
yeah.
That's
my
stand
for
snapdragon
x86,
okay,.
C
A
F
A
A
Oh,
I
don't
have
it.
I
took
it.
I
took
it
to
to
my
office.
I
have
a
remote
server,
it's
actually
a
a
minnow
board.
It's
an
x86
4x4
inch
board
with.
I
don't
remember
what
processor
is
on
it,
but
I
3d
printed
a
case
for
it.
I
was
very
proud
of
myself
finally
getting
getting
hands
on
with
things
for
the
first
time
in
a
while.
A
Okay,
well,
we
can
probably
give
people
a
half
an
hour
back.
I
I
don't
see
any
unless
we
have
stuff
to
talk
about
there's.
No,
you
know
one
of
one
of
the
best
practices
for
meetings
is
to
not
sit
there
in
silence
and
just
if
we're
out
of
stuff
to
talk
about,
we
can
move
on,
we
will
be
having
the
office
hours
again
in
a
couple
of
weeks.
A
So
unless
anybody's
got
anything
else,
we
can
just
wrap
it
up.