[RESEND for ML] wic: imager/direct: passno is set to 0 for all entries in the fstab

["Claudius Heine" <ch@denx.de>]

Hi,

I looked into periodic file system checks for ext* partitions, in order 
to increase robustness for systems that use those file systems and was 
surprised that the fstab that wic generates that `0` hard coded as the 
passno parameter [1]. This prevents for instance systemd-fsck@(8) [2] 
from running checks on those file systems.

It seems that wic/mic generated a fstab with passno=0 from the beginning 
[3]. What is the reason for that? Was it a conscious decision to do 
that, or just copy&paste for a different project?

How would a way forward look like? Should a patch that changes passno 
from 0 to 2 be enough, or do we rather have this parameter configurable 
somehow?

regards,
Claudius Heine

[1] 
https://git.openembedded.org/openembedded-core/tree/scripts/lib/wic/plugins/imager/direct.py?id=a59c246be05ca284fa27df87b5db09a70f527cc2#n141
[2] 
https://manpages.debian.org/stretch/systemd/systemd-fsck@.service.8.en.html
[3] 
https://git.openembedded.org/openembedded-core/tree/scripts/lib/mic/imager/direct.py?id=f87acc5e59d3c2c39ff171b5557977dab4c8f4a6#n110

-- 
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de

            PGP key: 6FF2 E59F 00C6 BC28 31D8 64C1 1173 CB19 9808 B153
                              Keyserver: hkp://pool.sks-keyservers.net