From: Henning Schild <henning.schild@siemens.com>
To: "balasubramanian.sundaram@sanmina.com"
<balasubramanian.sundaram@sanmina.com>
Cc: "Bezdeka, Florian" <florian.bezdeka@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: ISAR expand-on-first-boot
Date: Wed, 28 Sep 2022 11:22:40 +0200 [thread overview]
Message-ID: <20220928112240.1141bfa1@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <4e88c35bd35a207d1c07f2d93d53e635bd3eb66b.camel@siemens.com>
Am Tue, 27 Sep 2022 09:53:57 +0000
schrieb "Bezdeka, Florian" <florian.bezdeka@siemens.com>:
> Hi,
>
> On Tue, 2022-09-27 at 02:04 -0700, 'Balasubramanian Sundaram' via
> isar- users wrote:
> > Hi Team,
> >
> > I using 8 GB SD card for flashing .wic image with expand-on-first-
> > boot added in /conf/machine/imx6ull-14x14-evk.conf file .
> > It gets expand up to 6.5 GB
> > Is there any where we can change manually the size how much like 5
> > GB or 4 GB after flashing it to SD Card in ISAR
> > please suggest us for that without expand-on-first-boot , is there
> > any way we can alter the SD card size manually and build in ISAR
>
> expand-on-first-boot is designed to expand the *last* partition to the
> available maximum. If you want a fixed size you can modify your
> partition layout (.wic file) accordingly.
Right, i.e. --fixed-size 4G or --size 4G
see https://docs.yoctoproject.org/ref-manual/kickstart.html
And you want to not install expand-on-first-boot in that case, or add
another last partition to become the subject of growing.
That whole on first boot growing is meant for cases where one does not
know how big the storage medium is going to be and use all of it. If
you know how big it is going to be, or if you do not need the space ...
it is likely better to avoid such dynamic resizing.
Henning
> >
> > CONFIDENTIALITY
> > This e-mail message and any attachments thereto, is intended only
> > for use by the addressee(s) named herein and may contain legally
> > privileged and/or confidential information. If you are not the
> > intended recipient of this e-mail message, you are hereby notified
> > that any dissemination, distribution or copying of this e-mail
> > message, and any attachments thereto, is strictly prohibited. If you
> > have received this e-mail message in error, please immediately
> > notify the sender and permanently delete the original and any
> > copies of this email and any prints thereof.
> > ABSENT AN EXPRESS STATEMENT TO THE CONTRARY HEREINABOVE, THIS E-MAIL
> > IS NOT INTENDED AS A SUBSTITUTE FOR A WRITING. Notwithstanding the
> > Uniform Electronic Transactions Act or the applicability of any
> > other law of similar substance and effect, absent an express
> > statement to the contrary hereinabove, this e-mail message its
> > contents, and any attachments hereto are not intended to represent
> > an offer or acceptance to enter into a contract and are not
> > otherwise intended to bind the sender, Sanmina Corporation (or any
> > of its subsidiaries), or any other person or entity.
>
> ^^ This doesn't make sense on a public mailing list...
>
> Regards,
> Florian
>
prev parent reply other threads:[~2022-09-28 9:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 9:04 Balasubramanian Sundaram
2022-09-27 9:53 ` Bezdeka, Florian
2022-09-28 9:22 ` Henning Schild [this message]
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=20220928112240.1141bfa1@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=balasubramanian.sundaram@sanmina.com \
--cc=florian.bezdeka@siemens.com \
--cc=isar-users@googlegroups.com \
/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