From: "Thomas Bächler" <thomas@archlinux.org>
To: Ruediger Meier <sweet_f_a@gmx.de>, Karel Zak <kzak@redhat.com>
Cc: "Thomas Bächler" <thomas@archlinux.org>, util-linux@vger.kernel.org
Subject: Re: [PATCH] fstrim: add systemd units
Date: Tue, 08 Apr 2014 12:57:04 +0200 [thread overview]
Message-ID: <5343D600.7000507@archlinux.org> (raw)
In-Reply-To: <201404081225.21563.sweet_f_a@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1342 bytes --]
Am 08.04.2014 12:25, schrieb Ruediger Meier:
> Hm, isn't this a bit over the top? Adding a script just to
> call "fstrim -a" automatically?
It's a common task. I was getting tired of having to add this on every
single machine that I set up.
> Should we also add scripts for "mount -a" or "fsck -a" or "swapon -a"?
And what purpose would that serve? Did you just take random commands and
add '-a' to prove a point?
> And wouldn't we also need to add "example crontab" lines for non-systemd
> systems! Sounds a bit ridiculous, right?
You can add them if you feel like it. But this is not an "example" file,
it is ready to be used.
> I think it's the distro's or admin's job to write and add the scripts
> for filesystems maintenance etc.
That's ridiculous. We finally, for the first time ever, have a unified
way of creating service definitions that can be used unchanged in all
relevant distributions (except Gentoo and Slackware, of course). The
main advantage of this unification is that they can be shipped and
maintained by upstream projects - after all, the upstream projects know
what services make sense and how to start them properly.
> BTW fstrim.timer is missing in "make dist" tar ball.
Sorry, you are right. I'm a bit lost in this build system, Karel
probably knows how to fix this.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2014-04-08 10:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 21:41 [PATCH] fstrim: add systemd units Thomas Bächler
2014-04-07 10:43 ` Karel Zak
2014-04-08 10:25 ` Ruediger Meier
2014-04-08 10:57 ` Thomas Bächler [this message]
2014-04-08 12:07 ` Ruediger Meier
2014-04-08 15:42 ` Dave Reisner
2014-04-08 17:12 ` Ruediger Meier
2014-04-09 7:52 ` Karel Zak
2014-04-09 10:07 ` Ruediger Meier
2014-04-09 11:02 ` Karel Zak
2014-04-09 12:12 ` Ruediger Meier
2014-04-09 12:49 ` Thomas Bächler
2014-04-09 15:16 ` Ruediger Meier
2014-04-09 15:24 ` Thomas Bächler
2014-04-09 15:44 ` Ruediger Meier
2014-04-09 14:02 ` Markus Trippelsdorf
2014-04-09 15:48 ` Ruediger Meier
2014-04-09 15:55 ` Markus Trippelsdorf
2014-04-09 18:39 ` Theodore Ts'o
2014-04-10 8:05 ` Karel Zak
2014-04-10 9:17 ` Ruediger Meier
2014-04-10 12:49 ` Karel Zak
2014-04-10 13:16 ` Ruediger Meier
2014-04-10 13:22 ` Ruediger Meier
2014-04-08 17:26 ` Karel Zak
2014-04-08 17:30 ` Thomas Bächler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5343D600.7000507@archlinux.org \
--to=thomas@archlinux.org \
--cc=kzak@redhat.com \
--cc=sweet_f_a@gmx.de \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox