From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Minfei Huang <mhuang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Subject: Re: [PATCH] Replace the (in)dependency code to dracut-init.sh and dracut-functions.sh
Date: Wed, 2 Sep 2015 12:26:52 +0200 [thread overview]
Message-ID: <55E6CEEC.1040809@redhat.com> (raw)
In-Reply-To: <1438141091-30225-1-git-send-email-mhuang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
On 29.07.2015 05:38, Minfei Huang wrote:
> From previous reconstruction, dracut will put the dependency code into
> dracut-init.sh, and independency code to dracut-functions.sh. Then any
> script can source the public dracut-function.sh script.
>
> There are still a lot of errors when dracut-functions.sh is sourced in
> third-part script. So this patch try to move the dependency code from
> dracut-functions.sh to dracut-init.sh.
>
> Here are some sorts of errors about the dependency.
>
> logger: unknown facility name: .
> /usr/lib/dracut/dracut-logger.sh: line 339: ((: 4 <= : syntax error: operand expected (error token is "<= ")
> logger: unknown facility name: .
> /usr/lib/dracut/dracut-logger.sh: line 339: ((: 4 <= : syntax error: operand expected (error token is "<= ")
> logger: unknown facility name: .
>
What functions do you need? maybe we can source them out instead.
next prev parent reply other threads:[~2015-09-02 10:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 3:38 [PATCH] Replace the (in)dependency code to dracut-init.sh and dracut-functions.sh Minfei Huang
[not found] ` <1438141091-30225-1-git-send-email-mhuang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-07-29 4:05 ` Dracut GitHub Import Bot
2015-09-02 10:26 ` Harald Hoyer [this message]
[not found] ` <55E6CEEC.1040809-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-09-04 13:02 ` Minfei Huang
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=55E6CEEC.1040809@redhat.com \
--to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mhuang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.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