From: Ulrich Mueller <ulm@gentoo.org>
To: <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] [PATCH v4] mount-boot.eclass: Check if /boot is sane, but don't try to mount it.
Date: Wed, 11 Dec 2019 07:08:04 +0100 [thread overview]
Message-ID: <w6gtv67wg1n.fsf@kph.uni-mainz.de> (raw)
In-Reply-To: <w6gh82c4i2x.fsf@kph.uni-mainz.de> ("Ulrich \=\?utf-8\?Q\?M\=C3\=BC\?\= \=\?utf-8\?Q\?ller\=22's\?\= message of "Sat, 07 Dec 2019 10:10:14 +0100")
[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]
>>>>> On Sat, 07 Dec 2019, Ulrich Müller wrote:
> The eclass failed to remount a read-only mounted /boot, because package
> collision sanity checks in recent Portage versions prevented it from
> reaching pkg_preinst() at all. Furthermore, with the "mount-sandbox"
> feature enabled, the mount won't be propagated past pkg_preinst() and
> installed files would end up under the (shadowed) mount point.
> Therefore don't even attempt to mount /boot ourselves, but error out
> if it isn't mounted read/write and ask the user to mount /boot.
> Also clean up and simplify. (For example, awk is a grown-up program
> which doesn't need any help from egrep or sed. :-)
> Closes: https://bugs.gentoo.org/532264
> See-also: https://bugs.gentoo.org/274130#c5
> Signed-off-by: Ulrich Müller <ulm@gentoo.org>
> ---
> v3: Exit awk commands on first match.
> v4: Added die statements after awk commands
> Fixed typo in mount-boot_is_disabled function documentation
> Reverted renaming of I_KNOW_WHAT_I_AM_DOING variable
Pushed (with one small spelling change in an error message).
Ulrich
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2019-12-11 6:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-07 9:10 [gentoo-dev] [PATCH v4] mount-boot.eclass: Check if /boot is sane, but don't try to mount it Ulrich Müller
2019-12-07 13:39 ` Thomas Deutschmann
2019-12-07 16:02 ` Ulrich Mueller
2019-12-09 10:42 ` Jaco Kroon
2019-12-09 11:52 ` Ulrich Mueller
2019-12-09 12:28 ` Jaco Kroon
2019-12-11 6:08 ` Ulrich Mueller [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=w6gtv67wg1n.fsf@kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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