On Fri, Sep 19, 2014 at 1:48 PM, Zaman, Imran <[email protected]> wrote:
> Hi Krzysztof! > > I dont have much idea what (and where) changes are needed to use gumd at > image creation time. > It would good if we can use gumd at image creation time as well. > > I can see two options: 1) move the useradd functions to gum-utils (no dbus dependency) 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. -- Mikko > As you mentioned, if you can give it a try that would be great. Please let > me know if I can be of any help. > > BR > irman > ________________________________________ > From: Dev [[email protected]] on behalf of Krzysztof Sasiak [ > [email protected]] > Sent: 18 September 2014 17:30 > To: Jacek Bukarewicz; [email protected] > Subject: Re: [Dev] Gumd usage in building images > > Hi, > > The problem is that during image creation gumd user management is not > available. It's because of the gumd's architecture: there's a client and > a daemon. The client communicates with the daemon using DBUS (the actual > user creation is performed by the daemon). > > Mic image creation is done in a chroot, and only bash commands will > work there. There's no DBUS daemon available then, hence the problem. > > All this still has to be confirmed. I'm not sure if anybody has tried > it out ;) > > On 18.09.2014 16:19, Jacek Bukarewicz wrote: > > Hello, > > > > Can anyone clarify what exactly is the dbus-gumd issue? gumd depends > > on dbus-1 RPM requirement, which used to be provided by dbus-devel > > instead of dbus package. The consequence was that gumd pulled > > dbus-devel as its dependency. Today a fix has been merged to dbus > > package and it still needs to be submitted to the OBS. However, I'm > > not sure it was the reason for not putting gumd on the image. > > > > Best regards, > > > > On 09/18/2014 03:53 PM, Krzysztof Sasiak wrote: > >> Hello Imran, > >> > >> Thank You for answering. Any news on the issue? > >> > >> I'd be very much interested in having a operational multiuser > >> feature in Tizen, and so I would be very glad to help with coming up > >> with a solution to this dbus + gumd issue. > >> > >> On 09.09.2014 14:06, Zaman, Imran wrote: > >>> Hi Krzysztof! > >>> > >>> ... forked another thread for gumd to keep it separate. > >>> > >>> I think the only think that comes to my mind is that gumd has a > dependency on dbus. If that can be handled and has no issues at image > building time, then for sure we can use gumd. > >>> Mikko! Can you please let me know (if you know any) whom to contact > for this issue at image building stage? > >>> > >>> BR > >>> imran > >>> ________________________________________ > >>> From: Dev [[email protected]] on behalf of Krzysztof Sasiak > [[email protected]] > >>> Sent: 05 September 2014 16:06 > >>> To: Dominig ar Foll > >>> Cc:[email protected] > >>> Subject: Re: [Dev] Tizen 3 services: use case for multi user > >>> > >>> Hello, > >>> > >>> To aid integration, I would also suggest to start building images > >>> with gumd built-in. > >>> > >>> Is there any workaround for the issue of adding users with gumd > >>> during image creation yet? > >>> > >>> > >>> On 04.09.2014 16:04, Dominig ar Foll wrote: > >>>> Hello, > >>>> > >>>> we had in the recent days many discussion on the consequences of > >>>> activating multiuser in Tizen 3 services. > >>>> > >>>> In order to help the developers who have to integrate Multiusers > >>>> concepts in their services we have created a few pages which describe > >>>> some use cases. > >>>> > >>>> Currently we have created pages for: > >>>> Multi-user PackageApplicationManagement > >>>> Multi-user Bluetooth > >>>> Multi-user WINET > >>>> > >>>> And will will had more entries over the time. > >>>> See: > >>>> > https://wiki.tizen.org/wiki/Multi-user_Architecture#Multi_User_use_cases > >>>> > >>>> Thanks in advance for your feedback. > >>>> > >>> -- > >>> 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 > >>> --------------------------------------------------------------------- > >>> 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 > > > > > > -- > > Jacek Bukarewicz > > Samsung R&D Institute Poland > > Samsung Electronics > > [email protected] > > > > > > _______________________________________________ > > Dev mailing list > > [email protected] > > https://lists.tizen.org/listinfo/dev > > > -- > 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 > --------------------------------------------------------------------- > 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. > > _______________________________________________ > Dev mailing list > [email protected] > https://lists.tizen.org/listinfo/dev >
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
