tar/psx/bsdtar on CentOS 8

[Joel Sherrill]

This follow up from Jeff didn't hit the list.

On top of pax may be an inactive/dead project, there is the issue that
Grsecurity
has been cited as violating the GPL with their business of providing kernel
patches
to paying customers but not allowing redistribution of those patches.

https://lkml.org/lkml/2019/11/6/4

They sued Bruce Perens (
https://thenewstack.io/open-source-pioneer-bruce-perens-sued-grsecurity/)
for defamation after his comments on their actions.

But that's not where the CentOS 7 pax says it came from. Do an rpm -i
and you see the URL is http://ftp.suse.com/pub/people/kukuk/pax which
is now dead. The user has a directory but it only has glibc-addons.
I think this project died also.

Did you try yum provides "*pax"? or the dnf equivalent?

We may end up needing to identify an upstream pax implementation and
add it to the rtems-source-builder. I'm hoping that's the out here.

--joel

On Thu, Feb 27, 2020 at 8:41 PM Jeff Mayes <Jeff.Mayes at oarcorp.com> wrote:

> Hi,
> I think you misread that RHEL 8 page.  I had already looked there, but
> looked again tonight.  Pax is only listed once on the whole page, and it's
> under this heading:
>   A.4. Removed packages
>   The following packages are part of RHEL 7 but are not distributed with
> RHEL 8:
>
> The "Homepage of Pax" looks a little stale.  --->
> https://pax.grsecurity.net/
>
> Jeff
>
>
>
>
>
> From: Joel Sherrill <joel at rtems.org>
>
> Sent: Thursday, February 27, 2020 4:20 PM
>
> To: Chris Johns <chrisj at rtems.org>; Jeff Mayes <Jeff.Mayes at OARcorp.com>
>
> Cc: rtems-devel at rtems.org <devel at rtems.org>
>
> Subject: Re: tar/psx/bsdtar on CentOS 8
>
>
>
>
>
>
> Jeff.. try the stuff below and let us know.
>
>
>
>
> On Tue, Feb 25, 2020 at 9:12 PM Chris Johns <chrisj at rtems.org> wrote:
>
>
>
> On 25/2/20 5:09 am, Joel Sherrill wrote:
>
> > Hi
>
> >
>
> > CentOS 8 does not have a package for pax. It does have a package for
> bsdtar.
>
> >
>
> > Is bsdtar sufficient for the tests? I don't call the precise issue we
> favored
>
> > pax over
>
> > GNU tar.
>
> >
>
> > If so, could testsuites/libtests/configure.ac <http://configure.ac>
> accept both?
>
> >
>
> > Pax appears to be used only for the dl* and tar* tests. I had thought
> about it
>
> > not being a hard fail but those seem like bad tests to drop out.
>
>
>
> Does RTEMS understand the standard tar format? If PAX format is needed
> does your
>
> tar accept `--posix` or `--format pax`. I am happy for a change like this
> but it
>
> may only work on FreeBSD ;)
>
>
>
>
>
> Long ago, I swear it was just tar but something broke on some host. My
> vague recollection
> is very large user ids in a Mac networked environment. But the ustar
> format allows 8 octets
> for user ids.
>
>
>
>
> https://pubs.opengroup.org/onlinepubs/9699919799/utilities/pax.html#tag_20_92_13_06
>
>
>
>
> That may not have tripped the switch to pax except that pax is the POSIX
> name of the
>
>
> command.
>
>
>
> Looking for the RHEL 8 release notes about this, I found
>
>
>
>
> https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/considerations_in_adopting_rhel_8/index
>
>
>
>
> which indicates it moved to the "CodeReady Linux Builder repository" along
> with a
>
>
> number of other packages. That is in the PowerTools repo for CentOS.
>
>
>
>
> https://serverfault.com/questions/997896/how-to-enable-powertools-repository-in-centos-8
>
>
>
>
> Hopefully it works. Jeff will let us know.
>
>
>
> --joel
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Chris
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20200228/d5eac99a/attachment.html>