From: "Einar Jón" <tolvupostur@gmail.com>
To: poky@lists.yoctoproject.org
Subject: [question]: Creating tailored image without standard rootfs files?
Date: Wed, 13 Dec 2023 16:57:55 +0100 [thread overview]
Message-ID: <CABhNV21oUdDU7dULZOin11ex4UPGt5dLA0yoBkSQTbBaHw-abw@mail.gmail.com> (raw)
In-Reply-To: <CABhNV20HP8rNTkEfnUqbju43Z7K=LOHNanUc1nosnvHprxUa7A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]
Hello,
I basically want to be able to build an ext4 image for an extra partition
that is not a rootfs.
So I don't need the kernel, or /run /var /etc folders or anything like that.
Just a few packages are needed, but with a QT app on that partition, loads
of dependencies are pulled in and I end up with +80 entries in the manifest.
This was asked 10 years ago, but I still have the same issue now.
https://docs.yoctoproject.org/pipermail/yocto/2013-March/012804.html
This image would then be used by wic as well as swupdate, as a non-root
partition.
Are there some tweaks to actually build an image without pulling in
everything needed for a rootfs*?
I tried making my own tweaked version of image.bbclass, but I got lost in
the abstraction.
*) Building a basic container-test-image with a linux-dummy still has all
the folders /bin /boot /dev /etc /home /lib /media /mnt /proc /run /sbin
/sys /tmp /usr /var
and +20 entries in the manifest (17MB of stuff), just for a 12KB binary
(/usr/bin/theapp).
--
Regards
Einar Jón
[-- Attachment #2: Type: text/html, Size: 1589 bytes --]
next parent reply other threads:[~2023-12-13 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABhNV20HP8rNTkEfnUqbju43Z7K=LOHNanUc1nosnvHprxUa7A@mail.gmail.com>
2023-12-13 15:57 ` Einar Jón [this message]
2023-12-13 18:11 ` [poky] [question]: Creating tailored image without standard rootfs files? Ross Burton
2023-12-14 9:43 ` Einar Jón
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=CABhNV21oUdDU7dULZOin11ex4UPGt5dLA0yoBkSQTbBaHw-abw@mail.gmail.com \
--to=tolvupostur@gmail.com \
--cc=poky@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).