From: Harald Hoyer <harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: WANG Chao <chaowang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: rd.break=cmdline broken
Date: Fri, 12 Jul 2013 08:44:27 +0200 [thread overview]
Message-ID: <51DFA5CB.10200@redhat.com> (raw)
In-Reply-To: <20130712043749.GA4867-ALckc1lQpMDv8MId6FTy5BcY2uh10dtjAL8bYrjMMd8@public.gmane.org>
On 07/12/2013 06:37 AM, WANG Chao wrote:
> Hi, Harald
>
> I find that rd.break=cmdline will cause a dead lock of service
> dependencies.
>
> dracut-cmdline.service:
> [..]
> Before=systemd-vconsole-setup.service
>
> dracut-emergency.service:
> [..]
> After=systemd-vconsole-setup.service
> Wants=systemd-vconsole-setup.service
>
> So it appears to be a dead lock between systemd-vconsole-setup.service
> and dracut-cmdline.service if we issue dracut-emergency.service with
> rd.break=cmdline.
>
> Because vconsole.conf is generated under cmdline hook, so simply remove
> 'Before=systemd-vconsole-setup.service' wouldn't be a decent solution.
>
> Wondering if you have any idea how to fix it.
>
> Thanks,
> WANG Chao
>
We/I should either make the vconsole.conf cmdline parsing script a generator and
be moved out of the cmdline hook; or more likely remove the deprecated,
following kernel command line parameters, when using systemd:
- KEYTABLE
- SYSFONT
- CONTRANS
- UNIMAP
- KEYMAP
- FONT
- FONT_MAP
- FONT_UNIMAP
- UNICODE
- EXT_KEYMAP
- LANG
- LC_ALL
and only accept vconsole.* and locale.* parameters, which are handled by systemd
out of the box.
prev parent reply other threads:[~2013-07-12 6:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 4:37 rd.break=cmdline broken WANG Chao
[not found] ` <20130712043749.GA4867-ALckc1lQpMDv8MId6FTy5BcY2uh10dtjAL8bYrjMMd8@public.gmane.org>
2013-07-12 6:44 ` Harald Hoyer [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=51DFA5CB.10200@redhat.com \
--to=harald-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=chaowang-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.