From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Scott Olsen <olesen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: dmsquash-live-root + NFS?
Date: Wed, 09 Jun 2010 10:36:20 +0200 [thread overview]
Message-ID: <4C0F5284.4030706@redhat.com> (raw)
In-Reply-To: <AANLkTile6XogMyj-4ga8ftqbDIPUNRD8cjuBcWT1z8kj-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 06/04/2010 03:35 AM, Scott Olsen wrote:
> First of all, many thanks for all the work on Dracut. We're moving our
> network clients over to Dracut from custom mkinitrd build environment,
> and wow, what an improvement.
>
> What we are looking to do is: the exact execution path of
> dmsquash-live (with an ext3fs.img inside of squashfs) and copy to
> live_ram but with the source of the image being a NFS mount instead of
> a block device.
>
> We hacked it to work, but I want to know the proper way to put this
> into the dracut framework/architecture.
>
> What we have now is:
>
> - inside cmdline/parse-dmsquash-live, we set netroot to be the nfs server
>
> - let everything proceed as normal
>
> - then at the end of /sbin/nfsroot we just call
> /sbin/dmsquash-live-root and everything works (after a few tweaks)
> since the NFS mount is already mounted on NEWROOT and live_dir points
> to the squashfs image.
>
> --
>
> Like I said, its up and working but is there a better way to implement
> this? any architecture pointers would be greatly appreciated!!
>
> Is there any bad effect of having the udev rules created by
> dmsquash-live-genrules run along with the netroot/nfsroot code run?
>
> We had to disable the initqueue check_finished test in init because
> init would break after the retry limit saying no root device found
> (it's there but does not pass the test). Is this a consequence of
> having both dmsquash-live and nfsroot?
>
>
> thanks
>
> Scott
Care to show your modifications, so I can get a better feeling what you are doing?
prev parent reply other threads:[~2010-06-09 8:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTilxH61gB7Kx9EXP6rW--0Fhd5SKYQvFyd1miLXH@mail.gmail.com>
[not found] ` <AANLkTilxH61gB7Kx9EXP6rW--0Fhd5SKYQvFyd1miLXH-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-06-04 1:35 ` dmsquash-live-root + NFS? Scott Olsen
[not found] ` <AANLkTile6XogMyj-4ga8ftqbDIPUNRD8cjuBcWT1z8kj-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-06-09 8:36 ` Harald Hoyer [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=4C0F5284.4030706@redhat.com \
--to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=olesen-Re5JQEeQqe8AvxtiuMwx3w@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.