All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Peter A. Bigot" <pab@pabigot.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] systemd: fix runtime dependency
Date: Thu, 16 Oct 2014 06:29:42 -0500	[thread overview]
Message-ID: <543FAC26.70002@pabigot.com> (raw)
In-Reply-To: <lyr3y8z32e.fsf@ensc-virt.intern.sigma-chemnitz.de>

On 10/16/2014 06:06 AM, 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.
>
>
>> 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?

There are other units that use getty.  OE's systemd has a patch to use 
getty not agetty but for some reason console-getty is not one of the 
units patched (maybe the unit was created after the patch was made); 
that probably needs to be reviewed.  There is at least one other oe-core 
provider of getty (viz. mingetty); at one point it was important to use 
one of them (I forget which) on gumstix Overo boards.

Peter



  reply	other threads:[~2014-10-16 11:29 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 [this message]
2014-10-16 11:38     ` ChenQi

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=543FAC26.70002@pabigot.com \
    --to=pab@pabigot.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.