On 11/01/2013 06:44 PM, Richard Purdie wrote:
On Tue, 2013-10-29 at 20:33 +0800, ChenQi wrote:
ping
Any comment on this one?
Yes, shouldn't the boot ordering be tweaked to ensure the tmpfs is
available rather than force mounting it within this init script? This
looks like a hack around the pro
On Tue, 2013-10-29 at 20:33 +0800, ChenQi wrote:
> ping
>
> Any comment on this one?
Yes, shouldn't the boot ordering be tweaked to ensure the tmpfs is
available rather than force mounting it within this init script? This
looks like a hack around the problem rather than fixing a real issue.
The
ping
Any comment on this one?
Best Regards,
Chen Qi
On 09/26/2013 06:02 PM, qi.c...@windriver.com wrote:
From: Chen Qi
Previously, our system had no boot log even if the bootlogd daemon was
started correctly. The root cause is that the log file doesn't exist
when starting the bootlogd.
Add
ping
On 09/26/2013 06:02 PM, qi.c...@windriver.com wrote:
From: Chen Qi
Previously, our system had no boot log even if the bootlogd daemon was
started correctly. The root cause is that the log file doesn't exist
when starting the bootlogd.
Add '-c' option to bootlogd so that it will create th
On 09/26/2013 06:50 PM, Enrico Scholz wrote:
writes:
Besides, we need to make sure that tmpfs has been mounted. Otherwise,
the boot log will still be missing.
...
case "$ACTION" in
start)
+ mount -a -t tmpfs 2>/dev/null
This will mount filesystems out-of-order. E.g. it
writes:
> Besides, we need to make sure that tmpfs has been mounted. Otherwise,
> the boot log will still be missing.
> ...
> case "$ACTION" in
> start)
> + mount -a -t tmpfs 2>/dev/null
This will mount filesystems out-of-order. E.g. it will break an /etc/fstab
with
| /dev/mm
From: Chen Qi
Previously, our system had no boot log even if the bootlogd daemon was
started correctly. The root cause is that the log file doesn't exist
when starting the bootlogd.
Add '-c' option to bootlogd so that it will create the boot log if
it doesn't exist.
Besides, we need to make sur
