Hello,
Thanks for the suggestions. I'll gladly check out the p2p DBUS solution.
If this doesn't work, we can also try to make a development tool
which somehow directly links to gumd (or libgum) and is used only during
image creation. Just a rough idea.
On 22.09.2014 15:49, Zaman, Imran wrote:
Hi
As jussi highlighted below, gumd release has been pushed to Tizen with the
required changes (updated gumd should end up in Tizen in a day or two hopefully)
Krzysztof, you can try out (p2p) gumd (version 0.0.5) at image creation time:
1- export GUM_BUS_TYPE=p2p; and
2- start gumd daemon manually before calling gum-util (it doesn't need
dbus-daemon running)
Please let us know if you need any help in using gumd.
BR
imran
________________________________________
From: Dev [[email protected]] on behalf of Jussi Laako
[[email protected]]
Sent: 19 September 2014 17:24
To: [email protected]
Subject: Re: [Dev] Gumd usage in building images
Since gumd supports both p2p dbus and system bus, we just added support
to override the configured default using environment variable. If you
set GUM_BUS_TYPE=p2p and start the daemon manually before calling
gum-util it doesn't need dbus-daemon running. This still won't affect
the system-bus auto-invocation on the final install.
We'll make a new release today with this change.
2) come up with some 'first boot/configure target' that runs gumd user
config defined by tizen-<profile>-user-config package
The latter would be generic for all first boot configs.
This is good idea, we'll look into it. Cleans up some cases where salts
are used as the hash salts would be different on each result instead of
being static on the same image.
Of course there are number of first boot items where similar is already
used/needed, such as generating sshd host keys...
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
---------------------------------------------------------------------
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki
Business Identity Code: 0357606 - 4
Domiciled in Helsinki
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
--
Samsung Enterprise Portal mySingle
Samsung_Logo_for_Mail_Signature
Krzysztof Sasiak
Samsung R&D Institute Poland
Samsung Electronics
[email protected]
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev