Add GT-N5100 /proc/mounts with the Replicant 6.0 0003 image

Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>

2 files changed, 76 insertions, 0 deletions

diff --git a/devices/mounts/GT-N5100/replicant-6.0-0003/mounts b/devices/mounts/GT-N5100/replicant-6.0-0003/mounts
new file mode 100644
index 0000000..fa90267
--- /dev/null
+++ b/devices/mounts/GT-N5100/replicant-6.0-0003/mounts
@@ -0,0 +1,20 @@
+rootfs / rootfs ro,seclabel,relatime 0 0
+tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
+devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
+proc /proc proc rw,relatime 0 0
+sysfs /sys sysfs rw,seclabel,relatime 0 0
+selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
+/sys/kernel/debug /sys/kernel/debug debugfs rw,seclabel,relatime 0 0
+none /acct cgroup rw,relatime,cpuacct 0 0
+none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
+tmpfs /mnt tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
+none /dev/cpuctl cgroup rw,relatime,cpu 0 0
+/dev/block/platform/dw_mmc/by-name/SYSTEM /system ext4 ro,seclabel,relatime,errors=panic,user_xattr,barrier=1,data=ordered 0 0
+/dev/block/platform/dw_mmc/by-name/EFS /efs ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
+/dev/block/platform/dw_mmc/by-name/CACHE /cache ext4 rw,seclabel,nosuid,nodev,noatime,errors=panic,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
+/dev/block/platform/dw_mmc/by-name/USERDATA /data ext4 rw,seclabel,nosuid,nodev,noatime,errors=panic,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
+tmpfs /storage tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
+/dev/fuse /mnt/runtime/default/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
+/dev/fuse /storage/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
+/dev/fuse /mnt/runtime/read/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
+/dev/fuse /mnt/runtime/write/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
diff --git a/devices/mounts/README.txt b/devices/mounts/README.txt
new file mode 100644
index 0000000..7066db1
--- /dev/null
+++ b/devices/mounts/README.txt
@@ -0,0 +1,56 @@
+== Description ==
+There is already some information about the various partitions present on the
+devices. For instance, this repository already has the GPT and the PIT partition
+tables for various devices.
+
+However that information is incomplete as we cannot easily match the partition
+name (like BOOT) with its usage. For instance with 'BOOT', on some device it
+holds the bootloader, while on other it holds the boot.img.
+
+In some cases, that information is crucial, for instance writing a file that is
+small enough (like a version of u-boot that is loaded by the stock bootloader)
+to the bootloader partition instead of the boot.img partition can result in a
+broken device. Repairing it can be very complicated in some cases and beyond
+the skills of even some very technical people.
+
+In addition, it's interesting to have that information just to understand what
+each partition is supposed to contain, for instance for freedom, privacy and
+security evaluation or just to understand better how the device works.
+
+Having information on what partition are mounted, and if so where they are
+mounted, on various Android or GNU/Linux distributions can be really
+interesting. For instance if on a given distribution, a partition is not used
+by the bootloader nor mounted and that it only contains a huge number of 0x00,
+then we can assume that it's not used by the system, unless we later find some
+evidences of the contrary.
+
+As fstab files can be scattered around the distributions source code (which is
+not always available in the case of the stock distributions) and knowing what is
+really mounted for real once the device is booted is interesting, it's a good
+idea to also store information about mounts.
+
+To do that, /proc/mount can simply be used as its format is most probably
+standardized in the upstream Linux kernel, and that vendors kernels is not very
+likely to change it, whereas if we used the output of the mount command, the
+format may depend on what implementation is being used (toolbox, toybox,
+busybox, util-linux, etc), its version or even compilation options.
+
+== How to get the mount data ==
+
+To get the mount data, it's best to be root to be completely sure that all the
+mount information is displayed and that none is hidden because of lacking
+permissions. Once that is done, you can simply copy the /proc/mounts from your
+device in this repository.
+
+For instance, you can do it like that:
+    $ adb root
+    $ adb pull /proc/mounts ./
+
+For these commands to work in Replicant, you also need to get adb inside
+Replicant first, and enable root for adb. The Replicant wiki has more
+information on how to do that.
+
+It is also a good idea to also remove any external microSD before running that
+command as otherwise it could include information that is specific to the
+specific microSD and/or filesystem you use. For instance, for FAT partitioned
+filesystem, it will most likely include the FAT partition UUID.