From: Philippe Seewer <philippe.seewer-omB+W0Dpw2o@public.gmane.org>
To: wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Dracut questions
Date: Fri, 19 Dec 2008 09:03:03 +0100 [thread overview]
Message-ID: <494B5537.7020307@bfh.ch> (raw)
In-Reply-To: <494B2E2F.5090203-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Warren Togami wrote:
> 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?
From the description I'd guess so. Although I'd like to see both
options. A full one with all drivers for generic boots and another one
tailored for specific systems and fast booting (and maybe small memory
footprint).
>
> Does this also mean we only add network drivers if the initrd is
> explicitly built for netboot?
Makes sense, otherwise the image gets huge! My current 2.6.27 netboot
initrd reaches almost 8Megs...
>
> 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?
Maybe the LSB might help a bit. It doesn't say anything about where the
utilities actually have to go, but read this:
[quote]
16.4. Path For System Administration Utilities
Certain utilities used for system administration (and other privileged
commands) may be stored in /sbin, /usr/sbin, and /usr/local/sbin.
Applications requiring to use commands identified as system
administration utilities should add these directories to their PATH. By
default, as described in ISO POSIX (2003), standard utilities shall be
found on the PATH returned by getconf PATH (or command -p getconf PATH
to be guaranteed to invoke the correct version of getconf).
[/quote]
Cheers,
Philippe
--
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
next prev parent reply other threads:[~2008-12-19 8:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-19 5:16 Dracut questions Warren Togami
[not found] ` <494B2E2F.5090203-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2008-12-19 8:03 ` Philippe Seewer [this message]
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=494B5537.7020307@bfh.ch \
--to=philippe.seewer-omb+w0dpw2o@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=wtogami-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