Re: [PATCH v4 1/5] expand-on-first-boot: support resizing a btrfs

[Henning Schild <henning.schild@siemens.com>]

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.

Henning
 
> debraf@debraf:~$ sudo find / -name expand-last-partition.sh
> /usr/share/expand-on-first-boot/expand-last-partition.sh
> debraf@debraf:~$ mktemp -d -p "" "expand-last-partition.sh.XXXXXXXXXX"
> /tmp/expand-last-partition.sh.K9OhJ5KxIF
> 
> my suggestion is to use /dev/shm which usually is configured into the
> kernel or at least try also /dev/shm if the use of /tmp fails.
> 
> == FELIX ==
> 
> One problem remains: Where to mount.
> If we mount on /mnt this will not work on an RO rootfs out of the box.
> We currently have this issue in CIP core.
> 
> We could mount below /tmp which should be writable, but I don't know
> which side effects this as the tmpfs itself will be mounted / created
> by systemd.
> 
> == ==
> 
> Best regards, R-