[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#823069: RE: Bug#823069: live-boot-initramfs-tools: Kernel panic while booting live with Debian stretch busybox/live packages



That did not change a thing: output the same as in OP.

Arjen


On Mon, 9 May 2016 20:24:12 +0200 Kristian Klausen <klausenbusk@hotmail.com> wrote:
> Arjen could you try removing:
> PATH="/root/usr/bin:/root/usr/sbin:/root/bin:/root/sbin:/usr/bin:/usr/sbin:/bin:/sbin"
> export PATH
>
> from /lib/live/boot/9990-aaa-fixme.sh and see if it works?
>
> - Kristian
>
> ----------------------------------------
> > Subject: Bug#823069: live-boot-initramfs-tools: Kernel panic while booting live with Debian stretch busybox/live packages
> > From: ben@decadent.org.uk
> > To: 823069@bugs.debian.org
> > CC: util-linux@packages.debian.org
> > Date: Mon, 9 May 2016 17:55:55 +0100
> >
> > Control: clone -1 -2
> > Control: reassign -2 util-linux
> > Control: severity -2 important
> > Control: affects -2 live-boot-initramfs-tools
> > Control: retitle -1 live-boot-initramfs-tools: wrongly adds directories in /root to the PATH > > Control: retitle -2 util-linux: 'mount -o move' does not work with virtual filesystems
> >
> > On Sat, 30 Apr 2016 16:07:25 +0200 Arjen Balfoort <arjenbalfoort@solydxk.com> wrote:
> > [...]
> >> mount: /dev is write-protected, mounting read-only
> >> mount: /dev is not a block device
> >>
> >> The error is caused in /usr/share/initramfs-tools/scripts/init-bottom/udev
> >> Line: mount -n -o move /dev ${rootmnt}/dev
> > [...]
> >
> > This is a side-effect of my change in busybox 1.22.0-19, but I don't
> > think that change was wrong.
> >
> > live-boot-initramfs-tools adds directories under /root to $PATH, which
> > was formerly harmelss but now actually does result in some commands
> > being loaded from there. You must stop doing this; it is not
> > supportable and I will not support it.
> >
> > In particular, this mount command now invokes util-linux's mount. That
> > refuses to perform a move if the source filesystem was not mounted from
> > a block device. There is no good reason for this and obviously it
> > works with busybox and klibc's implementations of mount.
> >
> > Ben.
> >
> > --
> > Ben Hutchings
> > If you seem to know what you are doing, you'll be given more to do.
>
>


Reply to: