Hi Thomas,
Yes it does.
Applied fix-bash-5.patch with "patch -p1" under /usr/lib/dracut, then
ran "dracut --force" to regenerate the initramfs image.
After restarting, no problems at boot.
Regards,
Lehel
On 2019-05-05 21:34, Thomas Lange wrote:
Hi Lehel, hi Ingo,
it would be nice if you cou
Hi Lehel, hi Ingo,
it would be nice if you could check if fix-bash-5.patch from the URL
below fixes your problems.
I sure will also apply
0001-remove-bashism-in-various-boot-scripts.patch which is now also in upstream.
> On Sat, 4 May 2019 18:30:09 +0200, Lehel Bernadt said:
> For insp
I ran into the same problem. I have just one (root) filesystem, with ext4 on
it. I think it's trivial to reproduce it with an install with ext*
filesystems.
For inspiration on how to fix it you can look here:
https://github.com/void-linux/void-packages/tree/master/srcpkgs/dracut/patches
(I don'
On Thu, Jan 31, 2019 at 02:24:40PM +0100, Thomas Lange wrote:
> > On Sun, 27 Jan 2019 02:27:08 +0100, Ingo Saitz
> > said:
>
> > When generating an initrd with bash 5.0-2 installed, the generated
> initrd
> > fails to boot with the error message:
> I cannot confirm this bug. I h
> On Sun, 27 Jan 2019 02:27:08 +0100, Ingo Saitz
> said:
> When generating an initrd with bash 5.0-2 installed, the generated initrd
> fails to boot with the error message:
I cannot confirm this bug. I have a VM installed with buster and bash
5.0-2. After generating a new initrd
Package: dracut
Version: 048+80-1
Severity: important
Dear Maintainer,
When generating an initrd with bash 5.0-2 installed, the generated initrd
fails to boot with the error message:
> /lib/fs-lib.sh: line 109: _drv=e2fsck fsck_drv_com
The behaviour of "local" declared variables in POSIX mode s
6 matches
Mail list logo
