Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: initscripts + fsck.busybox problem
Date: Wed, 25 Mar 2015 09:11:32 -0500	[thread overview]
Message-ID: <5512C214.4090309@windriver.com> (raw)
In-Reply-To: <20150325134027.GA19408@saldanha.aker.com.br>

On 3/25/15 8:40 AM, Hugo Vasconcelos Saldanha wrote:
> Hi all,
> 
> Everytime my image boots, the following error message is printed:
> 
> fsck (busybox 1.23.1, 2015-03-14 10:13:03 BRT)
> 
> Invalid non-numeric argument to -C ("-y")
> 
> It seems that checkroot.sh script from initscripts package is
> calling the command "fsck -C -y". checkfs.sh script, apparently not
> installed by default, does the same. The problem is that busybox's fsck
> needs an argument to -C option, which is not needed by util-linux and
> e2fsprogs' versions of the tool.
> 
> Possible approaches that I can think of:
> 
> 1) Fixing the scripts, maybe removing references to -C option
> altogether.
> 
> 2) Placing a RDEPENDS in initscripts' recipe.
> 
> What do you think about it?
> 

From the util-linux man page on the -C option:

GUI front-ends may specify  a
              file  descriptor  fd, in which case the progress bar information
              will be sent to that file descriptor.

So the fd option is supposed to be optional.  I'd recommend in this case the bug
is with busybox, and someone submit a patch to make the fd optional in busybox.
 (default going to stdout)

--Mark


      reply	other threads:[~2015-03-25 14:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25 13:40 initscripts + fsck.busybox problem Hugo Vasconcelos Saldanha
2015-03-25 14:11 ` Mark Hatle [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5512C214.4090309@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox