On Thu, Jan 18, 2018 at 12:22:21PM +, Stuart Henderson wrote:
> A flag (fsck_flags) would be a better idea than a file, and more
> flexible (users with many disks and low RAM could use the same
> mechanism to force "-l 1" for example).
fsck_flags would be an idea. I prefer not to bring local
On 2018/01/18 13:30, Artturi Alm wrote:
> On Thu, Jan 18, 2018 at 12:13:54PM +0100, Otto Moerbeek wrote:
> > On Thu, Jan 18, 2018 at 12:12:39PM +0200, Artturi Alm wrote:
> >
> > > Hi,
> > >
> > > i think i've never answered "n" to fsck, so to me the lack of -y does
> > > mean unnecessary
Hi All,
For what its worth.. if they are devices that are regularly rebooted without
proper shutdown,( you may be better off avoiding the situation where FSCK
has to run)
I have found As Otto has pointed out fsck and all the way doesn't work
so well in some cases.
The most risk adverse way I
On Thu, Jan 18, 2018 at 12:13:54PM +0100, Otto Moerbeek wrote:
> On Thu, Jan 18, 2018 at 12:12:39PM +0200, Artturi Alm wrote:
>
> > Hi,
> >
> > i think i've never answered "n" to fsck, so to me the lack of -y does
> > mean unnecessary work/boards/VMs left waiting for the F..
> >
> > i would use
On Thu, Jan 18, 2018 at 12:12:39PM +0200, Artturi Alm wrote:
> Hi,
>
> i think i've never answered "n" to fsck, so to me the lack of -y does
> mean unnecessary work/boards/VMs left waiting for the F..
>
> i would use something like this if it was there:
>
> diff --git a/etc/rc b/etc/rc
> index
Hi,
i think i've never answered "n" to fsck, so to me the lack of -y does
mean unnecessary work/boards/VMs left waiting for the F..
i would use something like this if it was there:
diff --git a/etc/rc b/etc/rc
index c88e13ce7ab..e3a269be818 100644
--- a/etc/rc
+++ b/etc/rc
@@ -349,7 +349,11 @@
