From: Peter Korsgaard <peter@korsgaard.com>
To: Jens Maus via buildroot <buildroot@buildroot.org>
Cc: "Yann E . MORIN" <yann.morin.1998@free.fr>,
Jens Maus <mail@jens-maus.de>,
Pascal de Bruijn <p.debruijn@unilogic.nl>
Subject: Re: [Buildroot] [PATCH] package/linux-tools: fix SysV init script
Date: Fri, 13 Oct 2023 16:34:04 +0200 [thread overview]
Message-ID: <87edhy617n.fsf@48ers.dk> (raw)
In-Reply-To: <87bkdi7jwp.fsf@48ers.dk> (Peter Korsgaard's message of "Sun, 01 Oct 2023 11:48:38 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
>>>>> "Jens" == Jens Maus via buildroot <buildroot@buildroot.org> writes:
>> This commit fixes the S10hyperv SysV init script which expects binaries
>> to be locate in /sbin while they are installed in /usr/sbin. Please
>> note, that the systemd init scripts correctly reference them.
>> Furthermore, the SysV init script did not check for an actual HyperV
>> environment to be present, which is also corrected. In addition, this
>> commit also fixes check-package warnings regarding a missing DAEMON
>> definition.
>> Signed-off-by: Jens Maus <mail@jens-maus.de>
>> ---
>> package/linux-tools/S10hyperv | 8 ++++++--
>> 1 file changed, 6 insertions(+), 2 deletions(-)
> This means we can now drop the entry in .checkpackageignore. Committed
> with that included, thanks.
Committed to 2023.02.x and 2023.08.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-10-13 14:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-23 10:00 [Buildroot] [PATCH] package/linux-tools: fix SysV init script Jens Maus via buildroot
2023-10-01 9:48 ` Peter Korsgaard
2023-10-13 14:34 ` Peter Korsgaard [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=87edhy617n.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=mail@jens-maus.de \
--cc=p.debruijn@unilogic.nl \
--cc=yann.morin.1998@free.fr \
/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