Hi,
I noticed some strage behaviour with mkinitfs when running it against a different basedir using the -b switch.
Apparently, it loads modules to be included in the initramfs from $basedir, but the list of modules defined through the features is not.
This is quite inconsistent as those two things don't necessarily fit together, producing inusable initramfs images.
The attached patch proposes to read features for initramfs from $basedir if set, assuming that this behavour is not intentionally the way it is now.
Cheers,
Christian
---
Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org
Help: alpine-devel+help@lists.alpinelinux.org
---
[alpine-devel] [PATCH] mkinitfs: features should be read from $basedir if set
On Sun, 11 Oct 2015 17:50:06 +0200
Christian Kampka <christian@kampka.net> wrote:
> Hi,> > I noticed some strage behaviour with mkinitfs when running it against> a different basedir using the -b switch. Apparently, it loads modules> to be included in the initramfs from $basedir, but the list of> modules defined through the features is not. This is quite> inconsistent as those two things don't necessarily fit together,> producing inusable initramfs images.> > The attached patch proposes to read features for initramfs from> $basedir if set, assuming that this behavour is not intentionally the> way it is now.
I don't think this was intentional and the patch looks correct. Thanks!
-nc
---
Unsubscribe: alpine-devel+unsubscribe@lists.alpinelinux.org
Help: alpine-devel+help@lists.alpinelinux.org
---