ormat?
best regards,
matt
Original Message
Subject: Re: Support for plain dm-crypt and detached LUKS header
Local Time: April 9, 2017 6:29 AM
UTC Time: April 9, 2017 6:29 AM
From: arvidj...@gmail.com
To: Mat628 , g...@jelmail.com ,
help-g...@gnu.org , The development of GNU GRUB
>I would personally assume that something could be done in the dedicated
>/etc/grub.d/ directories that would allow grub-mkconfig to function as
>required without changing anything to it?
Xen, that is probably possible, but I chose to modify grub-mkconfig_lib.in
because that is where the origin
>Am I correct in stating that your patches would only require:
>- command line options on each invocation of grub-install to reference a
>config file of sorts - a config file in a dedicated directory that would allow
>this config to persist
Xen, yes you are correct. The config file (${prefix}/e
Hi,
I wanted to verify/clarify what would be an acceptable format for a disk id to
be used as a search parameter for a module to return the associated device.
Where on Linux, devices are mapped to a hardware specific path.
For hard disks it is
type-product_serial(-partition#)
ata-ST42443343DR_
There is no established standard and this changed over time. GRUB uses
platform firmware to access devices, so it can only use information
firmware exports. In general we have no way to query for this information.
Would it be considered acceptable to call nativedisk.mod to allow for query
of this
No. Nativedisk solves some very specific problems. It's not for general use
Okay the reason I was asking is to help solve the problem of reliably finding
the correct device for a LUKS device with detached header. I previously wrote a
search by disk/part UUID/GUID module which returned the device
