From: mwg@mwg.dp.ua   
      
   Dear Everyone,   
      
   Looking into https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+   
   ource/initramfs-tools/tree/scripts/local?h=ubuntu/noble ,   
   we can see logic added by Ubuntu in lines 220..268 for handling loop= option   
   in the kernel cmdline,   
   in which case root= specifies the filesystem containing the loop image,   
   and loop=path/rootfs.loop specifies the path of an image file to be mounted   
   with -o loop as a root filesystem.   
   Corresponding logic we see also in https://git.launchpad.net/~ub   
   ntu-core-dev/ubuntu/+source/initramfs-tools/tree/init?h=ubuntu/noble   
   where global variables are filled from cmdline in lines 134..145.   
      
   This logic greatly simplifies the creation of a bootable Linux instance as a   
   set of additional files and folders   
   coexisting with other data on a removable FAT32 volume (like a USB storage   
   drive), not requiring and kind of data removal or storage reformatting.   
      
   Looking into https://salsa.debian.org/kernel-team/initramfs-tool   
   /-/blob/v0.148.3/scripts/local and   
   https://salsa.debian.org/kernel-team/initramfs-tools/-/blob/v0.148.3/init , I   
   don't see any equivalent logic in Debian Trixie version,   
   despite it having bigger version number than that of Ubuntu Noble (0.142).   
      
   Can anyone please propose, how the same logic could be implemented within   
   Debian Trixie and its initramfs-tools ?   
   Probably there could be some kind of drop-in script for top or premount stage ?   
   I would greatly appreciate any samples of such script[s] from you for my   
   adoption and customization.   
      
   Thanks in advance for your help.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)