Dockstar Debian boot errors

System: dockstar with readonly emdebian on NAND with kernel Linux debian 3.3.3-dockstar-shyd and wheezy

I upgraded from "Linux debian 2.6.32-dockstar" to "Linux debian 3.3.3-dockstar-shyd" following the instructions from http://dev.shyd.de/2012/04/kernel-3-3-3-ready-to-use. After some struggle I am now able to log into Debian. However, I still have a few errors that I am unable to solve or not certain what would be the best solution. Any help would be helpful.

1)

Filesystem mounted on /var/run; setting up compatibility bind mount. ... (warning).
Please remove this mount from /etc/fstab; it is no longer needed, and it is preventing completion of the transition to /run. ... (warning).
Filesystem mounted on /var/lock; setting up compatibility bind mount. ... (warning).
Please remove this mount from /etc/fstab; it is no longer needed, and it is preventing completion of the transition to /run/lock. ... (warning).

According to http://askubuntu.com/questions/57297/why-has-var-run-been-migrated-to-run, /run replaces several existing locations described in the Filesystem Hierarchy Standard. So the error msgs make sense, but I can't seem to figure out how to solve it. fstab does not have /var/run and /var/lock in it. Earlier when I was trying to solve some other boot problem, I remember seeing a script that loop through a directory and mount everything in there as tempfs, but I can't seem to find this script again. Does anyone know where the script is?

2)

/sbin/dhclient-script: line 49: /etc/resolv.conf.dhclient-new: Read-only file system
chown: cannot access `/etc/resolv.conf.dhclient-new': No such file or directory
chmod: cannot access `/etc/resolv.conf.dhclient-new': No such file or directory
mv: cannot stat `/etc/resolv.conf.dhclient-new': No such file or directory

Root fs is read only and DHCP is still working. Would the best way to solve this problem be changing /sbin/dhclient-script so that it does not try to write to disk or would the best way be putting /etc/resolv.conf.dhclient-new on tempfs?

3)

/etc/rc.local: 14: /etc/rc.local: cannot create /sys/class/leds/dockstar:orange:health/trigger: Directory nonexistent
startpar: service(s) returned failure: rc.local ... failed!

Same thing here, what is the best way: disable LED or putting /sys/class/leds/ on tempfs?

Thanks

If you want, you can try the wide kernel that I have posted: http://forum.doozan.com/read.php?2,7676 ... tested and working on about 5 different machines.

=====================================================

• davy's Github Repo's rescue-dg

davygravy Wrote:
-------------------------------------------------------
> If you want, you can try the wide kernel that I
> have posted:
> http://forum.doozan.com/read.php?2,7676 ...
> tested and working on about 5 different machines.


Maybe I will downgrade to 3.3.2 as you suggested. But I do not truly believe the errors I described are part of 3.3.3. I think these error exists because of the difference between 2.6.32-dockstar and whatever I am upgrading to. Unless you did something specific to solve these problem, did you? Sorry if the question doesn't make sense to you but I don't actually know what is in the kernel.

You'll need a newer U-Boot for the newer kernels, BTW.
http://forum.doozan.com/read.php?3,6965

=====================================================

• davy's Github Repo's rescue-dg

davygravy Wrote:
-------------------------------------------------------
> You'll need a newer U-Boot for the newer kernels,
> BTW.
> http://forum.doozan.com/read.php?3,6965

Thanks, I'm already using your u-boot.

I fixed #3:

-------------------------
LED
-------------------------
/etc/rc.local: 14: /etc/rc.local: cannot create /sys/class/leds/dockstar:orange:health/trigger: Directory nonexistent
startpar: service(s) returned failure: rc.local ... failed!

Fix
mount / -o remount,rw
nano /sbin/init-ro
Replace
echo none > /sys/class/leds/dockstar:orange:health/trigger
with
echo none > /sys/class/leds/dockstar:orange:misc/trigger