From: ChenQi <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] systemd: fix runtime dependency
Date: Thu, 16 Oct 2014 19:38:03 +0800 [thread overview]
Message-ID: <543FAE1B.0@windriver.com> (raw)
In-Reply-To: <lyr3y8z32e.fsf@ensc-virt.intern.sigma-chemnitz.de>
On 10/16/2014 07:06 PM, Enrico Scholz wrote:
> Chen Qi <Qi.Chen-CWA4WttNNZF54TAoqtyWWQ@public.gmane.org> writes:
>
>> Previously, if we set 'NO_RECOMMENDATIONS' to "1", we cannot reach login
>> in systemd systems.
> IMO, this is just a configuration issue and can be fixed much better in
> a higher level packagegroup recipe. RRECOMMENDS for serial getty are
> fine; although a serial console is very common on embedded systems, it
> is not strictly necessary.
>
These serial-getty@.service is part of the systemd package. In our
system, it's first removed from systemd package, then generated from a
separate recipe.
That's just a configuration file which occupies almost no space in
image. However, without it, you cannot use serial console in systemd system.
In sysvinit, the serial console configuration is in /etc/inittab.
I just can't see any advantage of not using serial-getty@.service.
>> This patch makes the following changes.
>> 1. Add util-linux-agetty as a runtime dependency.
>> Otherwise, getty services in systemd cannot start correctly.
> afais, it would make more sense to move this dependency into
> systemd-serialgetty (and not systemd as in your patch). Or are there
> other units in systemd which call agetty?
>
>
> Enrico
getty@.service
util-linux-agetty is really a necessity, otherwise you just don't console.
//Chen Qi
prev parent reply other threads:[~2014-10-16 11:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-16 9:19 [PATCH 0/1] systemd: fix runtime dependency Chen Qi
2014-10-16 9:19 ` [PATCH 1/1] " Chen Qi
2014-10-16 10:59 ` Peter A. Bigot
2014-10-16 11:49 ` ChenQi
2014-10-16 12:32 ` Peter A. Bigot
2014-10-16 11:06 ` Enrico Scholz
2014-10-16 11:29 ` Peter A. Bigot
2014-10-16 11:38 ` ChenQi [this message]
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=543FAE1B.0@windriver.com \
--to=qi.chen@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.