This only affects initramfs-tools version 0.117 and 0.118, and then only
if fsck fails.
initramfs-tools already has a working function to open an emergency
shell, and I will change it to use this in the fsck failure case as
well. So you need not consider this bug to be a blocker for
On Sun, 04 Jan 2015, Paul Menzel wrote:
Not sure if it will make it into Jessie. It do not seem important
enough to try to push it past the freeze.
Under certain circumstances it does not allow to get into the
maintenance shell, which is a real problem for systems still using SysV
Dear Petter,
thank you for your reply!
I wish everyone a happy new year!
Am Freitag, den 26.12.2014, 12:34 +0100 schrieb Petter Reinholdtsen:
[Paul Menzel]
Please find the updated patch below, fixing a typo in the commit message
and removing the note.
Great. The patch need to be
On Fri, 26 Dec 2014, Petter Reinholdtsen wrote:
Great. The patch need to be moved to debian/patches/, but otherwise
look good. I hope someone with access to collab-maint can push a fix.
Not sure if it will make it into Jessie. It do not seem important
enough to try to push it past the
Control: found -1 2.88dsf-58
Control: merge -1 769743 772427
Dear Debian folks,
Am Dienstag, den 16.12.2014, 23:54 +0100 schrieb Paul Menzel:
Control: severity -1 important
Control: tags -1 patch
I found two more bug reports for this issue and merge this report with
those.
[…]
Please find
[Paul Menzel]
Dear Debian folks,
Thank you for looking into this.
Please find the updated patch below, fixing a typo in the commit message
and removing the note.
Great. The patch need to be moved to debian/patches/, but otherwise
look good. I hope someone with access to collab-maint can
Control: severity -1 important
Control: tags -1 patch
Dear Debian folks,
Am Mittwoch, den 08.10.2014, 17:45 +0200 schrieb Axel Beckert:
Pugachev Anatoly wrote:
Ahh, sorry, can't reproduce on the next boot log.
But it is there. I ran into it on a freshly bootstrapped Xen DomU with
On Tue, 16 Dec 2014, Paul Menzel wrote:
Note: The sleep of two seconds is also questionable. Unfortunately there
is no comment explaining what the reason for it is.
IMHO, we should never mess with sleep(some seconds) in this kind of utility.
IME, they're almost always security devices: Either
Hi,
Pugachev Anatoly wrote:
Ahh, sorry, can't reproduce on the next boot log.
But it is there. I ran into it on a freshly bootstrapped Xen DomU with
Debian Sid and currently can reproduce it easily again and again:
Begin: Loading essential drivers ... done.
Begin: Running
Package: sysvinit-utils
Version: 2.88dsf-53.4
Severity: normal
Dear Maintainer,
Booting unstable debian with lvm root/usr/etc.. volumes, leads sulogin to
sigserv and segmentation fault.
Console boot log:
/dev/mapper/v215-root: clean, 5047/591872 files, 252821/2367488 blocks
[ 92.420456]
Ahh, sorry, can't reproduce on the next boot log.
Please close this bug.
Thanks.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
11 matches
Mail list logo
