All of lore.kernel.org
 help / color / mirror / Atom feed
From: Warren Togami <wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: initramfs <initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Files copied from generating system
Date: Thu, 18 Jun 2009 16:25:46 -0400	[thread overview]
Message-ID: <4A3AA2CA.7000507@redhat.com> (raw)

We can't really predict the behavior of or support initrd's that end up 
with whatever customized config files are copied from the system, but 
options for dealing with this problem are not clear.  Any ideas?

modules.d/95nfs/install:
> /etc/nsswitch.conf
> /etc/idmapd.conf

These could possibly be edited and cause NFS to behave unexpectedly in 
the initrd.

(Harald and I agree we should write the needed user to /etc/passwd 
during dracut generation instead of copying the /etc/passwd.  I'm 
working on this.)

modules.d/90kernel-modules/install:
> [ -f /etc/modprobe.conf ] && dracut_install /etc/modprobe.conf
> dracut_install $(find /etc/modprobe.d/ -type f -name '*.conf')

Some of these are shipped by the distribution and important, but others 
can be edited and cause the initrd to behave differently.

modules.d/90mdraid/install:
> #!/bin/bash
> dracut_install mdadm
> inst /etc/passwd
> inst /etc/group

With agreement from Harald we're writing these during dracut generation 
instead of copying.

> instmods =drivers/md
> inst_rules "$moddir/61-mdadm.rules"
> [ -f /etc/mdadm/mdadm.conf ] && inst /etc/mdadm/mdadm.conf /etc/mdadm.conf
> [ -f /etc/mdadm.conf ] && inst /etc/mdadm.conf
> if [ -x  /sbin/mdmon ] ; then
>     dracut_install mdmon
>     inst_hook pre-pivot 30 "$moddir/mdmon-pre-pivot.sh"
> fi

mdadm.conf is another file that can influence the behavior of a system. 
  Shouldn't this be --hostonly?

Is dracut mdraid module usable at all without mdadm.conf?  I've used 
many RAID systems without mdadm.conf, although I don't understand why 
some systems seemingly need it while others don't.

modules.d/95udev-rules/install:
> #!/bin/bash
> # FIXME: would be nice if we didn't have to know which rules to grab....
> # ultimately, /lib/initramfs/rules.d or somesuch which includes links/copies
> # of the rules we want so that we just copy those in would be best
> dracut_install udevd udevadm /lib*/udev/*_id /etc/udev/udev.conf /etc/group
> dracut_install basename
> inst_rules 50-udev-default.rules 60-persistent-storage.rules \
>     61-persistent-storage-edd.rules 80-drivers.rules 95-udev-late.rules
> #Some debian udev rules are named differently
> inst_rules 50-udev.rules 95-late.rules
>
> if ldd $(find_binary udevd) |grep -q /lib64/libc; then
>     dracut_install /lib64/libnss_files*
> else
>     dracut_install /lib/libnss_files*
> fi

udev.conf could be another source of unexpected behavior?

Warren Togami
wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2009-06-18 20:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-18 20:25 Warren Togami [this message]
     [not found] ` <4A3AA2CA.7000507-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-06-19  3:00   ` Files copied from generating system David Dillow

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=4A3AA2CA.7000507@redhat.com \
    --to=wtogami-h+wxahxf7alqt0dzr+alfa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.