From: Worik Stanton <worik.stanton@tirotech.co.nz>
To: yocto@lists.yoctoproject.org
Subject: Introduction and my first query: Resources for learning
Date: Tue, 5 Mar 2024 11:12:18 +1300 [thread overview]
Message-ID: <CANuMBWFxwxt7Fr+qab4U+HHFiSMu4KeukjiMVkme-zgDVpiq=w@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1366 bytes --]
Kia ora
I am Worik Stanton, from Dunedin New Zealand. I am new to Yocto, and to
this list, with many decades experience programming computers.
My question is about what are the best resources for learning how to adapt
and maintain a Yocto system I am responsible for.
I have recently become responsible for a collection of Yocto "builds" (I am
unsure how I should describe them) that I must learn how to maintain,
adapt, and extend. Adapt and extend to new hardware and to new software
that we are writing.
The author of the system is available only sporadically and is cleary
moving to greener pastures and is unable to offer much help.
I have the "Embedded Linux Systems with the Yocto Project" and it is
helpful. However the systems I am working with are, I fear, quite
idiosyncratic and highly developed.
The example of the sort of problem I have faced and solved is I needed
"lsblk" in my build. I found that by adding the name of the Debian package
to a variable IMAGE_INSTALL "IMAGE_INSTALL += util_linux" essentially,
places "lsblk" in the root file system.
I have no idea why I used the name of a Debian package!
I do not feel ready to pester you folks with queries until I have done more
reading and have moved along the learning curve. I am hoping for some
meta advice about where I can look for guidance for problems like that.
Worik
[-- Attachment #2: Type: text/html, Size: 1707 bytes --]
next reply other threads:[~2024-03-04 22:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 22:12 Worik Stanton [this message]
2024-03-05 8:53 ` [yocto] Introduction and my first query: Resources for learning Michael Opdenacker
2024-03-06 4:03 ` Worik Stanton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CANuMBWFxwxt7Fr+qab4U+HHFiSMu4KeukjiMVkme-zgDVpiq=w@mail.gmail.com' \
--to=worik.stanton@tirotech.co.nz \
--cc=yocto@lists.yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).