All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/systemd: fix "Timed out waiting for device /dev/console."
Date: Sun, 3 Mar 2019 22:37:51 +0100	[thread overview]
Message-ID: <20190303213751.GM2721@scaer> (raw)
In-Reply-To: <87a7ibk62d.fsf@dell.be.48ers.dk>

Peter, All,

On 2019-03-03 22:21 +0100, Peter Korsgaard spake thusly:
> >>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
>  > Well, wecould make it simple, and use (pseudoc-ode):
>  >     if console:
>  >         SERVICE='console-getty'
>  >     elif vt:
>  >         SERVICE='getty@'
>  >     else:
>  >         SERVICE='serial-getty@'
> I don't think so, as we need both <name>@<target> and <target>:
> 
> 	ln -fs ../../../../lib/systemd/system/$${SERVICE}@.service \
> 		$(TARGET_DIR)/etc/systemd/system/getty.target.wants/$${SERVICE}@$(BR2_TARGET_GENERIC_GETTY_PORT).service
> 
> So we either end up with no @ in the symlink name, or a double @@.

Arg, I ndeed I missed that. Nice point.

> I don't know if that is problem or not for systemd.

Neither do I , but I would not wagger it isn't... ;-)

However, from what I understand, the part between the '@' and the
'.service' is used to fill in the %I placeholder in the service file.
Since the console-getty.service does not have a placeholder, it is
hopefully not a problem that we create the console-getty at console.service
file...

Xavier, if this is the case, please say so in the commit log. If I wrote
bullsh!t, then please also say so, and then explain how your patch makes
it work.

In either case, I think it would make sense to indeed do as Peter
suggested, because even if your patch works, it's probably a trick and
could break in a future systemd release...

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2019-03-03 21:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-03 11:30 [Buildroot] [PATCH 1/1] package/systemd: fix "Timed out waiting for device /dev/console." Xavier Ruppen
2019-03-03 11:54 ` Yann E. MORIN
2019-03-03 20:26   ` Peter Korsgaard
2019-03-03 20:48     ` Yann E. MORIN
2019-03-03 21:21       ` Peter Korsgaard
2019-03-03 21:37         ` Yann E. MORIN [this message]
2019-03-03 21:55           ` Xavier Ruppen
2019-03-03 20:04 ` [Buildroot] [PATCH v2 " Xavier Ruppen

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=20190303213751.GM2721@scaer \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@busybox.net \
    /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.