mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Warren Togami <wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Dracut questions
Date: Fri, 19 Dec 2008 00:16:31 -0500	[thread overview]
Message-ID: <494B2E2F.5090203@redhat.com> (raw)

https://fedoraproject.org/wiki/Initrdrewrite
> Probe at runtime instead of buildtime - Include all drivers, not just
> the drivers necessary for the hardware being run. (For storage, the
> common ones will be built-in to the kernel anyway)

This means include all storage drivers and firmware for the storage drivers?

Does this also mean we only add network drivers if the initrd is 
explicitly built for netboot?

How do we plan on dealing with the location of various standard 
utilities being different on other Linux distributions?

Fedora		Debian
/sbin/lspci	/usr/bin/lspci
/sbin/lsmod	/bin/lsmod
(just off the top of my head)

Perhaps use "which" to find it?  But then how do we choose its 
destination path in the initrd chroot if the distributions disagree on 
where they expect a command to go?  Will they disagree?

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:[~2008-12-19  5:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-19  5:16 Warren Togami [this message]
     [not found] ` <494B2E2F.5090203-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2008-12-19  8:03   ` Dracut questions Philippe Seewer
2008-12-19 16:46   ` Jeremy Katz

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=494B2E2F.5090203@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox