Bug 3774 - Enable systemd booting of core-image-sato
Summary: Enable systemd booting of core-image-sato
Status: VERIFIED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: core (show other bugs)
Version: 1.4
Hardware: All Multiple
: Medium enhancement
Target Milestone: 1.4 M4
Assignee: Ross Burton
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-01-22 14:17 UTC by Ross Burton
Modified: 2013-05-02 09:39 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ross Burton 2013-01-22 14:17:42 UTC
Now that systemd itself is integrated (#1625) the services can be done.  The aim is to boot core-image-sato under systemd.
Comment 1 Saul Wold 2013-01-22 15:16:09 UTC
We should also be selecting an image that we normally build to include systemd as the default, possibly x86-64.
Comment 2 Ross Burton 2013-02-14 16:43:31 UTC
This works now.
Comment 3 Alexandru Georgescu 2013-03-13 10:27:14 UTC
Hi Saul,

Regarding your comment for including systemd as the default, I would like to ask you what images you are thinking to include it. 

I was thinking that an idea would be to have systemd as default on qemux86_64, since it is tested at every fullpass. There are TC's created for SystemD, and it qemux86_64 will be with systemd as default, QA will add those test cases to the testing plan for it if needed.
Comment 4 Alexandru Georgescu 2013-03-14 16:30:10 UTC
Setting this to verified. 
I could build a core-image-sato image for Sugarbay configured with SystemD. It installed and booted into Matchbox interface.
Comment 5 Alexandru Palalau 2013-05-02 09:39:01 UTC
Following Testopia Test Case was created for this feature:
https://bugzilla.yoctoproject.org/tr_show_case.cgi?case_id=549