dhcpcd-discuss

Hi again,
Unfortunately the /sys/class/dmi .. solution cannot be implemented on our
platform. Also choosing to keep the DBDIR in ram to reduce flash wear
because it contains transient data.

The solution we opted for is to generating our own DUID in permanent
storage (one time) and creating a symlink from it to DBDIR/duid (eg
/var/run/duid).

Question: Can we trust dhcpcd to continue reading duid from the location as
is currently does or can it change in a future release? If later, then is
there a better alternative?

Thanks again!
-shahid

On Wed, Oct 10, 2018 at 5:45 PM Shahid Mahmood <shahid.avaya@xxxxxxxxx>
wrote:

> Thanks, I will try /sys/class/dmi/id/product_uuid option..
>
> On Wed, Oct 10, 2018 at 3:45 PM Roy Marples <roy@xxxxxxxxxxxx> wrote:
>
>> On 10/10/2018 19:34, Shahid Mahmood wrote:
>> > Hi,
>> > After recent upgrade to dhcpcd 7.0.8 (previously 6.11.5) the DUID value
>> > is observed changing on every restart of the device.
>> >
>> > Location of duid in current version: @DBDIR/
>> > Location of duid in previous version: @SYSCONFDIR/
>> >
>> > The @SYSCONFDIR/ is persistent storage while @DBDIR is not.
>> >
>> > How can we restore previous behavior or otherwise prevent duid from
>> > changing this often?
>>
>> Make DBDIR persistent storage.
>> Or better yet, expose a host specific UUID via
>> /sys/class/dmi/id/product_uuid on your product.
>>
>> Roy
>>
>>