Re: install/50033: WABPL(4) is not enabled by default in sysinst(8)

[Manuel Bouyer <bouyer%antioche.eu.org@localhost>]

The following reply was made to PR install/50033; it has been noted by GNATS.

From: Manuel Bouyer <bouyer%antioche.eu.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: install-manager%NetBSD.org@localhost, gnats-admin%NetBSD.org@localhost, netbsd-bugs%NetBSD.org@localhost,
        tsutsui%ceres.dti.ne.jp@localhost
Subject: Re: install/50033: WABPL(4) is not enabled by default in sysinst(8)
Date: Wed, 9 Sep 2015 22:53:21 +0200

 On Wed, Sep 09, 2015 at 05:00:01PM +0000, Izumi Tsutsui wrote:
 > The following reply was made to PR install/50033; it has been noted by GNATS.
 > 
 > From: Izumi Tsutsui <tsutsui%ceres.dti.ne.jp@localhost>
 > To: bouyer%antioche.eu.org@localhost
 > Cc: gnats-bugs%NetBSD.org@localhost, tsutsui%ceres.dti.ne.jp@localhost
 > Subject: Re: install/50033: WABPL(4) is not enabled by default in sysinst(8)
 > Date: Thu, 10 Sep 2015 01:59:01 +0900
 > 
 >  > I did have problems several times after unclean shutdowns.
 >  > It's serious enough for me to disable it on my servers (on a mail
 >  > server it can cause email loss for example).
 >  
 >  Such heavy NetBSD users already know the risk and
 >  they will disable it without any notice or documents.
 >  
 >  On the other hand, new novice users won't use NetBSD
 >  for such serious server and they will see awful slowness
 >  on pkgsrc tar extraction on the first trial with
 >  the default installation.
 >  
 >  That's my concern.
 
 And what will the novice user think if the system crash on a rm command,
 or has a corrupted filesystem after a hard reset ?
 
 -- 
 Manuel Bouyer <bouyer%antioche.eu.org@localhost>
      NetBSD: 26 ans d'experience feront toujours la difference
 --