X-Original-To: alpine-devel@lists.alpinelinux.org
Delivered-To: alpine-devel@mail.alpinelinux.org
Received: from mail-lb0-f176.google.com (mail-lb0-f176.google.com [209.85.217.176])
	(using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
	(No client certificate requested)
	by mail.alpinelinux.org (Postfix) with ESMTPS id 53CBEDC0158
	for <alpine-devel@lists.alpinelinux.org>; Thu, 13 Feb 2014 08:53:27 +0000 (UTC)
Received: by mail-lb0-f176.google.com with SMTP id w7so7856615lbi.7
        for <alpine-devel@lists.alpinelinux.org>; Thu, 13 Feb 2014 00:53:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=sender:date:from:to:cc:subject:message-id:in-reply-to:references
         :mime-version:content-type:content-transfer-encoding;
        bh=S13uOE+IS+9ajOHrliggHfXfLSuj4EnlUIwPxPzbFdQ=;
        b=Wh9PpWih5fgiP/PqMuLYbS8kzvqklI+Ddsg4+SHddhb5GMcX9Y5J3Aud7cuCSp5oIT
         SwrOtqUNwpM1MfjbQWrlS4ljSb3gykXy5a/4hVtCyLLEhDfNxGvyIxYoSGrXN0uBFhAX
         78bofeqlbEnCwboqyidxGvBvhJx21x1AKTp4HyaRs3q2UWPajt65unrOEns2AQ5gaDSp
         449Vwdp1tAgtsZo4XcSncIy5spv1BSxOTERN5QC6vxIiSJ5Dz4XsAr9yGUtuZDkTtJDP
         KxY4VpfVyw5HqJy5Qbqc8kOZhKQc7gLtCKsqoQS93huBxAvw949+3eOqlKzMr4n5SFa0
         h+zg==
X-Received: by 10.112.34.231 with SMTP id c7mr226904lbj.56.1392281603136;
        Thu, 13 Feb 2014 00:53:23 -0800 (PST)
Received: from vostro ([2001:1bc8:101:f402:21c:23ff:fefc:bf0b])
        by mx.google.com with ESMTPSA id gi5sm1330964lbc.4.2014.02.13.00.53.22
        for <multiple recipients>
        (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Thu, 13 Feb 2014 00:53:23 -0800 (PST)
Sender: =?UTF-8?Q?Timo_Ter=C3=A4s?= <timo.teras@gmail.com>
Date: Thu, 13 Feb 2014 10:54:06 +0200
From: Timo Teras <timo.teras@iki.fi>
To: developer@it-offshore.co.uk
Cc: alpine-devel@lists.alpinelinux.org
Subject: Re: [alpine-devel] [PATCH] Main/mkinitfs - small Patch for LUKS /
 Cryptsetup
Message-ID: <20140213105406.0b0c9eb6@vostro>
In-Reply-To: <52FBCAD2.5070606@it-offshore.co.uk>
References: <1392158622-21396-1-git-send-email-developer@it-offshore.co.uk>
	<20140212081021.24b9d693@vostro>
	<52FBCAD2.5070606@it-offshore.co.uk>
X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.20; i486-alpine-linux-uclibc)
X-Mailinglist: alpine-devel
Precedence: list
List-Id: Alpine Development <alpine-devel.lists.alpinelinux.org>
List-Unsubscribe: 
	<mailto:alpine-devel+unsubscribe@lists.alpinelinux.org?subject=unsubscribe>
List-Post: <mailto:alpine-devel@lists.alpinelinux.org>
List-Help: <mailto:alpine-devel+help@lists.alpinelinux.org?subject=help>
List-Subscribe: 
	<mailto:alpine-devel+subscribe@lists.alpinelinux.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Wed, 12 Feb 2014 19:26:10 +0000
IT Developer <developer@it-offshore.co.uk> wrote:

> When mkinitfs is run on it's own for example (as shown on the wiki):
> 
> /*mkinitfs -c $MNT/etc/mkinitfs/mkinitfs.conf -b $MNT*/

The differences are that when apk runs the trigger, it's executed in
chroot. And command is like 'mkinitfs -o /boot/$initfs $abi_release'

This sounds like mkinitfs bug, or mismatch with running kernel and
installed kernel versions. The wiki should likely be updated or
mkinitfs fixed.

> The initramfs does not contain cryptsetup
> 
> Cryptsetup is included when apk is run with:
> 
> /*apk fix --root $MNT linux-grsec*/ (or just /*apk fix linux-grsec*/
> on a running system)

So the problem occurs only when doing chroot installs?

> I don't know what extra "apk fix" does - but it does call mkinitfs
> correctly & generates an initramfs with cryptsetup included. At the
> moment upgrading a kernel on an encrypted system does not generate a
> new initramfs with cryptsetup included.
> 
> I am using a system with LVM on top of LUKS - when I upgraded to the
> edge kernel a few days ago I did not see any initramfs regeneration -
> even for LVM.

Mkinitfs trigger is "$pkgname.trigger=/usr/share/kernel/*" and I
believe only kernel images touch those files. Sounds like kernel module
packages as well as userland packages that go to initramfs should also
trigger mkinitfs.

ncopa, any idea how to do that properly? Perhaps we should have
some /usr/share/mkinitfs/components/ directory where each of these
package can install a file - and mkinitfs trigger monitors that
directory and in case something changes there it regens initfs for
all kernel flavors installed.

- Timo




---
Unsubscribe:  alpine-devel+unsubscribe@lists.alpinelinux.org
Help:         alpine-devel+help@lists.alpinelinux.org
---