From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v2] systemd: set default.target to multi-user.target
Date: Fri, 25 Jan 2013 15:10:54 +0000 [thread overview]
Message-ID: <1359126654.13917.13.camel@ted> (raw)
In-Reply-To: <CAJTo0LanTczb=N=dgA+3DHc=WABsivhsmPzO6riEy9_Neb6DbQ@mail.gmail.com>
On Fri, 2013-01-25 at 15:04 +0000, Burton, Ross wrote:
> On 25 January 2013 14:59, Radu Moisan <radu.moisan@intel.com> wrote:
> > +# "multi-user" vs "graphical"
> > +SYSTEMD_DEFAULT_TARGET ?= "multi-user"
>
> Default to "graphical", so we're not regressing and just introducing a
> warning if someone doesn't set this and doesn't have X.
>
> > @@ -95,6 +95,11 @@ do_install() {
> > install -m 0644 ${WORKDIR}/var-run.conf ${D}${sysconfdir}/tmpfiles.d/
> >
> > install -m 0644 ${WORKDIR}/00-create-volatile.conf ${D}${sysconfdir}/tmpfiles.d/
> > +
> > +
> > + if [ -n ${SYSTEMD_DEFAULT_TARGET} ]; then
> > + ln -s ${systemd_unitdir}/system/${SYSTEMD_DEFAULT_TARGET}.target ${D}${sysconfdir}/systemd/system/default.target
> > + fi
>
> This will have to happen at image construction time and not package
> generation time, as different images may have different targets but
> share the same systemd package.
>
> A rootfs-time postinstall script would work, but isn't very nice. I
> wonder if there's a better solution, hooking into the image creation
> should work.
>
> (thinks)
The point here is that images shouldn't give errors at runtime. Nothing
above does anything to address that. There is something going to have to
happen at image creation time so that systemd is correctly configured in
the current scheme of things.
Cheers,
Richard
next prev parent reply other threads:[~2013-01-25 15:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 14:59 [PATCH v2] systemd: set default.target to multi-user.target Radu Moisan
2013-01-25 15:04 ` Burton, Ross
2013-01-25 15:10 ` Richard Purdie [this message]
2013-01-28 9:41 ` Radu Moisan
2013-01-25 15:12 ` Martin Jansa
2013-01-25 17:50 ` Burton, Ross
2013-01-25 17:53 ` Andreas Müller
2013-01-25 18:06 ` Martin Jansa
2013-01-25 18:35 ` Andreas Müller
2013-01-25 19:34 ` Martin Jansa
2013-01-25 20:21 ` Ross Burton
2013-01-25 20:26 ` Martin Jansa
2013-01-25 21:09 ` Andreas Müller
2013-01-25 23:52 ` Richard Purdie
2013-01-28 10:44 ` Burton, Ross
2013-01-28 11:20 ` Otavio Salvador
2013-01-28 11:48 ` Andreas Müller
2013-01-28 11:50 ` Burton, Ross
2013-01-28 18:27 ` Martin Jansa
2013-01-28 19:27 ` Burton, Ross
2013-01-28 19:48 ` Martin Jansa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1359126654.13917.13.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox