On Wed, Apr 09, 2014 at 12:07:56PM +0200, Ruediger Meier wrote:
> Actually I think daily "fstrim -a" IS not a good idea for most of my
> systems
install service != enable (this is important detail, I'll never agree
with automatically enabled services).
BTW, why IS not a good idea for your systems?
> but I feel no need to discuss this here on util-linux because
> the decision whether, how, when and on which devices fstrim should be
> called should not be made here at all.
well, "fstrim -a" contains heruistic to select the right filestems (it
really does not call trim for all devices), it has been implemented to
*avoid* sysadmins creativity. If you don't like it, you can use
"fstrim <device>" (for example from crontab).
> If we add scripts with one generic use case for fstrim. Why don't we add
> the generic boot and maintenance scripts how and when to mount or fsck
> all filesystems, to activate swap, to get and set hwclock or whatever?
I really don't want to follow this insane direction of the discussion.
> Moreover the portability issue. Why adding scripts for systemd only
> allthough the same could be done without systemd in a more portable
> way.
is there any other unified, distribution independent and distribution
supported way to install, but no enable the stuff?
Karel
--
Karel Zak <kzak@xxxxxxxxxx>
http://karelzak.blogspot.com
--
To unsubscribe from this list: send the line "unsubscribe util-linux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
