From: Michal Soltys <soltys-R61QfzASbfY@public.gmane.org>
To: WANG Cong <xiyou.wangcong-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Making fsck optional
Date: Fri, 30 Sep 2011 12:55:07 +0200 [thread overview]
Message-ID: <4E85A00B.50203@ziu.info> (raw)
In-Reply-To: <j63tj6$r0p$1@dough.gmane.org>
I'll prep patches to make it all configurable, essentially:
in config file:
fscks - list exact program names you want installed
nofscks - to inhibit installation of any such programs
The latter option takes precedence over the first one
and from commandline:
--fscks [LIST] - additional programs to install
--nofscks - inhibit
similar precedence as in config
(option names subject to change ;)
If the fsck_helpers list is empty and nofsck is not set, dracut will
opportunistically try to install any helper it might need, otherwise it
will limit itself to only specified programs, or to none at all.
next prev parent reply other threads:[~2011-09-30 10:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 15:34 Making fsck optional Daniel Drake
2011-09-30 8:11 ` WANG Cong
2011-09-30 10:55 ` Michal Soltys [this message]
2011-10-04 2:23 ` WANG Cong
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=4E85A00B.50203@ziu.info \
--to=soltys-r61qfzasbfy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox