On Wed Apr 24, 2024 at 1:50 PM BST, Richard wrote:
> upon gathering my thoughts for answering to you I found the solution to
> this: update-initramfs can't handle the case that crypttab ends in the line
> of the last entry and not in a new line character. I think there either
> should be a fix for
On 26/04/2024 12:56, David Wright wrote:
On Fri 26 Apr 2024 at 11:27:24 (+0900), John Crawley wrote:
Innocent question: what difference does the comment make vs just ending the
file with an empty line?
Nothing for the computer, but visibility for me.
Say you print the file on paper. All you
On 26/04/2024 10:56, David Wright wrote:
Editor examples: a windowed emacs buffer has a ≣ decoration at the
extreme left edge after the last line of text, so that you can
distinguish an absence of lines from empty lines.
Perhaps that decoration should be explicitly enabled. However it
reminded
On Fri 26 Apr 2024 at 11:27:24 (+0900), John Crawley wrote:
> On 24/04/2024 22:37, David Wright wrote:
> > On Wed 24 Apr 2024 at 14:50:36 (+0200), Richard wrote:
> > > upon gathering my thoughts for answering to you I found the solution to
> > > this: update-initramfs can't handle the case that cry
On 24/04/2024 22:37, David Wright wrote:
On Wed 24 Apr 2024 at 14:50:36 (+0200), Richard wrote:
upon gathering my thoughts for answering to you I found the solution to
this: update-initramfs can't handle the case that crypttab ends in the line
of the last entry and not in a new line character. I
On Wed 24 Apr 2024 at 14:50:36 (+0200), Richard wrote:
> upon gathering my thoughts for answering to you I found the solution to
> this: update-initramfs can't handle the case that crypttab ends in the line
> of the last entry and not in a new line character. I think there either
> should be a fix
Hi Michel,
upon gathering my thoughts for answering to you I found the solution to
this: update-initramfs can't handle the case that crypttab ends in the line
of the last entry and not in a new line character. I think there either
should be a fix for this or at least a way to handle this case with
Hello Hans,
this is exactly what I did. To be precise, I followed this guide [1], with
the difference that instead of "crypt" I used the actual name, luks-
(Disks thanksfully shows everything relevant). It's not the first time I'm
doing this. Yet I experience the errors mentioned. Sure, I'm not usi
On 2024-04-23, Richard wrote:
> luks-775ea946-6797-4c4d-a042-72924309f3d2
> UUID=775ea946-6797-4c4d-a042-72924309f3d2 /crypto_keyfile.bin
> luks,keyscript=/bin/cat
> luks-78362aa3-760c-41de-b911-6531b684e3f7
> UUID=78362aa3-760c-41de-b911-6531b684e3f7 /crypto_keyfile.bin
> luks,keyscript=/
Am Dienstag, 23. April 2024, 22:26:17 CEST schrieb Richard:
Hi Richard,
this is, what I am doing when this happens:
1. booting into a live system (any new is working, I prefer kali-linux)
2. If you are using encrypted filesystems, open it. But you have to name it
like it is named in /
etc/crypt
Hi,
I've just set up a new computer with Debian Testing. I initially set it up
without a swap partition, but I want to add it now. The partition has
already been created as a LUKS2 partition, but I can't get update-initramfs
to add it so it will automatically be decrypted at boot (both have same
pa
11 matches
Mail list logo
