From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
Cc: "Schild, Henning" <henning.schild@siemens.com>,
"isar-users@googlegroups.com" <isar-users@googlegroups.com>,
"Joe_MacDonald@mentor.com" <Joe_MacDonald@mentor.com>
Subject: Re: [PATCH v4 1/5] expand-on-first-boot: support resizing a btrfs
Date: Wed, 14 Dec 2022 07:50:07 +0100 [thread overview]
Message-ID: <CAJGKYO5up59UfvgTYDHujW+Rzo97=b+ArUnrbfyFr3dYY2stTg@mail.gmail.com> (raw)
In-Reply-To: <e7278e7e510bb3eda23510a231f884574b005a1c.camel@siemens.com>
On Wed, 14 Dec 2022 at 04:33, Moessbauer, Felix
<felix.moessbauer@siemens.com> wrote:
> > What Felix tried to tell you was to use a variable like in my patch
> > but using TMPDIR as the name of the variable. When that variable is
> > not defined then "" is the default value. Now, what happens to mktemp
> > when it is called with -p ""? Nothing bad, it simply performs without
> > -p. Why was Felix pointing this out? Probably because in my patch tmp
> > variable should be set if null but using mktemp this is not necessary
> > anymore.
>
> No! Please also stop guessing what I could have meant and wait at least
> a day for me to answer (instead of trying to convince others of your
> interpretation of my opinion).
>
> The way Henning implemented it is exactly how I meant it.
>
> As this whole thing runs as a systemd service, a user can easily set
> TMPDIR via a drop-in file.
>
Felix, thanks for the clarification, the behaviour is aligned with the
manual but expliciting the variable would have been easier to read
without checking the manal
-p DIR, --tmpdir[=DIR]
interpret TEMPLATE relative to DIR; if DIR is not
specified, use $TMPDIR if set, else /tmp. With this option, TEMPLATE
must not be an absolute name; unlike with -t, TEMPLATE may contain
slashes, but mktemp creates only the final component
This is the output of the command without, with and with specified
TMPDIR variable
roberto:~/robang74/isar-nvidia-debian$ echo "x$TMPDIR"
x
roberto:~/robang74/isar-nvidia-debian$ mktemp -d -p "" ciao.XXX
/tmp/ciao.wLK
roberto:~/robang74/isar-nvidia-debian$ export TMPDIR=/dev/shm
roberto:~/robang74/isar-nvidia-debian$ mktemp -d -p "" ciao.XXX
/dev/shm/ciao.fYb
roberto:~/robang74/isar-nvidia-debian$ mktemp -d ciao.XXX
ciao.Lwp
roberto:~/robang74/isar-nvidia-debian$ mktemp -d -p "$TMPDIR" ciao.XXX
/dev/shm/ciao.gw1
Cheers, R-
next prev parent reply other threads:[~2022-12-14 6:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 10:15 [PATCH v4 0/5] expand-on-first-boot btrfs and CI testing henning.schild
2022-12-13 10:15 ` [PATCH v4 1/5] expand-on-first-boot: support resizing a btrfs henning.schild
2022-12-13 16:45 ` Roberto A. Foglietta
2022-12-13 17:18 ` Henning Schild
2022-12-13 20:44 ` Roberto A. Foglietta
2022-12-13 21:05 ` Henning Schild
2022-12-13 21:20 ` Roberto A. Foglietta
2022-12-14 3:33 ` Moessbauer, Felix
2022-12-14 6:50 ` Roberto A. Foglietta [this message]
2022-12-14 7:10 ` Roberto A. Foglietta
2022-12-13 17:01 ` Roberto A. Foglietta
2022-12-13 21:22 ` Henning Schild
2022-12-13 22:15 ` Roberto A. Foglietta
2022-12-13 10:15 ` [PATCH v4 2/5] meta-isar: introduce an example to use btrfs henning.schild
2022-12-13 10:15 ` [PATCH v4 3/5] CI: improve cibuilder readability henning.schild
2022-12-13 10:15 ` [PATCH v4 4/5] meta-isar: install expand-on-first-boot in most images and add space henning.schild
2022-12-13 10:15 ` [PATCH v4 5/5] CI: expect a message about filesystem resize vom expand script henning.schild
2022-12-13 10:25 ` [PATCH v4 0/5] expand-on-first-boot btrfs and CI testing Henning Schild
2022-12-20 9:37 ` Uladzimir Bely
2022-12-20 15:08 ` Henning Schild
2022-12-21 10:25 ` Uladzimir Bely
2022-12-21 12:13 ` Henning Schild
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='CAJGKYO5up59UfvgTYDHujW+Rzo97=b+ArUnrbfyFr3dYY2stTg@mail.gmail.com' \
--to=roberto.foglietta@gmail.com \
--cc=Joe_MacDonald@mentor.com \
--cc=felix.moessbauer@siemens.com \
--cc=henning.schild@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