mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Seewer Philippe <philippe.seewer-omB+W0Dpw2o@public.gmane.org>
To: Warren Togami <wtogami-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: initramfs <initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Dracut generation modes
Date: Fri, 29 May 2009 16:30:32 +0200	[thread overview]
Message-ID: <4A1FF188.5070703@bfh.ch> (raw)
In-Reply-To: <4A1EDEBF.4080009-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

Warren Togami wrote:
> So this might not have been clear earlier, but stating it on the list to 
> be sure everyone is on the same page.
> 
> * Default Dracut
> Dracut without any parameters should generate an initrd image capable of 
> booting a generic machine.  This means it must not detect anything of 
> the current running system to determine what to install in the image. 
> This includes stuff in /proc, /sys, lsmod, /proc/mounts and possibly more.

Yes

> 
> By necessity, stuff in the filesystem are usable to dracut in 
> determining what to install in the image.

...Dracut has to get it's tools from somewhere...

> 
> * --hostonly mode
> Host only mode is permitted to use runtime detection to generate an 
> image capable of booting the current system.  What exactly does this 
> mean?  Is this primarily for smaller sizes by avoiding irrelevant modules?

Yes. And possibly more optimization. I'm thinking "apt-get update 
linux-image" which automatically rebuilds the initrd...

> * (Some other generation mode)
> Perhaps we need more generation modes for other purposes.  One likely 
> case is where you need to generate a machine specific image for a 
> non-local system.  A combination of command line options and/or .conf 
> file would define the dracut image for a non-local system.  This might 
> be necessary for cases like:
> 
> - netboot initrd needs to be as small as possible for resource 
> constraint reasons
> - embedded systems with resource constraints

That's what dracutmodules in the configfile is for.

> - certificates or passwords for iscsi or kerberized nfs

I'd say either via injection or a site-specific add-on module.

--
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

      parent reply	other threads:[~2009-05-29 14:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-28 18:58 Dracut generation modes Warren Togami
     [not found] ` <4A1EDEBF.4080009-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2009-05-29 12:12   ` Victor Lowther
2009-05-29 14:21   ` Harald Hoyer
2009-05-29 14:30   ` Seewer Philippe [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=4A1FF188.5070703@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