UBports Robot Logo UBports Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    Partition layout

    Scheduled Pinned Locked Moved UT for Raspberry Pi
    5 Posts 2 Posters 1.5k Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
      Reply
      • Reply as topic
      Log in to reply
      This topic has been deleted. Only users with topic management privileges can see it.
      • joniusJ Offline
        jonius
        last edited by

        Afaik the partition layout on UT phones varies from phone to phone. We need to clarify, which partitions do we need or should have on the Raspberry Ubuntu Touch?

        1 Reply Last reply Reply Quote 0
        • flohackF Offline
          flohack
          last edited by

          @jonius said in Partition layout:

          varies from phone to phone. We need to clarify, which partitions do we need or should have on the Raspberry Ubuntu Touch?

          You only need a data partition that is recognized and mounted on startup. Inside, a folder named data will be searched, and there will be system.img and ubuntu.img IMHO. So you dont need a complex partition layout at all πŸ˜‰

          My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

          joniusJ 1 Reply Last reply Reply Quote 0
          • flohackF Offline
            flohack
            last edited by

            Means: All mounts in UT are bind-mounts and mounts of disk images.

            My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

            1 Reply Last reply Reply Quote 0
            • joniusJ Offline
              jonius @flohack
              last edited by

              @flohack additionally to the root partition, running the kernel? So we would have two partitions, an ubuntu root / and a /mnt/data? What are system.img and ubuntu.img for? Where does the read-only UT rootfs live (one /?) and where the writable home?

              1 Reply Last reply Reply Quote 0
              • flohackF Offline
                flohack
                last edited by

                @jonius Ok let me explain with a screenshot - this one is from the old boot layout, where android system is inside ubuntu.img and system.img is a hardlink to ubuntu.img, so please forgive the sizes of the files. This WILL change with Halium):
                partition BOOT: Contains initrd system with kernel and the usual initrd helpers

                0_1528024151564_5187ab83-cd25-4f04-85c8-4557a2dd807c-grafik.png
                partition DATA: ext4 formatted, contains:
                on /data:

                • ubuntu.img is the read-only root filesystem
                • system.img contains the Android LXC container. This will not be needed at all for Raspberry
                • folder user-data: Contains all user data from the home dir
                • folder system-data:Contains system settings like WiFi, network, future printing, etc.

                So, if you manage to boot the raspberry image, your bootloader basically needs to follow the steps of https://github.com/ubports/ubports-boot and its initrd workflow. Specifically, see this init: https://github.com/ubports/ubports-boot/blob/master/initramfs/init

                BR

                My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                1 Reply Last reply Reply Quote 2
                • First post
                  Last post