> It creates the /data partition, and adds it to the .wic file, all fine. But on > the first boot it is not auto-mounted. From the boot log: > > > [ 1.898069] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data > mode. Opts: (null) > [ 1.906798] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. > [ 1.919446] devtmpfs: mounted > [ 1.923113] Freeing unused kernel memory: 264K (c069e000 - c06e0000) > version 2.88 booting > Starting udev > [ 2.535288] udevd[657]: starting version 182
Hi again, fixed and found it myself already. There is an error while mounting that partition on the first boot because the mount point (/data) doesn't exist yet. Then, later during first boot, some application creates it. Which explains why it does work on the second boot. Which brings me to a new question: Is there are reason for mountall.sh to put all errors into /dev/null? See: https://github.com/openembedded/openembedded-core/blob/master/meta/recipes-core/initscripts/initscripts-1.0/mountall.sh#L20 Or shall I send a -tiny- patch dropping that 2>/dev/null? Best, Matthijs -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
