[Pkg-sysvinit-devel] Bug#872039: why the severity?

[Cameron Norman]

On Fri, 12 Jan 2018 03:56:42 +0100 Adam Borowski <kilobyte at angband.pl>
wrote:
> On Wed, Jan 10, 2018 at 08:38:39PM +0100, John Paul Adrian Glaubitz wrote:
> > > Please tell me why this would be serious: any filesystem from this
millenium
> > > can handle unclean shutdown fine -- especially if there's a sync
before
> > > reboot/poweroff.
> >
> > That's hardly an argument. There is still very much the possibility that
> > this bug causes data-loss, so the severity is definitely justified.
>
> Technically, yes.  If your filesystem is ext2, and there's a process that
> hasn't been killed, and continues to write after the final sync.
>
> But if you use ext2 for anything, you made the decision yourself.
>

Not necessarily, an admin could just have to use ext2 for internal company
policy reasons.

Let's not punish people for being stuck in a bad situation.

/usr is already mounted ro. Can we not remount other filesystems ro like
/var at the same time?

> > On the other hand, only a very small minority are still using sysvinit
on
> > Debian, so this I think it's ok to have the severity set to serious.
>
> According to my last data, 14% of unstable users; less on stable as those
> tend to be non-technical users.  Not a "very small minority".

Ignore him. He trolls non-systemd inits and actively roots for their exit
from Debian.

Regards,
--
Cameron nemo
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-sysvinit-devel/attachments/20180624/49c11aa5/attachment.html>