Re: [yocto] Busybox hwclock.sh initscript issues

2015-09-20 Thread Craig McQueen
On 2015-09-18 21:31, Gary Thomas wrote: > > On 2015-09-17 23:28, Craig McQueen wrote: > > I'm using Yocto dizzy. I've found a couple of issues with the Busybox > hwclock.sh initscript. > > > > 1) The script checks that /sbin/hwclock exists at the start. But after that > > it > runs hwclock withou

Re: [yocto] Busybox hwclock.sh initscript issues

2015-09-18 Thread Gary Thomas
On 2015-09-17 23:28, Craig McQueen wrote: I'm using Yocto dizzy. I've found a couple of issues with the Busybox hwclock.sh initscript. 1) The script checks that /sbin/hwclock exists at the start. But after that it runs hwclock without an explicit /sbin/hwclock path. So it only works if /sbin/

[yocto] Busybox hwclock.sh initscript issues

2015-09-17 Thread Craig McQueen
I'm using Yocto dizzy. I've found a couple of issues with the Busybox hwclock.sh initscript. 1) The script checks that /sbin/hwclock exists at the start. But after that it runs hwclock without an explicit /sbin/hwclock path. So it only works if /sbin/ is in the PATH. Thus it doesn't run properl