From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 2/3] package/iwd: add basic configuration file
Date: Mon, 15 Jun 2020 22:02:53 +0200 [thread overview]
Message-ID: <20200615200253.GC2346@scaer> (raw)
In-Reply-To: <20200615200910.6098e90c@gmx.net>
Peter, All,
On 2020-06-15 20:09 +0200, Peter Seiderer spake thusly:
> On Mon, 15 Jun 2020 09:22:47 +0200, "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> > On 2020-06-14 23:48 +0200, Peter Seiderer spake thusly:
> > > On Sun, 14 Jun 2020 23:36:10 +0200, "Yann E. MORIN" <yann.morin.1998@free.fr> wrote:
> > > > On 2020-06-14 23:28 +0200, Peter Seiderer spake thusly:
> > [--SNIP--]
> > > > > And what is about the LIBFOO_INSTALL_INIT_OPENRC mentioned in [1]?
> > > > Aha! If not specified, it defaults to using the sysv hook, quoting:
> > > > The only exception is when openrc is chosen as init system and
> > > > LIBFOO_INSTALL_INIT_OPENRC has not been set, in such situation
> > > > LIBFOO_INSTALL_INIT_SYSV will be called, since openrc supports
> > > > sysv init scripts.
> > > So, what do with the openrc-init case (for the config file)?
> >
> > In the openrc case, you'd get to use openresolv, so the config file
> > would be the same as for the sysv case. And since you are adding a
> > startup script for sysv (in the followup patch), it will also be used
> > for the openrc case.
>
> But in case of LIBFOO_INSTALL_INIT_OPENRC no (additional) entry will be
> written to the config file...
Not sure I followed you here... So let me clarify:
- when a user selects openrc as an init system, but LIBFOO_INSTALL_INIT_OPENRC
is not defined, then LIBFOO_INSTALL_INIT_SYSV will be used instead.
So this should cover the case you mentioned earlier (quoting you from
memory): "for systemd, iwd handles resolv.conf with systemd, for all
other init systems, it handles it with openresolv" (at least, that was
along those lines...).
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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2020-06-15 20:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 23:24 [Buildroot] [PATCH v1 1/3] package/iwd: needs dbus (runtime) Peter Seiderer
2020-06-12 23:24 ` [Buildroot] [PATCH v1 2/3] package/iwd: add basic configuration file Peter Seiderer
2020-06-14 9:56 ` Yann E. MORIN
2020-06-14 19:07 ` Peter Seiderer
2020-06-14 20:57 ` Yann E. MORIN
2020-06-14 21:28 ` Peter Seiderer
2020-06-14 21:36 ` Yann E. MORIN
2020-06-14 21:48 ` Peter Seiderer
2020-06-15 7:22 ` Yann E. MORIN
2020-06-15 18:09 ` Peter Seiderer
2020-06-15 20:02 ` Yann E. MORIN [this message]
2020-06-15 18:41 ` Peter Seiderer
2020-06-15 20:03 ` Yann E. MORIN
2020-06-12 23:24 ` [Buildroot] [PATCH v1 3/3] package/iwd: add sysv init script Peter Seiderer
2020-06-14 10:00 ` Yann E. MORIN
2020-06-14 19:22 ` Peter Seiderer
2020-06-14 9:44 ` [Buildroot] [PATCH v1 1/3] package/iwd: needs dbus (runtime) Yann E. MORIN
2020-07-13 6:39 ` Peter Korsgaard
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=20200615200253.GC2346@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox