Re: [OE-core] [PATCH] classes/npm: replace cache clear with cache clean --force

Hi, You wrote: > 2018-02-05 16:55 keltezéssel, Matthijs Vader írta: > > Hi, > > > > 2018-02-05 15:07, zboszor wrote: > >> I have already sent this patch (although a little extended) last week: > >> http://lists.openembedded.org/pipermail/openembedd

Re: [OE-core] [PATCH] classes/npm: replace cache clear with cache clean --force

Hi, 2018-02-05 15:07, zboszor wrote: > I have already sent this patch (although a little extended) last week: > http://lists.openembedded.org/pipermail/openembedded-core/2018- > February/147071.html Thanks! The second patch you sent in with that actually solved some other problems I was having a

[OE-core] udev/mount.sh: use lazy umount

Hi, umount will fail if there are processes accessing files at the device, use lazy umount to avoid this problem. I found this patch [1] a long long time ago, but don't see it in master now. Any reason why it was not accepted? Is there any harm in using lazy umount? I know that it is not a 100

Re: [OE-core] wic wks: data partition only mounted on second boot?

> 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) re

[OE-core] wic wks: data partition only mounted on second boot?

Hi, I have my wks file like this: part /boot --source bootimg-partition --ondisk mmcblk0 --fstype=vfat --label boot --active --align 4 --size 16 part / --source rootfs --ondisk mmcblk0 --fstype=ext4 --label root --align 4 part /data --ondisk mmcblk0 --size 100M --fstype=ext4 --label data --alig