All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Thomas Renninger <trenn-l3A5Bk7waGM@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 6/6] mkinitrd-dracut.sh: Build host images for default_kernel_images and -i/-k paths
Date: Wed, 02 Oct 2013 12:25:17 +0200	[thread overview]
Message-ID: <524BF48D.2030803@redhat.com> (raw)
In-Reply-To: <1380305940-64410-7-git-send-email-trenn-l3A5Bk7waGM@public.gmane.org>

On 09/27/2013 08:19 PM, Thomas Renninger wrote:
> default_kernel_images and -i/-k paths are new (SuSE) code paths and
> would have resulted in usage errors before.
> 
> There we want to build host only images for faster building and
> smaller images.
> Also force creation (overriding) of initrd images in these code paths.
> 
> Signed-off-by: Thomas Renninger <trenn-l3A5Bk7waGM@public.gmane.org>
> ---
>  mkinitrd-dracut.sh |   14 +++++++++++---
>  1 files changed, 11 insertions(+), 3 deletions(-)
> 
> diff --git a/mkinitrd-dracut.sh b/mkinitrd-dracut.sh
> index f7b53f1..a1519ea 100755
> --- a/mkinitrd-dracut.sh
> +++ b/mkinitrd-dracut.sh
> @@ -3,6 +3,8 @@ kver=$(uname -r)
>  
>  boot_dir="/boot"
>  quiet=0
> +host_only=0
> +force=0
>  
>  error() { echo "$@" >&2; }
>  
> @@ -104,7 +106,8 @@ default_kernel_images() {
>      for initrd_image in $initrd_images;do
>  	targets="$targets $initrd_image"
>      done
> -
> +    host_only=1
> +    force=1
>  }
>  
>  while (($# > 0)); do
> @@ -119,8 +122,8 @@ while (($# > 0)); do
>          --version)
>              echo "mkinitrd: dracut compatibility wrapper"
>              exit 0;;
> -        -v|--verbose) dracut_args="${dracut_args} -v";;
> -        -f|--force) dracut_args="${dracut_args} -f";;
> +        -v|--verbose) dracut_args="${dracut_args} -v --keep";;

do you really want to keep the entire files in /var/tmp/<tmpdir>  for --verbose?

  parent reply	other threads:[~2013-10-02 10:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-27 18:18 dracut: Make mkinintrd-dracut.sh SUSE mkinitrd compatible Thomas Renninger
     [not found] ` <1380305940-64410-1-git-send-email-trenn-l3A5Bk7waGM@public.gmane.org>
2013-09-27 18:18   ` [PATCH 1/6] mkinitrd-dracut.sh: Introduce -i -k parameters Thomas Renninger
2013-09-27 18:18   ` [PATCH 2/6] mkinitrd-dracut.sh: Enhance param parsing: Allow multiple arguments per param Thomas Renninger
2013-09-27 18:18   ` [PATCH 3/6] mkinitrd-dracut.sh: Implement --quiet|-q option Thomas Renninger
2013-09-27 18:18   ` [PATCH 4/6] mkinitrd-dracut.sh: Allow mkinitrd call without passing any parameters Thomas Renninger
2013-09-27 18:18   ` [PATCH 5/6] mkinitrd-dracut.sh: Also allow -d to specify the root_fs and -s dummy Thomas Renninger
2013-09-27 18:19   ` [PATCH 6/6] mkinitrd-dracut.sh: Build host images for default_kernel_images and -i/-k paths Thomas Renninger
     [not found]     ` <1380305940-64410-7-git-send-email-trenn-l3A5Bk7waGM@public.gmane.org>
2013-10-02 10:25       ` Harald Hoyer [this message]
     [not found]         ` <524BF48D.2030803-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-10-04 11:42           ` Thomas Renninger
2013-10-04 11:58             ` Harald Hoyer

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=524BF48D.2030803@redhat.com \
    --to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=trenn-l3A5Bk7waGM@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.