From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ea0-x22c.google.com (mail-ea0-x22c.google.com [IPv6:2a00:1450:4013:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mail.saout.de (Postfix) with ESMTPS for ; Tue, 18 Feb 2014 12:34:04 +0100 (CET) Received: by mail-ea0-f172.google.com with SMTP id l9so7170409eaj.17 for ; Tue, 18 Feb 2014 03:34:03 -0800 (PST) Sender: "Richard Z." Date: Tue, 18 Feb 2014 12:33:49 +0100 From: Richard Z Message-ID: <20140218113349.GC17249@localhost.localdomain> References: <20140217130429.GA1200@tansi.org> <53020C63.6040404@archlinux.org> <20140217143901.GB1984@tansi.org> <20140217175725.GA4299@tansi.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable In-Reply-To: <20140217175725.GA4299@tansi.org> Subject: Re: [dm-crypt] Boot Prompt Text List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Arno Wagner Cc: dm-crypt@saout.de On Mon, Feb 17, 2014 at 06:57:25PM +0100, Arno Wagner wrote: > On Mon, Feb 17, 2014 at 15:39:01 CET, Arno Wagner wrote: > > > Actually, it's systemd's doing: > > >=20 > > > http://cgit.freedesktop.org/systemd/systemd/tree/src/cryptsetup/crypt= setup.c#n266 > >=20 > > Ah, that evil monster. For that I would say those that=20 > > 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. > >=20 > > So fixing this goes something like this: > > - create a patch for the c-code > > - recompile and reinstall systemd > > - and maintain your patch forever > >=20 > > Pity. With a sane init system, it would just be a change to > > some shell-skript, i.e. 2 minutes with a text editor.=20 >=20 > Aparently, I was wrong. It seems the correct process to > do this (according to a personal communication from > Thomas B=E4chler) is as follows: >=20 > - 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. seems there are other ways to do it because on my Fedora 19 with=20 out of the box encrypted hard disk I do not see any prompt - just=20 an entry box without any text where I can type the password. > How that has any business replacing >=20 > - Start editor > - Fiddle with init-script until you like the prompt > - Enjoy _your_ solution to the problem, no matter what=20 > anybody else thinks about it =20 not always quite so easy, some distros have some kind of initial=20 ram disk. I would rather patch systemd than mess with the initial ramdisk every time a new kernel is installed. Richard --- Name and OpenPGP keys available from pgp key servers