[systemd-devel] [PATCH 2/2] fsck: Add support for EFI variable based fsck indication

[Lennart Poettering]

On Thu, 09.04.15 10:51, Jóhann B. Guðmundsson (johannbg at gmail.com) wrote:

> My above questions where directed directly at Lennart since you cannot know
> if Lennart's assumption which he bases his decisions on are
> premature,correct, wrong or misguided until you know what those assumptions
> are.
> 
> Once those assumptions are known one can compare it with ones own as well as
> facts and have a higher level discussion about what makes suitable upstreams
> defaults and why.

We generally follow the rule: we develop for the future, not for the
past. A file system like ext234 is clearly not the future, the concept
of requiring fsck on dirty is just broken with today's large
disks. Now, of course we will continue to support ext234, and fsck and
stuff. However, we will not add *new* features to this scheme, since
the whole idea of having something like this at all is yesterday's
idea.

Sure, btrfs is not particularly stable yet, but that hardly matters,
as not even xfs requires such an fsck scheme anymore!

I mean, it's really ext234 and vfat that require this, no other
commonly used fs does. And those we can support just fine with the
status quo, and don't need to invent completely new logic for it.

We will not add completely new features to the old stuff, if we
already know *now* that the old stuff is a dead end, and things are
already good enough in the area, and the future will make the whole
problem go away.

Lennart

-- 
Lennart Poettering, Red Hat