From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] sysvinit: Update to 2.98
Date: Fri, 12 Feb 2021 12:02:29 +0000 [thread overview]
Message-ID: <25DA6D32-BCE1-4A0E-B929-5F90C7F17803@ipfire.org> (raw)
In-Reply-To: <20210211124104.3661920-1-adolf.belka@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2200 bytes --]
Hello,
This patch removes “mountpoint” which we use in quite a number of scripts.
Has this been removed for good? Can we replace it?
-Michael
> On 11 Feb 2021, at 12:41, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> - Update sysvinit from 2.88dsf to 2.98
> - Update of rootfiles
> - Changelog is ~400 lines long from 2.88dsf to 2.98
> - For details see the Changelog in the doc directory in the tarball
>
> Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
> ---
> config/rootfiles/common/sysvinit | 6 ++++--
> lfs/sysvinit | 6 +++---
> 2 files changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/config/rootfiles/common/sysvinit b/config/rootfiles/common/sysvinit
> index ede5aa50d..a6fb1fd04 100644
> --- a/config/rootfiles/common/sysvinit
> +++ b/config/rootfiles/common/sysvinit
> @@ -1,5 +1,5 @@
> -bin/mountpoint
> bin/pidof
> +#etc/inittab.d
> #sbin/bootlogd
> #sbin/fstab-decode
> sbin/halt
> @@ -14,15 +14,17 @@ sbin/telinit
> usr/bin/last
> usr/bin/lastb
> usr/bin/mesg
> +#usr/bin/readbootlog
> usr/bin/utmpdump
> usr/bin/wall
> #usr/include/initreq.h
> #usr/share/man/man1/last.1
> #usr/share/man/man1/lastb.1
> #usr/share/man/man1/mesg.1
> -#usr/share/man/man1/mountpoint.1
> +#usr/share/man/man1/readbootlog.1
> #usr/share/man/man1/utmpdump.1
> #usr/share/man/man1/wall.1
> +#usr/share/man/man5/initctl.5
> #usr/share/man/man5/initscript.5
> #usr/share/man/man5/inittab.5
> #usr/share/man/man8/bootlogd.8
> diff --git a/lfs/sysvinit b/lfs/sysvinit
> index 0306b5518..93ee98f51 100644
> --- a/lfs/sysvinit
> +++ b/lfs/sysvinit
> @@ -24,10 +24,10 @@
>
> include Config
>
> -VER = 2.88dsf
> +VER = 2.98
>
> THISAPP = sysvinit-$(VER)
> -DL_FILE = $(THISAPP).tar.bz2
> +DL_FILE = $(THISAPP).tar.xz
> DL_FROM = $(URL_IPFIRE)
> DIR_APP = $(DIR_SRC)/$(THISAPP)
> TARGET = $(DIR_INFO)/$(THISAPP)
> @@ -40,7 +40,7 @@ objects = $(DL_FILE)
>
> $(DL_FILE) = $(DL_FROM)/$(DL_FILE)
>
> -$(DL_FILE)_MD5 = 6eda8a97b86e0a6f59dabbf25202aa6f
> +$(DL_FILE)_MD5 = e3254f7622ea5cf2322b1b386a98ba59
>
> install : $(TARGET)
>
> --
> 2.30.1
>
next prev parent reply other threads:[~2021-02-12 12:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 12:41 Adolf Belka
2021-02-12 12:02 ` Michael Tremer [this message]
2021-02-12 12:49 ` Adolf Belka (ipfire-dev)
2021-02-12 13:51 ` Michael Tremer
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=25DA6D32-BCE1-4A0E-B929-5F90C7F17803@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox