DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Bächler" <thomas@archlinux.org>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Boot Prompt Text
Date: Mon, 17 Feb 2014 16:02:17 +0100	[thread overview]
Message-ID: <53022479.8070402@archlinux.org> (raw)
In-Reply-To: <20140217143901.GB1984@tansi.org>

[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]

Am 17.02.2014 15:39, schrieb Arno Wagner:
> That this is in a c-file, not an easily changed shell-
> skript, already explains quite a bit of what is wrong
> with systemd.

Besides the fact that this is completely off-topic:

You could use the same argument on cryptsetup and claim that it should
be a shell script. Why isn't it? If I want 'cryptsetup luksOpen's prompt
to change, I need to change it in cryptsetup and recompile. If it was a
script, I could easily edit it.

It's *precisely* your argument. (Of course, it completely ignores that
the next system update would overwrite it, shell script or binary).

Really, please stop inventing weird arguments against things that you
don't use, are not interested in and don't know anything about - and
keep it on-topic.

> Pity. With a sane init system, it would just be a change to
> some shell-skript, i.e. 2 minutes with a text editor. 

Until the next system update - and then you edit it again. System
maintenance like it is done in 2014!



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]

  reply	other threads:[~2014-02-17 15:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-17 11:28 [dm-crypt] Boot Prompt Text Andrew Dunn
2014-02-17 13:04 ` Arno Wagner
2014-02-17 13:19   ` Thomas Bächler
2014-02-17 14:39     ` Arno Wagner
2014-02-17 15:02       ` Thomas Bächler [this message]
2014-02-17 15:18         ` Sven Eschenberg
2014-02-17 15:28           ` Thomas Bächler
2014-02-17 15:36             ` .. ink ..
2014-02-17 15:38             ` Arno Wagner
2014-02-17 15:40             ` Sven Eschenberg
2014-02-17 15:27         ` Arno Wagner
2014-02-17 17:57       ` Arno Wagner
2014-02-17 18:58         ` Dave Reisner
2014-02-17 20:09           ` Arno Wagner
2014-02-18 11:33         ` Richard Z
2014-02-18 16:21           ` Arno Wagner
2014-02-18 16:44             ` Milan Broz
2014-02-18 17:48               ` Arno Wagner
2014-02-18 16:34           ` 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=53022479.8070402@archlinux.org \
    --to=thomas@archlinux.org \
    --cc=dm-crypt@saout.de \
    /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