<div dir="ltr">I once used update-initramfs under ubuntu, building ramdisk to boot from remote iscsi disk.<br> <br></div><div class="gmail_extra"><br clear="all"><div><div dir="ltr">-----------------------------------------------------------------<br>
韦远科 <div>3479<br><div>中国科学院 计算机网络信息中心</div><div style="text-align:-webkit-left"><br></div><div></div><div></div><div></div><div></div><div></div><div></div><div></div></div></div></div>
<br><br><div class="gmail_quote">On Tue, Jul 8, 2014 at 12:15 PM, Adam Young <span dir="ltr"><<a href="mailto:ayoung@redhat.com" target="_blank">ayoung@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><div class="">
<div>On 07/07/2014 01:16 PM, Victor Lowther
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">As one of the original authors of dracut, I would
love to see it being used to build initramfs images for TripleO.
dracut is flexible, works across a wide variety of distros, and
removes the need to have special-purpose toolchains and packages
for use by the initramfs.</div>
<div class="gmail_extra"><br>
</div>
</blockquote></div>
Dracut rocks, and we can use it to get support for Shared nothing
diskless boot;<br>
<br>
<a href="http://adam.younglogic.com/2012/03/shared-nothing-diskless-boot/" target="_blank">http://adam.younglogic.com/2012/03/shared-nothing-diskless-boot/</a><div><div class="h5"><br>
<br>
<br>
<br>
<blockquote type="cite">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Jul 3, 2014 at 10:12 PM, Ben
Nemec <span dir="ltr"><<a href="mailto:openstack@nemebean.com" target="_blank">openstack@nemebean.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I've
recently been looking into using dracut to build the<br>
deploy-ramdisks that we use for TripleO. There are a few
reasons for<br>
this: 1) dracut is a fairly standard way to generate a
ramdisk, so users<br>
are more likely to know how to debug problems with it. 2)
If we build<br>
with dracut, we get a lot of the udev/net/etc stuff that
we're currently<br>
doing manually for free. 3) (aka the self-serving one ;-)
RHEL 7<br>
doesn't include busybox, so we can't currently build
ramdisks on that<br>
distribution using the existing ramdisk element.<br>
<br>
For the RHEL issue, this could just be an alternate way to
build<br>
ramdisks, but given some of the other benefits I mentioned
above I<br>
wonder if it would make sense to look at completely
replacing the<br>
existing element. From my investigation thus far, I think
dracut can<br>
accommodate all of the functionality in the existing ramdisk
element,<br>
and it looks to be available on all of our supported
distros.<br>
<br>
So that's my pitch in favor of using dracut for ramdisks.
Any thoughts?<br>
Thanks.<br>
<br>
<a href="https://dracut.wiki.kernel.org/index.php/Main_Page" target="_blank">https://dracut.wiki.kernel.org/index.php/Main_Page</a><br>
<br>
-Ben<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
OpenStack-dev mailing list
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>