Re: Bug#694928: asks for confirmation on config-file change on /etc/default/rcS, while file didn't change
On Mon, Dec 03, 2012 at 01:20:50PM +0000, Ben Hutchings wrote:
> On Mon, 2012-12-03 at 00:44 +0000, Roger Leigh wrote:
> > On Sun, Dec 02, 2012 at 11:49:44PM +0000, Roger Leigh wrote:
> > > On Sun, Dec 02, 2012 at 11:47:37PM +0000, Roger Leigh wrote:
> > > > clone 694928 -1
> > > > reassign -1 initscripts
> > > > thanks
> > > >
> > > > On Sun, Dec 02, 2012 at 12:23:07PM +0100, Martin Zobel-Helas wrote:
> > > >
> > > > Please find attached an example patch for flash-kernel to
> > > > support old and new (rcS and fsck) locations for FSCKFIX
> > > > as discussed on #debian-devel earlier.
> > >
> > > Hmm, actually attached now.
> >
> > Slight update to cope with commented-out lines (as provided
> > by default).
>
> This should really be the default for everyone... how many people know
> their filesystem well enough to answer fsck prompts intelligently?
I would personally be happy with it being set by default.
However, the few times this has been brought up, there have been
a number of examples where this might result in filesystem
corruption. I think the main argument was that the admin might
want to take an image before fsck ran, in case fsck caused
further problems. I'd have to check, but IIRC other issues
included checking parts of unreconstructed RAID arrays and/or
LVM PVs, but I don't think this is very likely.
I'd be tempted to enable it by default across the board, and
require admins who want this extra safety to explicitly
disable checking. The vast majority of users will benefit from
this, since they can't intelligently answer the prompts as you
say.
Regards,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools
`- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800
Reply to: