Bài đăng

make config vs oldconfig vs defconfig vs menuconfig vs savedefconfig

make config: Options are prompted one after another. All options need to be answered make menuconfig: Menu-driven user interface make  defconfig : Creates a ".config" file with default config from the ARCH defconfig make oldconfig: Reads the existing .config file and prompts the user for options in the current kernel source not found in the .config file. Useful when you are moving the existing kernel configuration to a new kernel version. make savedefconfig: Creates a 'defconfig' in the current directory. Used when you do a 'make defconfig' and modified few configuration changes Ref: http://embeddedguruji.blogspot.com/2019/01/make-config-vs-oldconfig-vs-defconfig.html?m=0

How to mount Linux image

Without kpartx Y ou can mount each partition individually by specifying an   offset   in the   mount   command. First examine the partitions in the image file and determine the offset by using  fdisk : $ fdisk -u -l rpi_image280914 Disk rpi_image280914: 16.0 GB, 16012804096 bytes 255 heads, 63 sectors/track, 1946 cylinders, total 31275008 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x000cdac7 Device Boot Start End Blocks Id System rpi_image280914p1 * 2048 514047 256000 c W95 FAT32 (LBA) rpi_image280914p2 540672 31242239 15350784 83 Linux Take the  Start  sector of the partition you want and multiply that value by the  Units  size. So if you want the second partition you'll get  540672 * 512 = 276824064 . Now create a folder and mount the partition: mkdir rpi_partition2 sudo mount -o lo