mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Jon Ander Hernandez <jonan.h-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Seewer Philippe <philippe.seewer-omB+W0Dpw2o@public.gmane.org>
Subject: Re: Live module for root=nfs using Aufs
Date: Wed, 10 Nov 2010 15:28:47 +0100	[thread overview]
Message-ID: <4CDAAC1F.6060308@redhat.com> (raw)
In-Reply-To: <AANLkTinNFeT8kuoe5FRJig=un76kE6bLoU4BzJKxp4OY-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

On 11/08/2010 08:03 PM, Jon Ander Hernandez wrote:
> 2010/11/8 Seewer Philippe<philippe.seewer-omB+W0Dpw2o@public.gmane.org>:
>
>> I just had a quick look over the patch and in itself it looks ok. Although
>> I'm not sure if having the aufs at this stage is necessary. What if you just
>> mount it later inside the rootfs? (Background: I'm using aufs overlays for
>> our read only nfs-roots, and I just put the necessary aufs mounts inside
>> fstab)
>
> I have to say that I haven't thought about it before.... It is really
> a good idea, and is probably better than have a specific module. :-)
>
> But something that worries me, is if the init process will cause
> problems, since we will be mounting a new root over the old one once
> we have processes which have previously opened files on the old /.
>
> Regards,
>
> Jon Ander.

So, do you still need this dracut module? Or is it good enough, to do this in 
the real root?

  parent reply	other threads:[~2010-11-10 14:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-08  0:43 Live module for root=nfs using Aufs Jon Ander Hernandez
     [not found] ` <AANLkTi=7coxwNNu22um=qO7Tz18QZj_N7h3=G5ABnjqV-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-11-08  8:19   ` Seewer Philippe
     [not found]     ` <4CD7B293.8050809-omB+W0Dpw2o@public.gmane.org>
2010-11-08 19:03       ` Jon Ander Hernandez
     [not found]         ` <AANLkTinNFeT8kuoe5FRJig=un76kE6bLoU4BzJKxp4OY-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-11-10 14:28           ` Harald Hoyer [this message]
     [not found]             ` <4CDAAC1F.6060308-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-11-10 15:40               ` Jon Ander Hernandez

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=4CDAAC1F.6060308@redhat.com \
    --to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=jonan.h-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=philippe.seewer-omB+W0Dpw2o@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