From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Boot Prompt Text
Date: Mon, 17 Feb 2014 18:57:25 +0100 [thread overview]
Message-ID: <20140217175725.GA4299@tansi.org> (raw)
In-Reply-To: <20140217143901.GB1984@tansi.org>
On Mon, Feb 17, 2014 at 15:39:01 CET, Arno Wagner wrote:
> > Actually, it's systemd's doing:
> >
> > http://cgit.freedesktop.org/systemd/systemd/tree/src/cryptsetup/cryptsetup.c#n266
>
> Ah, that evil monster. For that I would say those that
> use systemd shall suffer from the complexity they chose.
> That this is in a c-file, not an easily changed shell-
> skript, already explains quite a bit of what is wrong
> with systemd.
>
> So fixing this goes something like this:
> - create a patch for the c-code
> - recompile and reinstall systemd
> - and maintain your patch forever
>
> Pity. With a sane init system, it would just be a change to
> some shell-skript, i.e. 2 minutes with a text editor.
Aparently, I was wrong. It seems the correct process to
do this (according to a personal communication from
Thomas Bächler) is as follows:
- Find a solution for the problem that
a) is generic enough to fit your use case and satisfy others
b) can be implemented by the admin using appopriate configuration
files (without further editing shell scripts or binaries).
- Implement that solution in the code.
- Get the patch merged into systemd.
How that has any business replacing
- Start editor
- Fiddle with init-script until you like the prompt
- Enjoy _your_ solution to the problem, no matter what
anybody else thinks about it
is beyond me. But I do know a certain other OS where
they do not like you to customize your experience either.
I can only advise anybody that does want to customize what
their system does to stay away from these authoritarian
atrocities.
Arno
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. - Plato
next prev parent reply other threads:[~2014-02-17 17:57 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
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 [this message]
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=20140217175725.GA4299@tansi.org \
--to=arno@wagner.name \
--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