Hi Johnny I am sending you a copy of this message in CC in case you are not subscribed to the mailing list. However, can you please ensure that your reply goes to the mailing list, not just to me. Because this is a community discussion, not a private one. So I have copied your private reply below here so that the community does not miss part of the conversation. My reply is at the bottom of this message.
On Tue, 25 Oct 2022 at 06:36, Johnny de Villiers <devilliersjoh...@gmail.com> wrote: > > Hi David > > Thank you for the fast reply... Attempted to do just that but instead of > fdisk was using gparted and the system did just what you said... IT HUNG > ITSELF ;-P > > However when I found this to be the case I went ahead and reflashed, booted > and then after all was done attempted the resizing... however upon the next > reboot the partition was resized again!? Then while describing this to a > friend an idea popped up, the script was alway looking for the end of the > disk, right?! > > The script is looking for the end so why not swap the second and third > partitions places? Attempted it and... ... ... what would you know it worked! > Not ideal I know but. You say that the resize function does not exist outside > of "initrd", what are the chances that you guys would be able to add a > function/variable to prevent the resize? In raspbian this is achieved by > removing the init function on the cmdline.txt and in ubuntu by adding a > > growpart: > mode: disabled > > to the usrconfig that gets parsed to the cloud-init?! Or should I just have a > look into removing the " /scripts/local-bottom/rpi-resizerootfs " before > boot? > > Looking forward to hearing back from you! I am just a user of the image, not a developer. I just shared with you some experience that I had when using the image. If you want to have a conversation regarding changes to the image, you will need to contact the developer/team producing the image. I don't have any more information about this than I included in my previous message.
