All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: WANG Cong <xiyou.wangcong-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Q: How to add more modules when -H is specified?
Date: Fri, 29 Jul 2011 11:24:40 +0200	[thread overview]
Message-ID: <4E327C58.1000406@redhat.com> (raw)
In-Reply-To: <j0tsl5$2kj$2@dough.gmane.org>

On 29.07.2011 10:57, WANG Cong wrote:
> 
> Hi, dracut people,
> 
> I am not sure about the expected behaviour when I specify both
> -H and --add foo (where module foo is not automatially added
> by -H). It looks like with -H specified, --add foo will not
> take any effect?
> 
> At least `-H --add nfs` doesn't work if my rootfs is not nfs,
> I see the following check in modules.d/95nfs/module-setup.sh,
> 
>     [ $hostonly ] && ! egrep -q '/ nfs[34 ]' /proc/mounts && return 1
> 
> So, is this expected? I mean as long as I specify -H, there is
> no way to add more modules? Or just the nfs check code is wrong?

Hmm, yes, currently all "add" modules also have the hostonly check.
Sometimes you want that behaviour, sometimes not..

We might want s.th. like "--force-add" for that use case.

> 
> Also, I am looking for a way to add all needed modules for
> devices mounted in current system, as -H only adds modules
> needed by rootfs.
> 
> Thanks!
> 

Not (yet) implemented. I accept patches :-)

  reply	other threads:[~2011-07-29  9:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-29  8:57 Q: How to add more modules when -H is specified? WANG Cong
2011-07-29  9:24 ` Harald Hoyer [this message]
     [not found]   ` <4E327C58.1000406-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2011-07-29  9:44     ` Américo Wang

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=4E327C58.1000406@redhat.com \
    --to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=xiyou.wangcong-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.