mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Andrey Borzenkov <arvidjaar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] i18n: fix udev error due to empty rules file
Date: Wed, 10 Nov 2010 15:22:51 +0100	[thread overview]
Message-ID: <4CDAAABB.4090403@redhat.com> (raw)
In-Reply-To: <1288974698-21387-1-git-send-email-arvidjaar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

On 11/05/2010 05:31 PM, Andrey Borzenkov wrote:
> Empty rule file is causing udev error:
>
> dracut: udevd[99]: can not read '/etc/udev/rules.d/10-console.rules'
>
> Remove file completely instead of truncating it.
>
> Signed-off-by: Andrey Borzenkov<arvidjaar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>
> ---
>   modules.d/10i18n/parse-i18n.sh |    2 +-
>   1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/modules.d/10i18n/parse-i18n.sh b/modules.d/10i18n/parse-i18n.sh
> index 0a58cc2..8f7f8f8 100755
> --- a/modules.d/10i18n/parse-i18n.sh
> +++ b/modules.d/10i18n/parse-i18n.sh
> @@ -35,5 +35,5 @@ if [ -e /dev/tty0 ]; then
>       # if the device already exists, yes
>       # clear the udev rules and run it
>       /lib/udev/console_init /dev/tty0
> ->  /etc/udev/rules.d/10-console.rules
> +    rm /etc/udev/rules.d/10-console.rules
>   fi


http://dracut.git.sourceforge.net/git/gitweb.cgi?p=dracut/dracut;a=commitdiff;h=6545b9d7920cd4e09274b1d38d45c191e9991646

      parent reply	other threads:[~2010-11-10 14:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-05 16:31 [PATCH] i18n: fix udev error due to empty rules file Andrey Borzenkov
     [not found] ` <1288974698-21387-1-git-send-email-arvidjaar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-11-10 14:22   ` Harald Hoyer [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=4CDAAABB.4090403@redhat.com \
    --to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=arvidjaar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@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