From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com, felix.moessbauer@siemens.com,
Joe MacDonald <Joe_MacDonald@mentor.com>
Subject: Re: [PATCH v4 1/5] expand-on-first-boot: support resizing a btrfs
Date: Tue, 13 Dec 2022 21:44:01 +0100 [thread overview]
Message-ID: <CAJGKYO6xF6XiW2FS7SALXcm2xXOfHbi3g8UkEZFBO9NNMXb2tg@mail.gmail.com> (raw)
In-Reply-To: <20221213181805.0f369386@md1za8fc.ad001.siemens.net>
On Tue, 13 Dec 2022 at 18:18, Henning Schild <henning.schild@siemens.com> wrote:
>
> Am Tue, 13 Dec 2022 17:45:23 +0100
> schrieb "Roberto A. Foglietta" <roberto.foglietta@gmail.com>:
>
> > On Tue, 13 Dec 2022 at 11:15, <henning.schild@siemens.com> wrote:
> > >
> > > +MOUNT_POINT=$(mktemp -d -p "" "$(basename "$0").XXXXXXXXXX")
> >
> > this uses /tmp which could not be available
>
> The remark from Felix triggered the switch from '-p "/mnt"' to '-p ""',
> one can set TMPDIR if that does not work.
>
> A valid remark, while yours seems made up just to keep trolling around
> in the whole discussion. Stop it please.
Please Hanning, tell to it to my ubuntu - she has some issue to
understand your slang
roberto:~$ export TMPDIR=/dev/shm
roberto:~$ mktemp -d -p "" ciao.XXXXX
/dev/shm/ciao.X3wlT
Ah, oops - in this following way it working, instead
roberto:~$ mktemp -d -p "$TMPDIR" ciao.XXXXX
/dev/shm/ciao.jQFYr
Possibly you did not catch the Felix suggestion? LOL
Ciao, R-
next prev parent reply other threads:[~2022-12-13 20:44 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 [this message]
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
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=CAJGKYO6xF6XiW2FS7SALXcm2xXOfHbi3g8UkEZFBO9NNMXb2tg@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