From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Adam Duskett <adam.duskett@amarulasolutions.com>
Cc: Antoine Tenart <atenart@kernel.org>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v4 2/2] package/refpolicy/Config.in: depend on merged usr when selecting upstream
Date: Mon, 9 Oct 2023 22:05:53 +0200 [thread overview]
Message-ID: <20231009200553.GG14234@scaer> (raw)
In-Reply-To: <20231009172519.GF14234@scaer>
Adam, All,
On 2023-10-09 19:25 +0200, Yann E. MORIN spake thusly:
> On 2023-10-09 19:04 +0200, Adam Duskett spake thusly:
> > Refpolicy contexts expect a merged /usr file system. In fact, there
> > are no references to /bin, /sbin, /lib, or /lib64 at all.
> There is a file in the refpolicy upstream tree,
Bad copy-but-no-paste, so the file was: config/file_contexts.subs_dist
[--SNIP--]
> But maybe that no longer works? Or maybe we need to take action to make
> that work?
As discussed on IRC, that is indeed not an issue: refpolicy works even
without a merged /usr.
The issue stems from "dontaudit" rules that hid some other issue (if I
understood correctly).
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. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-10-09 20:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 17:04 [Buildroot] [PATCH v4 1/2] package/refpolicy: bump version to 2.20231002 Adam Duskett
2023-10-09 17:04 ` [Buildroot] [PATCH v4 2/2] package/refpolicy/Config.in: depend on merged usr when selecting upstream Adam Duskett
2023-10-09 17:25 ` Yann E. MORIN
2023-10-09 20:05 ` Yann E. MORIN [this message]
2023-11-04 17:33 ` [Buildroot] [PATCH v4 1/2] package/refpolicy: bump version to 2.20231002 Thomas Petazzoni via buildroot
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=20231009200553.GG14234@scaer \
--to=yann.morin.1998@free.fr \
--cc=adam.duskett@amarulasolutions.com \
--cc=atenart@kernel.org \
--cc=buildroot@buildroot.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.