mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: John Reiser <jreiser-Po6cBsTGB2ZWk0Htik3J/w@public.gmane.org>
To: Harald Hoyer <harald.hoyer-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: build initramfs: bad path in inst_rules when --local
Date: Fri, 16 Sep 2011 17:11:39 -0700	[thread overview]
Message-ID: <4E73E5BB.90208@bitwagon.com> (raw)

When dracut-013 --local, then inst_rules tests for a pathname such as
     [[ -f /etc/udev/rules.d//ext4/dracut/modules.d/10i18n/10-console.rules ]]
which obviously is bogus: there are two "root" there: /etc and /ext4
[The "/ext4/dracut" is where my --local versions live.]
Such a path never can exist, so something is wrong with the intent.

Analysis:
modules.d/10i18n/module-setup.sh: install_base() calls
        inst_rules ${moddir}/10-console.rules
Note no underscore '_' in "${moddir}".

moddir is a global variable that is set by dracut:
     for moddir in "$dracutbasedir/modules.d"/[0-9][0-9]*; do
When --local, then dracutbasedir is set in dracut:
    dracutbasedir="$(readlink -f ${0%/*})"

Based on both of these, then inst_rules() in dracut-functions does:
    for _rule in "$@"; do
        <<snip>>
        for r in /lib/udev/rules.d /etc/udev/rules.d; do
            if [[ -f $r/$_rule ]]; then
which leads to testing a pathname such as
     [[ -f /etc/udev/rules.d//ext4/dracut/modules.d/10i18n/10-console.rules ]]

-- 

             reply	other threads:[~2011-09-17  0:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-17  0:11 John Reiser [this message]
     [not found] ` <4E73E5BB.90208-Po6cBsTGB2ZWk0Htik3J/w@public.gmane.org>
2011-09-22 13:45   ` build initramfs: bad path in inst_rules when --local Harald Hoyer

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=4E73E5BB.90208@bitwagon.com \
    --to=jreiser-po6cbstgb2zwk0htik3j/w@public.gmane.org \
    --cc=harald.hoyer-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