| Summary: | Missing /etc/init.d directory while using jffs2 images | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Runtime] Installation | Reporter: | Holger Adams <Holger.Adams> | ||||||
| Component: | Installation | Assignee: | Saul Wold <sgw> | ||||||
| Status: | RESOLVED NOTABUG | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | Medium | CC: | kevin.tian, Qi.Chen, richard.purdie, sgw | ||||||
| Version: | 1.3 | ||||||||
| Target Milestone: | 1.4 | ||||||||
| Hardware: | Other | ||||||||
| OS: | arm | ||||||||
| Whiteboard: | |||||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||||
| Verified: | Documentation change: | --- | |||||||
| Attachments: |
|
||||||||
Created attachment 1024 [details]
BSP file being used
From this line "lrwxrwxrwx 1 root root 22 Jan 1 1970 S99rmnologin.sh -> ../init.d/rmnologin.sh", we can see that the initscripts package has been installed. It's strange that the /etc/init.d is missing. Is the initscripts package installed or not? For a quick test, I just built a default core-image-minimal image with distro set to 'poky' and machine set to 'qemux86'. The /etc/init.d directory was contained in the jff2 image. This looks like something is wrong with the mtdutils themselves or the creation of the jffs2 file. Did the jffs2 file run out of space? Have you checked the mtdutils upstream for reports of this kind of bug? (the fact the tar file is correct suggests that problem is in mtdutils) Hello Richard, Hello Everybody, thanks for your hint regarding running out of flash. This leaded us to the right direction for solving this problem. We missed some memory ranges using the 'erase' command while cleaning the flash, so jffs2 got confused and showed some real strange behavior during the boot and mounting progress. Everything works fine now :-) Thanks! Holger |
Created attachment 1023 [details] local.conf being used. Problem: Lots of symlinks (as expecting) are leading to /etc/init.d root@(none):/etc/rc5.d# ls -lah drwxr-xr-x 2 root root 0 Jan 1 1970 . drwxr-xr-x 17 root root 0 Jan 18 14:57 .. lrwxrwxrwx 1 root root 18 Jan 1 1970 S10dropbear -> ../init.d/dropbear lrwxrwxrwx 1 root root 20 Jan 1 1970 S20hwclock.sh -> ../init.d/hwclock.sh lrwxrwxrwx 1 root root 16 Jan 1 1970 S20syslog -> ../init.d/syslog lrwxrwxrwx 1 root root 22 Jan 1 1970 S99rmnologin.sh -> ../init.d/rmnologin.sh lrwxrwxrwx 1 root root 23 Jan 1 1970 S99stop-bootlogd -> ../init.d/stop-bootlogd But that directory doesn't exist: root@(none):/etc# cd init.d -sh: cd: can't cd to init.d The directory - including all required files - do exist in the created .tar file during the build process (in parallel). How to reproduce: 1. # source oe-init-build-env test 2. # bitbake core-image-minimal 3. Flash Kernel and jffs2 image 4. Boot I also tried poky/poky-bleeding and poky-1.4_M3.rc1, no change in the observed behavior. Best Regards, Holger