mkinitrd unification across distributions
 help / color / mirror / Atom feed
From: Maarten Vanraes <maarten.vanraes-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: Re: patches
Date: Wed, 21 Jul 2010 17:18:28 +0200	[thread overview]
Message-ID: <201007211718.28574.maarten.vanraes@gmail.com> (raw)
In-Reply-To: <4C46DAF1.1090603-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

Op woensdag 21 juli 2010 13:33:05 schreef Harald Hoyer:
> On 07/14/2010 02:05 AM, Maarten Vanraes wrote:
> > Hi,
> >
> > Here are some patches, some that were used as patches in the mandriva
> > builds, and a first one from me, to fix nfs hostonly on chrooted
> > installs.
> >
> > Kind regards,
> >
> > Maarten Vanraes
> 
> -[ "$1" = "-h" ] && ! egrep -q '/ nfs[34 ]' /proc/mounts && exit 1
> +[ "$1" = "-h" ] && ! egrep -q '\s/\s+nfs[34]?\s' /etc/fstab && exit 1
> 
> Hmm, I think "hostonly" should be really "hostonly", so the check is valid.
> 
> You can always force the addition of nfs, if you are building a special
>  image for an NFS client. Or just boot with the generic (non-hostonly) one,
>  and build the hostonly one on the client.
> 

i see what you mean, but i beg to differ.

this thing is not really about nfs, it's about building an initrd on a chroot.

if you're building initrd on a chroot, it's always a hostonly, in fact, only 
distros ship generic initrds. and even that's not always true.

this fix has no consequences whatsoever in any case, except that it checks 
fstab instead of /proc/mounts. which means if you adjust your fstab, because 
you're going to run it elsewhere.

I was planning on checking everywhere and trying to reduce the dependencies on 
/proc and /sys, IF it works the same everywhere without any consequences (just 
like this here).

Also, if you look at it; not having / mounted as an nfs WILL disable the use 
of this module entirely and thus all the root=nfs stuff will fail.

What do you think?

  parent reply	other threads:[~2010-07-21 15:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-14  0:05 patches Maarten Vanraes
     [not found] ` <201007140205.35944.maarten.vanraes-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-07-21 11:33   ` patches Harald Hoyer
     [not found]     ` <4C46DAF1.1090603-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-07-21 15:18       ` Maarten Vanraes [this message]
     [not found]         ` <201007211718.28574.maarten.vanraes-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-07-26  7:42           ` patches Maarten Vanraes
2010-07-21 11:41   ` patches Harald Hoyer
     [not found]     ` <4C46DCD0.3020608-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-07-21 15:03       ` patches Maarten Vanraes
     [not found]         ` <201007211703.36797.maarten.vanraes-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-07-21 15:13           ` patches Harald Hoyer
     [not found]             ` <4C470EAD.705-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2010-07-21 15:20               ` patches Maarten Vanraes
2011-01-08  6:41       ` [PATCH] load dracut.conf.d before dracut.conf (was: Re: patches) Anssi Hannula
     [not found]         ` <4D280724.8050405-4qZELD6Fgxhg9hUCZPvPmw@public.gmane.org>
2011-02-18 10:15           ` [PATCH] load dracut.conf.d before dracut.conf Harald Hoyer
     [not found]             ` <4D5E46DC.4020303-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-02-20 17:29               ` Anssi Hannula
     [not found]                 ` <4D614F8D.10505-4qZELD6Fgxhg9hUCZPvPmw@public.gmane.org>
2011-02-25 12:43                   ` Harald Hoyer
  -- strict thread matches above, loose matches on Subject: below --
2010-07-26  7:58 patches Maarten Vanraes

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=201007211718.28574.maarten.vanraes@gmail.com \
    --to=maarten.vanraes-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@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