[Bug 2065408] [NEW] growroot-almost should be inhibitable from boot partition

[Dave Jones]

Public bug reported:

Some users wish to handle post-boot partitioning or fs configuration
themselves. For this use-case it is important that the rootfs is *not*
expanded on first boot. On the server images, this is relatively trivial
by appending "growpart: off", but on the desktop images it's handled by
the growroot-almost service and this is only capable of being inhibited
by touching /etc/growroot-grown. It should be possible to inhibit this
behaviour from the boot partition only which, being FAT, can be mounted
from other OS'.

** Affects: ubuntu-raspi-settings (Ubuntu)
     Importance: Undecided
     Assignee: Dave Jones (waveform)
         Status: Confirmed

** Changed in: ubuntu-raspi-settings (Ubuntu)
     Assignee: (unassigned) => Dave Jones (waveform)

** Changed in: ubuntu-raspi-settings (Ubuntu)
    Milestone: None => ubuntu-24.10

** Changed in: ubuntu-raspi-settings (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-raspi-settings in
Ubuntu.
https://bugs.launchpad.net/bugs/2065408

Title:
  growroot-almost should be inhibitable from boot partition

Status in ubuntu-raspi-settings package in Ubuntu:
  Confirmed

Bug description:
  Some users wish to handle post-boot partitioning or fs configuration
  themselves. For this use-case it is important that the rootfs is *not*
  expanded on first boot. On the server images, this is relatively
  trivial by appending "growpart: off", but on the desktop images it's
  handled by the growroot-almost service and this is only capable of
  being inhibited by touching /etc/growroot-grown. It should be possible
  to inhibit this behaviour from the boot partition only which, being
  FAT, can be mounted from other OS'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-raspi-settings/+bug/2065408/+subscriptions